Shopify Flow: automate without code

Shopify Flow is Shopify’s native automation engine. It executes actions on your behalf when an event occurs in your store: tagging a customer, hiding an out-of-stock product, alerting your team about a suspicious order, or triggering an invoice. All this without writing a single line of code, and at no extra cost, as Flow is included in all Shopify plans, not just Shopify Plus. The promise can be summed up in one sentence: anything you do manually several times a week in your back-office can likely be delegated to a workflow. And since the Winter 2026 edition, you can even describe this workflow to Sidekick in French instead of assembling it block by block.

In brief

• What it is: a no-code automation engine integrated into the Shopify admin, based on the trigger, condition, action triad.
• Available on which plans: all of them, from Basic to Plus. The Flow app can be installed for free from the App Store.
• How much it costs: nothing. Only third-party applications connected to your workflows might have a cost.
• What it replaces: a portion of manual back-office tasks and several small paid applications for tagging, alerting, or inventory management.
• The 2026 novelty: Sidekick can generate a Flow workflow from a request made in natural language, and the editor allows you to test it on a real event from your store before activation.
• The case that illustrates it: at Angell, a single Flow workflow manages the two-part payment for the MINI E-Bike 1 pre-order at €3,490, including a 30% deposit, dual invoicing, and a withdrawal window. No market application could do this.
• Its main limitation: Flow orchestrates the internal logic of your store; it does not modify the checkout or discount rules, and it does not handle loops.

What exactly is Shopify Flow?

Shopify Flow is an official Shopify application that listens to events in your store and triggers automatic actions in response. It lives directly in your admin, alongside orders and products, and requires no technical skills: the interface works using blocks that are assembled visually.

The important, and often misunderstood, point is its availability. For a long time, Flow was a selling point reserved for Shopify Plus. This is no longer the case: Shopify Flow is now free and can be installed on any plan. If you are on a Basic or Grow plan and thought you weren't entitled to it, you are missing out on one of the few efficiency levers that costs nothing.

What Flow replaces in practice: macros cobbled together in a spreadsheet, reminders in a shared calendar, manual inventory checks on Monday mornings, and a large portion of small paid applications that do only one thing. An active back-office quickly accumulates a dozen of these micro-tasks; each insignificant in isolation, all costly when combined. This is actually the first reflex we apply during an audit: before adding an application, we check if a free workflow isn't already doing the job. Our selection of the best Shopify apps in 2026 is based on this same principle of sobriety.

The task remains to define the boundary: what we delegate to the machine and what we keep for human decision-making. This is the first trade-off we impose on the accounts we take over.

“We systematically refuse to automate the cancellation of an order based on a fraud score. A false positive costs more than a thirty-second human check. Flow tags and alerts; it does not decide.”

Florian Pohl, co-founder of Stellar Projects

How a workflow works: trigger, condition, action

Every Flow workflow is built on three bricks, always in the same order. A trigger detects an event. One or more conditions filter the cases to be handled. One or more actions are executed. This is the tool's reference vocabulary, and it is sufficient to describe any automation, from the simplest to the most elaborate.

A useful way to formulate a workflow before even opening the interface: “when this happens, if that is true, then do this.” If you don't know how to fill in the three boxes, the workflow isn't ready.

The most useful triggers

Shopify provides several dozen native triggers, but a handful cover the majority of real-world needs. Here are the ones we find in almost all the stores we equip.

The scheduled trigger is the most underutilized of the seven. Yet, it is the one that transforms Flow from a reactive tool into a control tool: a workflow that reviews products without images, descriptions, or prices every Monday prevents you from discovering the problem from a customer.

Conditions

Conditions are filters applied to the event data. Order amount exceeding a threshold, high fraud risk indicator, product belonging to a specific collection, customer carrying a specific tag, metafield value. Flow accepts multiple branches, which allows handling several cases in a single workflow instead of multiplying copies of them.

Available actions

The most common actions involve tags (adding or removing a tag from an order, customer, or product), notifications (internal email, Slack message), the catalog (hiding or republishing a product, modifying a metafield), and orders (canceling, marking, capturing payment). Flow is based on the Shopify Admin API, which explains the breadth of its scope. Third-party application connectors further extend the list: Klaviyo, review tools, loyalty platforms, logistics solutions, invoicing solutions.

Ten concrete automations to implement

Here are ten proven Shopify workflows, formulated in the trigger, condition, action triad. They are intentionally simple: in automation, value comes from the accumulation of small, reliable workflows, not from a single behemoth system.

1. Tag VIP customers. Trigger: order paid. Condition: total amount spent by the customer exceeds your VIP threshold. Action: add the “VIP” tag to the customer, which then feeds into a marketing segment.
2. Alert on a high-risk fraud order. Trigger: order created. Condition: high risk level. Action: tag the order “to be checked” and notify the team by email before preparation.
3. Hide an out-of-stock product. Trigger: inventory level changed. Condition: quantity available equals zero. Action: remove the product from the sales channel. A second workflow reverses this by republishing it when restocked.
4. Tag new customers for the welcome flow. Trigger: customer created. Condition: no prior orders. Action: add a tag used as an entry criterion in your Klaviyo welcome sequence.
5. Notify on a high-value order. Trigger: order paid. Condition: amount exceeds your average basket multiplied by three. Action: Slack message or email to the manager for priority processing.
6. Follow up on a review request after delivery. Trigger: order delivered. Condition: product belonging to a targeted collection. Action: trigger the review solicitation via your customer review tool's connector.
7. Isolate orders to be checked manually. Trigger: order created. Condition: shipping address outside the usual zone, or abnormally high quantity on the same reference. Action: tag the order and suspend preparation.
8. Manage pre-orders. Trigger: order created. Condition: the order contains a product tagged “pre-order.” Action: tag the order, notify logistics, and exclude the order from the standard shipping flow.
9. Segment customers at risk of churn. Trigger: scheduled, once a week. Condition: last order was more than six months ago. Action: add a reactivation tag used in an email campaign.
10. Reapply a loyalty tag on the anniversary date. Trigger: scheduled, daily. Condition: customer sign-up date equals today's date, previous year. Action: tag the customer to trigger an anniversary offer.

A clarification that prevents frequent disappointment: Flow does not act on abandoned carts, which are not orders and therefore do not emit an actionable trigger. This battle is fought elsewhere, and we detail it in our guide on abandoned cart recovery.

A real case: the two-part payment for the MINI E-Bike 1 pre-order

Recipe #8 deserves to be explained, because it shows the moment when Flow ceases to be a convenience to become the only solution. Angell, which designs and markets MINI electric bikes in partnership with the BMW Group, was launching the MINI E-Bike 1 for pre-order. On a premium bike priced at nearly 3,500 euros, requiring full payment several months before delivery is a massive conversion barrier. The brand therefore wanted precise sequencing: a 30% deposit at the time of order with a first invoice, then a capital call and a second invoice for the balance once the bikes were received in stock.

No pre-order application on the market managed this scenario reliably. We built it with Flow: a workflow tags the customer and the order at the time of the deposit, splits the purchase into two stages, and manages the issuance of both invoices via the Sufio connector. Between the two installments, an automatic email goes out to the customer just before the capital call, giving them the option to withdraw and be refunded before the balance is debited.

This is exactly the scenario where the trade-off favors Flow rather than an application: the need was not a standard feature, it was a business rule specific to the brand, with invoicing constraints and a legal withdrawal constraint. An application gives you what it has planned. A workflow gives you what you have decided. If your subject involves the compliance of issued documents, our Shopify invoicing guide details the mandatory information and the trade-offs between native invoicing, Order Printer Pro, and Sufio.

If your subject is wholesale, the logic of restocking and professional orders follows different rules. We cover them in our guide on wholesale order management on Shopify, and the entry point for wholesale has actually changed since Shopify B2B was opened to Basic, Grow, and Advanced plans.

Flow and AI: what really changes in 2026

The real evolution of Flow in 2026 is not a new trigger; it is the way one builds a workflow. Shopify has connected its Sidekick assistant to Flow: you describe the automation you want in natural language, and the assistant assembles the corresponding workflow in the editor. You go from “I’m looking for the right block in a list” to “I’m explaining my business rule.”

Technically, Shopify documented this shift in April 2026 on its engineering blog: workflow generation relies on an open-source model, Qwen3-32B, fine-tuned internally, retrained automatically every week, and deployed gradually starting from 1% of traffic. Shopify claims a model 2.2 times faster and 68% cheaper than the previous approach, with superior semantic quality. Three takeaways for a merchant:

• The cost of entry is collapsing. The barrier was never the price of Flow; it was learning the interface. That barrier is gone.
• The quality of the prompt becomes the quality of the workflow. A vague request produces a vague automation. The trigger, condition, action triad remains the right way to formulate the request, even in French.
• Testing becomes the critical step again. Since December 2025, Flow has allowed you to launch a test run directly in the editor, on a real event from your store: the workflow is simulated in about ten seconds, and actions that modify external data are not executed. Use it: an automation generated in thirty seconds deploys just as quickly, errors included.

On the features side, in June 2026, Shopify added a native action for automatic debit on saved payment methods for B2B orders with payment terms. It is only used with the payment deadline trigger, assumes Shopify Payments, and direct debit from a bank account remains reserved for merchants and customers located in the United States. And in the background, the opening of catalogs to conversational agents changes the nature of the data your workflows must keep clean: an incorrectly placed tag or an incomplete page no longer just penalizes your back-office; it penalizes your visibility in answer engines. We develop this point in our guide on agentic commerce.

Flow, Functions, apps, or Zapier: which one for what?

This is the question that comes up most often once the principle is understood. The four tools do not compete; they occupy different layers of your store. Choosing the wrong level is the number one cause of abandoned automation projects.

Our arbitration rule for any Shopify automation project: always start with Flow. It is free, reversible, and sufficient in the majority of cases. Only move to Functions if the need relates to the checkout, and to Zapier or Make only if data needs to leave Shopify.

A note of caution regarding the calendar: Shopify Scripts were definitively discontinued on June 30, 2026. If your store still relied on a discount or shipping script, migrating to Functions is no longer a matter of convenience, but a technical compliance requirement. Flow does not take over in this area: it never had control over the checkout.

The limitations of Shopify Flow and how to work around them

Flow is powerful within its scope and frustrating outside of it. Knowing its four structural limitations will save you hours of forcing a tool to do what it wasn't designed for.

• No loops. Flow cannot repeat an action on a list of items. Processing every line item of an order, for example, requires a workaround or custom development.
• Limited debugging. The execution history indicates that a workflow was triggered and whether it succeeded, but it does not replace actual logs. On a workflow with multiple branches, error analysis remains laborious.
• Dependency on connectors. An action on a third-party tool only exists if the developer has published the corresponding connector. Without a connector, you must use a webhook or a request to the Admin API.
• No complex cross-store logic. If you operate multiple Shopify stores with shared rules, Flow quickly hits its ceiling. This is where external orchestration takes over.

When these limitations become blocking, there are two directions: Shopify Functions for everything related to the checkout, and custom development via the Admin API for the rest. Our ultimate Shopify guide places these building blocks within the overall architecture of a store.

Making your automations last over time

This is the part that no one writes down and everyone suffers through. A workflow is created in five minutes and maintained for years. The risk is not that it will break, but that no one will know why it exists. For accounts we take over, the most embarrassing question is rarely technical: "What is this tag for?", followed by silence.

Four rules are enough to avoid automation debt.

1. A naming convention, decided before the first workflow. We name workflows by scope and then by effect, for example, "CUSTOMER - VIP tag" or "STOCK - hide out of stock". Tags follow the same discipline: lowercase, no accents, with a category prefix. A poorly named tag today becomes debt in six months.
2. One workflow, one intent. It is tempting to stack branches in an existing workflow. Two distinct business rules deserve two distinct workflows: it is more readable and, above all, can be deactivated independently.
3. A quarterly review. Open the list of active workflows and check the execution history of each one. Those that haven't triggered in three months are either useless or broken. In both cases, you must make a decision.
4. A written record outside of Shopify. A three-column table is enough: workflow name, business rule in one sentence, and the person responsible. This is the document that saves a team handover.

The critical threshold is around twenty active workflows. Below that, the team can keep track of everything in their heads. Above that, without conventions or documentation, no one knows what is running or why, and the first reaction becomes to disable everything "just to be safe." This is exactly what must be avoided.

Where to start: your first workflow in 5 minutes

Automating your Shopify store begins with a workflow you can verify immediately. Do not start with your most ambitious automation: start with one whose result you will see within the hour.

1. Install the Flow app from the Shopify App Store. The installation is free and takes less than a minute.
2. Start from a template. Flow offers a library of ready-to-use templates. "Tag high-risk orders" is an excellent first case: useful, with no side effects, and immediately verifiable. You can also describe your need to Sidekick and start from what it generates.
3. Verify the trigger and the condition. Adjust the threshold or the tag to your store's vocabulary, while respecting the naming convention you just established.
4. Test on a real order, then consult the workflow's execution history to confirm that it triggered correctly.
5. Activate, then move on to the next. One reliable workflow per week is better than ten approximate workflows deployed on the same day.

Need to automate complex processes?

Flow covers the essential automations for a back office. Beyond that, when logic involves the checkout, multiple stores, or external business tools, technical arbitration becomes structural and must be prepared in advance. This is one of the tasks we oversee on the Shopify projects we support. Let's talk about your store; we respond within 24 hours.