Repair an inventory alert when the stock source is accurate and a bounded threshold, location, recipient, permission, or timing error explains the problem. Replace it when the alert cannot support required locations, variants, delivery speed, ownership, or audit evidence. Retire it after every dependent workflow and recipient is identified and a controlled test proves it is inactive.
Repair configuration and source data
Begin with one item, variant, and location. Record the available quantity, alert threshold, qualifying event, expected recipient, documented delivery window, and actual result. Reconcile the inventory count before changing alert logic because a notification cannot repair inaccurate source data.
Square documents low-stock thresholds by item and location and says its alert emails follow each location's configured closing time. Shopify describes inventory quantities across locations and records inventory adjustments. These details make repair appropriate when the correct feature exists but the monitored location, timing expectation, or stock state is wrong.
Replace a workflow that cannot meet the need
Replacement is justified when the tool lacks required multi-location scope, recipient routing, immediacy, permissions, integrations, or reliable history. List those requirements and run a pilot with a test item or approved quiet period. Compare matching and nonmatching events, delivery latency, inventory history, and failure reporting.
Product retirement by the vendor is another replacement trigger. Shopify's Stocky low-stock page states that Stocky is no longer available after August 31, 2026 and directs users toward Shopify inventory features. When a dependency reaches end of service, do not keep an alert alive through unsupported workarounds; inventory its thresholds and recipients, then migrate with an overlap test.
Retire obsolete notifications safely
Retire duplicate, unactionable, or superseded alerts only after identifying who relies on them. Export or record thresholds, locations, recipients, schedules, and downstream automations. Disable one rule, cross its threshold with a controlled non-customer test, and verify both that the old alert stays silent and the replacement behaves as expected.
Do not delete inventory history or change out-of-stock selling behavior as a side effect of alert retirement. Those are separate operational choices. Preserve adjustment evidence and a rollback path until the new workflow has survived a complete business cycle.
Use explicit decision gates
Repair when one bounded correction produces the expected alert and a negative test stays quiet. Replace when a documented requirement is missing and the pilot closes that gap. Retire when the alert has no unique consumer or an approved replacement is verified.
Record the decision owner, effective date, evidence, and next review. If source counts, location ownership, or recipients remain uncertain, mark the work as hold rather than silencing an alert that may still protect fulfillment.
Sources
- Create Inventory Alerts — Square Support
- Inventory and locations — Shopify
- Low Stock — Shopify Help Center