What Shopify Flow does well
Shopify Flow is Shopify's own automation app, free on the Basic, Grow, Advanced, and Plus plans. In plain terms, it runs rules triggered by store events within Shopify and connected apps: when something happens (an order is created, a variant sells out, a return is requested), check a condition, then take an action (add a tag, hold fulfillment, send an internal email). It can also run on a schedule.
That covers a lot of real eCommerce work. Flow lives where your orders already are, it is maintained by Shopify, and a reasonably technical person on your team can build and change workflows from the Shopify admin. Third-party apps such as MESA offer similar rule-based automation with their own templates. For many brands, these tools are the right first stop.
When Flow or a single app is the right answer
If the workflow looks like “when X happens in Shopify, do Y,” you probably do not need a custom system, and you do not need Cadence Ridge. Typical examples:
Hold and tag risky orders
When Shopify's order risk analysis comes back high, tag the order and hold fulfillment so someone checks it before it ships.
Unpublish out-of-stock products
When a variant sells out, unpublish the product or email the merchandiser, and publish it again when stock returns.
Tag customers for segments
Tag first-time buyers, wholesale accounts, or customers who bought a specific product, so a segment or a connected app can pick them up.
Alert the team on specific orders
Send an internal email when an order includes a pre-order item, a fragile product, or a shipping method that needs special handling.
Flag return requests
When a return is requested, tag the order and notify the person who handles returns, so nothing waits in the admin unseen.
The same goes for single-purpose apps. If a returns app, a subscription app, or your helpdesk already does the job inside its own product, configure it well and move on. Paying for a build that duplicates a tool you already own is money spent twice.
When a workflow outgrows Flow
The line is rarely about Flow being weak. It is about the shape of the work. Flow is built to react to one event and act on it. Trouble starts when the job is really about comparing systems, catching what doesn't match, and deciding what to do about it. That is common once a brand runs a 3PL, Klaviyo, a helpdesk, and a spreadsheet or two next to Shopify. Typical examples:
Reconcile 3PL shipments against Shopify
Compare what the 3PL says it shipped with what Shopify says was fulfilled, every day, and put each mismatch in front of a person with the order details attached.
Refunds that need a decision
Pull the ticket from Gorgias, the order from Shopify, and the return receipt from the 3PL. Small, clear cases move ahead; anything over the limit you set waits for a person to approve.
One weekly report from five tools
Shopify, ad platforms, Klaviyo, and the 3PL in one view, with the gaps between sources flagged instead of averaged away. See eCommerce reporting.
Orders into NetSuite or accounting
Post orders, refunds, and fees to the ERP or books, and queue the ones that fail a check (unknown SKU, tax mismatch, duplicate) instead of posting them wrong.
Inventory across channels and a purchasing sheet
Line up Shopify, the 3PL count, and the purchasing spreadsheet, flag drift, and draft a purchase order for someone to review before it goes out.
Notice what these share: data from more than one tool, a check on whether that data agrees, a queue for the cases that don't, and often a person who approves before anything changes. You can sometimes stretch Flow to cover parts of this, but you end up maintaining a fragile chain of workflows, webhooks, and spreadsheets that only one person understands.
The decision checklist
Score the workflow you have in mind against each row. If most answers fall under “Flow or one app,” start there. If two or more fall under “custom automation,” a custom system is worth scoping.
| Factor | Flow or one app is usually enough | Custom automation is worth scoping |
|---|---|---|
| Where the work happens | Inside Shopify, or Shopify plus one app with a ready-made connection. | Across tools: 3PL, Klaviyo, Gorgias, NetSuite, Google Sheets, ad platforms. |
| Reconciliation and exceptions | One event, one rule, one action. Nothing to compare. | Two sources must agree, and the mismatches need to land somewhere useful. |
| Human approval | No sign-off needed, or a tag and a hold are enough. | A person approves before money moves, a customer hears back, or a record changes. |
| Volume | Any volume, as long as each run is simple. | High volume with many edge cases, where manual cleanup eats hours. |
| Who maintains it | Someone on your team who is comfortable editing workflows in the admin. | Nobody in-house wants to own logic that spans several tools and their APIs. |
| Cost of failure | A missed tag or late email is annoying, not expensive. | A silent failure means wrong refunds, oversold stock, or books that don't close. |
Two of these rows deserve a closer look, because they are the ones brands underestimate.
Who maintains it
Every automation needs an owner. A Flow workflow is easy to edit, which is good, but it also means anyone with access can change it, and nobody notices when it stops matching how the team works. Before building anything, name the person who will check that it still runs correctly next quarter.
Cost of failure
Ask what happens on the day it breaks quietly. If the answer is “a tag is missing,” Flow is fine. If the answer is “we refunded the wrong orders” or “we oversold a launch,” you want logs, alerts, and a person reviewing exceptions, whichever tool runs it.
You can use both
This is not either-or. Most brands that need a custom system should keep their Flow workflows. Flow keeps handling the simple, in-store rules. The custom system handles the cross-tool work: pulling data from the 3PL, Klaviyo, or NetSuite, reconciling it, and routing exceptions to a person. On the Grow, Advanced, and Plus plans, Flow can also send HTTP requests to outside services, which is one way the two can hand work to each other.
When Cadence Ridge builds the custom side, it is designed to:
- Run in accounts your brand owns, so you are not locked into us.
- Keep a person in charge of refunds, customer messages, and anything that needs judgment.
- Log every run and alert someone when a step fails, instead of failing silently.
- Start with one workflow, scoped in writing, before anything bigger.
Scope and starting prices are on the pricing page, and what automation costs covers what moves the number. To check whether a build would pay for itself at all, run your numbers through the ops cost calculator. For the most common cross-tool case, see eCommerce reporting automation.
A quick way to decide
Pick one workflow that annoys your team every week and answer three questions:
- Does it touch any tool besides Shopify?
- Does someone have to compare two numbers or lists to do it?
- Would a mistake cost money or a customer?
Three “no” answers: try Flow first. Two or three “yes” answers: that workflow is a good candidate for a custom system, and a good one to bring to an audit.