Skip to main content

Shopify Flow vs Custom App: Which Do You Need?

  • November 2, 2026
  • 7 min read
  • By CYPHEX
Shopify Flow vs Custom App: Which Do You Need?
Illustrative animation with example data

Shopify Flow vs custom app is a decision most store owners face once a manual task starts eating hours: do you wire it up with Flow, or pay for something built? This guide is for owners and operations leads who want a straight answer. You will see what Flow does well, where it runs out, what a custom app adds, and a table to decide with, so you do not build what a free tool already does.

What Shopify Flow actually is

Shopify describes Flow as an ecommerce automation platform: it watches your store for events and runs actions in response. Workflows are built from triggers (something happens), conditions (only if this is true) and actions (do this). According to Shopify’s Flow help page, the Flow app is free to install and is available on the Basic, Grow, Advanced and Plus plans. Most features are on every plan, while the Send HTTP Request action needs Grow or above, and tasks from custom partner apps are limited to Plus.

Flow is built for the merchant, not the developer. Someone on your team can set up “when an order is created and the total is high, tag it and notify the team” without code. For many stores that covers the first handful of automations. Our Flow automation examples show typical ones.

What a custom app is

A custom app is software built for your store that talks to Shopify’s APIs. It can read and write orders, products, customers and inventory, listen to webhooks, show its own screens inside the Shopify admin, and connect to systems outside Shopify. If you want the full picture, read Shopify custom apps explained and how to build one with the Admin API and webhooks.

Shopify’s developer documentation describes how custom apps are now created through the Dev Dashboard, where you make a version with scopes and webhooks and then install it on a store. Check the Dev Dashboard guide for the current steps, since the process has changed over time.

They are not strict rivals

The two connect, which surprises people. Apps can extend Flow with their own triggers, actions and templates. Shopify’s Flow developer guide lists these extension types and notes a constraint that matters here: if your app is a custom app, its Flow extensions work only for Shopify Plus stores that have it installed. So a common pattern is Flow for the logic a merchant owns and an app for the heavy lifting underneath.

Where Flow works well

  • Tagging and routing. Tag orders by value, country or product, and notify staff.
  • Simple alerts. Low stock, high-risk orders, failed payments, so that someone reacts.
  • Housekeeping. Updating customer or product data when a condition is met.
  • Light connections. Sending an HTTP request to another service, if your plan includes that action.
  • Speed to value. You can have it running the same day, without a developer.

If an hour of tidy-up work a week is the problem, Flow is the first thing to try.

Where Flow stops

Flow has real limits, and most are about plan, scale and shape of the task.

  • Plan limits. As above, some actions depend on your plan, and usage limits follow Shopify’s API rate limits. Shopify’s help page does not list numbers, so check the current documentation for your plan.
  • Back-and-forth with other systems. Sending one request is easy. Receiving a confirmation, retrying on failure, matching records and logging errors usually needs a program.
  • Large or complex data. Reconciling thousands of records or running long jobs is a poor fit for a visual workflow.
  • Custom screens. Flow doesn’t give your staff a new page in the admin or a branded customer-facing tool.
  • Strict reliability. Anything where a missed or duplicated action costs real money (payments, stock sync) needs idempotency, queues and monitoring. Shopify’s webhook documentation is explicit that delivery isn’t always guaranteed, and recommends reconciliation jobs. That is application work.

Where a custom app earns its keep

SituationFlowCustom app
Tag and notify on order eventsYesOverkill
Alert on low stockYesOverkill
Sync orders and stock with an ERP or warehouseWeakYes
A branded order tracking tool for customersNoYes (see custom order tracking pages)
Staff-only screen to review and approve ordersNoYes
Complex pricing, rules or calculationsPartlyYes, possibly with Shopify Functions
Needs retries, logs and error handlingLimitedYes
One-off clean-up of historical dataWeakYes, often a script
You have no developer and little budgetYesNot yet

A practical way to decide

Run through these in order.

  1. Write the task as “when X happens, do Y”. If you can, it is a Flow candidate.
  2. Does Y happen inside Shopify? Tagging, notes, emails and metafield updates fit. Calling out to other systems may need a plan upgrade or an app.
  3. What happens if it fails once? If the answer is “someone notices tomorrow,” Flow is fine. If it is “we ship the wrong thing” or “we double-charge,” you need logging and retries.
  4. How many events a day? A dozen is Flow territory. Thousands of records need a purpose-built process.
  5. Will it change monthly? If so, merchant-editable logic in Flow may be cheaper to maintain than a coded rule.
  6. Does it need its own screen or customer-facing feature? Then it is an app.

A common outcome is a hybrid: the app handles integration and data, and exposes events that Flow can act on.

What a custom app costs, and how to scope it

I will not quote prices, because honest numbers depend on your exact requirements, and published ones come from sellers. The factors that move a quote are the number of systems it connects to, how much error handling and monitoring it needs, whether it has an admin interface, the volume of data, testing effort and how long you want it supported. Our article on third-party app bloat is a useful counterweight: sometimes the cheaper long-term answer is replacing three apps with one custom one, and sometimes it is removing an app you don’t need.

Ask any developer for:

  • The task described back to you in plain words.
  • Which Shopify APIs and scopes the app needs, and why.
  • How failures are handled: retries, logs, alerts.
  • Who owns the code and the hosting account.
  • What happens when Shopify releases a new API version (versions are numbered and change on a schedule, so apps need periodic updates).
  • The cost of support after launch.

Our Shopify app development service covers planning and delivery of this kind of work.

Frequently Asked Questions

Is Shopify Flow free?

The Flow app is free to install, and Shopify says it is available on Basic, Grow, Advanced and Plus plans. Some actions depend on plan: Send HTTP Request needs Grow or higher, and tasks from custom partner apps need Plus. Check the current help page for any changes.

Can Shopify Flow connect to my ERP?

It can send an HTTP request to another service on eligible plans, which suits simple one-way messages. A proper ERP connection usually needs receiving data, matching records, handling errors and retrying, which is app territory. See our guide to Shopify ERP integration.

Can a custom app work with Flow?

Yes. Apps can add triggers, actions and templates to Flow. If it’s a custom app, those extensions work only for Plus stores that have the app installed, according to Shopify’s developer docs.

When should I stop using Flow and build an app?

When workflows need retries, logging, large data volumes or their own screens, or when you keep stacking workarounds to make Flow do something it wasn’t designed for.

Do I need a developer for Flow?

Often not. Merchants build many workflows themselves. A developer helps when the task crosses into other systems or needs custom logic.

Conclusion

In the Shopify Flow vs custom app decision, start with Flow for anything that is “when X, do Y” inside your store, and move to an app when reliability, volume, outside systems or custom screens come in. The two can work together, and the best answer is often both. Write the task down, decide what failure costs you, and let that guide the build. If you would like help with this, CYPHEX can plan and deliver it for you, with one project lead as your contact.

Stock photography provided by Pexels under the Pexels License.

Want your online store to sell more?

We can review your store and show you what to fix first to turn more visitors into buyers.

Comments

  1. Loading comments...

Leave a comment

Selling online?

Turn more visitors into orders

A faster, clearer store with better product pages and checkout. We handle Shopify and WooCommerce from setup to growth.

Step 1 of 3

Tell us what you need

Three quick steps. We reply within one business day.

What do you need help with? Pick all that apply