The shelf still holds several days of stock, but your supplier takes longer than that to replenish it. The reorder point formula sets a trigger before the shelf is empty: reorder point = expected demand during replenishment lead time + safety stock. With a steady daily demand assumption, that becomes average daily demand × lead time in days + safety stock.
Compare the threshold with the inventory position defined by your replenishment policy, including open supply and unfilled demand, rather than an unqualified on-hand count. Then check when receipts become usable. A total that includes a late purchase order can look sufficient while the warehouse runs short before it arrives.
Define the item, location, units, and time basis
Start with one item at one replenishment location. Record the stocking unit, the demand period, and which days count toward lead time. A carton of twelve pieces cannot be added to a purchase order expressed in individual pieces until both are converted to the same unit. Stock in another warehouse needs a transfer rule and transit time before it can cover this location.
Demand means the quantity the operation needs to consume or fulfill. Check whether the historical series excludes demand lost during stockouts; shipments alone may understate that need. Separate unusual projects or promotions from a steady-demand assumption rather than hiding them in an average without explanation.
Replenishment lead time runs from the policy’s ordering decision to usable stock. Include relevant approval, supplier, transport, receipt, and inspection delays once each. The lead-time calculation explains how to distinguish receipt from availability and handle partial deliveries.
Oracle’s Inventory 12.2 documentation combines lead-time demand and safety stock for reorder-point planning and provides preprocessing, processing, and postprocessing lead-time fields. Its implementation also has supply and demand cutoffs. Those details are a reason to inspect your ERP configuration before copying a spreadsheet threshold into it.
Calculate a threshold with explicit assumptions
Consider a hypothetical purchased component stocked in individual pieces. Assume demand is twenty pieces per working day, usable replenishment lead time is eight working days, and the planner has approved forty pieces of safety stock. Safety stock is an input here, not a statistically validated buffer or a promised service level.
Lead-time demand = 20 pieces/day × 8 days = 160 pieces. Reorder point = 160 + 40 = 200 pieces. The day units cancel, leaving a stock quantity. This example uses the same working-day calendar for demand and replenishment; mixing twenty pieces per workday with eight calendar days would require a calendar adjustment.
If usable lead time becomes ten working days while the other assumptions stay fixed, lead-time demand becomes two hundred pieces and the threshold becomes two hundred forty. That is a sensitivity calculation, not a recommendation to hold safety stock constant after a supplier change. Review the buffer when the uncertainty changes.
Compare the threshold with inventory position
A standard continuous-review definition is inventory position = on-hand stock + outstanding replenishment orders - backorders. The research paper An extension of the reorder point method by using advance demand spike information uses this definition and a trigger at or below the reorder point. ERP implementations can use different netting and boundary rules, so document the one you apply.
Continue the hypothetical example with 170 usable pieces on hand, thirty pieces on an existing purchase order, and no backorders. Inventory position is 170 + 30 - 0 = 200 pieces. Under the stated at-or-below policy, this reaches the reorder trigger. Assume the separately approved order quantity is three hundred pieces; releasing that order raises position to five hundred while physical stock remains 170.
The order quantity answers how much to buy. The reorder point answers when to review or release that replenishment under the chosen policy. Supplier pack sizes, minimum quantities, storage, and purchasing economics can affect the order size without changing the threshold calculation above.
If a system has already reduced available stock for reservations, do not subtract those reservations again. Likewise, decide how confirmed sales orders consume expected demand before adding both to a dated projection. The inventory reconciliation process helps establish which balances and transaction cutoffs the calculation is using.
Check the stock path between today and delivery
For the worked example, assume the existing thirty pieces arrive at the end of working day two and the new three hundred arrive at the end of day eight. Demand occurs before receipts each day. After two days, stock is 170 - 40 + 30 = 160 pieces. The next six days consume 120, leaving forty immediately before the new receipt and 340 afterward.
That path matches the chosen forty-piece buffer under these exact assumptions. If the new receipt instead arrives at the end of day eleven, two hundred twenty pieces of cumulative demand face only two hundred pieces of starting stock plus the earlier receipt. Twenty pieces are short before replenishment, even though the purchase order already appeared in inventory position.
Microsoft’s Business Central planning documentation distinguishes projected inventory from inventory available at a specific time. Use a dated supply-and-demand view when receipt timing, reservations, or large orders can create an earlier shortage. A single stock-position number cannot establish that every day is covered.
Test the assumptions before using the trigger
- A supplier changes a carton from twelve to ten pieces. Does the calculation use the conversion attached to the receipt rather than silently applying the old pack?
- An open purchase order passes its promised date. Is it flagged for confirmation rather than counted as usable stock today?
- A counted balance includes quarantined material. Is that quantity excluded from usable stock until its release is recorded?
- A customer order is reserved and also included in expected demand. Can the planner show that the same requirement was not subtracted twice?
- The replenishment check runs weekly. Has the policy accounted for time until the next review rather than assuming continuous monitoring?
Safety stock needs its own method, assumptions, and owner. Demand variability, lead-time variability, service objectives, and the consequences of a shortage affect that decision. An average-demand formula with an arbitrary buffer does not demonstrate a particular service level. For intermittent demand or project-specific components, evaluate a planning approach that uses the dated requirements instead.
Keep the physical balance credible through cycle counting. A correct threshold applied to an overstated balance delays the purchasing signal. Investigate recurring differences before responding by raising the buffer, because extra stock does not explain missing transactions.
Where Permute fits in the replenishment review
Permute sells connected business data and custom applications. We can scope a replenishment review that combines permitted inventory, receipt, and purchase-order records, keeping item identities and unit conversions attached to their sources. The work begins with agreed definitions of usable stock, open supply, and the dates that matter.
A planner-facing application can be designed to show the declared calculation alongside the records behind it. Conflicting units, stale receipts, and missing confirmations should remain visible for review. Verify source access, refresh behavior, and supported operations for the proposed implementation before relying on its output.
Explore a replenishment review on your data
Start with a permitted item-level sample and the receipts behind its current stock position.
Keep demand and purchasing policy with their owners
Permute is not a forecasting engine, and we do not select your service target or safety-stock policy. A reorder flag is not authorization to issue a purchase order. Any purchasing action needs a defined, supported, permissioned workflow and the required approval; this calculation alone does not provide one.
Use lead-time demand plus safety stock to establish the reorder threshold, then apply the inventory-position definition your policy specifies. Check receipt dates before concluding that stock will last. Keep the order quantity, buffer assumptions, and review frequency explicit. Recalculate when demand or usable lead time changes, and preserve the evidence behind the revision.
Review the inputs behind a replenishment rule
Bring one item’s stock, demand, and open-order records to examine where the calculation needs clearer definitions.
Questions about reorder points
Is the reorder point the quantity to purchase?
No. It is the trigger level for the stated replenishment policy. The order quantity is a separate decision that can reflect minimums, pack sizes, storage limits, and purchasing economics.
Can I use this calculation if I review stock once a week?
Do not assume a continuous-review trigger covers the delay until your next weekly check. Include the review schedule in the planning policy and test the resulting stock path. Otherwise, demand can consume stock before anyone acts on the threshold.
What if an item has many days without demand?
A daily average can hide occasional large requirements. Inspect the order sizes and dates, and evaluate an intermittent-demand or dated-requirements approach with the planner. The steady-demand example does not establish the right policy for that item.
Does reaching the reorder point mean a stockout is imminent?
Not necessarily. It signals that the chosen policy calls for replenishment review or release. Check usable stock, open receipts, demand timing, and uncertainty before deciding whether an expedite or other exception is required.