The Shopify Flow automations worth setting up first are the ones that replace a check you already do by hand every day: a low-stock alert, hiding products that sell out, holding high-risk orders for review, and flagging orders that have not shipped on time. Add one more before any of them: an alert that tells you when a workflow fails. Flow is a free Shopify app on the Basic, Grow, Advanced and Plus plans, and each of these workflows starts from a Shopify template you can install in a few clicks.
Below: the setup order, the triggers and conditions to use, the settings that trip people up, and a modelled estimate of the time each saves. Everything here comes from Shopify’s Help Center and Flow pages, checked on October 21, 2026. We have not tested these workflows in a live store, and the time figures are a hypothetical model, not measured results.
Before you build: what Flow can do on your plan
Every Flow workflow has one trigger (the event that starts it), plus conditions (checks on the data) and actions (what Flow does). You open it from Apps > Flow in the Shopify admin.
- Plans. Shopify lists Flow on the Basic, Grow, Advanced and Plus plans. Starter is not on that list. Most features are available on every listed plan.
- Plan-limited actions. The Send HTTP request action, which lets Flow call outside services, is available only on Grow, Advanced and Plus. Tasks created by custom partner apps are Plus only. Usage limits vary by plan, based on API rate limits.
- Language. Shopify says Flow is only available in English.
None of the seven workflows below needs Send HTTP request, so all work on Basic. For tools Flow does not connect to, see our guide to Zapier, Make and n8n for online stores.
Three ways to create a workflow
- From a template. Click Create workflow, then Browse templates. Pick one, click Install, replace placeholder tags and email addresses, then click Turn on workflow.
- Manually. Click Create workflow, select a trigger, then add conditions and actions.
- With Sidekick. On a desktop, open Sidekick inside Flow and describe the workflow in plain language. Shopify says Sidekick workflows are created inactive and tagged
sidekick, and that Sidekick “may omit business-specific logic in complex workflows,” so review every condition before you turn one on.
Templates are the safest start because they already use the right trigger.
Which Flow automation to set up first, and why
Our recommended first seven, in setup order: safety first, then the workflows that replace the most repeated checking.
1 Workflow error alert Workflow error occurred None needed Send internal email or Send Shopify alert for errors
2 Low-stock alert Product variant inventory quantity changed Available at or below your threshold, and prior quantity above it Send internal email
3 Hide and republish stock-outs Product variant out of stock / back in stock All variants out of stock at all locations Unpublish product / Publish product
4 High-risk order hold Order risk analyzed Risk level is high Add order tags, Hold fulfillment order, Send internal email
5 Late unfulfilled order flag Scheduled time (daily) Unfulfilled and older than your shipping promise Add order tags, Send internal email
6 Expedited shipping tag Order created Shipping method name matches your express rates Add order tags, Send internal email
7 Spend-tier customer tags Order paid Customer lifetime spend above each tier Add customer tags
Triggers and actions named as they appear in Shopify’s Flow reference, checked October 21, 2026. Setup order is our recommendation.1. Get an alert when any workflow fails
Once you rely on Flow to hide products or hold orders, you stop checking by hand, so a silent failure is worse than no automation.
Use Shopify’s template “Get notified by email when workflow run errors are detected” (or the version that sends a Shopify alert). It uses the Workflow error occurred trigger, which starts a workflow when another workflow fails during execution.
Two details matter:
- Run history is short. Shopify keeps workflow runs for 14 days after they complete, then removes them. If you check the Recent runs list once a month, you can miss a failure entirely.
- The alert fires once per version. Shopify says the trigger runs only once per workflow version within a 30-day period, even if that workflow fails repeatedly. Ten failures in one day produce one alert. So when the email arrives, open the run and fix the workflow; do not wait for a second warning. Editing the workflow creates a new version, so a failure after your fix will alert you again.
2. Low-stock alerts that fire once, not on every sale
Use the Product variant inventory quantity changed trigger, which Shopify says fires when a variant’s inventory changes from an order, a manual adjustment or an app.
The common mistake is the condition. Check only “available is at or below 5” and Flow emails you after every sale until you restock. Shopify’s workflow examples page says to pair the current quantity condition with the prior quantity condition so the alert goes out once, when stock crosses the threshold. In practice:
- Condition 1: the variant’s prior inventory quantity (
inventoryQuantityPrior) is above your threshold. - Condition 2: the current available quantity at your location is at or below your threshold.
- Action: Send internal email to whoever reorders stock.
Two caveats from Shopify’s trigger page. The trigger fires even when Inventory tracked is turned off for a product, so exclude untracked items in your conditions. And to check stock at one location you need the location-specific inventory level fields, so test with a manual inventory adjustment before you trust it.
If you prefer one summary to many emails, Shopify’s Scheduled time templates include a weekly low-stock summary. Scheduled workflows have no product attached, so they need a Get product data action to pull records in.
Flow tells you when to reorder, not how much. For reorder quantities and multi-location stock, see our guide to choosing inventory software.
3. Hide products that sell out, and bring them back
Shopify’s templates include “Hide and republish products based on inventory level,” which hides out-of-stock products and republishes them when at least one variant has inventory again.
The Unpublish product action removes the product from the sales channels you choose in its Publication field. It only works with product and inventory triggers such as Product variant out of stock and Product variant back in stock. Check two things before turning it on:
- Choose the channels on purpose. If you want a sold-out product to stay visible in one channel, for example for a back-in-stock signup, leave that publication out.
- Exclude pre-order and made-to-order items. Use a product tag condition so items you sell without stock are never hidden.
4. Hold high-risk orders for review, before you automate cancellation
Shopify’s Risk templates include “Cancel and restock high-risk orders” and “Capture payment if order is not high fraud risk.” Neither is where we would start.
First, the trigger. Shopify says to use Order risk analyzed, not Order created, because fraud analysis takes time and these workflows should run only after it finishes. The trigger uses Shopify’s own risk analysis only; third-party fraud app results do not start it.
Second, the payment setting. Shopify says the capture workflow does not work if automatic capture is on. With automatic capture, Flow can cancel a high-risk order but cannot stop the payment. To use the capture template you must set card payments to capture manually, which changes how every order is paid.
Third, the cancel template cancels, refunds, restocks, tags the order and customer, and sends an email. Shopify’s trigger page recommends checking orders manually after cancellation, which tells you a high-risk rating is a reason to review, not a verdict.
A safer first version:
- Trigger: Order risk analyzed.
- Condition: the order’s risk level is high.
- Actions: Add order tags (for example
risk-review), Hold fulfillment order, and Send internal email to whoever reviews fraud.
Nothing ships until a person looks. After a few months of tagged orders, you will know whether automatic cancellation is worth it. If a fraudulent order slips through, our guide to what happens when a customer files a chargeback on Shopify covers the next steps.
5. Flag orders that have not shipped on time
Shopify’s Add order tags templates include tagging unfulfilled orders older than two days, run daily.
Build it on the Scheduled time trigger set to repeat daily, add Get order data with a query for unfulfilled orders, loop through them with For each, then tag each one and send yourself a single summary email. Set the age to match your own shipping promise.
Test the date window: scheduled workflows use the store’s time zone by default, and a query off by a day misses late orders or flags fresh ones. If an order goes missing after it ships, our guide to what to do when a customer says their package never arrived picks up from there.
6 and 7. Tag expedited orders and your best customers
- Expedited shipping tag. Shopify’s templates include “Tag orders by shipping method.” Match the names of your express rates and tag those orders so they are packed first.
- Spend-tier customer tags. Shopify’s template “Organize customers by lifetime spend tiers” tags customers by total spend; its getting-started example tags a customer
VIPafter an order over $500. These tags feed segments and email lists.
One warning: Shopify says an order tag Flow reports as added can be overwritten when another app or staff member edits the order afterwards, which is common on Order created. Its suggested fix is a Wait step before tagging. Shopify also notes that tag conditions may not work if an order, product or customer has more than 250 tags.
How much time these workflows can save: a worked model
We modelled a hypothetical store with 600 orders a month: how long each manual check takes today, and how long you would still spend handling alerts once Flow does the checking. All counts and minutes are our assumptions, not data from a real store.
Low-stock alert 12 min daily check x 30 = 360 min 18 alerts x 4 min = 72 min 288 min 30 min 3.1 days
Hide and republish stock-outs 50 hide or republish edits x 3 min = 150 min One 15 min monthly spot check 135 min 30 min 6.7 days
Late unfulfilled order flag 5 min daily check x 30 = 150 min 8 flagged orders x 3 min = 24 min 126 min 30 min 7.1 days
High-risk order hold 600 orders x 15 seconds = 150 min 9 high-risk orders x 6 min = 54 min 96 min 45 min 14.1 days
Spend-tier customer tags 40 customers x 2 min = 80 min None 80 min 30 min 11.2 days
Expedited shipping tag 60 orders x 1 min = 60 min None 60 min 20 min 10.0 days
Total 950 min 165 min 785 min (13.1 hours) 185 min 7.1 days
Hypothetical 600-order store, 30-day month. Payback is setup time divided by minutes saved per day. Calculated with a formula and again with an event-by-event loop in Python; both gave 785 minutes.
Modelled minutes saved per month for each workflow. Assumptions are in the table above.
What the model shows:
- Daily checks are where the time goes. The biggest savings replace a check you do every day whether or not anything changed.
- The fraud workflow saves the least time of the big four, because you still review each flagged order. Its value is fewer missed fraud orders, which this model does not count.
- The error alert saves no time, so it is not in the chart. It protects the time the others save.
- At an assumed $25 an hour for staff time, 13.1 hours is worth about $327 a month. Flow itself has no separate charge on the listed plans, so the main cost is your setup time.
Test every workflow before you turn it on
Flow has a built-in test mode. Open the workflow, click Edit, then Test your workflow at the trigger. Shopify offers three ways to get test data:
- Record events waits for a real event, or one you trigger yourself, such as a real order you place.
- Create events builds a simulated event from existing store data, such as an existing order, without changing anything.
- Generate events asks Sidekick to create two simulated events, usually one that passes the conditions and one that fails.
Shopify says test mode uses real store data but stops at the first action that would change something, so it sends no emails and updates no orders, and test runs do not appear in Recent runs. A test proves your conditions, not delivery, so watch the first few real runs after you turn a workflow on.
Common mistakes with a first Flow setup
- Emailing customers from Send internal email. Its recipient field does not accept variables, so it cannot address each customer. Shopify points to marketing automations instead.
- Reusing data after a Wait. A Wait can last up to 90 days, but Shopify says data from earlier Get, Sum or Count steps is not available afterwards, so fetch it again.
- Expecting code to call other services. The Run code action runs JavaScript for up to 5 seconds, but it cannot make HTTP calls or import modules.
What you should check next
- Confirm your plan is Basic, Grow, Advanced or Plus, then install the workflow error template first.
- Set a low-stock threshold per product type and install the alert with both quantity conditions.
- Check your payment capture setting before you touch any Risk template.
- Write down your shipping promise and set the late-order flag to match it.
- Review Recent runs at least every two weeks, inside the 14-day history window.
Frequently asked questions
Does Shopify Flow cost extra?
Shopify describes Flow as a free app. It is listed for the Basic, Grow, Advanced and Plus plans, so the cost is your Shopify plan, plus any paid app a workflow connects to.
Can Flow send emails to customers?
The Send internal email action is meant for staff, and you cannot use variables in its recipient field. Shopify points to marketing automations for customer emails, such as abandoned checkout and welcome messages.
Can Flow connect to apps outside Shopify?
Yes, through connector apps, and through the Send HTTP request action on Grow, Advanced and Plus. Templates that use an app need its connector installed.
How do I know a workflow actually ran?
Open Apps > Flow > Recent runs, or use More actions > Search Flow runs on an order, product or customer. Runs are kept for 14 days after they complete.
The takeaway
Start with the error alert, then automate the checks you repeat every day: low stock, sold-out products, late orders. Hold high-risk orders for a person before you let Flow cancel anything, and test every workflow before it goes live.
Sources
- Shopify Help Center, “Shopify Flow”. help.shopify.com
- Shopify Help Center, “Getting started with Shopify Flow”. help.shopify.com
- Shopify Help Center, “Workflow examples”. help.shopify.com
- Shopify Help Center, “Creating a workflow”. help.shopify.com
- Shopify Help Center, “Testing a workflow”. help.shopify.com
- Shopify Help Center, “Finding and monitoring workflow runs”. help.shopify.com
- Shopify Help Center, Flow triggers reference: Workflow error occurred, Product variant inventory quantity changed, Order risk analyzed, Scheduled time. help.shopify.com
- Shopify Help Center, Flow actions reference: Send internal email, Add order tags, Unpublish product, Wait, Run code, Send HTTP request. help.shopify.com
- Shopify Help Center, “Using Shopify Flow to protect orders”. help.shopify.com
- Shopify, “Shopify Flow” product page. shopify.com
Last reviewed: October 21, 2026. Plan availability, admin paths, trigger and action behaviour, and limits match Shopify’s documentation as checked on that date.
How this article was made: researched and drafted with AI assistance, with every factual claim checked against the sources above. The 600-order store, its task counts, minutes, setup times and the $25 hourly rate are hypothetical assumptions, and the time savings are modelled, not measured.
Related guides
- You’re overpaying for automation: the 2026 math
- Zapier vs Make vs n8n for online stores
- Chargeback ratio limits: Visa VAMP, Mastercard and Shopify thresholds
- How to analyze your Shopify sales export with ChatGPT or Claude
