Shopify low-stock alerts: thresholds and reorder points

# Shopify tracks the count, but a warning needs a rule

Shopify can tell you how much inventory is available. That does not answer when somebody should place the next order. A low-stock alert needs a threshold, and the threshold needs enough room for the supplier to deliver before the shelf is empty.

Shopify's inventory documentation points merchants who need direct low-stock notifications toward Shopify Flow or an inventory alert app. Stocky also offered low-stock reports and reorder points, but Shopify is retiring Stocky on August 31, 2026. If that report has been part of the morning routine, now is a good time to write down the rule behind it rather than copy a list of old numbers into a new tool.

# A threshold and a reorder point are related, not identical

A fixed threshold is a number you choose: alert me when this variant reaches 20 available units. It is easy to maintain and works well for steady products with predictable deliveries. The catch is that twenty units could be a month's supply for one SKU and half a day for another.

A reorder point ties the threshold to how the product sells and how long replenishment takes. A useful starter formula is average daily unit sales multiplied by supplier lead time, plus safety stock. If a variant sells four units per day, takes twelve days to arrive, and needs a fifteen-unit buffer, the reorder point is 63 units: 4 × 12 + 15.

Do not make the formula more impressive than the data. A thirty-day average can be fine for a steady consumable and terrible for a Christmas range. Promotions, wholesale orders, supplier holidays, and minimum order quantities all deserve a manual check. Recalculate fast sellers more often than the long tail. The ABC analysis guide gives you a simple way to decide which variants need that attention first.

# Choose the inventory number the alert should watch

Warehouse teams often say stock when they mean several different things. Units can be physically present, committed to orders, available to sell, or on the way from a supplier. A reorder alert usually belongs on available inventory because committed units already have a job. Incoming stock can inform the buying decision, but it should not silence an alert unless somebody trusts the delivery date.

Multiple Shopify Locations add another decision. A healthy total across the business can hide an empty fulfillment warehouse. If your alert tool watches the combined variant quantity, pair it with a location-level review. If it supports thresholds by Location, set them around the demand and lead time for that building rather than copying the same number everywhere.

BinTech evaluates its configured thresholds against Shopify's current available inventory for the variant. It does not forecast demand or create a purchase order. The threshold is the merchant's decision; BinTech watches the line and reports when inventory crosses it.

# Pick a notification method that matches the urgency

A saved Shopify inventory view is enough when one person checks purchasing every morning and a day's delay is harmless. Shopify Flow suits stores that want to build their own condition and send an internal message or apply a tag. An inventory alert app makes sense when the team wants a dedicated queue, per-variant thresholds, email delivery, or a record of which warnings are still open.

Timing matters most on quick sellers. A report that runs overnight may catch the problem several hours after a promotion has burned through the buffer. BinTech listens for Shopify inventory changes and checks the threshold when the event arrives. The alert fires when stock moves from above the threshold to at or below it, so the same low SKU does not send another email after every sale.

When inventory rises above the threshold, the BinTech alert resolves. If the variant later drops below it again, a new alert fires. That small detail keeps the alert list useful: the team sees a new crossing, not a daily reminder that nothing has changed. The stock-alert documentation covers recipients, test emails, recomputing thresholds, and the alert limits on each plan.

# Bad thresholds train people to ignore the inbox

The fastest way to ruin a low-stock system is to set every SKU to ten. Slow items sit in the triggered list for months, fast items sell out before anyone can react, and the inbox becomes background noise. Start with the variants that either sell quickly or hurt when they are unavailable. Give each one a threshold you can explain in a sentence.

Add the supplier or next action to the note when your alert tool supports it. Reorder from Northwind, move one case from overstock, or check the delayed purchase order is more useful than low stock. Review triggered alerts at a fixed time, assign an owner, and remove thresholds for discontinued products. The software can notice the crossing. A person still has to decide what happens next.

Watch for repeat alerts too. If a variant crosses the same line every few days, the threshold may be fine while the order quantity or replenishment routine is wrong. If an alert fires straight after receiving, the accepted quantity may not have been recorded correctly. That is a count problem, not a notification problem.

# Replace the part of Stocky you actually used

Stocky's low-stock report combined sales rate, lead time, and reorder points. A fixed-threshold alert is narrower. It can tell you that the line was crossed, but it will not calculate what to buy or choose a supplier. Stores that relied on Stocky for forecasting and purchase orders should choose a planning tool for that work.

Stores that only need straightforward low-stock warnings may not need another planning suite. Keep purchase orders in Shopify or the buying tool you already chose, then use BinTech for the floor work: thresholds, quantified bins, pick lists, cycle counts, and variance review. The Stocky migration guide separates those jobs so you can replace them without buying the same feature twice.

Begin with ten important variants. Calculate a defensible reorder point, enter the threshold, and send a test email. After a month, compare the alerts with what the buyer actually ordered. A number that looked sensible on a spreadsheet may need adjusting once real supplier delays and sales spikes get involved.