A planner at a regional food manufacturer reviews the reorder list on Tuesday afternoon. One of the items, a packaging film, shows a current stock of two thousand meters and a reorder point of fifteen hundred. The system has not flagged it because stock is above the trigger. On Wednesday morning, a confirmed production order kicks off that consumes eighteen hundred meters of that film over the next three days. The supplier's lead time is twelve business days. By Friday afternoon, the planner is on the phone trying to expedite a shipment, paying premium freight, and explaining to the line supervisor why production is paused. The reorder point worked exactly as designed. The problem is that the reorder point is the wrong calculation. What matters is not how much stock is on hand right now, but how much stock will be needed before the next shipment can possibly arrive. That is lead time demand, and the inability to calculate it correctly is the most common source of reactive procurement.
Lead time demand calculation is the foundation of every functioning replenishment system. The formula is straightforward. The execution requires looking at demand the way it actually occurs, not the way an annualized average suggests it should.
The LTD Formula and Its Implicit Assumptions
The basic lead time demand formula is average daily demand multiplied by lead time in days. If a material consumes one hundred units per day on average and the supplier lead time is fourteen days, lead time demand is fourteen hundred units. The reorder point is then lead time demand plus safety stock, with safety stock sized to cover variability in either demand or lead time.
The implicit assumption is that demand is uniform and predictable. In a discrete or batch manufacturing environment, this assumption fails. Demand does not arrive at one hundred units per day. It arrives in clumps tied to confirmed production orders, which themselves cluster around customer commitments, seasonal patterns, and shift schedules. A material that averages one hundred units per day across a quarter may actually consume zero on twenty days, fifty on thirty days, and three hundred on the remaining forty.
A reorder point built on the average daily demand assumption fires at the right time only when consumption is uniform. When consumption is lumpy, the reorder point either fires too late (because the next confirmed order will burn through stock faster than the average suggests) or too early (because the next two weeks have no production scheduled and the existing stock is sufficient). The LTD formula is correct. The inputs are wrong, because the inputs treat every day as average.
Demand During Lead Time Should Use Confirmed Demand
The honest way to calculate demand during lead time is to look at confirmed demand within the lead time window, not at historical averages projected forward. If the supplier lead time is twelve days, the question is not "what is twelve times average daily demand," but "what production orders are confirmed to consume this material within the next twelve days, and what is the total quantity required."
This is a different calculation. It is deterministic where the average-based version is probabilistic. It produces a number that is anchored to specific scheduled events rather than to a statistical projection. When confirmed demand within the lead time window exceeds available stock plus incoming receipts, you have a real shortage and a real reorder need. When confirmed demand is below available stock, you do not need to order yet, regardless of what the reorder point says.
This calculation is what a horizon-based planning system performs. Running net requirements across configurable horizons of seven, fourteen, thirty, and sixty days lets the system surface the exact lead time window relevant to each material's supplier and check confirmed demand against available supply within that window. FalOrb's MRP engine performs this horizon-aware lead time demand calculation as part of its standard recommendation logic, which means the LTD figure used to drive reorder timing reflects what is actually scheduled, not what an annualized average implies. The layered horizon approach is explored in more depth in the discussion of MRP planning horizons.
When Average Daily Demand Still Has a Role
Confirmed demand is the right anchor when production is scheduled in advance. For materials that are consumed by demand patterns that are not encoded in production orders, like maintenance supplies, indirect materials, or finished goods sold from inventory, average daily demand from historical consumption is still the best available signal.
In these cases, the lead time demand calculation uses a moving average of recent consumption rather than confirmed orders. The window over which the average is calculated matters. A thirty-day moving average captures recent trends but smooths out short-term spikes. A seven-day moving average is responsive but volatile. A ninety-day average is stable but slow to react to genuine shifts in demand.
The right window depends on the volatility of the item. High-volume, stable items can use longer windows. Low-volume or seasonal items require shorter windows or more sophisticated treatment. The discipline is choosing the window deliberately rather than defaulting to whatever the system happens to provide. A planning system that lets you configure the consumption window per item, or per item category, produces lead time forecasts that reflect the reality of each material rather than forcing every material through the same averaging logic.
Accounting for Seasonality and Production Cadence
Seasonality is the third complication. A material whose average daily demand looks stable across a year may actually triple in the run-up to a peak season and drop to nothing in the off-season. Reordering based on the annual average produces stockouts during peak and overstock during the trough. The same problem appears at shorter cycles, like end-of-month production pushes or weekly batch runs.
Adjusting lead time demand for seasonality requires either explicit seasonal indices applied to the average, or a confirmed-demand approach that captures the seasonal pattern through the production schedule itself. The latter is the cleaner method when production planning is reasonably mature, because the seasonal pattern is already encoded in the orders that have been confirmed for the upcoming weeks.
When confirmed demand is sparse, like for distant horizons where the production schedule has not been firmed up, a seasonal adjustment to the average daily demand fills the gap. The supplier replenishment window for items with long lead times often extends into this sparse-demand territory, which is why long-lead-time items benefit most from explicit seasonality treatment. A material with a sixty-day lead time needs lead time demand calculated across a sixty-day window, and most production schedules are not firm that far out, so the calculation has to blend confirmed demand for the firm portion with seasonally adjusted average demand for the rest.
Order-by Date as the Operational Output
Lead time demand calculation produces a quantity. The operational output the planner actually needs is a date, specifically the latest date by which an order must be placed to avoid a stockout. This is the order-by date, calculated as the projected stockout date minus the supplier lead time.
If projected available stock falls below zero on day twenty-two, and the supplier lead time is ten days, the order-by date is day twelve. Place the order on or before day twelve, and the new shipment arrives in time. Place it after, and there will be a gap. The order-by date is the actionable signal. The lead time demand quantity is the input that produces it.
A planning system that displays order-by dates alongside reorder quantities turns the reorder list into a prioritized action queue. Items with imminent order-by dates rise to the top, regardless of how their reorder points compare to current stock. Items with comfortable order-by dates drop down the queue, even if their stock is technically below the reorder point. The reorder list stops being a list of items below threshold and becomes a list of decisions sorted by urgency. FalOrb calculates order-by dates as part of its restock intelligence engine, with urgency tiers (critical, soon, monitor) that reflect how close each item is to its order-by deadline. This is the same shift in mindset that defines the move from reactive to predictive procurement.
Why Static Reorder Points Underperform Horizon-Aware LTD
Static reorder points are the legacy approach. They are easy to set up, easy to explain, and they were the best available technology when inventory systems could not perform real-time demand projections. They are also structurally limited, because they reduce a multi-variable problem (demand, lead time, variability, seasonality, confirmed orders) to a single threshold.
A horizon-aware lead time demand calculation captures the variables that static reorder points cannot. It accounts for the actual production schedule, not just historical averages. It adjusts for the lead time of each item's supplier, not a global default. It updates as orders are confirmed, cancelled, or rescheduled, so the LTD figure reflects the current state of the schedule rather than the state at the time the reorder point was last reviewed.
The result is reorder timing that responds to the actual operational situation. When a large production order is confirmed for next month, the LTD for the materials it consumes increases immediately, and the order-by dates for those materials shift earlier. When a production order is cancelled, the LTD decreases and the order-by dates relax. The reorder list reorganizes itself as the schedule changes, without anyone manually updating reorder points. The pattern of building intelligence into the planning data rather than maintaining static thresholds is the same pattern that distinguishes systems that scale from spreadsheets that do not.
Lead Time Demand as a Living Calculation
Lead time demand is not a number that is calculated once and posted to an item master. It is a calculation that should run continuously, reflecting every change to the production schedule, every receipt of incoming stock, every adjustment to supplier lead times, and every shift in consumption patterns. Treating it as a living calculation rather than a static parameter is what separates planning systems that drive proactive procurement from systems that produce reactive lists.
The work of moving from static reorder points to horizon-aware LTD is not a software project. It is a planning discipline supported by a system that performs the calculation correctly and updates it in real time. Once the discipline is in place, the planner's job changes. Time spent maintaining reorder points is redirected to investigating why the order-by dates are shifting, which is a more useful question. The system handles the arithmetic. The planner handles the judgment. That is the right division of labor in a planning function that has matured beyond chasing reorder triggers. Visit falorb.com to see how horizon-aware lead time demand and order-by dates work together in a single planning view.
FalOrb helps manufacturers calculate lead time demand with horizon awareness, so reorder timing reflects confirmed production rather than annualized averages. Book a 30-minute walkthrough or email us at [email protected] to see how it applies to your operation.