A Shopify reorder-point threshold is the inventory level at which a product should move from “watch this” to “start the next replenishment.” It is not a prediction of the exact day a SKU will sell out, and it is not the same as the quantity currently sitting in the warehouse. It is an operating boundary: when available inventory falls to that point, there should be enough time left to place and receive the next order before customers reach an empty shelf. For a Shopify store, the threshold gives the team a shared action line across variants, locations, and the daily order stream instead of leaving replenishment to whoever happens to notice a low-stock badge first.
That distinction matters because a threshold only becomes useful when it is read beside live inventory. A product can be above its reorder point and still be in trouble if sales have accelerated, a supplier has started missing its lead time, or a promotion is pulling demand forward. The reverse is also true: a product can sit below a static threshold without needing an immediate reorder if sell-through has slowed, an inbound PO is confirmed, or the quantity on hand covers the actual window to restock. Current on-hand quantity answers “how much is available now?” The threshold answers “when should the next decision begin?” Keeping those questions separate prevents a healthy buffer from looking like excess stock and a fast-moving SKU from looking safe just because its absolute count is still high.
The threshold signals the loop reads together
- Reorder-point threshold versus current on-hand quantity — the gap shows whether the SKU is approaching the action line or has already crossed it.
- Recent sell-through, using a short window instead of a stale seasonal average — a threshold should respond when demand changes, not after the stockout.
- Days of cover against current velocity — the same 300 units mean something different at ten units a day than at thirty.
- Supplier lead time and confirmed inbound dates — the reorder window has to include the time the vendor actually takes, plus enough room for slippage.
What the loop does — and what it does not
Vendloom reads the Shopify threshold with inventory quantity, sell-through, days of cover, and supplier lead time on the same beat. When those signals agree, the loop drafts the reorder while there is still room to review it, carries the reasoning into the PO context, and keeps watching for the inbound date to slip. It can account for the fact that two variants share a supplier, that an inbound PO is only partly filled, or that a sales spike is isolated to one channel rather than the whole catalog. When the signals disagree, it holds the draft rather than turning a static threshold into an automatic buy: a sudden promotion, a slowing channel, or a confirmed shipment can change the right action. The founder should not have to re-check every SKU just because an inventory number crossed a line.
“A threshold is the start of a decision, not the decision itself.”
If the threshold is crossed while sell-through is holding and the supplier window is getting tight, the reorder becomes a real assignment: draft the order, watch for confirmation, and ping the founder only when the combined signals require attention. That is the same quiet automation loop behind the stockout-risk, pause-underperforming-ads, and supplier-health notes. Inventory thresholds provide the line; live demand and supplier behavior explain whether crossing it deserves action. The work stays drafted and monitored between pings, so the founder sees the few moments that need judgment instead of a queue of alerts that all look urgent.