An inventory-alert recovery plan should name the inventory source of truth, preserve each threshold and recipient, define a manual check, and provide a one-item test that proves alerts work after repair. Build the plan before an alert fails, while normal settings and recent history are still visible.
Shopify's inventory adjustment history records who made an adjustment, when it happened, and how it affected quantity. Shopify's broader inventory adjustment guidance says adjustments are recorded with who, when, and why. Square's inventory alert documentation explains that a low-stock alert is generated when the in-stock count falls below a threshold and that thresholds are configured by location. Together, these facts identify the evidence needed for recovery.
Map the alert before an incident
For each critical SKU, record the product and variant ID, location, source-of-truth quantity, low-stock threshold, alert status, recipients, delivery channel, and expected send schedule. Note any app, integration, or automation between the inventory ledger and the notification. Assign an owner for the stock figure and another for the alert configuration if those duties differ.
Export or screenshot the configuration, but also store a text list that can be searched. Keep the snapshot private because recipient addresses and inventory levels may be commercially sensitive. Review the map after adding a location, renaming a variant, or changing fulfillment systems.
Define the failure signals
A failure is more than a missing email. Watch for an alert that never arrives after stock crosses the threshold, an alert for the wrong location, repeated alerts at the wrong quantity, recipients who no longer work there, or inventory that never reaches the alert system. A message sent to spam is a delivery failure even if the automation reports success.
Set a time-based fallback for important items. For example, the inventory owner can review a low-stock report at opening and before the final replenishment cutoff. The fallback should state who checks, what report is used, and where the result is recorded.
Preserve evidence before repair
When an alert seems wrong, freeze bulk configuration changes. Record the SKU, location, observed quantity, threshold, expected alert time, recipients, actual messages, and recent inventory adjustments. Shopify says its interface shows the most recent 180 days of adjustment history in that view, with older history available through a report, so capture or export relevant events before they age out of the immediate interface.
Check for receiving, returns, order edits, manual corrections, transfers, and integration updates. Do not force the quantity up and down merely to trigger a message until the physical and system counts are reconciled.
Recover in a fixed order
First, confirm the physical count or approved external source. Second, reconcile the platform quantity and inspect recent adjustments. Third, verify that the rule points to the correct variant and location. Fourth, restore the approved threshold and active recipients. Fifth, confirm that the delivery channel is connected and that messages are not filtered.
Change one component at a time and record the result. If several rules are broken, repair the most contained example first. This makes the causal check clearer and limits the chance of sending a flood of alerts.
Test the boundary safely
Use a test SKU or an approved low-risk item at one location. Set a documented starting quantity above the threshold, then apply a legitimate test adjustment that moves it below the threshold. Square defines the alert boundary as the in-stock count falling below the configured threshold. Record the before count, adjustment, after count, event time, recipient, delivery time, and message content.
Restore the test quantity through the normal adjustment workflow and give the adjustment a clear reason. Do not falsify the physical count of a live item. If the platform provides a sandbox or test catalog, prefer it.
Verify and close
A successful recovery has four pieces of evidence: the reconciled quantity, correct rule and location, successful notification to an active recipient, and a recorded test adjustment. Check that no duplicate or delayed messages appear after the test window. Re-enable any paused rules only after the contained case passes.
Update the recovery card with the root cause, repaired component, verification time, owner, and next review. If the alert remains unreliable, keep the manual fallback active and escalate to the platform or integration provider. Do not label the issue resolved because a settings page saved; resolution requires a real, controlled boundary test and confirmed delivery.
Sources
- Viewing Inventory Adjustment History — Shopify
- Managing inventory quantities — Shopify
- Create Inventory Alerts — Square Support