Reorder Point (ROP) Formula: How to Calculate with Example
Calculate a replenishment trigger from lead-time demand and safety stock, while checking inventory position and inbound orders.
Jainul Vaghasia/Published /Updated /8 min read
Use the definition
Turn procurement terms into an operating system.
This reference page should help you understand the concept first. When the term affects purchasing execution, LineNow connects it to live POs, supplier replies, receiving, and accounting handoff.
The reorder point (ROP) is the inventory level at which a new purchase order should be placed. It is sized so that the order arrives just before existing stock is depleted, with a safety buffer for variability.
Quick answers
What is a reorder point? The reorder point is a replenishment threshold, commonly compared with inventory position: usable on-hand plus usable on-order less unfilled demand. When stock drops to this level, the system (or operator) places an order so the new shipment arrives just before existing stock runs out.
What is the reorder point formula?ROP = (consumption rate × lead time in days) + safety stock. Safety stock is z × σ × √(lead time), where z is the z-score for your target service level and σ is the standard deviation of daily demand.
How is a reorder point different from a PAR level?Reorder point is the level at which you order. PAR level is the level you order up to. When both are used in one policy, define the trigger and target consistently; they are not universally ordered across different models. A continuous-review system fires an order when stock crosses ROP; a periodic-review system reorders up to PAR on a schedule regardless.
Why does my reorder point need to change? Lead times shift, demand shifts, supplier reliability shifts. A static reorder point gets stale within months. The right system recomputes ROP daily from rolling consumption data.
Read before ordering
A dense operator briefing for teams that need sharper buying, cleaner supplier follow-up, and fewer expensive surprises.
The formula
ROP = (consumption rate × lead time in days) + safety stock
safety stock = z × σ × √(lead time), per the standard formula
Input
What it means
Example source
Consumption rate
Average daily usage or sales
POS sales, ecommerce orders, production consumption
Lead time
Days from order sent to usable stock
Purchase order and receiving history
Safety stock
Buffer for demand and supplier variability
Demand standard deviation and target service level
In short: reorder point answers when to order. EOQ answers how much to order when the order is triggered.
Worked example
A retailer sells 12 units of a SKU per day. The order becomes usable stock 4 days after placement. Assume fixed lead time and independent daily demand. Daily-demand σ is 3 units. Target service level is 95% (z = 1.65).
Lead-time demand = 12 × 4 = 48 units
Safety stock = 1.65 × 3 × √4 = 9.9 units
ROP ≈ 58 units
In this illustrative continuous-review policy, trigger when inventory position reaches 58 units. You can run your own numbers through the free reorder point calculator.
Reorder point in units vs days of cover
Operators often understand reorder point faster when it is expressed as days, not units. The two views are the same signal:
View
Formula or trigger
Best for
Unit ROP
inventory position <= (daily usage × lead time) + safety stock
Inventory systems, scanners, SKU-level alerts
Days of cover
on hand ÷ daily usage <= lead time + safety stock days
Operator dashboards and prioritization
If a cafe uses 10 pounds of espresso per day, the supplier lead time is 5 days, and the team wants 2 days of buffer, the reorder point is 70 pounds. The same logic in days of cover is: reorder when espresso falls to 7 days of coverage.
Days-of-cover framing is useful because it normalizes across items. A 70-unit reorder point may be urgent for a fast mover and irrelevant for a slow mover. "Below supplier lead time plus safety buffer" is easier to rank across a mixed catalog.
What data should feed ROP
The formula is simple, but the data model matters:
Inventory after receiving variance, shrink, and waste
Accounting inventory value only
Supplier constraints
Pack size, MOQ, order cutoff, truck day
Free-form notes in a spreadsheet
Most reorder points fail because one of those inputs is invisible. The formula says "order at 58," but an open PO for 60 units is arriving tomorrow. Or it says "wait until 20," but the supplier's truck only comes on Fridays. Reorder point has to live inside the procurement workflow, not in a spreadsheet cell nobody trusts.
In a continuous-review system, you reorder whenever inventory hits ROP, ordering up to PAR. In a periodic-review system (e.g. you order every Tuesday), you reorder up to PAR regardless of whether ROP was crossed. Many operators run periodic review because supplier truck days, consolidated orders, or weekly review routines matter as much as the formula.
A just-in-time (JIT) strategy is the limiting case of continuous review where safety stock → 0: ROP equals only the lead-time demand with no buffer. This only holds when both demand variance and lead-time variance are negligible — a condition most SMB catalogs cannot meet across all SKUs.
A third way to express the same threshold is days of inventory on hand (DOH): when DOH drops below lead time plus safety stock days, the item is in reorder territory — the same signal as crossing ROP, expressed in days rather than units.
The category-level counterpart to ROP is open-to-buy (OTB) — the total dollar buying budget for a period. ROP tells you when to place an item-level order; OTB constrains how much of the period budget you have left to spend across all items. Both are required in a complete retail replenishment system.
The two replenishment modes
LineNow supports both:
Continuous review: orders triggered by inventory crossing ROP. Best for high-velocity items where stockout cost is high.
Periodic review: orders triggered by the calendar (e.g. weekly). Best for items where consolidation onto a single supplier truck matters more than tightness.
The replenishment trigger types LineNow supports include below_threshold, out_of_stock, always, below_days_of_stock, below_lead_time_coverage, and reorder_point. Each maps to a different operational pattern.
A third model — vendor managed inventory (VMI) — moves the reorder calculation to the supplier entirely. The buyer shares stock-level data; the supplier decides when and how much to deliver based on contractual service levels. VMI delegates replenishment decisions within the agreement; price controls and substitution approval can still be retained by contract. Buyer-managed closed-loop procurement automates the same math while keeping the reorder decision and order confirmation with the buyer.
Why ROP is often wrong in practice
The artisanal procurement stack rarely calculates ROP — the operator just orders "when it looks low." This is fine for items with stable demand and a forgiving lead time. It fails badly when:
Lead times spike (supplier delays, port congestion)
Use the SKU's demand pattern to decide update cadence:
Demand pattern
ROP update cadence
Why
Smooth
Weekly or monthly
Demand is stable enough that frequent movement is noise
Intermittent
After each demand event plus monthly review
Zero-sales periods distort naive daily averages
Erratic
Weekly, with volatility-based safety stock
Demand moves often enough to change urgency
Lumpy
Event-driven, not purely average-based
Large occasional orders overwhelm simple averages
Perishable
Daily during active buying windows
Waste and expiry change usable coverage quickly
The point is not to create a busy dashboard. The point is to avoid stale reorder points. A reorder point calculated six months ago is usually a guess with a formula attached.
How LineNow operationalizes ROP
LineNow treats reorder point as one trigger inside a closed-loop procurement system. The software does not only say "this item is below ROP." It connects the alert to the next action:
Sales and usage update the consumption rate.
Supplier lead time is measured from actual PO and receiving history.
Safety stock is sized from demand volatility and target service level.
Open POs reduce the new-order recommendation so the team does not duplicate inbound stock.
Pack size and MOQ round the suggested quantity into something a supplier can accept.
The buyer reviews the recommended PO, supplier, quantity, and rationale.
Supplier replies, substitutions, partial fills, and ETA changes update the PO before the next replenishment cycle.
That last step is the difference between a reorder point calculator and procurement software. A calculator can trigger the order. A closed loop learns from what happened after the order was sent.
Reorder point checklist
Before trusting an ROP, verify the inputs:
Input
Question to ask
Failure mode
Consumption rate
Is it based on recent sales or stale history?
Orders lag behind demand shifts
Lead time
Is it measured from actual PO history?
Orders arrive after the item stocks out
Safety stock
Does it reflect volatility and service target?
Top movers are under-buffered
Pack size and MOQ
Can the supplier sell the recommended quantity?
The order cannot be placed as recommended
Inbound inventory
Are open POs counted before recommending more?
Duplicate orders inflate stock
Decay or expiry
Does usable inventory shrink before sale?
Perishables look safer than they are
Most bad reorder points are not bad formulas. They are good formulas fed by stale or incomplete data.
When to use ROP instead of PAR
ROP is strongest for items you monitor continuously: high-velocity retail SKUs, critical ingredients, replacement parts, regulated inventory, or anything where the cost of a stockout is high. PAR is often better for calendar-based buying: weekly restaurant orders, vendor truck days, or consolidated supplier runs.
Many teams need both. A product can have a reorder point that flags urgency and a PAR level that defines the target order-up-to quantity. The operator then sees not only that the item needs attention, but how much to order.
