To troubleshoot an inventory alert with a change log, identify the exact item and location, capture the stock count and threshold, record when the qualifying event occurred, and test one reversible change at a time. Do not adjust live inventory blindly just to make a notification appear.
Define the alert precisely
Record the product and variant identifier, location, available quantity, alert threshold, sales channel, recipient, time zone, and alert method. State the expected trigger in a complete sentence, such as an email after one location falls below five available units. Then record what actually happened and the source of the inventory count.
Location matters. Shopify documents inventory as quantities attached to locations and records adjustments so operators can know when and why a quantity changed. Square's alert instructions also configure thresholds by item and location. A correct total across a business can still produce the wrong alert if the rule watches a different location or variant.
Build the event timeline
Add the sale, return, transfer, receipt, manual adjustment, and alert times to the log. Note whether the alert is immediate, scheduled, or delayed until a business event. Square says its low-stock alert emails are sent after each location's configured closing time, so a missing midday email is not necessarily a failed trigger. Shopify's documented Stocky daily report is also passive rather than immediate, while Shopify Flow can support reactive workflows.
Record the platform's actual behavior instead of assuming all alerts are real time. Check the recipient address, spam handling, workflow status, user permissions, location hours, and whether the item is enabled for inventory tracking.
Run a controlled test
Use a test item or a quiet period approved for inventory work. Capture the starting quantity, lower it across the threshold with one documented adjustment, and wait through the documented delivery window. Do not create a customer order unless that is an authorized test. Confirm the platform's inventory history, workflow execution, and receiving mailbox separately.
If the alert does not arrive, change only one factor: recipient, threshold, location, workflow enabled state, or permission. Restore the starting quantity and record the rollback after each test. If the inventory count itself is wrong, stop alert testing and reconcile the count first because an alert cannot correct its source data.
Close without hiding the cause
Retest the matching and nonmatching cases. One should alert and the other should remain quiet. Keep the final threshold, location, recipients, timing expectation, and owner in the log. Label the outcome resolved and retested, delayed by design, contained, or unresolved.
A useful inventory-alert change log makes the rule auditable: it shows which count crossed which threshold at which location, when the platform evaluated it, and where the notification was expected to arrive.
Sources
- Inventory and locations — Shopify
- Low Stock — Shopify Help Center
- Create Inventory Alerts — Square Support