If manual stock checks are becoming hard to keep up with, Shopify Flow offers a low-stock email template that can prompt an owner to review inventory. Keep manual checking if it remains manageable; otherwise, consider this option before paying for another inventory app. The email is a prompt to review stock, not an instruction to buy.
As checked on November 17, 2026, Shopify lists Flow as free and available on Basic, Grow, Advanced and Plus. Your existing Shopify bill, stock purchases and time spent reviewing alerts remain separate. This is an existing workflow, not a new release.
The example is an owner-run US homewares shop: one nontechnical person, an existing Shopify Basic subscription and email inbox, one inventory location, 50 tracked product variants and US$0 a month for additional software. Those are planning assumptions, not a customer case or a verified capacity allowance. A variant is a particular product option, such as a mug in one colour.
Should you keep manual checks or add email alerts?
Choose by how often stock needs attention, which quantity matters, how frequently you want a reminder, who will act on it and how much setup you can maintain. An unread alert does not solve a missed stock check.
Route | When it fits | Additional software cost | Main limitation |
|---|---|---|---|
Manual review in Shopify | An agreed checking routine is reliable and manageable. | US$0 with the existing store and tools assumed here. | You must keep checking; no event email is configured. |
Flow owner-email alert | You need a prompt when stock changes and can review the rule and inbox. | No Flow app charge under the current Free listing. | Quantity, threshold and recipient need configuration; receipt and follow-up need checking. |
Neither route removes the existing store subscription or the work of deciding what to order. There is no verified setup-time estimate, time-saving figure or numeric internal-email allowance for this example. Fifty variants does not mean fifty emails: the notification rule and subsequent changes determine which events qualify.
A fixed numerical rule does not need an AI model, demand forecast or agent subscription. For the broader distinction, see when to choose a chatbot, workflow or agent. Here, the useful job is narrow: identify a stock condition and bring it to a person’s attention.
What do you need before installing Flow?
Shopify’s current eligibility page includes businesses in all countries on Basic, Grow, Advanced and Shopify Plus, and says Flow is available only in English. Do not assume an unlisted plan is eligible.
An owner or authorized operator able to install and access Flow.
Accurate inventory tracking for the intended variants, with one relevant inventory location. Check the workflow’s scope; do not assume it excludes untracked items automatically.
An owner-controlled inbox, a sender address to check and a plan for reviewing alerts during absences.
A chosen stock quantity, threshold and repeat-notification rule, plus an initial review of variants already low.
Install the Shopify-developed app if needed, and review its requested access. The Flow app listing discloses access to customer information, store-owner and staff information, and order-related data. Choosing a stock-only workflow does not mean the app has inventory-only permissions. Keep customer details out of these stock emails.
Which template should you install?
Look for Get notified by email when product variant inventory is low, listed in Shopify’s internal-email documentation. Other templates initiate supplier reorders or hide products when stock runs out. Those perform different jobs and are outside this owner-notification setup.
Follow Shopify’s documented template-creation sequence:
In Shopify admin, open Apps > Flow, choose Create workflow, then Browse templates.
Find the low-variant-inventory email template and review its purpose before selecting Install.
Inspect the installed trigger, conditions, actions and placeholder values. Keep it inactive while configuring and checking it.
Confirm that the intended outcome is only an email to the owner. Do not enable supplier messages, purchasing, inventory writes, product hiding or unrelated connectors as part of this workflow.
The public template listing establishes its intended task, not the exact defaults in your installed copy. Check every branch before activation; a familiar template name is not a substitute for reviewing its actions.
Which stock quantity should the alert watch?
Use the quantity that answers your operational question, and use the same meaning in the condition and email. Shopify’s variant reference defines inventoryQuantity as the variant’s total sellable quantity. That is not a definition of physical stock on a particular shelf.
Shopify’s inventory-state documentation distinguishes available stock from physical on-hand stock, committed items and incoming deliveries. Incoming stock is not available to sell until received. Items reserved on a draft order can already be committed before that draft becomes an order; do not treat every draft as having no inventory effect.
For example, “four available to sell” and “four physically present” can lead to different decisions. Compare the selected field with the stock view you actually use. The before-and-after quantities must describe the same variant and comparable stock scope.
This guide stays with the single-location assumption. It does not establish a location-specific field recipe or exactly which draft-order reservation changes fire the selected trigger. If you cannot reconcile the quantities—or need separate warehouse alerts—keep manual review while those details are resolved.
How can you avoid an email for every low-stock change?
Decide whether you want a reminder whenever stock changes while low, or only when it first falls below a boundary. Shopify’s inventory workflow examples describe checking both current and prior quantities to limit repeated notifications. The page’s numeric example is inconsistent about that boundary, so verify the operators in your own preview.
For a proposed rule of falls below five, the arithmetic is current < 5 AND prior >= 5. Both conditions must be true. Five is an illustrative threshold, not a recommended reorder point; the table describes mathematical results, not observed Flow runs or default template settings.
Before → after | Rule result | Why |
|---|---|---|
6 → 4 | True | Crosses below five, even though the change skips five. |
5 → 4 | True | Moves from the boundary into the low range. |
6 → 5 | False | Five is not below five. |
4 → 3 | False | Already below the threshold. |
3 → 4 | False | Still low, but rising rather than crossing down. |
4 → 7 | False | Moves back above the threshold. |
7 → 4 | True | A later fall crosses the boundary again. |
If you mean “five or fewer”, that is a different boundary: conceptually, current <= 5 AND prior > 5. Do not mix the two definitions. Check the actual current/prior fields, both comparisons and their AND relationship before adopting either design.
A true result does not guarantee exactly one message or successful delivery. Nor is a crossing rule a backlog scan: an item already at four when you enable it still needs attention, even if its next change to three would not qualify. Review already-low stock separately and keep a record of unresolved items.
What should the owner’s email contain?
In Send internal email, enter the owner’s fixed recipient address. Shopify’s email-action reference says recipient addresses cannot be variables; multiple fixed recipients can be separated by commas. For this one-person example, use the single inbox the owner will actually check.
Keep the message focused on the variant, the quantity being watched and the next human action. Suggested wording:
Subject: Stock review needed: [variant name]
Review [variant name / SKU if present]. The selected [quantity label] is [current value], below the chosen threshold [value]. Check current stock and existing commitments before deciding whether to order. This alert has not placed an order.
The brackets are human-readable placeholders, not paste-ready Flow code. Use Add a variable for supported variant details and quantity values, then check the preview. The available choices depend on data supplied by earlier workflow steps. Write the quantity label and threshold to match the condition; do not leave unexplained numbers or placeholder text in the final email.
Also check the sender. The email-action documentation says Flow uses the store’s configured sender address and notes that authentication and recipient filtering can affect messages. Confirm the identity actually shown in the received email rather than assuming an old Flow sender address still applies.
How do you check the logic and actual delivery?
Use two separate checks. Shopify’s workflow test mode previews logic and variables without sending notifications or changing live store data; it stops at the first action that would make a change. A successful preview therefore cannot confirm inbox receipt.
For the logic check, open the workflow in Edit and choose Test your workflow at its trigger. Under + Add event, use a permitted recorded event or create a simulated event. Select it, inspect the highlighted path, and open a condition or action’s Preview tab. The event fields depend on the trigger; check what your account requires.
Use the proposed boundary cases above to review matching and nonmatching paths, including a jump past the threshold, equality and another change while already low. Confirm the variant, comparable quantity fields, fixed recipient and readable message. These are checks for you to run, not reported test results.
After those checks and the action review, Shopify’s activation instructions use Turn on workflow. Then confirm live receipt separately:
Observe the next legitimate qualifying stock change, or arrange a controlled, reversible real event with truthful stock data and a non-customer-facing test item where feasible. Do not falsify live stock just to generate an email.
Compare the event with the message: correct variant, understandable quantity, intended recipient and expected sender. Check actual receipt, including spam or filtering.
Record what changed, the expected branch, the observed result and relevant times. Keep manual stock review while delivery or behavior remains unconfirmed.
If no message arrives, distinguish a condition that did not qualify from a sender or inbox problem. Shopify does not specify a fixed workflow completion time, so do not assume immediate delivery. Investigate the run and configuration instead of repeatedly changing live quantities to force another attempt.
What should you do after an alert arrives?
Open the current stock record before deciding anything. Review sellable stock, existing commitments and incoming purchases; then decide whether to reorder, investigate a discrepancy or take no action. Record the decision somewhere you already use. An email should not become an untracked purchasing obligation.
If event emails become too noisy, reconsider the threshold and repeat rule first. Shopify also lists a weekly low-stock summary template, but its query limits, filters and coverage need checking before relying on it for all 50 assumed variants. It is a separate option, not a verified replacement in this setup.
Keep the scope small: notification, stock review, human decision. The owner still chooses whether to spend money, and the alert does not forecast demand or guarantee stock availability. If manual review remains simpler and reliable, there is no need to add automation.
For a separate store-maintenance task using existing Shopify tools, see preparing accurate product photos without another app. That guide covers listing images, not inventory alerts.
