15 Shopify Flow Examples (Copy These Workflows Today) | MESA Blog

You know automation could save you hours every week. You've opened Shopify Flow, stared at that blank canvas, and thought: "Where do I even start? What's actually possible here?"

Flow's visual builder is powerful, but without concrete examples, it's like having a fully equipped kitchen without any recipes. You can see the ingredients and tools, but you're not sure what you can actually cook.

This guide solves that problem. You're about to see exactly what 15 real Shopify merchants have built with Flow—from simple order tagging that takes 5 minutes to set up, to sophisticated fraud prevention systems that save thousands in chargebacks every month.

What you'll find in this guide

Each example in this guide includes everything you need to build it yourself today:

The examples are organized by category—order management, inventory control, customer engagement, fulfillment operations, and marketing automation—so you can jump straight to the workflows that matter most for your store right now.

How to use this guide

Don't try to implement everything at once. The merchants who see the best results start with just one example addressing their biggest time drain, test it thoroughly over a week, then gradually layer in additional workflows.

Here's the recommended approach:

  1. Scan the categories and identify your biggest operational pain point
  2. Start with a beginner example to build confidence with Flow's interface
  3. Follow the step-by-step setup exactly as written
  4. Test with Flow's preview function using historical order data
  5. Monitor the first 10-20 workflow runs to ensure everything works correctly
  6. Customize the conditions based on your results (adjust dollar thresholds, tag names, etc.)
  7. Add another example next week and repeat the process

By the end of the month, you'll have 4-5 workflows running smoothly, saving you 10+ hours weekly.

What to expect

These are examples you build, not templates you install. While Shopify offers pre-built templates you can install with one click (covered in our Shopify Flow Templates guide), this article shows you what's possible when you build workflows from scratch. This gives you complete control over the logic, conditions, and actions.

You don't need coding skills. Beginner and intermediate examples use Flow's visual interface with dropdowns and simple conditions. Advanced examples may include Liquid code snippets, but we provide copy-paste examples you can use as-is—no programming knowledge required.

Some examples require MESA. Flow is powerful, but it has limitations—no scheduled triggers, no external app connections beyond what has Flow connectors, no historical data queries. Where Flow can't handle an example, we show you exactly how MESA extends those capabilities. You'll always see what's possible with free Flow first, then understand when upgrading to MESA makes sense.

Ready to see what you can build? Let's start with beginner examples that take just minutes to implement.

Beginner examples

Start here if you're new to Shopify Flow. These examples take 5-15 minutes to build, use simple triggers and conditions, and deliver immediate value. No coding required—just follow the step-by-step instructions using Flow's visual interface.

Example 1: Tag high-value orders ⭐

What it does: Automatically tags orders over $500 as "VIP" so your team knows which orders deserve special attention, expedited processing, or personalized thank-you notes.

Business impact:

Step-by-step setup:

  1. Create new workflow in Shopify Flow
  2. Select trigger: Order → Order created
  3. **Add condition:**Check a condition
  1. Add actions(in the "true" path):
  1. Save and turn on the workflow

Customization tips:

Flow vs MESA:

Feature Flow MESA
Basic order tagging ✅ Simple threshold check ✅ Simple threshold check
Email notifications ✅ Plain text only ✅ HTML formatted with order details
Slack/SMS alerts ❌ Internal email only ✅ Slack channels + SMS to manager
CRM updates ❌ Not available ✅ Update Salesforce/HubSpot contact
Dynamic thresholds ❌ Fixed $500 year-round ✅ Adjust by season, product category, region
Customer tier calculation ❌ Manual tag only ✅ Auto-calculate Silver/Gold/Platinum based on LTV
Account assignment ❌ Manual ✅ Assign specific account manager by region/tier

Try this MESA template: Tag customers as VIP after $500 spend

Example 2: Low stock inventory alerts ⭐

What it does: Sends email notification when any product variant drops below 10 units, giving you time to reorder before selling out completely.

Business impact:

Step-by-step setup:

  1. Create new workflow in Shopify Flow
  2. Select trigger: Product → Product variant inventory quantity changed
  3. **Add first condition:**Check a condition
  1. Add second condition(nested under first): Check a condition
  1. Add actions(when both conditions are true):
  1. Save and turn on the workflow

Why the second condition matters:

Without checking "Quantity prior ≥ 10," you'd receive alerts every time inventory decreases:

With the second condition, you only get ONE alert when inventory crosses the threshold from 10 → 9 units. This prevents inbox flooding.

Customization tips:

Flow vs MESA:

Feature Flow MESA
Fixed threshold alerts ✅ Set to specific number (10 units) ✅ Set to specific number
Variable thresholds ⚠️ Requires multiple workflows ✅ Different per product/collection in one workflow
Sales velocity calculation ❌ Not available ✅ Alert based on "days of stock remaining"
Supplier integration ❌ Manual reorder process ✅ Auto-email suppliers with calculated quantities
Seasonal adjustment ❌ Fixed threshold year-round ✅ Increase thresholds Oct-Dec automatically
Multi-location support ⚠️ Separate workflow per location ✅ Consolidated alerts across locations
Reorder task creation ❌ Email only ✅ Create Asana/Clickup tasks with reorder details

Try this MESA template: Send Slack message when Shopify inventory runs low

Example 3: Welcome first-time customers ⭐

What it does: Automatically tags customers on their first purchase and triggers welcome email sequence, creating a positive first impression that drives repeat purchases.

Business impact:

Step-by-step setup:

  1. Create new workflow in Shopify Flow
  2. Select trigger: Order → Order created
  3. **Add condition:**Check a condition
  1. Add actions(when condition is true):
  1. Save and turn on the workflow

Step-by-step setup (without email platform connector):

If your email platform doesn't have a Flow connector, use this approach:

  1. Follow steps 1-4 above (tag customer and order)
  2. In your email platform (Klaviyo, Mailchimp, Omnisend):
    • Create a segment: "Customers with tag: First-Time-Buyer"
    • Set up automated welcome series triggered by this segment
  3. Flow adds the tag → Email platform detects tag → Welcome series sends automatically

Customization tips:

Flow vs MESA:

Feature Flow MESA
First order detection ✅ Simple condition ✅ Simple condition
Customer tagging ✅ Included ✅ Included
Email platform trigger ⚠️ Only if app has Flow connector ✅ Klaviyo, Mailchimp, Omnisend, etc.
Product-based segmentation ⚠️ Requires multiple workflows ✅ Dynamic segmentation in one workflow
Personalized content ⚠️ Limited variables ✅ Include first product purchased, recommendations

Try these MESA templates

Example 4: Tag orders by sales channel ⭐

What it does: Automatically tags every order with its source channel (Instagram, Facebook, Online Store, POS, Amazon, etc.) for clean reporting on which platforms drive the most revenue.

Business impact:

Step-by-step setup:

  1. Create new workflow in Shopify Flow
  2. Select trigger: Order → Order created
  3. Add action(no condition needed):
  1. Save and turn on the workflow

How it works:

Flow's {{ order.sourceName }} variable automatically contains the channel name:

Customization tips:

Flow vs MESA:

Feature Flow MESA
Basic channel tagging ✅ Simple variable insertion ✅ Simple variable insertion
Tag standardization ⚠️ Multiple workflows needed ✅ Mapping rules in one workflow
Channel-specific actions ⚠️ Separate workflows per channel ✅ Conditional logic in one workflow
Analytics integration ❌ Tags only ✅ Push to MixPanel, Google Sheets for dashboard
Historical data ❌ Only tags new orders ✅ Backfill tags for historical orders
Attribution tracking ❌ Channel only ✅ Capture UTM parameters, landing pages

Example 5: Hide out-of-stock products ⭐

What it does: Automatically unpublishes products from your online store the moment inventory hits zero, preventing frustrated shoppers from attempting to buy unavailable items.

Business impact:

Step-by-step setup:

  1. Create new workflow in Shopify Flow
  2. Select trigger: Product → Product variant inventory quantity changed
  3. **Add condition:**Check a condition
  1. Add actions(when condition is true):
  1. Save and turn on the workflow

Important considerations:

Multi-variant products: This workflow unpublishes the ENTIRE product when ANY variant hits zero. If you have a t-shirt with sizes S, M, L, XL and only size M sells out, the entire product becomes hidden.

To handle multi-variant products better, you need more complex logic (see "Advanced tip" below).

Customization tips:

Advanced tip for multi-variant products:

For products with multiple variants, you'd need to:

  1. Count how many variants have quantity > 0
  2. Only unpublish if ALL variants = 0
  3. This requires MESA or advanced Liquid code in Flow

Flow vs MESA:

Feature Flow MESA
Basic unpublishing ✅ When any variant hits zero ✅ When any variant hits zero
Multi-variant handling ❌ Unpublishes entire product ✅ Only unpublish when all variants OOS
Auto-republishing ⚠️ Requires separate workflow ✅ Included in same automation
"Notify when available" ❌ Manual setup ✅ Auto-enable back-in-stock notifications
Alternative recommendations ❌ Not available ✅ Show similar products on hidden product pages
Inventory buffer ❌ Hide only at zero ✅ Hide at 2-3 units (prevent overselling)

Try these MESA templates

You've completed the beginner examples! These five workflows form the foundation of smart store automation. Once you've implemented 2-3 of these and they're running smoothly for a week, you're ready to progress to intermediate examples with more complex logic and app integrations.

Next steps: Choose ONE example from above that addresses your biggest pain point. Build it in the next 15 minutes. Monitor it for a week. Then come back and add another.

Intermediate examples

These examples require understanding conditions, multiple actions, and some business logic. Build time: 20-30 minutes. Best implemented after you're comfortable with beginner workflows and ready for more sophisticated automation.

Example 6: Fraud prevention workflow ⭐⭐

What it does: Automatically detects potentially fraudulent orders using Shopify's risk analysis, holds fulfillment, tags for review, and notifies your fraud team before products ship.

Business impact:

Step-by-step setup:

  1. Create new workflow in Shopify Flow
  2. Select trigger: Order → Order risk analyzed
  3. Add condition group(using OR logic):
  1. Add actions(when any condition is true):

Order: {{ order.name }}

Customer: {{ customer.email }}

Amount: ${{ order.totalPrice }}

Risk: {{ order.risk.level }}

Details: {{ order.risk.message }}

Billing: {{ order.billingAddress.address1 }}

Shipping: {{ order.shippingAddress.address1 }}

Review at: https://{{ shop.domain }}/admin/orders/{{ order.id }} 5. Save and turn on the workflow

Understanding the condition logic:

This workflow flags orders if EITHER:

The OR logic casts a wider net—catching both Shopify's automated risk detection AND suspicious patterns you've identified.

Customization tips:

Flow vs MESA:

Feature Flow MESA
Shopify risk analysis ✅ Uses built-in risk score ✅ Uses built-in risk score
Multiple risk factors ✅ Combine with OR/AND logic ✅ Combine with OR/AND logic
Additional risk signals ❌ Limited to order data ✅ IP geolocation, email verification, velocity checks
Blacklist management ❌ Not available ✅ Check against Google Sheets blacklist
Historical fraud patterns ❌ Can't query past orders ✅ Check customer's previous risk scores
Auto-cancel obvious fraud ⚠️ Possible but risky without confidence scoring ✅ With multi-factor confidence scoring

Try these MESA templates

Example 7: Review request automation ⭐⭐

What it does: Automatically triggers review collection emails through your review platform (Yotpo, Judge.me, Loox) at the optimal time after delivery, with exclusions for unhappy customers.

Business impact:

Step-by-step setup:

  1. Create new workflow in Shopify Flow
  2. Select trigger: Order → Order fulfilled
  3. **Add condition 1:**Check fulfillment status
  1. **Add condition 2 (nested):**Exclude problem customers
  1. **Add action 1:**Wait for time delay
  1. Add action 2:(Depends on your review app)
  1. Save and turn on the workflow

Optimal timing research:

Don't send review requests immediately after fulfillment. Customers need time to receive and use products:

Adjust the "Wait" duration based on your product category.

Customization tips:

Setting up the "Negative-Reviewer" tag workflow:

Create a companion workflow:

This prevents future review requests to customers who've already left negative feedback.

Flow vs MESA:

Feature Flow MESA
Basic review trigger ✅ If app has Flow connector ✅ All major review apps
Timing customization ✅ Fixed wait duration ✅ Dynamic by product type/category
Exclude negative reviewers ⚠️ Requires manual tagging ✅ Automatic exclusion based on past ratings
Personalization ⚠️ Limited variables ✅ Product images, purchase details, names
Delivery confirmation ⚠️ Based on fulfillment only ✅ Wait for actual delivery (tracking integration)
Review rate tracking ❌ Manual ✅ Track conversion by segment

Try these MESA templates

Example 8: B2B wholesale order routing ⭐⭐

What it does: Automatically identifies wholesale/B2B orders and routes them through special handling—dedicated fulfillment, account manager notification, payment terms application, and custom workflows.

Business impact:

Step-by-step setup:

  1. Create new workflow in Shopify Flow
  2. Select trigger: Order → Order created
  3. Add condition group(OR logic):
  1. Add actions(when conditions met):

Company: {{ customer.company.name }}

Contact: {{ customer.firstName }} {{ customer.lastName }}

Order #: {{ order.name }}

Amount: ${{ order.totalPrice }}

Review order: https://{{ shop.domain }}/admin/orders/{{ order.id }}

  1. Save and turn on the workflow

Customization tips:

Flow vs MESA:

Feature Flow MESA
Basic B2B identification ✅ Tag or company detection ✅ Tag or company detection
Account manager routing ⚠️ Static email addresses ✅ Dynamic assignment by territory/tier
ERP integration ❌ Not available ✅ Sync to Odoo, QuickBooks
Payment terms management ⚠️ Note only, manual enforcement ✅ Integrate with accounting system
Pricing verification ❌ Not available ✅ Flag if discount doesn't match tier
Volume discount validation ❌ Manual ✅ Auto-verify quantity breaks applied

Try these MESA templates

Example 9: Rush order expedited handling ⭐⭐

What it does: Automatically detects orders with expedited shipping and prioritizes them through your fulfillment process with immediate notifications and special handling tags.

Business impact:

Step-by-step setup:

  1. Create new workflow in Shopify Flow
  2. Select trigger: Order → Order created
  3. Add condition group(using OR logic):
  1. Add actions(when any condition true):

MUST SHIP TODAY by 3pm for on-time delivery

Delivery promise: [calculate based on method]

Order: {{ order.name }}

Shipping: {{ order.shippingLine.title }}

Customer: {{ customer.firstName }} {{ customer.lastName }}

Destination: {{ order.shippingAddress.city }}, {{ order.shippingAddress.provinceCode }}

Process immediately. 5. Save and turn on the workflow

Advanced setup with SMS (requires MESA):

Add SMS notification to warehouse manager's mobile for immediate awareness:

Customization tips:

Flow vs MESA:

Feature Flow MESA
Shipping method detection ✅ Keyword matching ✅ Keyword matching
Email notifications ✅ Standard alerts ✅ HTML formatted with priority styling
SMS alerts ❌ Not available ✅ Send to warehouse manager mobile
Carrier selection ❌ Manual ✅ Auto-select fastest carrier by destination
SLA monitoring ❌ Not available ✅ Track processing time, escalate if delayed
Priority queue ⚠️ Tag only, manual prioritization ✅ Integrate with 3PL API for queue position
Shipping label creation ❌ Manual ✅ Auto-generate draft labels

Try these MESA templates

Example 10: International order customs preparation ⭐⭐

What it does: Automatically flags international shipments and prepares them for customs documentation, reducing delays and ensuring compliance with destination country requirements.

Business impact:

Step-by-step setup:

  1. Create new workflow in Shopify Flow
  2. Select trigger: Order → Order created
  3. **Add condition:**Check shipping destination
  1. Add actions(when condition true):

Requires customs documentation

Declared value: ${{ order.totalPrice }}

HS codes required: Check products for codes

Restricted items: Verify destination allows all products

Destination: {{ order.shippingAddress.city }}, {{ order.shippingAddress.country }}

Value: ${{ order.totalPrice }}

Items: {{ order.lineItems.size }}

Required documents:

- Commercial invoice

- Customs declaration

- HS codes for all items

Review order: https://{{ shop.domain }}/admin/orders/{{ order.id }} 5. Save and turn on the workflow

Customization tips:

Flow vs MESA:

Feature Flow MESA
International detection ✅ Country comparison ✅ Country comparison
Basic customs flagging ✅ Tag and notify ✅ Tag and notify
HS code lookup ❌ Manual ✅ Auto-populate from product database
Commercial invoice ❌ Manual creation ✅ Auto-generate PDF
Restricted item checking ⚠️ Manual conditions ✅ Database of country restrictions
Duties calculation ❌ Not available ✅ Estimate duties for customer
Courier integration ❌ Manual ✅ Create customs documents via ShipStation/ShipBob
Compliance tracking ❌ Not available ✅ Flag permits needed, track expiration

You've completed the intermediate examples! These five workflows introduce multi-condition logic, app integrations, and more sophisticated business rules. Once you've successfully implemented 2-3 intermediate examples and they're running smoothly, you're ready for advanced workflows requiring external data, scheduled triggers, and complex automation.

Next steps: Choose one intermediate example that solves a current operational challenge. Build it following the step-by-step instructions. Test thoroughly. Monitor for 1-2 weeks. Then add another.

Advanced examples

These examples combine multiple conditions, require external integrations, use scheduled triggers, or implement complex business logic that Flow cannot handle natively. Build time: 45-60 minutes. These workflows require MESA or advanced Flow techniques. Best implemented after mastering beginner and intermediate workflows.

Example 11: Multi-order consolidation ⭐⭐⭐

Why it's advanced: Requires querying order history, comparing timestamps across multiple orders, and coordinating actions on orders that aren't the current trigger.

What it does: Detects when a customer places 2+ orders within 24 hours and automatically holds all orders to ship together in one package, reducing shipping costs and improving the customer experience.

Business impact:

Why Flow can't do this:

Shopify Flow lacks critical capabilities:

MESA implementation:

  1. Trigger: Order created
  2. **Get Order Data action:**Query orders
  1. **Condition:**Check order count
  1. **Loop action:**For each order in results
  1. **Send email:**Notify warehouse

[Loop through orders listing order numbers, items, totals]

Total consolidated value: $[sum of all order totals] 6. **Send email:**Notify customer

Orders included:

[List order numbers]

Expected ship date: [tomorrow's date]

Thank you for helping us reduce our environmental impact!

Setup requirements:

Customization tips:

Advanced features:

Testing strategy:

  1. Create test customer account
  2. Place 2 test orders within minutes
  3. Verify both orders get tagged and held
  4. Check that emails send with correct order details
  5. Confirm warehouse can identify which orders to combine
  6. Test edge cases: 3 orders, orders 23 hours apart, orders with different shipping addresses

Example 12: Win-back campaign trigger ⭐⭐⭐

Why it's advanced: Requires scheduled daily triggers, customer history analysis, date calculations, and email platform API integration.

What it does: Runs daily automated checks to identify customers with no purchase in 90+ days and automatically triggers segmented re-engagement campaigns with escalating offers.

Business impact:

Why Flow can't do this:

Shopify Flow lacks essential capabilities:

MESA implementation:

  1. Schedule Trigger:
    • Frequency: Daily
    • Time: 9:00 AM (adjust to your timezone)
  2. **Get Customer Data action:**Fetch customers with orders
  1. **Transform data:**Calculate days since last order
  1. **Filter condition:**Segment 90-day inactive
  1. **Loop:**For each 90-day inactive customer
  1. Repeat steps 4-5for other segments:
  1. **Send summary report:**Daily digest email

Today's churn segments:

- 90-day: {{ count_90 }} customers tagged

- 120-day: {{ count_120 }} customers tagged

- 180+ day: {{ count_180 }} customers suppressed

Total win-back emails triggered: {{ total_triggered }}

Setup requirements:

Customization tips:

Advanced features:

Expected results:

Testing strategy:

  1. Run initial query to identify current segment sizes
  2. Start with 90-day segment only (test on smaller group)
  3. Monitor email deliverability and engagement rates
  4. Verify customers are properly tagged in Shopify
  5. Check email platform for sequence triggering
  6. After 2 weeks of data, add 120-day segment
  7. After 1 month, add 180+ day suppression

Example 13: Seasonal inventory threshold adjustment ⭐⭐⭐

Why it's advanced: Requires date-based logic, dynamic threshold calculations, and scheduled automation to adjust inventory alerts based on season.

What it does: Automatically increases low-stock alert thresholds during peak seasons (Q4 holiday) and returns them to normal levels during slower periods, preventing stockouts during high demand without carrying excess inventory year-round.

Business impact:

Why Flow can't do this:

Shopify Flow cannot:

MESA implementation:

  1. **Trigger:**Schedule
  1. **Get current date action:**Store today's date
  1. Determine season action: Conditional logic

IF current_date between Oct 1 and Dec 31:

season = "peak" multiplier = 2.5

ELSE IF current_date between Jan 1 and Mar 15:

season = "post-holiday" multiplier = 1.0

ELSE:

season = "standard" multiplier = 1.0 4. **Get Products action:**Fetch all active products

  1. **Loop:**For each product
  1. **Send summary report:**Daily digest

Setup requirements:

Customization tips:

Advanced features:

Example threshold calculations:

Product: Winter Coat

Product: Basic T-Shirt

Testing strategy:

  1. Start with small product subset (10-20 SKUs)
  2. Run manual calculation to verify math is correct
  3. Compare historical peak season stockouts to baseline
  4. Monitor first seasonal transition closely
  5. Adjust multipliers based on actual performance
  6. Expand to full catalog after successful pilot

Example 14: Dynamic promotion activation ⭐⭐⭐

Why it's advanced: Requires scheduled triggers to automatically activate and deactivate workflows, discount codes, or collection visibility at precise times without manual intervention.

What it does: Automatically enables seasonal promotion workflows at scheduled times (Black Friday double points starts Nov 24 at 12:01 AM), runs them for the promotional period, then disables them and cleans up promotional tags when the sale ends.

Business impact:

Why Flow can't do this:

Shopify Flow cannot:

MESA implementation:

Part 1: Promotion Start Automation

  1. **Trigger:**Schedule
  1. **Enable workflow action:**Activate BFCM workflow
  1. **Update collection:**Make sale collection visible
  1. **Activate discount code:**Enable promo code
  1. Send notifications:
    • **Slack:**Post to #marketing channel

Part 2: Promotion End Automation

  1. **Trigger:**Schedule
  1. **Disable workflow action:**Deactivate BFCM workflow
  1. **Update collection:**Hide sale collection
  1. **Deactivate discount code:**Disable promo code
  1. Clean up promotional tags:
    • Get all orders with tag "BFCM-2026"
    • Loop through orders
    • Remove tag: "BFCM-2026"
    • Add tag: "BFCM-2026-Ended" (for historical tracking)
  2. Send notifications:
    • **Slack:**Post to #marketing

Setup requirements:

Customization tips:

Advanced features:

Testing strategy:

  1. Test in staging environment:
    • Schedule test promotion for tomorrow at 1:00 PM
    • Verify all actions execute correctly
    • Confirm notifications send
    • Check workflow enables/disables properly
  2. Dry run before live promotion:
    • Schedule "test activation" 1 week before actual promotion
    • Execute all steps but with test workflows/collections
    • Verify timing is correct
    • Confirm team receives notifications
  3. Monitor first live promotion closely:
    • Have team member awake at activation time
    • Verify promotion started correctly
    • Check customer-facing elements (collection visible, code works)
    • Document any issues for next promotion

Example 15: Intelligent fulfillment routing ⭐⭐⭐

Why it's advanced: Requires querying multiple data sources (inventory at multiple locations, shipping zones, carrier performance), complex decision trees based on product availability and delivery promises, and integration with fulfillment systems.

What it does: Automatically analyzes each order and intelligently routes it to the optimal fulfillment location based on inventory availability, customer proximity, carrier performance, product type, and delivery speed requirements—minimizing shipping costs while maximizing delivery speed.

Business impact:

Why Flow can't do this:

Shopify Flow cannot:

MESA implementation:

  1. Trigger: Order created
  2. **Get inventory data:**Check all locations
  1. Calculate fulfillment options:

For each location:

- Check if has all items in stock

- Calculate shipping zone to customer

- Look up carrier performance to destination

- Check location-specific constraints

  1. Decision tree - Location selection:

Priority 1: Inventory availability

IF only one location has full inventory:

→ Route to that location

→ Skip further logic

IF multiple locations have full inventory:

→ Continue to Priority 2

IF no location has full inventory:

→ Tag "Split-Shipment-Required"

→ Route each item to nearest location with stock

→ Notify customer of multiple shipments

Priority 2: Shipping speed requirements

IF order has expedited shipping:

→ Route to location closest to customer

→ Select fastest carrier to zone

IF order is standard shipping:

→ Continue to Priority 3

Priority 3: Cost optimization

Calculate shipping cost from each location:

LA to customer: $8.50 (Zone 6)

Chicago to customer: $6.25 (Zone 4)

NJ to customer: $5.75 (Zone 3)

Route to location with lowest shipping cost

Priority 4: Inventory balancing

IF multiple locations have equal shipping cost:

→ Check inventory levels

→ Route to location with highest stock levels

→ Goal: Prevent any one warehouse from running out

  1. Select optimal carrier:

For destination zone:

- Check carrier on-time performance (last 30 days)

- UPS: 96% on-time

- FedEx: 94% on-time

- USPS: 89% on-time

IF expedited shipping:

→ Select carrier with best performance

IF standard shipping:

→ Select carrier with best cost/performance ratio

  1. Apply routing actions:
    • **Action 1:**Assign fulfillment location

Reason: {{ routing_reason }}

Carrier: {{ carrier_name }} ({{ on_time_percentage }}% on-time)

Shipping cost: ${{ shipping_cost }}

Expected delivery: {{ estimated_delivery_date }}

  1. Handle split shipments (if needed):

IF no single location has full inventory:

- Split order by item

- Route each item to nearest location with stock

- Tag order: "Split-Shipment"

- Email customer: Explain multiple packages

- Coordinate timing for simultaneous delivery where possible

  1. Track routing performance:
    • Log decision to Google Sheets
    • Columns: Order, Location, Carrier, Shipping Cost, Zone, Delivery Time
    • Monthly analysis: Optimize routing logic based on performance data

Setup requirements:

Customization tips:

Advanced features:

Check sales velocity at each location:

- LA: Fast-moving inventory running low

- Chicago: High stock levels

Route orders to Chicago to preserve LA inventory

Gives time to restock LA before it sells out

Example routing scenarios:

Scenario 1: Standard order, multiple options

Scenario 2: Rush order

Scenario 3: Split shipment required

Testing strategy:

  1. Start with test location subset:
    • Test routing between 2 locations first
    • Verify inventory checks work correctly
    • Confirm assignments update in Shopify
  2. Test each priority tier:
    • Create test orders that hit each routing rule
    • Verify Priority 1 (inventory) works
    • Test Priority 2 (speed) overrides cost when needed
    • Confirm Priority 3 (cost) works for standard orders
  3. Edge case testing:
    • Out of stock everywhere → What happens?
    • Split shipments → Are costs still optimized?
    • Same-day cutoff → Does it route correctly by time?
  4. Monitor first 50 routed orders:
    • Track actual delivery times vs estimates
    • Verify shipping costs align with projections
    • Check warehouse feedback on routing decisions
    • Adjust logic based on real-world results
  5. A/B test routing logic:
    • Route 50% of orders using intelligent routing
    • Route 50% using existing logic (control group)
    • Compare: Costs, delivery times, customer satisfaction
    • Full rollout after proving ROI

Expected results:

You've completed the advanced examples! These five workflows represent the cutting edge of ecommerce automation—multi-order logic, scheduled customer analysis, dynamic inventory management, and time-based promotion control. These examples require MESA's advanced capabilities but deliver exponential returns in time savings and operational efficiency.

Important reminder: Don't attempt advanced workflows until you've successfully implemented several beginner and intermediate examples. Build your automation confidence incrementally.

Implementation best practices

Building workflows is exciting, but the merchants who see lasting success follow a methodical approach. Here's how to implement these examples without overwhelming yourself or your team.

Start small, scale strategically

The biggest mistake is trying to automate everything in the first week. Instead, build momentum with this proven progression:

Week 1: Your foundation workflow

Week 2-3: Build confidence

Month 2: Layer in complexity

Month 3+: Advanced automation

By month 3, you'll have 8-12 workflows running smoothly, saving 15+ hours weekly without ever feeling overwhelmed.

Testing workflow examples before going live

Flow has no sandbox environment—every workflow runs on live data. This makes testing critical.

Pre-activation testing:

1. Use Flow's Preview function

2. Verify all connections

3. Start workflows paused

Post-activation monitoring:

First 10 runs are critical:

Testing checklist (complete before activating):

Avoiding common mistakes

Mistake #1: Automation overload

Problem: Implementing 15 workflows in one week creates chaos and makes troubleshooting impossible.

Solution: Add maximum 2 workflows per week. Give each workflow 5-7 days to prove itself before adding another.

Mistake #2: Skipping the testing phase

Problem: Workflow accidentally sends 500 customer emails with wrong discount code or tags every order incorrectly.

Solution: Always use Preview function. Always monitor first 10-20 runs. Always start with harmless actions (add internal tags) before customer-facing actions (send emails).

Mistake #3: Set-it-and-forget-it syndrome

Problem: Seasonal Black Friday workflow still running in March, or workflow silently failing for 2 weeks unnoticed.

Solution: Monthly workflow audit (15 minutes). Review which workflows haven't triggered in 30 days. Check error rates. Disable seasonal workflows when out of season. Update notification recipients as team members change.

Mistake #4: Notification fatigue

Problem: Sales team receives 50+ Slack messages daily from various workflows and starts ignoring all automation alerts.

Solution: Consolidate similar notifications into daily digests. Use priority-based routing (only alert manager for orders >$1,000). Audit notification volume monthly—if your team ignores alerts, you've over-automated.

Mistake #5: Building when templates exist

Problem: Spending 2 hours building custom logic that MESA template solves in 5 minutes.

Solution: Before building complex workflows, check MESA's template library. Many advanced examples already exist as one-click templates. Save custom building for truly unique business logic.

When to upgrade from Flow to MESA

Flow handles 70-80% of common automation needs. Consider MESA when you need:

External integrations: CRM ( Salesforce, HubSpot), productivity tools ( Google Sheets, Airtable, Slack), email platforms without Flow connectors

Scheduled workflows: Daily inventory audits, weekly customer segmentation updates, monthly report generation

Historical data queries: "Find all customers with no purchase in 90+ days," "Identify products with zero sales this month"

Advanced logic: Complex calculations, conditional aggregation (sum only items over $50), multi-step data transformations

Decision framework: If you're spending 2+ hours trying to make Flow do something, check if MESA handles it natively. If a MESA template exists, the monthly subscription pays for itself in saved time.

See the full feature-by-feature breakdown on our MESA vs Shopify Flow comparison page.

The next section covers additional resources to support your automation journey.

Additional resources

Building automation is a journey, not a destination. These resources will help you continue learning and get support when you need it.

Related guides

Deepen your Flow knowledge:

MESA template library

Don't want to build workflows from scratch? Browse 500+ pre-built MESA templates that handle complex automation with one-click installation:

Each template includes setup instructions, required apps, and customization guidance.

Get expert help

Automation shouldn't feel overwhelming. MESA's team is here to help:

Got questions about a specific example? Reach out via chat or email—we help with both Flow and MESA workflows.

Frequently asked questions

What's the difference between Shopify Flow examples and templates?

Examples are workflow ideas you build yourself following step-by-step instructions. Templates are pre-built workflows from Shopify you install with one click. Examples give you more customization control; templates are faster to deploy. Most merchants use both: install templates for common tasks, build examples for unique business needs.

Do I need coding skills to build these Flow examples?

No coding required for beginner and most intermediate examples. Advanced examples may use Liquid code (Shopify's templating language), but we provide copy-paste snippets you can use as-is. If you can follow step-by-step instructions, you can build these workflows. For complex custom logic, consider using MESA templates instead of coding yourself.

How long does it take to build an example workflow?

Beginner examples: 5-15 minutes | Intermediate examples: 20-30 minutes | Advanced examples: 45-60 minutes. This includes setup, testing, and customization. Your second workflow takes half the time as your first because you understand Flow's interface. Most merchants build 1-2 examples per week rather than rushing through everything at once.

Can I use these examples on Shopify Basic plan?

Yes, Shopify Flow is available on all Shopify plans (Basic, Shopify, Advanced, Plus). All examples work on every plan except those specifically noted as "Shopify Plus only." B2B-specific examples require Plus because they use company accounts. Advanced examples requiring MESA work on any Shopify plan with a MESA subscription.

What if an example doesn't work for my store?

Common reasons: missing app integrations, incorrect condition operators, typos in tag names, or the example needs customization for your business model. Check our troubleshooting steps in each example. If stuck, reach out to MESA support - we help with both Flow and MESA workflows.

How do I know if I need Flow or MESA for an example?

Use Flow when: workflow stays in Shopify, simple logic, no external apps, budget is tight. Use MESA when: need CRM/Google Sheets/Slack connections, scheduled workflows, complex calculations, or testing environment. Many merchants use both - Flow for simple automation, MESA for advanced needs.

Can I modify these examples for my business?

Absolutely! These examples are starting points meant for customization. Adjust dollar thresholds, change tag names, modify notification recipients, add additional conditions, or combine multiple examples. The "Customization tips" section in each example shows common modifications. Document your changes so you remember what you customized.

Will these examples work with my existing workflows?

Most examples work alongside existing workflows without conflicts. Potential issues: multiple workflows trying to set different tags on the same trigger, or duplicate notifications. Review existing workflows before adding new ones. Use clear naming conventions to track which workflows serve which purposes.

Conclusion

You now have 15 proven workflow examples with step-by-step instructions for automating every major aspect of your store—order management, inventory control, fraud prevention, customer engagement, fulfillment operations, and marketing campaigns. Each example includes the exact triggers, conditions, and actions you need to build it yourself today.

But here's what matters more than having all these examples: actually implementing them.

The difference between stores that successfully automate and those that don't isn't knowledge—it's execution. Don't bookmark this guide planning to "come back to it later." Don't try to implement everything at once. And definitely don't let perfect be the enemy of good enough.

The merchants seeing 15+ hours saved weekly all followed the same pattern:

  1. Week 1: Choose ONE beginner example (low stock alerts or VIP tagging)
  2. Week 2-3: Add 2 more simple workflows, monitor results closely
  3. Month 2: Layer in intermediate examples (fraud prevention, review automation)
  4. Month 3+: Explore advanced workflows (consolidation, win-back campaigns, scheduled tasks)

This incremental approach builds your automation confidence while delivering measurable results at each stage. You're not just saving time—you're learning how automation actually works in your specific business context.

Your next steps right now:

  1. Scroll back to the category matching your biggest operational pain point
  2. Choose ONE beginner example that would save you the most time
  3. Open Shopify Flow in your admin
  4. Follow the step-by-step setup instructions exactly as written
  5. Test with Flow's Preview function using 3-5 historical records
  6. Monitor the first 20 workflow runs over the next week
  7. Add another example next week and repeat

Need workflows that Flow can't handle—external integrations, scheduled automation, complex data transformations, or a testing environment? Browse MESA's template library for pre-built workflows that extend beyond Flow's native capabilities.

Stop reading. Start automating. Pick your first example and build it in the next 15 minutes. Every workflow you activate is time you're giving back to yourself. Your future self will thank you.

What to do next…

The fastest way to automate anything is to start with a single task.

  1. 1Try MESA free — 7-day free trial included
  2. 2Start from a template — pre-built workflows for the most common tasks
  3. 3Describe your workflow — let our AI assistant build it for you

Written by

Ryan O'Donnell

Designing Shopify apps and digital commerce experiences for brands worldwide since 2012.

MESA AI assistant

+×

Describe your task...

You've known what your store should be doing. Now it can. Describe the task then MESA handles it from there.