A procurement manager at a contract manufacturer keeps a spreadsheet on her second monitor. The leftmost column lists every raw material the plant uses. Two columns over, in cells that are mostly green, sits her reorder point logic: a fixed minimum stock level for each item, set last year by a colleague who has since left the company. When current stock dips below the minimum, she places a purchase order for a quantity that is also fixed in the spreadsheet, calibrated to a vague memory of historical consumption. The system has worked, mostly, for the last three quarters. Last week it stopped working. A new contract with a regional distributor doubled the planned production volume of one finished good, and the raw materials that go into it started showing critical alerts five days earlier than the reorder point predicted. By the time procurement reacted, the supplier could not deliver in time, and the plant ran a partial shift instead of a full one.
The problem was not the spreadsheet itself, though spreadsheets make this kind of mistake easier. The problem was the architectural assumption underneath the reorder point. A static minimum stock level treats demand as constant. It assumes that whatever the consumption rate was when somebody set the threshold, that rate will hold steady going forward. In a manufacturing operation with shifting production schedules, seasonal demand, and multi-product lines that compete for shared materials, this assumption is wrong almost continuously. Reorder point mistakes are not occasional surprises. They are the predictable output of a method that cannot see beyond the present quantity on the shelf.
Why Static Minimum Stock Lies About Demand
The static minimum stock model is appealing because it is simple. Set a number, watch the system, react when the number is breached. The simplicity is also the failure. The number is not a measurement of demand. It is a guess about demand made at a moment in the past, then frozen. Real demand is dynamic. It shifts when production schedules shift. It shifts when a new customer comes online. It shifts when a BOM changes. It shifts when one product line is paused and another is accelerated. None of these shifts are visible to a static threshold, because the threshold has no relationship to the upcoming production schedule that actually drives material consumption.
The lie compounds in two directions. When demand drops, static reorder points trigger purchases that the operation does not need, tying up working capital in surplus stock. When demand rises, static reorder points fire too late, because the buffer they were sized for assumed the previous consumption rate. The procurement team finds themselves alternating between excess buffer stock on some items and emergency expedites on others, often within the same week. The pattern is so familiar that many teams have come to assume it is just the nature of the job. It is not. It is the nature of the model.
What Horizon-Based Replenishment Actually Calculates
A horizon-based replenishment model replaces the static threshold with a forward-looking calculation. For each material, the system answers a different question: given everything we have committed to produce in the next seven, fourteen, thirty, or sixty days, do we have enough material to execute, including stock currently on hand and purchase orders already in flight, and if not, how much more do we need and by when? The model does not ask whether the current quantity is below some arbitrary minimum. It asks whether the projected balance is sufficient to cover projected demand across a meaningful planning horizon.
The inputs to this calculation are concrete. Confirmed production orders define the gross requirement. Their dates and quantities, exploded through the relevant bills of materials, produce a time-phased demand for every component material. Open purchase orders define scheduled receipts, with their expected arrival dates. Current available stock is the starting balance. The output is the projected available balance day by day across the horizon, with shortfalls flagged at the dates they would occur. The deeper mechanics of how this works are covered in MRP planning horizons explained, and the practical impact is that procurement decisions become responses to specific projected shortfalls rather than reactions to threshold breaches.
Multiple Horizons for Different Planning Questions
A single horizon is not enough. Manufacturing operations need different horizons for different planning questions. A seven-day horizon answers the question of whether the immediate execution window is safe. A fourteen-day horizon catches issues that are far enough out to address with a transfer or an expedited order. A thirty-day horizon supports normal procurement cycles for materials with standard lead times. A sixty-day horizon supports long-lead-time materials and capacity decisions that require advance commitment.
The four horizons are not redundant. They each surface a different category of risk. An item that is sufficient at the seven-day horizon but shortfall at the thirty-day horizon does not need an emergency response, but it does need a purchase order placed soon. An item that is shortfall at the seven-day horizon needs an immediate intervention, possibly an internal transfer if surplus exists elsewhere in the network, possibly an expedite if not. Configurable horizons let the operations team match the analysis to the question. A static minimum stock field cannot answer any of these questions, because it has no concept of time at all.
The Smart Reorder Action
When MRP identifies a shortfall, the right next step is not always a purchase order. The right next step depends on the network. If another location in the organization has surplus of the same material, a transfer may resolve the shortfall faster and more cheaply than a new purchase order. This is where smart reorder logic earns its place. Rather than triggering a purchase the moment a threshold is breached, the system evaluates the full set of restock options: internal transfer if surplus exists, external reorder if it does not, and redistribution if total stock across the network is sufficient but distributed in the wrong proportions.
FalOrb's restock intelligence engine implements this logic explicitly. Each recommendation comes with an urgency badge, a plain-English headline, and a one-click action. Reorder recommendations include a pre-filled purchase order draft with a suggested quantity rounded to the supplier's minimum order quantity and an order-by date calculated from the production schedule minus the supplier's lead time. Internal transfer recommendations include the source and destination locations and the recommended quantity. The shift from a static minimum stock model to this approach is the difference between a system that fires alerts at noise and a system that fires alerts that warrant action. The broader procurement implications are explored in moving from reactive to predictive procurement.
Auto-Resolution and the End of Alert Noise
A subtle but important detail is how alerts behave when conditions change. In a static reorder point system, alerts often persist until somebody manually clears them, which trains the team to ignore the alert queue because most of what is in it is stale. In a horizon-based replenishment system, alerts auto-resolve when the underlying condition resolves. A shortfall flagged on Tuesday is automatically dismissed on Wednesday if a purchase order receipt covers the gap. The alert queue stays clean because every alert in it represents a current condition that needs current attention.
The discipline this enforces matters operationally. When the alert queue is reliable, the team treats it as actionable. When it is unreliable, the team treats it as background noise, and real shortfalls get missed because they are buried under stale ones. Auto-resolution is not a small feature. It is the mechanism that makes the entire alert layer usable, which in turn makes the entire planning system usable. A system that surfaces shortfalls but cannot reliably tell the team when they are gone is not significantly better than the spreadsheet it replaced.
Why the Spreadsheet Cannot Catch Up
A common reaction to the limits of static minimum stock is to add complexity to the spreadsheet. Build seasonal adjustments. Layer on safety stock formulas. Create a separate tab that pulls in production schedule data. Each addition makes the spreadsheet a little smarter and a lot more brittle. Within six months, the spreadsheet has become an unmaintainable artifact that depends on one person's tribal knowledge, breaks when anyone changes a column, and still cannot calculate net requirements properly because it is fundamentally a tool for static analysis being asked to perform dynamic planning.
The spreadsheet ROP failure is not a question of effort. It is a question of architecture. The data the system needs is structured, time-phased, and cross-referenced: production orders linked to BOMs, BOMs exploded into material requirements, material requirements netted against current stock and scheduled receipts, with horizons and lead times applied. This is a graph problem, not a list problem. Spreadsheets handle lists. Graphs require a real database, real data integrity, and real computational logic. The deeper failure modes of trying to run a manufacturing operation on spreadsheets are covered in why spreadsheet inventory fails at scale, and reorder point logic is one of the clearest places where the architectural ceiling becomes visible.
Closing on the End of the Expedite Cycle
The cycle of late expedites and excess buffer stock is not a personality flaw of any procurement team. It is the rational response to a planning model that does not see far enough ahead. When the model only knows the current quantity, the team can only react to current breaches, which by the time they fire are usually too late to address through normal channels. The fix is to give the model time depth: a forward view of confirmed demand, a forward view of scheduled supply, and a calculation that surfaces shortfalls at the dates they will occur, not the dates they have already occurred.
Operations teams that make this transition usually report two changes. The expedite count drops, because shortfalls get caught early enough to be addressed through normal procurement. The buffer stock count drops too, because static minimums are no longer needed when the system is genuinely planning ahead. The combined effect is meaningful working capital recovery and a procurement function that spends its time on supplier strategy rather than firefighting. Visit falorb.com to see how horizon-based MRP and restock intelligence work together in practice.
FalOrb replaces static reorder points with horizon-based MRP and restock intelligence that recommends transfers, reorders, or redistributions based on actual projected demand. Book a 30-minute walkthrough or email us at [email protected] to see how it applies to your operation.