Shopify automation

Shopify Flow Workflow Library

Twelve Shopify Flow workflows you can import today. We ran each one in a Shopify development store, recorded the results, and wrote down what you need to change before it touches your own orders, customers, or catalog.

Updated November 20, 2026 13-minute read Aesymmetric Blog
Shopify Flow workflow library with twelve tested workflows

Most Shopify Flow lists give you a diagram. You find out whether it works when a real order arrives.

Here you get the workflow file. Every download is a .flow file exported by Shopify Flow after we ran it against test orders and inventory changes in a development store. Each entry lists the cases that passed, the cases we could not run, and the settings you must replace.

Still choosing what to automate? Start with our 25 Shopify Flow examples, then come back here for the build.

12 tested workflows 12 Shopify Flow exports Run evidence for every file

How we tested

Where: A Shopify development store on the Basic plan with one location, Shopify Payments in test mode, and B2B companies turned on. Tests ran between November 12 and November 19, 2026.

How: We turned each workflow on, created real test events (draft orders marked as paid, checkout orders with test cards, inventory changes, scheduled runs, B2B payment terms), and read the result from Shopify Flow’s run details. No .flow file was written by hand.

What it does not prove: Your plan, apps, shipping rates, and policies are different from our test store. Run the listed cases in your own store before you rely on a workflow.

Contents

  1. How to import and set up a workflow
  2. Low Inventory Alert
  3. Cancel and Tag High-Risk Orders
  4. Tag a Customer’s First Order
  5. Hide and Republish Out-of-Stock Products
  6. POS Restock Alert
  7. Customer Lifetime Spend Tiers
  8. Fraud Review Before Payment Capture
  9. Rush Order and Expedited Fulfillment Routing
  10. Markets and Multi-Currency Order Tagging
  11. Scheduled Daily Fulfillment Summary
  12. Update Customer Metafield on Order Creation
  13. B2B Net Payment Terms Reminder
  14. Test data, run evidence, and manifest
  15. What the test store taught us

How to import and set up a workflow

  1. Download the .flow file. Each workflow below has its own download link.
  2. Import it. In Shopify admin, open the Flow app and use Import to load the file. It arrives turned off.
  3. Replace the test values. Every email in these files goes to ops@example.com. Thresholds, tags, sales channels, and locations come from our test store. Change them all.
  4. Run the cases. Each entry lists the cases we ran. Repeat them with test data in your store and check the run details in Flow.
  5. Turn it on and plan the rollback. Know how you will undo a wrong tag, cancellation, or unpublish before you need to.

Workflow 01 · Inventory · Tested

Low Inventory Alert

Email your team when a variant’s stock first drops below a threshold. Later changes below that line send nothing.

Trigger: Product variant inventory quantity changed

Logic: Alert only when the previous total quantity was at or above 5 and the new total is below 5.

Download: low-inventory-alert.flow

Passed in the test store

  • Drop that crosses the threshold sends one email
  • Drop that stays above the threshold sends nothing
  • Restock sends nothing
  • A second drop after a restock alerts again
  • A further drop while already below the threshold sends nothing

Not run

  • Inventory tracking turned off. The file has no tracked-inventory guard; add one if you sell untracked products.

Change before you turn it on

  • Threshold (5)
  • Recipient email

Limitation: The condition uses the variant’s total quantity across all locations. For one location, use Workflow 08.

Workflow 02 · Fraud · Tested

Cancel and Tag High-Risk Orders

Cancel an order Shopify rates as high risk, void the payment, restock the items, and flag the customer for review.

Trigger: Order risk analyzed

Logic: If the risk level is High: cancel for fraud with refund and restock on and the customer notice off, add the order tag high-risk-cancelled, add the customer tag high-risk-review, and email the team.

Download: cancel-and-tag-high-risk-orders.flow

Passed in the test store

  • High-risk checkout order: cancelled, payment voided, item restocked, both tags added, email sent
  • Low-risk checkout order: no action

Not run

  • Medium risk. Shopify’s test markers only produced High and Low. The condition matches High exactly, so Medium takes the no-action branch.
  • Risk scores from third-party fraud apps. This trigger only uses Shopify’s own assessment.

Change before you turn it on

  • Refund, restock, and customer-notice settings
  • Tags and recipient

Limitation: Automatic cancellation can cost real sales on false positives. If you would rather review first, use Workflow 10 instead.

Workflow 03 · Customer lifecycle · Tested

Tag a Customer's First Order

Tag the order and the customer when a registered customer places their first order.

Trigger: Order created

Logic: If the order has a customer and that customer’s order count is 1, add the order tag first-order and the customer tag first-order-customer.

Download: tag-first-order.flow

Passed in the test store

  • First order from a new customer: both tags added
  • Second order from the same customer: no tags
  • Order with no customer: no action

Not run

  • Tag already present on the customer

Change before you turn it on

  • Order and customer tag names

Limitation: Orders paid with a test gateway or with Shopify Payments in test mode do not count toward the customer’s order count, so this workflow does not tag them. Test it with a draft order marked as paid.

Workflow 04 · Catalog · Tested

Hide and Republish Out-of-Stock Products

Hide a product from the Online Store when every variant is sold out, and show it again when stock returns. Preorder products stay visible.

Trigger: Product variant inventory quantity changed

Logic: Hide when no variant has stock, inventory is tracked, and the product has neither the Out of stock nor the preorder tag; then add Out of stock. Republish when the product has Out of stock and any variant has stock; then remove the tag.

Download: hide-and-republish-out-of-stock-products.flow

Passed in the test store

  • Single-variant product sold out: tagged and hidden
  • Two-variant product with one variant sold out: stayed visible
  • Sold-out product tagged preorder: stayed visible
  • Stock restored: tag removed and product published again

Change before you turn it on

  • Sales channel: the file holds our test store’s Online Store ID, so reselect your own in both publish steps
  • The preorder exclusion tag, if you use a different one

Limitation: The tag Out of stock is how the workflow remembers what it hid. Products you hide by hand are not republished.

Workflow 08 · Retail inventory · Tested

POS Restock Alert

Email your team once when stock at one chosen location falls to a threshold, and once more when it is restocked.

Trigger: Product variant inventory quantity changed

Logic: Alert when the chosen location has 5 or fewer available and the variant metafield flow_stock.variant_out_of_stock is not true, then set it to true. Send a restocked email when the location has 6 or more and the metafield is true, then set it to false. The email lists product, variant, SKU, location, and quantity.

Download: pos-restock-alert.flow

Passed in the test store

  • Location drops to 3: one alert, with the right quantity in the email
  • Location drops again to 2: no second alert
  • Location restocked to 6: one restocked email
  • Healthy stock change (13 to 12): no email

Not run

  • A drop at a different location. The test store has one location.
  • A location ID that does not exist. By design, no email is sent; the workflow does not warn you about the bad setting.

Change before you turn it on

  • Location ID: the file holds our test store’s location, so replace it in both conditions
  • Thresholds (5 and 6) and recipient

We fixed Shopify’s template: The starter template only alerts when the memory metafield already exists with the value false. A variant that never had the metafield never alerts. Our version checks that the metafield is not true, so first-time drops alert too.

Workflow 09 · Customer lifecycle · Tested

Customer Lifetime Spend Tiers

Give every customer exactly one spend tier tag and move them up as they spend more.

Trigger: Order created

Logic: Lifetime spend of 750 or more gets Gold VIP, 500 or more gets Silver VIP, 250 or more gets Bronze VIP. Each branch removes the other two tier tags first.

Download: customer-lifetime-spend-tiers.flow

Passed in the test store

  • Spend reaches 255: Bronze added, the others removed
  • Spend reaches exactly 500: Silver added, Bronze removed; the customer kept one tier tag

Not run

  • Refunds. This workflow only runs when an order is created, so a refund never moves a customer down a tier.

Change before you turn it on

  • Thresholds, in your store currency
  • Tier tag names

Good to know: When the order is created, the customer’s lifetime spend already includes that order.

Once those tiers exist, your email platform can use them for segmentation; compare the options in our guide to the best email marketing platforms for Shopify.

Workflow 10 · Fraud · Tested

Fraud Review Before Payment Capture

Capture payment automatically for orders Shopify does not rate high risk, and hold the rest for a person to review.

Trigger: Order risk analyzed

Logic: If the risk level is not High and the order can be captured, capture payment. Otherwise send a “Review before capture” email.

Download: fraud-review-before-payment-capture.flow

Passed in the test store

  • Low-risk order with an open authorization: payment captured
  • High-risk order: no capture, review email sent

Not run

  • Medium risk. As shipped, Medium-risk orders are captured. Change the condition to “risk level equals Low” if you want them reviewed.
  • An order that cannot be captured

Change before you turn it on

  • Set Shopify Payments to capture payment manually, or nothing waits for this workflow
  • Review recipient

Limitation: It only acts on the risk event for the order. Later transactions, such as post-purchase upsells, need their own workflow.

Workflow 12 · Fulfillment · Tested

Rush Order and Expedited Fulfillment Routing

Tag expedited orders and tell the warehouse once, so they ship first.

Trigger: Order created

Logic: If any shipping line is titled Express, Expedited, or Overnight and the order does not already have the tag rush, add rush and send one email.

Download: rush-order-routing.flow

Passed in the test store

  • Express shipping: tagged and email sent
  • Standard shipping: no action
  • Order already tagged rush: no second tag or email

Not run

  • A renamed or translated shipping title as its own order. Any title outside the list behaves like standard shipping.

Change before you turn it on

  • Your exact shipping rate titles
  • Tag and recipient

Limitation: We tested with custom shipping lines on draft orders, not carrier rates at checkout. Check the titles your checkout really shows.

Workflow 16 · International operations · Tested

Markets and Multi-Currency Order Tagging

Tag every order with the currency the customer paid in and the country it ships to, so you can filter and route international orders.

Trigger: Order created

Logic: Add currency- plus the presentment currency code. If a shipping address exists, add country- plus the country code.

Download: markets-and-multi-currency-order-tagging.flow

Passed in the test store

  • US order in USD: currency-usd and country-us
  • Order with no shipping address: currency tag only
  • Checkout and draft orders both tagged

Not run

  • An order in a currency other than USD. The test store sold in USD only.

Change before you turn it on

  • Tag prefixes, if you use a different naming scheme

Note: These are currency and country tags. They do not tell you which Shopify Market handled the order.

Workflow 17 · Fulfillment · Tested

Scheduled Daily Fulfillment Summary

Send one email a day that lists every unfulfilled order older than two days, with the count and total value.

Trigger: Scheduled time, daily at 5:00 pm Eastern

Logic: Get up to 100 orders created at least two days ago that are unfulfilled and not cancelled, oldest first. If there is at least one, email the count, the total, and one line per order. If the list reaches 100, the email warns that more orders may exist.

Download: scheduled-daily-fulfillment-summary.flow

Passed in the test store

  • Scheduled run listed the 5 matching orders and their $240.90 total
  • Cancelled and same-day orders were left out

Not run

  • No matching orders. The count check stops the email, so a quiet day sends nothing.
  • 100 or more orders. The warning is in the email and appears only at that size.

Change before you turn it on

  • Time and time zone
  • Recipient
  • The order query, if “two days” is the wrong age for you

Limitation: Get order data returns at most 100 orders. Larger stores need a narrower query, several workflows, or a custom Shopify app. Shopify warns that a broken query can return every order, so test the query first.

Workflow 22 · Customer data · Tested

Update Customer Metafield on Order Creation

Record the date of each customer’s latest order in a customer metafield. The workflow uses Flow’s own metafield action, so the file holds no API call or access token.

Trigger: Order created

Logic: If the order has a customer, set the customer metafield custom.last_order_at (date and time) to the order’s creation time.

Download: update-customer-metafield-on-order-creation.flow

Passed in the test store

  • Customer order: metafield written
  • Second order for the same customer: metafield updated
  • Order with no customer: no action

Not run

  • A value that does not match the metafield type

Change before you turn it on

  • Metafield namespace, key, and type

Limitation: Each new order overwrites the value. That is what you want for “last order date” but not for a running list.

Workflow 25 · B2B · Tested

B2B Net Payment Terms Reminder

Send Shopify’s payment reminder to a B2B customer on the day an unpaid invoice is due.

Trigger: Payment schedule is due

Logic: If the payment terms are not “due on receipt” and the schedule is not yet paid, send the payment reminder.

Download: b2b-net-payment-terms-reminder.flow

Passed in the test store

  • B2B order due today: reminder sent to the company’s main contact
  • B2B order on Net 7 terms: no reminder before the due date
  • Turning the workflow on: Shopify warned about overlapping standard payment reminders

Not run

  • A schedule paid before its due date. The condition skips paid schedules.

Change before you turn it on

  • Turn off any standard payment reminders that cover the same date, or customers get two

Limitation: B2B on a live store requires Shopify Plus. The reminder always goes to the company’s main contact; the action cannot change the recipient.

Test data, run evidence, and manifest

Every workflow has three files. The manifest lists them all with SHA-256 checksums, so you can confirm a download has not changed.

Run evidence

What we ran, what Shopify Flow reported, and which cases we did not run. One file per workflow, for example pos-restock-alert.run-evidence.json.

Test fixtures

The test data and expected results for each workflow, for example pos-restock-alert.fixture.json. Use them as a checklist when you test in your own store.

Manifest

All twelve workflows with their trigger, merchant inputs, limitations, official sources, and file checksums.

Download manifest.json

What the test store taught us

  • Test payments do not count. Checkout orders paid in test mode do not raise a customer’s order count or lifetime spend. Use draft orders marked as paid to test customer-based workflows.
  • Shopify’s templates need checking. The POS template never alerted for a variant that had no memory metafield yet. We changed one condition to fix it.
  • Risk tests need Shopify Payments. The bogus test gateway always reported low risk. A high-risk result needed Shopify Payments in test mode with Shopify’s high-risk test address.
  • Sold-out logic needs the whole product. A product can have one sold-out variant and others still in stock. The tested workflow checks every variant before it hides anything.

What still changes from store to store

No workflow library can decide your fraud tolerance, payment policy, inventory scope, customer tags, email recipients, B2B process, or sales channels. Make those decisions before you turn a workflow on.

If you want these set up and watched after launch, our Shopify support team can run that work. For more about how we approach Shopify builds, see our methodology.

Post last updated November 20, 2026

Need a Shopify Flow workflow built around your store?

Tell us your store’s edge cases and policy rules, and which systems the workflow must work with.

Start a project enquiry
Alex Espinoza portrait photo

Written by

Alex is the founder of AESYMMETRIC, a Shopify agency specializing in conversion rate optimization, custom app development, and theme customizations. With eight years of experience in the Shopify ecosystem and e-commerce industry, he helps brands maximize sales and reduce costs through data-driven strategies and innovative technical solutions.