Guides
Reorder Point vs. Forecast: Which Signal Should Trigger a PO?
A reorder point draws one fixed line in the sand; a demand forecast moves with reality — and that difference decides whether your next order lands on time.
What a reorder point actually is
A reorder point is the stock level that triggers a replenishment order. The classic formula is simple: average demand over the lead time, plus a cushion of safety stock. Sell roughly ten units a day, wait two weeks for a supplier, and you set the trigger so the order goes out while there is still enough on the shelf to cover the wait. When inventory crosses that line, you buy.
The appeal is that it needs almost nothing to run. One number per SKU, checked against on-hand stock, and the reorder practically fires itself. That is exactly why it works well for a small, stable catalog: one sales channel, steady demand, and lead times that rarely surprise you. In a world that holds still, a fixed line is enough — the average it was built on stays true week to week, so the trigger keeps firing at roughly the right moment.
Where a static reorder point misleads
The trouble is the word static. A reorder point is set once from a snapshot of the past, and most of the time it is left alone. The moment demand stops matching that snapshot, the line is wrong — and it fails quietly, because nothing about the number changes to warn you.
Two things move underneath it. The first is demand. Seasonality, a promotion, a product going viral — any of these lifts real velocity above the average the trigger assumes, so stock crosses a line calibrated for a slower week and the reorder fires far too late. The reverse hurts too: demand cools, the old line keeps ordering to a peak that has passed, and capital piles up in overstock. The second is lead time. Most reorder-point math assumes the supplier takes a consistent number of days, but real lead times wobble with supplier delays, port congestion, and customs. A trigger tuned to a good month leaves no room when the shipment runs long. Set-and-forget thresholds drift out of sync, and the result is the familiar trio: late reorders, stockouts, and dead inventory.
What a forecast-driven signal does differently
A forecast replaces the frozen average with something forward-looking. Instead of one average-daily-demand figure standing in for every future week, demand forecasting estimates what each period will actually look like — reading trend and seasonality out of historical sales rather than flattening them into a single line. The trigger stops being a static threshold and becomes a projection that updates as the underlying reality changes.
This reframes both halves of the decision. Timing improves, because the signal anticipates the busy stretch instead of reacting once stock has already fallen through a fixed line. Quantity improves too, because the order is sized against projected need for the period ahead rather than a backward-looking average. Forecasting and reorder points are not really rivals — an accurate forecast produces a better, self-updating version of the same trigger. You can replenish on static thresholds; a forecast just makes the timing and the amount track what is coming.
| Static reorder point | Demand forecast | |
|---|---|---|
| Reacts to a demand trend | No — a fixed line | Yes — recomputed as demand moves |
| Accounts for lead-time change | Only via a manual buffer | Built into the projection |
| Signals what to order | Just "you hit the line" | A suggested quantity in the Buying Table |
How Assisty turns the forecast into the trigger
Assisty operationalizes exactly that motion. It forecasts what each product — and each variant — will sell over the horizon you choose, and because buying decisions happen at variant level, so do the forecasts. The projection is not just a chart: it marks which items run out before the period ends and which are overstocked, so the signal to act is built into the forecast itself.
From there, seeing a risk and fixing it are the same motion. At-risk items carry straight into the Smart Buying Table, where every SKU gets an AI-suggested quantity you can check, adjust, and turn into purchase orders. Each suggested quantity is computed from your sales velocity, lead times, and incoming stock, then rounded to your case sizes and capped at your maximum stock levels — the reorder amount comes out of the same forward-looking numbers that flagged the risk. The table ranks its findings by money at stake, including items that run out before a reorder can land, and hands each one a one-tap fix. You can also ask "what if" — trend up 20%, or exclude the weeks you were out of stock so the forecast reflects real demand — and the forecast and reorder needs update in front of you. When the plan is right, Atlas splits your selection into one PO per supplier.
Which signal should trigger your PO?
The honest rule of thumb: a static reorder point is fine at small, stable scale. One channel, a modest catalog, predictable suppliers — the fixed line holds. Add a second channel, a promo calendar, a growing assortment, or lead times that vary, and it starts misfiring in the ways above. That is the point to move to a forecast-driven trigger, where the timing and the quantity update themselves instead of waiting for you to re-tune a number that has already gone stale.