Write the alert's decision statement
Start with one sentence that states what the alert is meant to protect. For example, the alert may warn the purchasing owner when available inventory for a sellable variant falls below a reorder point at a specific location. Name the decision that follows the alert. Without that statement, the team may receive a message but still disagree about who should act.
Identify the exact inventory quantity
Document whether the rule uses on-hand, available, committed, incoming, or another platform-defined quantity. Include the product variant, location, sales channel, and any excluded stock. Shopify distinguishes setting an inventory quantity to a specific value from adjusting it by a positive or negative amount. That distinction belongs in the alert record because a manual correction and a shipment movement can affect the same displayed total in different ways.
Record the threshold and timing
Write the threshold, comparison operator, evaluation frequency, and quiet period. State whether an alert fires once, repeats while the condition remains true, or clears and can fire again after recovery. Include time zone and business-calendar assumptions. If a threshold differs by location or product, store each rule explicitly instead of hiding exceptions in free-form notes.
Assign four ownership roles
Name the rule owner, data owner, first responder, and escalation owner. The rule owner approves thresholds. The data owner investigates inventory accuracy. The first responder handles the operational action. The escalation owner decides what to do when the alert cannot be resolved. One person can hold more than one role, but every role should have a named backup.
Document delivery settings
Record the workflow name, trigger, conditions, recipients, sender identity, and message template. Shopify Flow's Send internal email action uses a configured sender address and supports multiple recipients. Shopify also notes that recipient addresses in that action cannot be populated with variables. Treat those platform details as part of the configuration record, not tribal knowledge. Never add an external recipient during troubleshooting without authorization.
Create a controlled test
Use a test variant or another approved low-risk method. Capture the inventory value before the test, the change applied, the time the rule evaluated, the recipient who received the message, and the value after restoration. If the test requires an inventory adjustment, record the reason. Shopify's inventory history is intended to show who changed inventory, when it changed, and why it changed, which makes a reason field valuable evidence.
Handle false positives and silence
For a false positive, compare the alert's quantity definition with the platform's current quantity and location. For a missing alert, check trigger conditions, workflow status, sender configuration, recipient spelling, mail filtering, and the event timestamp. Do not lower the threshold or broaden recipients merely to make the test pass. Correct the documented mismatch and rerun the same controlled case.
Keep a change log
For every configuration change, preserve the previous value, new value, reason, approver, implementer, and verification result. Link changes to incidents or purchasing decisions. Review the alert after a location change, fulfillment-policy change, major assortment change, or repeated false alert.
Define closure
An inventory alert is operationally ready when the quantity definition is unambiguous, the threshold is approved, owners and backups are named, the delivery path is verified, and a controlled test has passed. A screenshot of the workflow alone is not proof that the data, recipient, and response process work together.
Sources
- Managing inventory quantities — Shopify
- Adjusting inventory quantities — Shopify Help Center
- Send internal email action — Shopify Help Center