Set three SKU-level thresholds tied to sales pace and replenishment time. For an item selling 4 units a day with a 14-day replenishment lead time and 20 units of safety stock:
- Watch alert: 104 units
- Reorder alert: 76 units
- Urgent alert: 20 units
For a store with one location, predictable replenishment, and straightforward variants, a simple Shopify automation can handle the job. When inventory is spread across locations, bundles share components, or purchasing depends on supplier lead times and purchase orders, inventory planning software is the better fit.
Build SKU Thresholds Around Lead Time
A fixed low-stock number such as 10 or 20 units rarely works across an entire catalog. Ten units may last six months for one product and disappear in two days for another.
Base the reorder point on how much stock you expect to sell before the next replenishment arrives.
Reorder point = average daily sales × replenishment lead time + safety stock
Using the example above:
- Average daily sales: 4 units
- Lead time: 14 days
- Safety stock: 20 units
- Reorder alert: 4 × 14 + 20 = 76 units
Add a watch threshold far enough above the reorder point to give the buyer time to review demand and prepare an order. If inventory is reviewed weekly, add one week of expected sales.
Watch threshold = reorder point + average daily sales × review period
For the same SKU:
- Reorder point: 76 units
- Weekly demand: 4 × 7 = 28 units
- Watch threshold: 76 + 28 = 104 units
- Urgent threshold: 20 units, matching the safety-stock level
Start with the SKUs where a stockout causes the most trouble: fast sellers, products with long supplier lead times, and items that generate customer-service issues when unavailable. Slow-moving products with short replenishment cycles can use lighter monitoring.
Choose the Right Type of Inventory Tool
Use the simplest setup that matches the way stock is purchased, stored, and fulfilled. A threshold alert is useful when someone only needs to decide whether to order more of a SKU. It is not enough when the real task involves supplier orders, inbound stock, transfers, bundle components, and allocation across locations.
| Approach | Best fit | What it handles well | Maintenance burden | Where it falls short |
|---|---|---|---|---|
| Shopify admin review | Very small catalogs with manual purchasing | Finding low-stock items during scheduled inventory reviews | Little setup, but someone must review inventory consistently | No automatic reminder when stock changes between reviews |
| Shopify Flow or similar automation | One location, simple SKU rules, and clear internal ownership | Internal email, task, or team-message alerts after an inventory event | Low once thresholds and routing are established | Location rules, bundles, supplier timing, and purchasing logic become hard to manage |
| Dedicated inventory alert tool | Growing catalogs that need digests, escalation, or several alert conditions | Multiple thresholds, scheduled summaries, alert routing, and repeat reminders | Moderate; thresholds and recipients need periodic review | Alerts do not replace purchasing workflows or demand planning |
| Inventory planning system or ERP | Multi-location operations, purchase orders, bundles, and formal replenishment processes | Forecasting, supplier lead times, inbound inventory, purchase orders, and replenishment workflows | Highest; inventory records and purchasing processes must stay disciplined | More administration than a simple catalog needs |
For a small Shopify store, an internal alert often covers the immediate need: stock has reached its reorder point, and the buyer needs to place an order.
Move beyond simple alerts when the question is no longer “Should we reorder this SKU?” but “Which supplier order should we place, for which warehouse, and how much stock remains after bundle demand and inbound inventory are considered?”
Set Alert Timing Without Creating Noise
An alert system that sends a message for every inventory change quickly becomes background noise. A better pattern separates early warnings from stockout risk.
Use three notification levels:
- Send an immediate urgent alert when available inventory reaches safety stock.
- Send a daily digest for SKUs at the reorder point.
- Send a weekly watch list for products approaching the reorder point.
This gives the purchasing team a regular list to work through while reserving immediate messages for problems that cannot wait.
A digest only works when one person owns it. If no one reviews a daily inventory email or operations channel, use a more direct alert for reorder-level items rather than relying on a report that sits unread.
Match Alerts to the Way You Sell
Variants
Set thresholds at the variant level when customers buy different sizes, colors, pack sizes, or other options independently.
A product may show 100 units in total while the best-selling size has no available stock left. Parent-product totals are useful for catalog reporting, but they do not prevent a variant-level stockout.
Multiple fulfillment locations
When inventory is held in several warehouses, stores, or fulfillment partners, tie alerts to the location that serves the order.
A warehouse with 200 units does not solve a problem at a local fulfillment location with 15 units left, especially when transfers take several days.
Bundles and kits
Bundles need component-level monitoring. A gift set may show five sellable bundles remaining, but one component could also support several other products and be close to depletion.
Finished-goods alerts alone can miss that shared demand. Use component alerts when the same item feeds multiple bundles or products.
Made-to-order products
Made-to-order stores should alert on materials rather than finished goods. Track the inputs that limit production, such as fabric, blanks, ingredients, packaging, or other components.
Set those material thresholds around production capacity and supplier lead times. A finished product can remain available in Shopify while the material needed to make it is already running low.
Keep Thresholds Updated
Inventory rules need maintenance because sales rates and supplier timing change.
Review stable products monthly. Review seasonal items, new launches, promotions, and supplier disruptions weekly until demand returns to a predictable pattern.
Update average daily sales after any meaningful change. If a SKU moves from 1 unit per day to 6 units per day, its old reorder point will send the alert far too late.
Also decide what happens after the first alert. Many workflows notify the team once when stock crosses a threshold, then stay silent while the item remains below it. Add a repeat reminder or an unresolved-alert process so an overlooked reorder does not disappear after the first message.
Keep a short record of:
- Stockouts
- Rush orders
- Excess inventory
Those outcomes show whether lead-time assumptions or safety-stock levels need adjustment.
Tool Requirements That Matter
The tool should follow the same inventory logic your operation uses. Variant-level tracking, location-level tracking, and available-stock logic matter more than a long list of notification templates.
Use this list when selecting an alert system:
- Inventory basis: Base replenishment alerts on available units, not only on-hand units.
- Variant support: Give each sellable option its own threshold when demand or replenishment differs.
- Location support: Separate stock by warehouse, store, or fulfillment partner when inventory is distributed.
- Notification routing: Send alerts to a purchasing inbox, operations channel, or assigned team member.
- Alert timing: Support event-based alerts, scheduled digests, or both.
- Escalation: Route urgent alerts to a second recipient when the first person does not act.
- Permission scope: A notification tool does not need permission to change inventory quantities when it only reads stock and sends messages.
- Alert history: Keep a record of when alerts fired and how the issue was resolved.
Before turning on live alerts, use a non-selling test SKU. Set its threshold at 10 units, adjust inventory from 11 units to 9 units, and confirm that the alert reaches the intended channel with the SKU, variant, location, and available quantity. Restore the test quantity afterward.
When Alerts Are Not Enough
Standalone alerts are not the right answer when the real issue is replenishment planning.
A business with erratic demand, long production cycles, supplier minimums, or complex purchase orders needs a system that helps plan orders, not simply a larger volume of notifications.
Avoid adding a separate alert tool on top of an ERP or 3PL platform that already controls inventory unless there is one clear source of truth. Conflicting stock counts lead to duplicate alerts, missed replenishment, and manual reconciliation.
Dropshippers need a different workflow as well. Supplier availability updates, feed reliability, and backorder rules matter more than a Shopify-only stock threshold.
Questions to Answer Before Setting Up Alerts
- Do you need alerts for one location or several?
- Are thresholds set for individual variants or parent products?
- Does available inventory drive the alert?
- Does each SKU have a documented supplier lead time?
- Do bundles or kits consume shared component stock?
- Who owns the alert after it arrives?
- Does the workflow repeat or escalate unresolved reorder alerts?
- Will a daily digest reduce noise without delaying action?
- Is another system already the inventory source of truth?
A store with one location, simple variants, predictable lead times, and one buyer can usually stay with lightweight automation. Once inventory involves multiple locations, shared components, supplier orders, or inbound-stock decisions, a planning system becomes more appropriate.
Inventory Alert Mistakes to Avoid
Using one threshold for every SKU
A universal 10-unit or 20-unit alert ignores sales velocity and replenishment time. The same quantity can represent two days of sales for one SKU and six months for another.
Alerting on product totals instead of variants
A product with 100 units spread across five sizes can still create a stockout if the fastest-selling size reaches zero available units.
Sending every alert to every person
Broad notifications create message fatigue and blur responsibility. Route watch alerts to the person planning purchases. Reserve urgent alerts for people who can approve or place an order.
Counting inbound stock as ready to sell
Do not treat incoming inventory as available for fulfillment until it has been received. Purchase orders can slip, transfers can arrive late, and received quantities can differ from expected quantities.
Bottom Line
Automate Shopify inventory alerts around SKU-level available stock, lead-time demand, and safety stock.
A simple Shopify workflow works well for centralized inventory and predictable replenishment. Move to inventory planning software when stock is split across locations, bundles draw from shared components, or purchasing decisions depend on supplier lead times, inbound inventory, and purchase orders.
Decision Checklist
| Check | Why it matters | What to confirm before choosing |
|---|---|---|
| Fit constraint | Keeps the guidance tied to the real setup instead of generic tips | Size, compatibility, timing, budget, skill level, or storage limits |
| Wrong-fit signal | Shows when the default answer is likely to disappoint | The setup, upkeep, storage, or follow-through requirement cannot be met |
| Lower-risk next step | Turns the guide into an action plan | Measure, compare, test, verify, or choose the simpler path before committing |
FAQ
How many inventory alert thresholds should a Shopify store use?
Use three: watch, reorder, and urgent. The watch threshold gives purchasing time to review demand. The reorder threshold signals that an order should be placed. The urgent threshold marks safety stock or a near-stockout situation.
Should Shopify inventory alerts use available or on-hand inventory?
Use available inventory for customer-facing replenishment alerts. On-hand inventory can include units committed to existing orders or otherwise unavailable for sale, which can overstate the stock that remains.
Does Shopify Flow work for inventory alerts?
Shopify Flow can handle straightforward internal inventory alerts when the workflow has the needed inventory trigger and notification action. It suits stores with one location, clear SKU thresholds, and simple routing rules.
How should inventory alerts work for product variants?
Track each sellable variant separately when sizes, colors, bundles, or pack sizes have different demand and replenishment patterns. Parent-product inventory is useful for catalog reporting, but it is too broad for preventing variant-level stockouts.
Do inventory alerts replace demand forecasting?
No. Alerts tell you when stock has reached a predefined point. Forecasting estimates future demand and replenishment needs before that point is reached. Stores with seasonal sales, long supplier lead times, or multi-location inventory need both.