When an inventory alert is missing, late, duplicated, or wrong, preserve the alert and inventory evidence before editing the workflow. Record the exact SKU or variant, location, quantity state, threshold, recipient, alert time, and the inventory change that should have triggered it. Then contain the notification problem without changing real stock to fit the alert.
Open a precise incident record
Save the alert message and its message ID, delivery channel, sender, recipients, timestamp, SKU, variant, location, reported quantity, and threshold. Capture the current inventory states and the recent adjustment history. Shopify says its adjustment history records who made a change, when it happened, what caused it, and how quantities changed. That trail helps distinguish a bad alert from a legitimate sale, return, transfer, reservation, app update, or manual adjustment.
Record the workflow name, enabled state, last edit, owner, trigger, conditions, cooldown, and recent run IDs. Redact customer and staff information that is not necessary to explain the incident.
Classify the failure before acting
For a missing alert, check whether the quantity actually crossed the threshold, whether the workflow watches the correct inventory state and location, and whether delivery failed after the trigger ran. For a duplicate, check whether several quantity changes, retry layers, locations, or overlapping workflows produced separate runs. For a false alert, confirm that the message did not use stale inventory or the wrong variant.
Shopify's Product variant inventory quantity changed trigger starts on inventory changes from orders, manual edits, or apps and provides the prior quantity. Shopify also notes that a Stocky daily low-stock email is passive rather than immediate and goes to one address. Do not compare a daily report with a real-time workflow as if they promise the same timing.
Contain the notification defect
If alerts are flooding recipients, disable the alert workflow or delivery action while leaving inventory tracking intact. Preserve the workflow version and last known-good settings. Do not delete adjustment history, change saleable quantity, or turn off inventory tracking merely to silence a message. If alerts are missing, add a temporary manual review of the affected SKU and location until the automated path passes a test.
Use one test SKU or sandbox item to reproduce the problem. Cross the threshold with the smallest documented adjustment, include an adjustment reason, and record the workflow run and resulting message. Restore the test quantity with another documented adjustment.
Recover and close with evidence
Restore the last known-good threshold, scope, recipients, and cooldown. Re-enable the workflow and repeat one safe test. Verify exactly one message, the correct location and quantity, and a reasonable delivery time. Check that no customer-facing message, purchase order, product publication change, or external webhook ran unintentionally.
Close the incident as confirmed, probable, or unknown. Include the timeline, affected items, root cause, containment, test evidence, restored version, and follow-up owner. Keep monitoring through at least one normal inventory change. If the cause is unknown, retain the evidence and avoid claiming that the problem is fixed merely because the next message arrived.
Sources
- Viewing Inventory Adjustment History — Shopify
- Product variant inventory quantity changed — Shopify Help Center
- Low Stock — Shopify Help Center