Is Shopify Flow enough for an ecommerce back office?

It is enough when the work starts and ends inside Shopify, such as tagging orders, holding a fulfillment order or sending an alert. Flow is a free app on the Basic, Grow, Advanced and Plus plans. When a workflow needs code that runs longer than 5 seconds, a call that can take more than 30 seconds or a second system, check Flow's published limits first.

Should I self-host n8n for my store?

Only if someone on your team will keep it running. n8n's docs list hosting and maintenance as your responsibility when you self-host. n8n Cloud removes that work for a monthly fee. The Sustainable Use License limits use to your own internal business purposes or non-commercial or personal use, so read it if a third party will host the instance for you.

How do I know when an automation has silently stopped?

In Flow and n8n, the docs describe building the alert yourself: use the Workflow error occurred trigger in Flow, and set an error workflow in n8n. Make emails you on errors by default, so check that the right person gets those emails, that incomplete executions are stored and that your scenarios are still switched on. Then run a weekly reconciliation: compare the orders Shopify updated with the orders your automation handled.

All resources

Guide8 min read

Shopify Flow vs n8n vs Make for Your Ecommerce Back Office

Use Shopify Flow when the job starts and ends inside Shopify. Look at n8n or Make when a workflow has to work with a second system, such as a helpdesk, a 3PL or an ERP. Whichever you pick, give it an owner and a failure alert before the first workflow goes live.

By Maksudur Rahman, FounderPublished October 17, 2026Last reviewed October 17, 2026

What we found

On October 14, 2026, we read the vendors' own documentation for all three tools instead of reviews. These are the limits that should decide your choice. We did not load-test any of them.

Shopify Flow keeps workflow runs for 14 days. After that, the run is removed.
Flow's Run code step stops at 5 seconds and 10MB, and its code can't make HTTP calls.
Make disables a scheduled scenario after 3 errors in a row by default. A scenario that starts from an instant (webhook) trigger is disabled on its first error.
n8n Cloud counts workflow executions, not steps. Make counts credits, and for non-AI apps one operation is one credit.

What each one is good at

Shopify Flow is a free app on the Basic, Grow, Advanced and Plus plans. It watches your store for events and runs actions in response, such as adding order tags, holding a fulfillment order or sending a Slack message. There is no server to run.

n8n runs on n8n Cloud or on your own server. Its pricing page says you pay for full executions, not for each step. Its Shopify node covers orders and products, with five operations each: create, delete, get, get all and update. For anything else, n8n's docs tell you to use the HTTP Request node and call Shopify's API with your credential.

Make bills by credit. Take a scenario with five modules that handles one order: about five credits. At 1,000 orders a month, that is about 5,000 credits. The same five steps in n8n count as 1,000 executions. That is our arithmetic, not a vendor quote, and loops or extra bundles change it.

Where Flow runs out

Flow's limits are published, and they are specific. Check them against the job you have in mind.

Run code executes JavaScript for at most 5 seconds with 10MB of memory. It can't make HTTP calls.
Send HTTP request is only on the Grow, Advanced and Plus plans. Flow waits up to 30 seconds for a response code. A failing call can be set to retry for up to 24 hours, fail the run or be ignored.
Send Admin API request supports mutations only. It does not support queries or asynchronous mutations.
Wait holds a workflow for 90 days at most.
Loops over long lists can trigger a GraphQL throttled error. One of Shopify's examples is looping over shop.orders in a large shop, and Shopify warns that the error can affect other workflows.

When n8n or Make is worth the upkeep

None of those limits is a flaw. Flow's core job is to react to a Shopify event with a short run of steps. Past that job, you may need something else.

Our rule: if the work starts and ends inside Shopify, use Flow. On the Grow plan and up, Flow can send an HTTP request, so one simple outbound call is possible. The day a workflow needs to read from or reconcile with a second system, such as a helpdesk, a 3PL or a spreadsheet, price n8n and Make against the upkeep.

Upkeep is the hidden line. On n8n Cloud, n8n hosts the server. Self-hosted, n8n's docs list hosting and maintenance as your responsibility. The Community edition is free, and the Sustainable Use License says you may use it "only for your own internal business purposes or for non-commercial or personal use." If someone else will host it for you, read the license first.

As of October 14, 2026, n8n Cloud Starter is listed at 20 euros a month billed annually for 2,500 executions. Pro is 50 euros a month billed annually for 10,000. Prices move, so check the page.

One bias to weigh: we build with n8n. Our founder placed 3rd in the Hostinger n8n hackathon in December 2025, working alone, and has published two n8n templates. Two n8n automations run in production on a build for one of our professional-services clients, which is not an ecommerce store.

We apply the same skepticism to every tool pitch. For one of our subscription clients, a $499-a-month upgrade pitch was tested against the live account, and 5 of the 8 pitched features were already available on the plan the store had.

What breaks, and who watches it

A failed workflow can fail quietly. Flow's and n8n's docs describe building the alert yourself, and Make emails you by default, so check whose inbox that is. The fix is organizational, not technical: one owner, one place where alerts land and one weekly check for each automation. Here is what each tool gives you.

Flow: the Workflow error occurred trigger can start an alert workflow, and Shopify provides email, Slack and Shopify alert templates. You still have to set it up. The trigger runs once per workflow version in 30 days, so a workflow that fails 10 times in a day sends one alert.
n8n: you set an error workflow for each workflow, in Workflow Settings. It must start with the Error Trigger node. Without one, a failed run shows up in the Executions list, and someone has to go and look.
Make: by default it emails you when a scenario errors and when it disables a scenario after repeated errors. With no error handling set and incomplete executions off, which is the default, a failed run is rolled back and repeated errors deactivate the scenario. Turn on Store incomplete executions in scenario settings if you want failed runs kept for a retry.
Webhooks: Shopify's developer docs say webhook delivery isn't always guaranteed, and they recommend a reconciliation job that periodically fetches data from Shopify. The docs are written for app developers, but the point holds for any workflow you start from a webhook.

When plain code beats all three

Some jobs do not fit a visual builder. A nightly comparison of Shopify orders against your ERP, helpdesk or 3PL is one. A scheduled script has no 5-second step cap and no per-step meter, and it can live in version control with a test. n8n Cloud's Starter plan also lists a 5-minute maximum execution duration.

Code costs more to write and needs someone who can read it. So start with the cheapest tool that fits, and move up only when one of the limits above is hit.

We have not benchmarked these tools against each other. This comparison comes from their documentation on October 14, 2026, and vendors change limits. Read the pages again before you commit.

Check this in your own store

This check is read-only. Run it before you pick a tool, or before you trust the one you have.

List every automation: each Flow workflow, each n8n workflow, each Make scenario. Write down its trigger, its owner and when it last ran.
In the Flow app, open Recent runs and filter by Errors. The search only reaches back 14 days, so older failures are gone.
In Flow, look for a workflow that starts with Workflow error occurred. If there is none, you have not set up an alert.
In n8n, open each workflow's Settings and check the Error workflow field. In Make, open Scenario settings and check Store incomplete executions, and check your email preferences so error and deactivation emails reach someone who reads them. Also confirm every scenario you rely on is still switched on, because Make disables a scenario after repeated errors.
Pick one order from the last 7 days. Trace it through every automation and confirm each step fired.
Ask Shopify for the orders updated in the last 24 hours, and compare that count with what your automations handled. Shopify's docs say many GraphQL queries accept updated_at filters for this kind of check. A gap between the two numbers tells you where to start looking.

Sources

Every limit above was read on October 14, 2026.

Frequently asked questions

Is Shopify Flow enough for an ecommerce back office?: It is enough when the work starts and ends inside Shopify, such as tagging orders, holding a fulfillment order or sending an alert. Flow is a free app on the Basic, Grow, Advanced and Plus plans. When a workflow needs code that runs longer than 5 seconds, a call that can take more than 30 seconds or a second system, check Flow's published limits first.
Should I self-host n8n for my store?: Only if someone on your team will keep it running. n8n's docs list hosting and maintenance as your responsibility when you self-host. n8n Cloud removes that work for a monthly fee. The Sustainable Use License limits use to your own internal business purposes or non-commercial or personal use, so read it if a third party will host the instance for you.
How do I know when an automation has silently stopped?: In Flow and n8n, the docs describe building the alert yourself: use the Workflow error occurred trigger in Flow, and set an error workflow in n8n. Make emails you on errors by default, so check that the right person gets those emails, that incomplete executions are stored and that your scenarios are still switched on. Then run a weekly reconciliation: compare the orders Shopify updated with the orders your automation handled.

Not sure which of the three fits your store? Book a diagnosis call. We read your current workflows first and recommend after. For a wider look at how your team runs, start with the free 10-minute assessment, or see our work on ecommerce operations. If you are also weighing who should build it, read how to choose an ecommerce automation agency.

Back to resources Book a diagnosis call