What can Shopify Flow automate, and where does it stop?

Shopify Flow is the natural first stop for a Shopify brand that wants to automate. It is free, it already sees your orders, products and customers, and it needs no code. It also has edges that are easy to miss until a workflow quietly fails. This guide sorts 14 common ecommerce jobs into what Flow does alone, what it does with an app connector or an HTTP call, and what it cannot do, then gives six workflows to copy. Every Flow fact links to Shopify's own help center, checked October 2, 2026.

What is Shopify Flow, and how does it work?

Shopify describes Shopify Flow as an ecommerce automation platform for tasks in your store and across your apps, and as "a free app available on the Basic, Grow, Advanced, and Plus plans" (checked October 2, 2026). You build workflows in the Shopify admin, from scratch or from one of Shopify's templates. Each workflow waits for something to happen in your store, checks whether it matters, and then does something about it.

Those three parts have names. The trigger is the event that starts the workflow, and each workflow has exactly one: Order created, Order paid, Product variant inventory quantity changed or Scheduled time, among the full list of triggers. The condition is the if-then check: a field from your store compared with a value using operators such as equal to, greater than, includes or at least one of, with several checks joined by AND or OR, per Shopify's conditions reference. The action is what happens next: add a tag, hold a fulfillment order, unpublish a product, send an internal email.

Past the store actions, Flow reaches outward in three ways. Connectors are apps that add their own triggers and actions; Shopify notes that the app actions you see depend on which connectors are installed. Send HTTP request calls any web address or API. Send Admin API request runs most GraphQL Admin API mutations, including ones that have no Flow action yet. The plans differ on two of these:

Usage limits also vary by plan, because they follow the API rate limits each plan gets. When workflows use too many resources, Shopify's usage limits page says Flow will limit how runs execute on your store, which can cause delays and timeout errors.

What can Shopify Flow automate, and what can't it?

This is the map we work from when a Shopify brand asks what to automate. Each row is a common job. "Yes" means Shopify documents the trigger and the actions it needs, usually with a template of the same purpose on its workflow examples page. "With an app connector" means another app supplies a trigger or action. "With Send HTTP request" means Flow calls an outside API, on Grow or above. "No" means Flow has no trigger or connector for it as of October 2, 2026. The last column is where the job goes when Flow runs out.

The pattern is clear once the rows sit together. Flow is strong when both the event and the change live in Shopify. It weakens when the data starts somewhere Shopify cannot see, such as an inbox, a marketplace or a bank payout, or has to end in a system with no connector. Shopify's list of apps that work with Flow includes Slack, Google Sheets, Gorgias, Klaviyo, Asana and Trello, but no Amazon, Walmart, QuickBooks or Xero connector (checked October 2, 2026), and the actions list has no purchase-order action. Sorting incoming customer emails is a helpdesk job; our support-ticket triage recipe shows where an AI model fits in it and where a person stays.

Which Shopify Flow workflows can you copy today?

Each of the six below uses only triggers and actions Shopify documents. The thresholds are illustrative; set your own. Build one, run it on a few test orders and watch its runs for a week before you add the next.

1. Hold high-risk orders for a person to review

• Trigger: Order risk analyzed.
• Condition: the order's risk level is high.
• Actions: Add order tags (for example "risk-review"), Hold fulfillment order with a reason, Send internal email to whoever reviews them.

The Order risk analyzed trigger fires when Shopify's fraud analysis finishes, not the moment the order is created, and only for Shopify's own risk assessments. Shopify's hold action page lists templates that hold orders when the risk level is high. Shopify also offers a template that cancels and restocks high-risk orders. We would start with the hold, and keep the cancel decision with a person.

2. A low-stock alert that fires once, not on every sale

• Trigger: Product variant inventory quantity changed.
• Condition: the new quantity is below your threshold (say 10 units) and the previous quantity was at or above it.
• Action: Send internal email to purchasing, or a Slack message through the Slack connector.

Shopify says the inventory trigger fires on any change, from an order, a manual edit or an app, and passes the previous quantity. Checking both numbers stops a fresh alert on every sale below the line. One catch: Send internal email cannot take a variable recipient address, so route alerts for different suppliers with separate branches.

3. Hide sold-out products and bring them back on restock

• Trigger: Product variant inventory quantity changed.
• Condition: no variant of the product has stock left.
• Action: Unpublish product from your online store. A second branch publishes it again once at least one variant has stock.

The Unpublish product page lists templates for both halves, including one that hides out-of-stock products and republishes them when a variant has inventory. Decide first whether a sold-out product should disappear or stay visible with a back-in-stock form; that is a merchandising call, not a technical one.

4. Tag VIP customers by lifetime spend

• Trigger: Order paid.
• Condition: the customer's total spent is above your tier (say $1,000) and the customer does not already carry the tag.
• Action: Add customer tags, such as "VIP".

Shopify's examples include "Organize customers by lifetime spend tiers". The tag then works in customer segments, discounts and email apps with a Flow connector, such as Klaviyo.

5. Send paid orders to your 3PL and hold the rest

• Trigger: Order paid.
• Condition: the order requires shipping and is assigned to your 3PL's fulfillment service.
• Action: Submit fulfillment request. Otherwise, Hold fulfillment order with a reason.

Shopify documents this template on its Submit fulfillment request page, and notes that the action works only with third-party fulfillment service apps, not custom fulfillment services. So your 3PL needs a Shopify app. Move fulfillment order can reassign an order to another location, but Flow will not weigh carrier cost or a marketplace's ship-by date for you.

6. A morning digest of orders stuck for two days

• Trigger: Scheduled time, every day at 8:00.
• Action: Get order data, with a query for unfulfilled orders created more than two days ago.
• Actions: Count and Sum, then Send internal email or a Slack message with the number and the value.

Shopify's Sum page describes a template built the same way: a daily summary of unfulfilled orders older than two days. Two cautions from Shopify's Get order data page: it returns up to 100 orders at a time, and when a query fails, the API often returns all results instead of none. Test the query before the email goes to the whole team. The Scheduled time trigger can repeat, and its smallest interval is 10 minutes.

Where does Shopify Flow stop?

Flow's limits are documented; they are just spread across many help pages. These are the five we check before building anything that matters, with the numbers Shopify published as of October 2, 2026.

Stock across channels is the edge Shopify brands hit first. Flow can hide a sold-out product on your store, but it cannot tell Amazon or Walmart that the last unit just sold, and it cannot see units that sit in FBA unless an app syncs them into Shopify. Our page for Shopify brands covers when Marketplace Connect is enough and when you need one stock count, and our guide to adding marketplaces with the same team covers the rest of the work each channel adds.

The audit trail is the edge brands notice last. Fourteen days of runs is enough to debug a workflow, not to answer "why was this order canceled in March?" Two habits help. Add a workflow on the Workflow error occurred trigger that emails you when any run fails; Shopify lists that template among its examples. And for workflows that change prices, cancel orders or move money, write each run to a Google Sheet or your own log through a connector.

Shopify Flow vs Zapier, Make and n8n: which should you use?

Use Flow for anything that starts and ends in Shopify. Reach for a workflow tool when the job spans several apps with simple logic, and for custom code when volume, exceptions or several systems that must agree outgrow both. Our workflow automation page sets out that ladder, from your platform's own automation to custom code, and the tool table there is the one we use to pick a level. Here is how the four compare for a Shopify store (pricing checked October 2, 2026):

The tools also work together. Flow can decide which orders matter, using a condition and a tag, and then call a workflow tool's webhook through Send HTTP request on Grow or above. The workflow tool handles only those orders, so its task or credit count stays small. For the three workflow tools side by side, with the usage math at 120 orders a day, see our Zapier vs Make vs n8n comparison.

When should you bring in a developer?

Most brands can build the first five workflows above without one. Bring in a developer, or a team like ours, when a workflow shows any of these signs:

A developer does not replace Flow. Keep Flow for the steps inside Shopify, and move the parts that span systems into a small service with its own log, tests and alerts. That split keeps the free parts free and puts code only where it earns its cost.

Who builds the parts Shopify Flow can't?

Ecomsellertool builds the automation around Shopify Flow. We keep Flow for the work it does well and add the connectors, stock rules and logs it lacks, on your own accounts. Send one workflow through the project brief and a person replies within 2 business days with a written plan: what to automate, which tool fits, what stays with your team, the timeline and a fixed price.

Where Flow stops at the store's edge, the connectors take over. Ecom Global, a platform we built for 100M+ products, 20+ marketplaces and 13+ carriers, connects its marketplaces from one Connectors page and keeps its carriers and routing rules in one shipping master. The other hard part is often stock logic. For Cheddy we built stock and warehouse management software in which kits, multipacks and single-pack ASINs on Amazon draw on components held in the warehouse, a mapping the ready-made software available at the time was missing features for. Flow cannot hold that kind of rule either.

For brands that sell beyond Shopify, the work runs on Ecomsellertool Growth OS, the base system we deploy for listings, stock, orders, warehousing, advertising and reporting. We have built on Amazon's seller APIs since 2017. You keep your accounts, your data and the custom code we build; the Growth OS base is licensed to you.

Where should you start?

Install Flow, build the low-stock alert and the high-risk hold, and add the workflow error email. Then take the map above and mark the rows your team still does by hand. If those rows say "No" or "Partly", send us the workflow and we will tell you whether Flow, a workflow tool or code is the right home for it.