The reorder point formula has been a cornerstone of inventory management for decades. It's elegant, teachable, and fast to calculate: take your average daily demand, multiply by your supplier lead time in days, add your safety stock, and that's your trigger quantity. When on-hand inventory drops to that number, place an order.
At small scale — 50 SKUs, one sales channel, predictable demand — this works. The moment you add a second channel, a promotional calendar, a growing catalog, or a supplier with lead time variability, the cracks appear. Not because the formula is wrong, but because it was designed for a simpler decision environment than most mid-market brands actually operate in.
What the reorder point formula assumes
The standard reorder point (ROP) formula is: ROP = (average daily demand × lead time in days) + safety stock
Buried in that formula are several assumptions worth examining:
- Demand is relatively stable. The formula uses a point estimate — "average daily demand" — not a distribution. It doesn't account for the fact that demand is higher in October than in March for a seasonal SKU, or that a flash sale will spike units sold by 3× for a 72-hour window.
- Lead time is fixed. Real supplier lead times have variance. An overseas supplier with a 60-day stated lead time may deliver anywhere from 45 to 90 days depending on their production queue, port congestion, and your order size relative to their MOQ thresholds.
- There's one channel. The ROP formula produces one trigger number. If that SKU sells on Shopify, Amazon Seller Central, and through two wholesale accounts, which channel's demand velocity feeds the formula? What counts as "on-hand" when inventory is split across a 3PL warehouse and a retail store backroom?
- You want a steady-state answer. ROP is designed for steady-state operation. It doesn't tell you anything about how your replenishment strategy should change 10 weeks before Black Friday, when your demand curve is about to accelerate and your supplier lead time is simultaneously lengthening due to Q4 production pressure.
What replenishment planning adds
Replenishment planning is a broader decision framework that incorporates everything the ROP formula treats as fixed.
A replenishment plan typically covers:
- Demand forecasting by period: Instead of average daily demand as a single number, replenishment planning uses a forecast — a projected demand quantity by week or month, incorporating trend, seasonality, and planned promotional events.
- Lead time modeling: Rather than a fixed lead time, replenishment planning uses historical lead time distributions to set safety stock at a target service level. If your supplier's lead time has a standard deviation of 8 days, that gets incorporated into your buffer calculation rather than ignored.
- Channel-level allocation: Replenishment planning can split inbound inventory allocation across channels based on each channel's projected demand — so when 500 units land at your 3PL, the system knows to allocate 220 to Shopify, 180 to Amazon FBA, and 100 to your retail store based on their respective demand forecasts.
- Order timing and quantity optimization: EOQ (Economic Order Quantity) as a concept is compatible with replenishment planning — but where EOQ assumes static demand, replenishment planning adjusts order quantities dynamically based on the current forecast and the inventory position across the full planning horizon.
A scenario where the difference matters
Consider an outdoor apparel brand managing roughly 600 active SKUs across Shopify Plus and Amazon Vendor Central, with a 4PL supplier in Vietnam and a domestic 3PL in Tennessee. Their top-selling waterproof jacket SKU — call it WJK-200-GRN-M — has an average weekly velocity of 90 units during spring season and 20 units in the off-season.
A static ROP approach set in March using spring-season demand would calculate a trigger at roughly 560 units (90 units/day × 7 lead time weeks — simplified for illustration). By November, when weekly demand has dropped to 20 units, that 560-unit reorder point would constantly be firing false triggers — they'd be over-ordering into a slow period because the formula was calibrated for spring.
A replenishment planning approach, by contrast, would use a seasonally-adjusted demand forecast to drive the reorder calculation. The effective trigger drops to roughly 140 units in the off-season and rises ahead of the spring season ramp, with a forward-looking order placed in January to account for the 8–10 week offshore lead time before spring demand peaks. The plan would also incorporate the brand's MOQ from the supplier (minimum order 200 units per colorway), so the system doesn't recommend an order that violates the minimum case pack threshold.
The transition point: when do you outgrow ROP?
We're not saying reorder point formulas are bad — for brands under 200 SKUs with a single channel and stable demand patterns, a well-maintained ROP spreadsheet with quarterly formula updates can be perfectly adequate. The math is sound at that scale.
The transition to replenishment planning typically becomes necessary when one or more of the following is true:
- You're managing 300+ active SKUs and reorder points haven't been updated in more than 90 days
- You're selling across two or more channels with distinct demand patterns (DTC velocity differs from Amazon velocity by more than 20%)
- Your top 10 SKUs account for more than 50% of revenue, and any one of them stocking out during peak causes a material revenue miss
- You have a seasonal demand pattern where in-season velocity is more than 2× off-season velocity
- Your supplier lead times vary by more than ±2 weeks from the stated nominal
If three or more of those apply, you're likely making replenishment decisions with a formula that can't account for enough of the variables that actually drive your inventory position.
Integration layer: where your OMS and ERP fit
One practical friction point in the transition from ROP-based spreadsheets to replenishment planning is the integration question. Your current ROP triggers are probably manual — someone checks the spreadsheet, sees a SKU at or below the trigger quantity, and places an order. Replenishment planning systems typically connect to your OMS or ERP (NetSuite, Brightpearl, Cin7, Linnworks) to create draft purchase orders or push order recommendations automatically.
This integration requirement is real, and it's worth being explicit about it. A standalone replenishment planning tool that produces recommendations in a dashboard but doesn't push those recommendations into your OMS reduces friction only modestly — you've replaced a spreadsheet formula with a dashboard alert, but the manual step of creating the actual PO is still there. The full value of replenishment planning automation comes from closing that loop to your order management system.
Stockorlo's integrations page covers the OMS and ERP connections currently supported. If you want to understand how the replenishment recommendation layer works end to end, the product walkthrough covers the three-step process from data connection to replenishment queue.