UgurKeser.art

A safety-stock policy for volatile lead times

Define usable lead time, service objectives, uncertainty scenarios, operating limits and review conditions for a provisional buffer policy.

Uğur Keser4 min read

A safety-stock policy should explain which uncertainty the business is willing to absorb with inventory. When lead times vary widely, adding a fixed percentage to average demand can look simple while giving little insight into the risk being covered.

The policy does not need to begin with a sophisticated model. It needs reliable definitions, an explicit service objective, a bounded decision, and a review process. Extra stock can reduce some availability risk while increasing cash exposure, storage cost, and obsolescence.

Measure the lead time that matters

Define the start as the relevant replenishment commitment and the end as inventory becoming usable for the intended fulfillment process. Production, transport, receiving, and inspection may all contribute. A carrier transit estimate alone may omit much of the delay.

Keep promised and actual dates separate. Capture partial deliveries and cases where some units arrived but were not usable. If the process changes materially, do not combine old and new observations without marking the difference.

Review the distribution rather than only the mean. A supplier with mostly short deliveries and occasional very long delays creates a different planning problem from one with a consistently moderate lead time.

Define the outcome the buffer should protect

A service objective must specify what is counted. Avoiding any stockout during a replenishment cycle is different from fulfilling a high share of requested units. Those measures can lead to different buffer choices.

Also define the cost of failing the promise. A readily substitutable accessory and a critical component needed to complete a bundle may deserve different policies. Product importance should be supported by actual customer and operating context, not only revenue rank.

Do not claim a precise service level from a small or unreliable sample. An initial policy can be provisional, with conservative limits and a clear plan to collect better evidence.

Examine demand during actual replenishment windows

For each observed replenishment interval, examine the demand that needed to be served during that interval. This connects demand and lead time in a way that two separate averages can miss. Mark periods distorted by stockouts or unusual promotions.

Use those observations to test candidate buffers against plausible scenarios. Where the data is sparse, state the assumptions directly. Demand surges and supplier delays may occur together, so assuming independence without examination can understate exposure.

The purpose is not to find one mathematically impressive number. It is to understand how often a candidate policy would have failed, how much excess it would have created, and whether the past conditions resemble the upcoming period.

Add operating limits

A buffer recommendation must fit cash, storage, shelf life, and minimum-order constraints. If the desired service objective requires an unaffordable quantity, the decision may involve a different promise, a secondary source, or a shorter replenishment process.

Do not silently lower the buffer and continue advertising the same service as if nothing changed. The inventory policy and customer promise should be evaluated together.

Assign an owner for exceptions. A planned campaign, supplier shutdown, or known transport disruption may justify a temporary adjustment. Record its reason and expiry so a temporary buffer does not become permanent excess.

Test the policy before automating purchases

Replay historical replenishment decisions using only information that would have been available at each point. Compare a simple baseline with the proposed policy. Include holding exposure and stockout consequences with consistent definitions.

A historical simulation has limits: it cannot fully recover demand lost during unavailable periods, and future conditions may differ. Use it to reject obviously weak policies and identify sensitive assumptions, then validate through bounded real operation.

An alert can recommend review without having authority to place an unlimited order. Automation should reflect the confidence and financial boundaries of the policy.

Review causes, not only quantities

When a stockout occurs, ask whether the cause was demand uncertainty, lead-time variation, inaccurate records, a missed reorder, or unavailable stock in the wrong location. Raising safety stock addresses only some of these problems.

When excess accumulates, examine whether assumptions became stale or temporary adjustments were never removed. A policy review should be capable of reducing inventory as well as increasing it.

For the demand-history problem, read forecasting around stockouts. For distributed inventory decisions, see splitting fulfillment across two locations.