- Shopify Flow is Shopify's free automation app, available on the Basic, Grow, Advanced and Plus plans. It only works on Shopify. WooCommerce and Magento stores need other tools.
- For marketing ops, Flow is best at keeping store data clean and current: tagging customers and orders, flagging stock problems on products you advertise, and alerting the right person. Your email and SMS platform should still send the customer-facing messages.
- Build a few workflows well rather than many badly. Use a naming convention for tags and metafields, test every workflow on test orders, and review them on a schedule.
What is Shopify Flow and which plans include it?
Shopify Flow is an automation app built by Shopify. Each workflow has three parts: a trigger (an event in the store), optional conditions (checks on the data) and actions (what happens next). It is a Shopify-only feature.
At the time of writing, Shopify’s Help Center says:
- Flow is free and available on the Basic, Grow, Advanced and Plus plans.
- The Send HTTP request action, which calls outside systems, is limited to the Grow, Advanced and Plus plans.
- Tasks from custom partner apps are available on Plus only.
- Usage limits vary by plan, in line with API rate limits.
Flow also includes a template library, and many installed apps add their own triggers and actions. Shopify updates Flow often, so check the current trigger and action reference before you build.
How does a Shopify Flow workflow work?
A few building blocks cover most marketing ops work.
| Building block | Examples from Shopify’s reference | What it is used for |
|---|---|---|
| Order triggers | Order created, Order paid, Order fulfilled, Order risk analyzed, Refund created | Tag orders and customers, react to risk and refunds |
| Customer triggers | Customer created, Customer tags added, Customer subscribed to email marketing, Customer joined segment | Keep customer data current, start follow-up work |
| Inventory triggers | Product variant out of stock, Product variant back in stock, Product variant inventory quantity changed | Stock alerts, merchandising changes |
| Returns and subscriptions | Return requested, Subscription billing attempt failure | Service and retention follow-up |
| Scheduled time | Runs on a schedule you set | Daily or weekly checks across many records |
| Data actions | Add customer tags, Add order tags, Update customer metafield, Update order note | Write data other tools can read |
| Store actions | Add product to collections, Unpublish product, Hold fulfillment order | Change the store itself |
| Alerts and logic | Send internal email, Wait, Get customer data, For each loop, Run code | Notify staff, delay, process lists, custom logic |
The key idea for marketing teams is that Flow writes data. A tag or metafield written by Flow can be synced to your email service provider, used in Shopify customer segments or read by your ad and analytics tools. Check which Shopify fields your ESP syncs before you rely on one.
Which Shopify Flow automations are worth setting up for marketing ops?
These workflows earn their keep for most stores. Each one either keeps data clean or protects margin.
| Workflow | Trigger | Condition | Action | Why it matters |
|---|---|---|---|---|
| Value tiers | Order paid | Customer amount spent above your tier thresholds | Add or remove customer tags | Segments for VIP offers and exclusions |
| First order source | Order paid | Customer has one order; discount code used | Add customer tag for the code family | Compare discount-acquired cohorts with full-price ones |
| Ad stock alert | Product variant inventory quantity changed | Product tagged as a paid hero; quantity below a set level | Send internal email to the media buyer | Stop spending on ads for items about to sell out |
| Out of stock handling | Product variant out of stock | Product tag or collection | Add product tag; internal email | Feed merchandising and back-in-stock flows |
| Risky orders | Order risk analyzed | Risk level is high | Hold fulfillment order; add order tag; internal email | Avoid shipping fraud that wipes out margin |
| Frequent returners | Return requested | Customer has several prior returns | Add customer tag | Exclude from deep discount campaigns, review service |
| Failed subscription payments | Subscription billing attempt failure | None or by product | Add customer tag; internal email | Trigger recovery messaging before the customer churns |
| Workflow monitoring | Workflow error occurred | None | Send internal email | Catch broken automations quickly |
A few notes on the most useful ones.
Value tiers based on spend and order count
Tagging customers by lifetime spend or order count gives every tool the same definition of a VIP. Use clear tiers and remove the old tag when a customer moves up, so a customer never carries two tiers. For a richer model, compute tiers with RFM analysis in your ESP or data tool and use Flow only to write the result back. Our RFM segmentation guide covers how to define the segments.
Stock alerts tied to paid media
Ads that send traffic to a product about to sell out waste budget. Tag the products your campaigns depend on, and have Flow alert the media buyer when inventory falls below a few days of sales.
Out of stock and back in stock
Flow can tag products or move them between collections when they go out of stock and come back. Be careful with actions that unpublish products. Removing a product page that ranks in search can cost traffic you need later; our guide to out-of-stock products and SEO explains when to keep pages live. The customer-facing waitlist message belongs in your ESP, as covered in our guide to back-in-stock emails.
Risky orders
A workflow on Order risk analyzed can hold fulfillment of high-risk orders and alert your team to review them. Each fraudulent order you ship costs the product, the shipping and often a chargeback fee.
How should you name tags and metafields?
Flow makes it easy to write tags, and other apps write them too. Set rules before you build:
- Prefix by owner. For example,
flow_vip_goldorflow_acq_welcome10. You can tell at a glance which tags Flow owns. - Lowercase, no spaces. Tags are matched as text, and small differences break segments.
- Tags for states, metafields for values. “VIP gold” is a state and fits a tag. “Last return date” or “lifetime returns” is a value and fits a metafield.
- Remove what no longer applies. Every workflow that adds a state tag needs a rule to remove it when the state ends.
- Keep a register. A simple sheet listing each tag, the workflow that writes it, what it means and which tools read it.
Worked example: a value tier workflow step by step
All thresholds below are illustrative. Set yours from your own spend distribution.
The goal is three tiers: silver above $300 lifetime spend, gold above $750, platinum above $1,500.
- Trigger. Order paid. This runs after payment, so unpaid or canceled orders do not promote anyone.
- Condition 1. Customer amount spent is $1,500 or more. If true, add
flow_tier_platinumand removeflow_tier_goldandflow_tier_silver. - Condition 2. If not, check $750 or more. If true, add
flow_tier_goldand removeflow_tier_silver. - Condition 3. If not, check $300 or more. If true, add
flow_tier_silver. - Sync. Confirm the tags appear on the profile in your ESP, then build segments on them.
- Use it. Exclude platinum customers from discount-led campaigns they do not need, and send them early access instead. Suppress tiers from acquisition audiences in paid media so you do not pay to reach customers you already have.
- Test. Place test orders that cross each threshold and confirm the right tag is added and the old one removed. Check in the workflow run log whether the amount spent already includes the order that triggered the run.
Note that this workflow only promotes customers. Customers who stop buying keep their tier until something removes it. A scheduled workflow, or a recency-based segment in your ESP, should handle downgrades. That is also the natural starting point for a win-back campaign.
What should Shopify Flow not be used for?
Flow is strong at store data and operations. It is a poor fit for some jobs:
- Customer-facing marketing sequences. Multi-step email and SMS sequences with content, timing and A/B tests belong in your ESP. Flow can prepare the data they use.
- Heavy analytics. Calculating cohorts, margins or attribution across thousands of orders is a job for your analytics stack. Our ecommerce KPIs guide covers which numbers to track and where.
- Complex integrations without the plan. If a workflow needs to call an outside system with Send HTTP request, check that your plan includes it. For larger API integration projects, a dedicated integration may be more reliable.
- Workflows that can trigger themselves. A workflow that updates a product on the Product updated trigger, for example, can run again on its own change. Add conditions that stop the loop.
Checklist: launching and maintaining Flow workflows
- [ ] Each workflow has a written purpose and an owner.
- [ ] Tags and metafields follow the naming convention and are in the register.
- [ ] Every state tag has a matching removal rule.
- [ ] Plan availability is checked for each action used, including Send HTTP request.
- [ ] The workflow was tested with test orders or test customers before activation.
- [ ] Your ESP shows the tags or metafields the workflow writes.
- [ ] Actions that change the storefront, such as unpublishing products, are reviewed with SEO in mind.
- [ ] A Workflow error occurred alert is active and goes to someone who will act on it.
- [ ] Workflows are reviewed every quarter, and unused ones are turned off.
FAQ
Is Shopify Flow free?
Yes. Shopify lists Flow as free on the Basic, Grow, Advanced and Plus plans. Some actions, such as Send HTTP request, are limited to higher plans, and usage limits vary by plan.
Can Shopify Flow send marketing emails to customers?
Flow’s own core actions focus on store data and internal alerts, such as tags, metafields, notes and internal emails. Some connected apps add their own actions. For most stores, the cleaner setup is to let Flow write the data and let your ESP send the customer-facing email automation, where consent, design and testing are already handled.
Does Shopify Flow work with WooCommerce or Magento?
No. Flow is a Shopify app and only runs on Shopify stores. WooCommerce and Magento stores can build similar automations with platform extensions or a separate automation service, but the triggers and actions will differ.