Replenishment planning is the process of deciding when and how much stock to reorder at each location so you meet demand without tying up excess working capital. Most companies run this process on reorder point (ROP) values set years ago, calculated once during an implementation project and rarely touched since. That is why the same warehouse can show a stock-out on one SKU and overstock on another in the same month.
This guide covers the replenishment planning process, the reorder point formula, and why static logic keeps producing both problems at once.
What Is Replenishment Planning?
The replenishment planning meaning most vendor glossaries use stops at “reordering stock,” which misses where it actually sits: between demand forecasting and procurement. Forecasting predicts what customers will want; replenishment planning decides when and how much of that forecast to convert into an actual order at each location, and production executes it.
The distinction that matters is pull allocation vs push replenishment: allocation pushes inventory to a location based on a plan, while replenishment pulls inventory based on what that location actually consumed. A single-warehouse example makes this concrete. A distributor holds 400 units of one SKU, sells 20 units a day, and waits 10 days for a refill. Once inventory position (what’s on-hand vs on-order) drops to roughly 10 days of demand plus a buffer, replenishment planning triggers the next order. Get demand, lead time, or the buffer wrong, and the trigger fires at the wrong moment.
The Replenishment Planning Process, Step by Step
- Measure inventory position. Add what’s on-hand to what’s already on order, then subtract anything already committed to outbound orders. This number, not the on-hand count alone, is what gets compared against the reorder point.
- Forecast lead-time demand. Estimate how much will sell or get consumed during the supplier’s lead time. Lead time demand equals average daily demand multiplied by lead time in days.
- Set safety stock. Size a buffer for the variability in both demand and lead time, beyond the average alone. A wider spread in either one calls for more safety stock at the same service level.
- Trigger at the reorder point. When inventory position drops to lead-time demand plus safety stock, the system generates a purchase or production order automatically, on a continuous review basis rather than waiting for a calendar date.
- Decide the order quantity and lot size. The reorder point answers when to order; a separate calculation, often the economic order quantity (EOQ), answers how much. Order too little and you reorder constantly; order too much and cash sits on the shelf.
What Is the Reorder Point Formula?
The reorder point formula is: reorder point = (average daily demand × lead time) + safety stock.
Worked example: a manufacturer sells 40 units a day of one component, the supplier’s lead time is 7 days, and the target service level is 95 percent. Lead-time demand is 40 × 7 = 280 units. Safety stock at a 95 percent service level, sized against demand variation, adds roughly 50 to 80 units depending on how much daily demand swings. That puts the reorder point at roughly 330 to 360 units, the trigger to place the next order.
Retail service levels average 90 percent, with high-demand items targeted closer to 95 percent. Moving from 90 to 95 percent looks like a small jump on paper; the safety stock required to hit it grows faster than the service level does, because the Z-score climbs steeply as the target approaches 100 percent.
The reorder point answers when to order. Economic order quantity answers how much. Confusing the two, or tracking fill rate as if it were service level, is a common error in a spreadsheet-based replenishment planning process. A third way to express the same trigger is days of cover: when coverage drops below lead time plus safety stock days, the SKU is in reorder territory.
Common Replenishment Methods Compared
| Method | How It Works | Works When | Breaks When |
| Fixed min-max replenishment | Order up to a max whenever stock falls below a min | Stable demand, simple SKU sets | Demand or lead time shifts and nobody resets the min/max |
| Periodic review | Check stock on a fixed order cycle and order up to a target | Low-value SKUs, predictable order cycles | Fast movers stock out between review dates |
| ROP / continuous review | Order the moment inventory position crosses the reorder point | Mid-to-high velocity SKUs with known lead times | Reorder point never gets recalculated as inputs drift |
| Demand-driven replenishment (DDMRP-style) | Dynamically sized buffers pull replenishment from actual consumption at decoupling points | Volatile demand, multi-echelon networks, variable lead times | Buffer parameters still need disciplined review; not fully automatic |
The pattern across all four: every replenishment strategy needs its parameters reviewed on a cadence, or it degrades into whichever failure mode fits it best. Fixed min-max and periodic review fail fastest because nobody expects to touch them. ROP and demand-driven methods fail slower, but they still fail once the inputs underneath them go stale.
Why Static Reorder Logic Keeps Failing
Static reorder logic does not fail because the formula is wrong. It fails because the inputs to the formula stop being true, and nobody reviews them.
- Parameter decay. A reorder point calculated during implementation reflects that month’s demand and that supplier’s lead time. Eighteen months later, both have moved, and the reorder point has not.
- Lead times treated as constants. The formula uses a single lead-time number, but real suppliers run early, late, and everything between. A reorder point built on the average lead time is wrong roughly half the time by definition.
- Single-node math in a multi-node distribution network. A reorder point calculated per warehouse ignores stock sitting one node away that could cover the gap.
- Flat averages ignore seasonality and promotions. Average daily demand smooths out the exact spikes a reorder point exists to protect against.
- Safety stock as guesswork instead of parameter review. Many teams set safety stock as a round number or a few weeks of cover, not a service-level calculation tied to actual demand and lead-time variation.
Research assessing DDMRP through discrete-event simulation of a multi-echelon replenishment system found that even dynamically sized buffers require careful, non-subjective parameterization to hold up; static reorder points, calculated once and left alone, carry that same parameterization risk with none of the review discipline.
What Dynamic Replenishment Planning Looks Like
Dynamic replenishment planning recalculates its own parameters instead of waiting for a planner to notice they are stale. Lead-time demand updates as actual lead times shift. Safety stock resizes as demand variability changes. Demand sensing feeds near-term signals into the reorder trigger instead of relying on a flat historical average. Multi-node awareness means the system checks nearby inventory before generating a new order, and exception alerts flag the SKUs where a human should look rather than requiring a review of every line.
Demand-driven replenishment, most visibly formalized as DDMRP, is one proven expression of this consumption-based planning principle rather than the only one. It replaces fixed stock levels with dynamically adjusted buffers, using a red-yellow-green zone model at strategically placed decoupling points, so variability absorbs at those points instead of cascading through the network. A real limitation is worth carrying forward: computing orders from flawed lead-time estimates, inside DDMRP or a classic reorder point, still generates a mix of overstock and stock-outs depending on which direction the estimate is wrong, a limitation of the underlying math rather than any specific vendor’s implementation. Dynamic parameters reduce that risk; they do not eliminate the need for good inputs.
This is what an AI planning layer automates on top of the ERP. Oritiq combines coverage data with real-time pending sales order data, so replenishment triggers stay in sync with what is actually happening on the ground, not what a spreadsheet assumed months ago.
FAQs
What is replenishment planning in simple terms?
It is deciding when and how much stock to reorder at each location so demand gets met without tying up excess cash in inventory. In practice, that means tracking inventory position, forecasting lead-time demand, and triggering an order once stock drops to a calculated reorder point.
What is the difference between replenishment planning and demand planning?
Demand planning forecasts what customers will want, at what quantity, over a future horizon. Replenishment planning takes that forecast and decides when and how much to order at each location right now. Demand planning answers what is coming; replenishment planning answers what to do about it today.
What is the reorder point formula?
Reorder point equals average daily demand multiplied by lead time, plus safety stock. It tells you the inventory level that triggers the next order, combining how much you will sell while waiting for a refill with a buffer against demand and lead-time variability.
How is safety stock different from the reorder point?
Safety stock is the buffer added for uncertainty; the reorder point is the full trigger level that combines expected lead-time demand with that buffer. Safety stock protects against variability alone. The reorder point is safety stock plus the demand expected before the next delivery arrives.
What is demand-driven replenishment?
Demand-driven replenishment sizes and positions inventory buffers dynamically at strategic decoupling points, then pulls replenishment from actual consumption instead of a fixed reorder point. DDMRP, developed by Carol Ptak and Chad Smith, is the most formalized version, using red, yellow, and green buffer zones to absorb variability.
How often should reorder points be reviewed?
Reorder points should be reviewed whenever demand, lead time, or supplier reliability shifts meaningfully, and at minimum every quarter for volatile SKUs. Reorder points calculated once during implementation and never revisited are the most common reason a warehouse shows both stock-outs and overstock in the same month.
Closing
Replenishment planning means deciding when and how much to reorder at each location, and every method for doing it, from fixed min-max to full demand-driven replenishment, breaks down once its parameters go stale. The formula, the process steps, and the methods table above are the textbook. The failure modes are what the textbook usually leaves out.
See what dynamic, multi-echelon replenishment planning looks like against your own SKUs, lead times, and pending sales orders.