What Shopify Flow Actually Does (and Why Most Stores Underuse It)
Shopify Flow is a visual automation builder available on Shopify Basic plans and above. It lets merchants create custom workflows using a simple three-part structure: trigger, condition, and action. No code. No third-party app subscription. No developer required.
That structure sounds basic. It is not. The combinatorial power of triggers, conditions, and actions lets you automate workflows that would otherwise require a virtual assistant, a spreadsheet, and several hours per week.
Most Shopify stores either do not know Flow exists or set up one or two workflows and stop. Meanwhile, high-performing stores run 10-20+ active workflows that collectively eliminate hours of manual operations every week.
These shopify flow automation examples cover 15 specific workflows across five categories. Each includes the exact trigger, condition, and action configuration so you can build it in minutes.
For merchants looking at automation more broadly — including email and marketing flows — our automation resource hub covers the full landscape.
How Shopify Flow Works: Triggers, Conditions, and Actions
Before diving into specific workflows, understanding Flow's architecture makes every example easier to implement.
Triggers
Triggers are events that initiate a workflow. Shopify provides built-in triggers for orders (created, paid, fulfilled, cancelled, refunded), customers (created, updated, deleted), products (added, updated, inventory changed), draft orders, and fulfillments.
Third-party apps can also register custom triggers. Tools like Mesa and Alloy Automation extend Flow's trigger library to include events from external platforms — reviews submitted in Judge.me, support tickets in Gorgias, subscribers added in Klaviyo.
Conditions
Conditions act as filters using AND/OR logic. Examples:
- Order total is greater than $150 AND shipping country is United States
- Customer has tag "wholesale" OR customer total spent is greater than $5,000
Actions
Built-in actions include adding/removing tags, sending HTTP requests (webhooks), sending internal emails, creating draft orders, hiding/publishing products on sales channels, updating metafields, and introducing wait delays.
The wait action is particularly powerful. It lets you build multi-step sequences — tag a customer now, wait 30 days, check if they have ordered again, then take a different action based on the result.
Now, onto the 15 workflows.
Customer Management Workflows (1-4)

Customer segmentation and tagging are foundational. Every personalized marketing campaign, every loyalty program, and every VIP experience depends on clean, accurate customer tags. These workflows keep your customer data organized without manual intervention.
Workflow 1: Auto-Tag Customers by Spend Tier
This is the single most valuable Flow workflow for most stores. It segments customers into spend tiers automatically, which powers everything from email personalization to ad audiences.
| Component | Configuration |
|---|---|
| Trigger | Order paid |
| Condition 1 | Customer total spent is greater than $500 |
| Action 1 | Add customer tag "VIP-Gold" |
| Condition 2 | Customer total spent is greater than $200 AND less than or equal to $500 |
| Action 2 | Add customer tag "VIP-Silver" |
| Condition 3 | Customer total spent is less than or equal to $200 |
| Action 3 | Add customer tag "Standard" |
Why it matters: Once customers carry spend-tier tags, you can build segmented email flows in Klaviyo or Omnisend, create exclusive discount codes for VIP tiers, and exclude low-value customers from expensive retention campaigns. Stores that segment by spend tier see 15-25% higher email revenue per send, according to Klaviyo's 2025 benchmark report.
Pro tip: Add a "Remove tag" action before each "Add tag" action to prevent customers from accumulating stale tier tags. When a Silver customer crosses the $500 threshold, you want them tagged Gold only — not Gold and Silver.
Workflow 2: Tag First-Time Buyers
First-time buyers need different messaging than repeat customers. A welcome discount, onboarding sequence, or product education campaign only makes sense for new customers.
| Component | Configuration |
|---|---|
| Trigger | Order paid |
| Condition | Customer orders count is equal to 1 |
| Action | Add customer tag "First-Purchase" |
After a customer's second purchase, you can run a complementary workflow that removes the "First-Purchase" tag and adds "Repeat-Customer." This two-workflow pairing gives you clean segments for both acquisition-focused and retention-focused campaigns.
Workflow 3: Segment Customers by Product Type Purchased
When you sell across multiple product categories, knowing which category a customer prefers changes everything about how you market to them.
| Component | Configuration |
|---|---|
| Trigger | Order paid |
| Condition | Order line items product type contains "Skincare" |
| Action | Add customer tag "Interest-Skincare" |
Duplicate this workflow for each major product category in your store. A customer who buys skincare products should receive skincare-focused emails, not footwear promotions. This granular tagging feeds directly into business strategy decisions around product development and inventory allocation.
Workflow 4: Flag Customers Who Have Not Ordered in 90 Days
Win-back campaigns work. But only if you identify lapsed customers before they disappear permanently.
| Component | Configuration |
|---|---|
| Trigger | Order paid |
| Action 1 | Wait 90 days |
| Condition | Customer orders count has not changed since the workflow started |
| Action 2 | Add customer tag "At-Risk-Lapsed" |
This workflow fires on every paid order, waits 90 days, then checks if the customer has placed another order in that window. If not, they get tagged for a win-back sequence. You can adjust the wait period based on your average repurchase cycle — 60 days for consumables, 120 days for apparel, 180 days for high-ticket items.
Inventory Management Workflows (5-7)
Inventory issues are silent revenue killers. An out-of-stock product showing on your storefront frustrates customers. A slow-moving product tying up cash goes unnoticed until the quarterly review. These workflows put inventory management on autopilot.
Workflow 5: Low-Stock Alerts via Email and Slack
Running out of a best-seller without warning is avoidable. This workflow notifies your team the moment inventory drops below a threshold.
| Component | Configuration |
|---|---|
| Trigger | Inventory quantity changed |
| Condition | Product inventory quantity is less than or equal to 10 |
| Action 1 | Send internal email to purchasing@yourstore.com with subject "Low Stock Alert: [Product Title]" |
| Action 2 | Send HTTP request to Slack webhook URL with product details |
Set the threshold based on your lead time. If your supplier takes 14 days to restock and you sell 2 units per day, your alert threshold should be at least 28 units — not 10. Adjust the condition accordingly.
For stores tracking inventory performance at a deeper level, analytics and data tools can surface sell-through rates and reorder timing recommendations.
Workflow 6: Auto-Hide Out-of-Stock Products
Nothing tanks conversion rates like a customer landing on a product page, selecting their size, and seeing "Out of Stock." This workflow removes that friction entirely.
| Component | Configuration |
|---|---|
| Trigger | Inventory quantity changed |
| Condition | Product inventory quantity is less than or equal to 0 |
| Action | Hide product from Online Store sales channel |
Pair this with Workflow 7 below to automatically republish when inventory is restocked. The two workflows together mean your storefront always reflects actual availability — no manual catalog management needed.
Important caveat: If you run Google Shopping or Facebook Catalog ads, hiding a product from the Online Store channel may also remove it from those feeds. Test this with a single product before applying store-wide.
Workflow 7: Auto-Republish When Restocked
The companion to Workflow 6. When inventory comes back in, the product should immediately go live again.
| Component | Configuration |
|---|---|
| Trigger | Inventory quantity changed |
| Condition | Product inventory quantity is greater than 0 AND product status is "Active" |
| Action | Publish product to Online Store sales channel |
Adding the "product status is Active" condition prevents draft or archived products from accidentally going live when someone adjusts inventory during receiving.
Order Management Workflows (8-10)

Orders are where revenue happens. Mishandling a high-value order, missing a fraud signal, or fumbling a gift purchase erodes trust and costs money. These workflows add guardrails.
Workflow 8: Flag High-Risk Orders for Manual Review
Shopify's built-in fraud analysis catches obvious issues. But nuanced fraud patterns — like a new customer placing a large order with expedited shipping to an address that does not match the billing — require human review.
| Component | Configuration | --- | --- | Trigger | Order created | Condition 1 | Order risk level is "High" | Action 1 | Add order tag "Review-Fraud" | Action 2 | Send internal email to fraud@yourstore.com with order details | Action 3 | Add order note "HIGH RISK — Manual review required before fulfillment" | ||||||
| Component | Configuration (Extended) | --- | --- | Condition 2 (Alternative) | Order total is greater than $500 AND customer orders count is equal to 1 | Action | Add order tag "Review-HighValue-NewCustomer" |
The second condition catches orders that Shopify's risk engine might rate as "Medium" but that still warrant a human look. A brand-new customer dropping $500+ on their first order is not necessarily fraud — but it deserves a quick verification before fulfillment.
According to Shopify's fraud protection documentation, merchants who review flagged orders before fulfillment reduce chargebacks by up to 50%.
Workflow 9: Auto-Tag VIP Orders for Priority Fulfillment
Your best customers should get the best experience. This workflow ensures VIP orders are visually flagged in the admin so your fulfillment team prioritizes them.
| Component | Configuration |
|---|---|
| Trigger | Order created |
| Condition | Customer has tag "VIP-Gold" (from Workflow 1) |
| Action 1 | Add order tag "Priority-Fulfillment" |
| Action 2 | Add order note "VIP CUSTOMER — Ship same day if possible" |
If you use a 3PL, the order tag can trigger priority handling on their end as well. Most 3PLs can filter by order tags and apply different service levels based on the tag.
Workflow 10: Gift Order Handling
Gift orders need different treatment — no receipt with pricing in the package, a gift message included, and possibly gift wrapping. This workflow routes them correctly.
| Component | Configuration |
|---|---|
| Trigger | Order created |
| Condition | Order note contains "gift" OR order has gift card line items |
| Action 1 | Add order tag "Gift-Order" |
| Action 2 | Send internal email to fulfillment team "Gift order — exclude pricing, include gift message" |
For stores processing high gift-order volume (seasonal retailers, food and beverage brands), this workflow eliminates the manual scanning of orders for gift instructions. Your fulfillment team filters by the "Gift-Order" tag and knows exactly how to handle each package.
Marketing and Loyalty Workflows (11-13)
Marketing automation and Shopify Flow work as a team. Flow handles the tagging and segmentation; your email or SMS platform handles the messaging. These workflows create the data foundation that makes personalized marketing possible.
Workflow 11: Tag Customers for Win-Back Campaigns
This builds on Workflow 4 but adds a marketing-specific layer. Instead of just flagging lapsed customers, this workflow pushes them into your email platform's win-back flow.
| Component | Configuration |
|---|---|
| Trigger | Order paid |
| Action 1 | Wait 60 days |
| Condition | Customer orders count has not increased |
| Action 2 | Add customer tag "Winback-Eligible" |
| Action 3 | Send HTTP request to Klaviyo/Omnisend API to add customer to "Win-Back" list |
The HTTP request action is what makes this powerful. Rather than waiting for your email platform to sync tags (which can take up to 24 hours), you push the customer directly into a win-back list via API. The win-back email fires immediately, not a day later when the tag finally syncs.
For detailed tracking on how these win-back flows perform, Littledata provides server-side analytics that tie Flow-triggered campaigns to actual revenue attribution — solving the data gap that browser-based tracking often misses.
Workflow 12: Review Request Triggers
Post-purchase review requests convert at 5-15% when timed correctly. Too early and the customer has not used the product. Too late and the purchase excitement has faded.
| Component | Configuration |
|---|---|
| Trigger | Fulfillment created |
| Action 1 | Wait 14 days |
| Action 2 | Add customer tag "Request-Review" |
| Action 3 | Send HTTP request to review app (Judge.me, Stamped, etc.) API |
The 14-day wait starts from fulfillment, not from order creation. That distinction matters — it accounts for shipping time and gives the customer enough days with the product to form an opinion.
Adjust the delay by product type. Skincare products might need 21-30 days before a customer can speak to results. Electronics might only need 7 days. Create separate workflows for different product categories with appropriate wait times.
Workflow 13: Birthday and Anniversary Data Collection Trigger
Collecting customer birthdays for promotional campaigns is effective — birthday emails see 3x higher transaction rates than standard promotional emails. This workflow helps build that data.
| Component | Configuration |
|---|---|
| Trigger | Customer created |
| Condition | Customer birthday metafield is empty |
| Action 1 | Wait 7 days |
| Action 2 | Add customer tag "Request-Birthday" |
The tag triggers a targeted email (via your email platform) asking the customer to share their birthday in exchange for a special offer. The 7-day wait ensures you are not bombarding a new customer with data requests before they have even received their first order.
Once collected, the birthday data stored in a customer metafield can trigger an annual workflow: customer birthday metafield equals today's date sends a birthday discount automatically. Merchants building these kinds of personalized experiences are investing in long-term business strategy that compounds customer lifetime value.
Operations and Team Workflows (14-15)

Flow is not just for customer-facing automation. Internal operations — team notifications, vendor management, product publishing — benefit equally from removing manual steps.
Workflow 14: Auto-Publish Products and Notify the Team on Returns
These are two workflows that solve two common operational headaches.
Auto-Publish New Products on a Schedule:
| Component | Configuration |
|---|---|
| Trigger | Product added |
| Condition | Product tag contains "Scheduled-Launch" |
| Action 1 | Wait (set duration based on launch date) |
| Action 2 | Publish product to Online Store |
| Action 3 | Publish product to Google and Facebook channels |
| Action 4 | Send Slack notification "Product [Title] is now live" |
Notify Team on Returns:
| Component | Configuration |
|---|---|
| Trigger | Refund created |
| Condition | Refund amount is greater than $100 |
| Action 1 | Send internal email to returns@yourstore.com |
| Action 2 | Add order tag "High-Value-Return" |
| Action 3 | Send HTTP request to Slack with order and refund details |
Filtering returns above a dollar threshold prevents notification fatigue. Your team does not need an alert for every $15 return — but a $300+ return warrants immediate attention for quality investigation and customer recovery outreach.
For stores with custom Shopify development workflows, these notifications can also trigger webhook-based processes in external systems like inventory management or ERP platforms.
Workflow 15: Vendor Performance Tracking
Multi-vendor stores need visibility into which vendors generate issues. This workflow automatically tracks vendor-specific problems.
| Component | Configuration |
|---|---|
| Trigger | Refund created |
| Condition | Refund reason contains "defective" OR "damaged" OR "quality" |
| Action 1 | Add order tag with vendor name "Vendor-Issue-[VendorName]" |
| Action 2 | Send HTTP request to Google Sheets API (log vendor, product, refund reason, amount) |
| Action 3 | Send email to vendor-relations@yourstore.com |
Over time, the order tags and Google Sheets log create a vendor quality scorecard. When it is time for vendor negotiations or lineup decisions, you have data — not anecdotes.
Extending this with third-party tools: Alloy Automation can bridge Shopify Flow with Airtable, Notion, or project management tools, turning this basic tracking workflow into a full vendor management system.
Building Workflows That Scale: Best Practices
Setting up 15 workflows is straightforward. Keeping them running reliably as your store grows requires discipline.
Name workflows descriptively. "Customer Tag - VIP Gold Tier" is infinitely more useful than "Workflow 3" when you are troubleshooting six months from now. Include the category and function in every workflow name.
Test with a single product or order first. Before activating a workflow store-wide, create a test order and verify the tags, notifications, and actions fire correctly. Flow's "Run history" tab shows exactly what happened at each step — use it.
Audit workflows quarterly. Business rules change. Your VIP threshold might need to move from $500 to $750 as your average order value grows. Your low-stock alert threshold might need to decrease as you optimize inventory turns. Schedule a quarterly review of all active workflows.
Avoid circular triggers. A workflow that updates a product can trigger another workflow that listens for product updates, which could trigger the first workflow again. Flow has some built-in protections against infinite loops, but poorly designed workflows can still create rapid-fire cascading actions. Map your triggers before building.
Use tags consistently. Establish a naming convention for tags — "VIP-Gold" not "vip gold" or "VIP_GOLD." Inconsistent tagging makes segmentation unreliable and creates phantom segments that look full but contain duplicates.
| Best Practice | Why It Matters |
|---|---|
| Descriptive naming | Faster debugging and team onboarding |
| Test before activating | Prevents unintended actions on real orders |
| Quarterly audits | Keeps thresholds aligned with business changes |
| Avoid circular triggers | Prevents infinite loops and API overload |
| Consistent tag format | Ensures clean segmentation downstream |
When Shopify Flow Is Not Enough: Extending with Third-Party Tools

Flow covers 80% of automation needs for most stores. The remaining 20% — complex multi-step workflows, cross-platform integrations, conditional branching with external data — requires additional tooling.
Mesa** extends Flow with 100+ integrations, scheduled workflows (run every Monday at 9am), and data transformations that Flow alone cannot handle.
Alloy Automation** provides an enterprise-grade workflow builder connecting Shopify with 200+ apps — particularly strong for syncing data between Shopify, your CRM, warehouse management, and accounting software in a single workflow.
Littledata** solves the analytics gap that Flow creates. When Flow triggers actions affecting marketing campaigns, Littledata ensures downstream revenue attribution is accurate — connecting server-side events to Google Analytics and ad platforms.
Start with native Shopify Flow, identify gaps after 30-60 days, and then layer in a third-party tool for workflows that Flow cannot handle natively.
Our Shopify experts network includes automation specialists who can audit your current workflows and recommend where native Flow ends and third-party tools begin.
Start With Five, Scale to Fifteen
You do not need to build all 15 workflows in a single afternoon. That path leads to errors, untested logic, and notification fatigue from Slack messages you forgot to throttle.
Start with the five highest-impact workflows:
- Workflow 1 — Auto-tag customers by spend tier (powers all downstream segmentation)
- Workflow 2 — Tag first-time buyers (enables welcome-specific marketing)
- Workflow 5 — Low-stock alerts (prevents revenue loss from stockouts)
- Workflow 6 — Auto-hide out-of-stock products (improves storefront experience)
- Workflow 8 — Flag high-risk orders (reduces chargebacks)
These five workflows take 30-45 minutes to build and immediately start saving time. Once they are running reliably for two weeks, add the marketing workflows (11-13). Then layer in the operations workflows (14-15) as your team gets comfortable with Flow's interface.
Every hour you spend building a Flow workflow saves 10-50+ hours over the following year. That compounding effect is why automation is not optional for stores that want to scale without proportionally scaling headcount.
Join the Talk Shop community to share your workflow configurations, get feedback from other merchants, and discover new automation patterns that are working right now. If you want hands-on help building or auditing your Shopify Flow setup, connect with a Shopify automation expert who can accelerate the process.

About Talk Shop
The Talk Shop team — insights from our community of Shopify developers, merchants, and experts.
Related Insights
The ecommerce newsletter that's actually useful.
Daily trends, teardowns, and tactics from the top 1% of ecommerce brands. Delivered every morning.
