A low-stock number can be a useful warning, but it answers only one question: at what count should you pay attention? A reorder point answers a different question: when should you place an order, given how quickly this item sells and how long replenishment takes?
The two numbers can be the same, but they do not have to be. A fixed-unit threshold is a stock-count boundary. A sales-velocity reorder point uses recent sales and supplier lead time to estimate when to replenish. This guide shows how to choose, calculate, and review either approach for your catalog.
This is general merchant guidance, not a report on any store or a promise of an inventory result. ShelfSparrow currently supports fixed-unit workspace thresholds, product-specific overrides that take precedence over the workspace value, and active low-stock alerts when stock is at or below the effective threshold. It does not calculate sales velocity, adjust thresholds automatically, connect to a POS, provide threshold presets, or create purchase orders.
What is a fixed-unit threshold?
A fixed-unit threshold is a number of units. When stock reaches that number or goes below it, the item is considered low. The boundary stays the same when demand rises or falls, so it is easy to explain and predict. It also means that a threshold chosen during a quiet month can be too low during a seasonal rush—or unnecessarily high after demand slows.
Use a fixed threshold when you need a simple warning, sales history is thin, or demand and supplier timing are relatively steady. For each SKU or variant, write down the stock count you want to trigger attention, the supplier lead time you used when choosing it, and the date you last reviewed it. A threshold is more useful when it reflects the replenishment time and a buffer your store has actually chosen, rather than an unexplained round number.
The examples in the sources are not universal defaults. WooCommerce gives 2 units as an example threshold; its documentation tells merchants to enter the inventory count that should trigger a low-stock notification rather than prescribing one number for every store. 2 3
One secondary inventory guide describes a 50-unit reorder-point example made from a 20-unit par floor plus average demand during supplier lead time. That is one guide’s example, not a recommended starting point for every SKU. 10
Another secondary guide describes Min-Max replenishment as assigning each SKU a minimum and maximum. It says the approach can suit smaller store networks with limited demand variability; it is less responsive when demand changes materially. 11
What should I know about how the platform examples differ?
In WooCommerce, the setting is at WooCommerce → Settings → Products → Inventory → Low stock threshold. It provides a store-wide threshold and permits individual products to override it. The same value controls in-app and email low-stock alerts, and low-stock email notifications must be enabled for email alerts to send. 2 3
BigCommerce sets thresholds by inventory location. Its low-stock webhook fires at or below the location threshold only when an order changes stock; the out-of-stock threshold is zero. BigCommerce does not allow negative stock or backorders. These are BigCommerce behaviors, not ShelfSparrow settings. 6 7
How does a sales-velocity reorder point work?
A velocity-based reorder point changes with demand and supplier timing. The formula is:
Reorder Point = (daily sales velocity × supplier lead time in days) + safety stock 4 8
- Daily sales velocity is the average number of units sold per day for that SKU over the chosen period, expressed in units per day.
- Supplier lead time is the number of days from placing the order until replenishment is available for sale.
- Safety stock is the extra number of units kept as a buffer against demand or supply variation.
The units must match: units per day multiplied by days gives units, and safety stock is also in units. To calculate this responsibly, keep dated sales quantities by SKU and a current estimate of supplier lead time. If you do not have reliable item-level sales or replenishment dates, the result can look precise without being dependable; start with a fixed threshold and improve the underlying records first.
What should I know about a clearly hypothetical calculation?
Suppose a sample product sells 3 units a day, its supplier lead time is 14 days, and the store chooses 12 units of safety stock. Estimated lead-time demand is 3 × 14 = 42 units, so the reorder point is (3 × 14) + 12 = 54 units. The 12-unit buffer is about 29% of lead-time demand in this example. These sample inputs illustrate the calculation; they are not ShelfSparrow data or a universal setting.
One secondary guide recommends a rolling 30-day velocity window for stable products and 7 days for seasonal or promotion-driven SKUs. It describes safety stock of 20–30% of lead-time demand and order quantities to cover 30–45 days of current velocity, reduced for short shelf life or seasonal demand. Treat these as that guide’s starting guidance, then check whether it fits your own sales pattern, supplier performance, cash limits, and product life. 8
What does a days-of-cover check show?
If you do not want to maintain a full reorder-point calculation, estimate how long current stock will last:
days of cover = current stock on hand ÷ daily sales 9
The result is in days. Compare it with supplier lead time. The cited small-shop guide says that when stock has fewer days of cover than the supplier lead time, it needs immediate ordering. It describes 1–3 days of average sales as a typical buffer, with another 1–2 days for lead-time variability or supplier reliability concerns. These are estimates from that guide. They are not interchangeable with the 20–30% of lead-time demand buffer described by the other guide; use one method consistently and validate it against your own history. 9 8
For a sample SKU with 39 units on hand and sales of 3 units a day, days of cover is 39 ÷ 3 = 13 days. If its lead time is 14 days, cover is shorter than lead time, matching the cited guide’s immediate-order condition. This is an illustrative calculation, not a purchase instruction for a real store.
How should I choose a method for each SKU?
Choose a fixed-unit threshold when a stable, simple stock warning is enough; use a velocity-based point when you can maintain recent SKU sales and supplier lead-time data.
- Choose the item and stock basis. Work at the SKU or variant level, and keep locations separate if stock or lead times differ. Use the same definition of stock on hand each time you review it.
- Write down the data you have. Record current units, dated sales by SKU, supplier lead time, recent stockouts, and the date of the last count. Note when a sale or season makes the recent period unusual.
- Choose the method. Use a fixed-unit boundary when a simple, predictable alert is more valuable than adapting to changing demand. Use a velocity-based point when you have current sales and supplier lead-time data and can recalculate it. A weekly days-of-cover check is a practical middle step.
- Set and review the boundary. For a fixed threshold, choose and record the unit count that should prompt action. For a velocity method, calculate the reorder point from the stated formula and record its sales window, lead time, and buffer. Keep the order quantity decision separate: the threshold says when to review or reorder; it does not by itself determine how much to buy.
- Recalculate when the pattern changes. The cited guide suggests reviewing seasonal SKUs weekly and stable SKUs monthly. Review sooner after a promotion, a supplier delay, or a meaningful change in sales. 8
- Check what happened. At the next review, compare the threshold crossing with actual sales, delivery timing, stockouts, and leftover stock. Adjust the merchant-set value if the evidence supports a change, and write down why.
Fixed thresholds are easier to configure and offer predictable count-based warnings, but they do not respond when demand changes. Velocity methods can reflect recent demand and replenishment time, but only when sales and supplier data stay current and someone reviews the calculation. Neither method guarantees that a product will never stock out or that inventory costs will fall. 8 11
In ShelfSparrow, you can set a fixed-unit threshold for the workspace and override it for a product; the product-specific value takes precedence. An alert is active when stock is at or below that effective threshold. Sales-velocity formulas in this article are general merchant guidance: ShelfSparrow does not calculate velocity or automatically change a threshold or place an order.
How can I request a free listing snapshot?
ShelfSparrow’s free listing snapshot reviews one public listing and emails exactly one named finding plus a score from 0 to 100. It is separate from the full Store Audit and ongoing monitoring. It is not a threshold calculation or a full inventory review, and it does not promise additional findings. Request a free listing snapshot.
Which sources explain these inventory examples?
The official WooCommerce and Shopify documentation describes platform settings, while the other cited sources provide secondary examples with their own stated limits.
- Smart Inventory Alerts - WooCommerce Marketplace — Official source; fetched 2026-11-05.
- Woo Mobile App notifications Documentation - WooCommerce — Official source; fetched 2026-11-05.
- Products Settings Documentation - WooCommerce — Official source; fetched 2026-11-05.
- Reorder Point Formula: A Retailer’s Guide - Shopify — Official source; fetched 2026-11-05.
- BigCommerce Pricing and Plan Information | BigCommerce — Official source; fetched 2026-11-05.
- Inventory and Location Webhooks | BigCommerce Docs — Official source; fetched 2026-11-05.
- Allowing out of stock purchases while tracking inventory. — Official source; fetched 2026-11-05.
- Auto Reorder + Low-Stock Alerts for Ecommerce Guide | US Tech Automations — Secondary source; fetched 2026-11-05.
- Reorder points for small shops: stop running out of best sellers | Fluent Blog — Secondary source; fetched 2026-11-05.
- Inventory Management Best Practices for Retail Stores 2026 Guide — Secondary source; fetched 2026-11-05.
- Min-Max vs Demand-Based Store Replenishment | Olabi — Secondary source; fetched 2026-11-05.
- Inventory Thresholds vs Manual Reorders: 3-Way Breakdown 2027 | US Tech Automations — Secondary source; fetched 2026-11-05.