This is not a feature-list war. Shopify talks to both. The question is cost per order, how ugly the branches are, and whether your staff will ever open the editor.
Stay on Zapier when
- The store already has working Zaps and the team knows Zap History.
- Each order is one contact, one tag, one notification. No line-item loop.
- You need an app Zapier supports well and Make’s Shopify app is weaker for that action.
- Volume is modest and the task bill is not the reason you are reading this.
Zapier is faster to a first green run. For a founder who will not maintain a 20-module scenario, that matters more than “Make is cheaper per operation.”
Move to Make (or start there) when
- You must walk line items (SKU to Airtable, kit components, per-item fulfillment flags).
- One order fans to CRM + accounting + warehouse + a Google Sheet, with routers and aggregators.
- Operations per month make Zapier’s task math painful. Make’s operations are usually cheaper at that shape.
- You need error handlers that retry a single module without replaying the whole Zap.
Make is not “more professional.” It is a better graph when the graph is actually a graph.
The Shopify-specific traps
Customer vs order vs checkout
Guest checkout, draft orders, and POS do not all send the same customer payload. A Zap that “creates a GHL contact from customer email” is empty on guest orders unless you take email from the order object. I have rebuilt this twice; it shows up as “Shopify → CRM is on but sales sees nobody.” Details in the empty-bundle note if you are on Make: why scenarios return [].
Line items
Zapier can loop with some patterns; it gets expensive and hard to read. Make’s iterator is the honest tool. If your “done” includes “every SKU in the order is a row,” budget Make.
Refunds and edits
Paid, partially refunded, and edited orders are different events. One Zap on “new order” will not keep Xero or Airtable honest. You need the update/refund topic or a scheduled reconcile. Cheap builds skip this. Then the catalog and the invoices disagree — the finance case on Work is that story with Stripe; Shopify is the same idea.
I do not migrate Zapier → Make for sport. If the Zap is readable and the bill is fine, we patch it. If you are paying for tasks that are really line-item loops, we move that slice to Make and leave the simple Slack Zaps alone. Hybrid is allowed.
What to send if you want a recommendation
App list (Shopify plus CRM / Slack / sheets / accounting). Rough orders per month. Whether line items matter. A screenshot of the current Zap or scenario, even if it is half-broken. I will say stay, move, or split — and a timeline. I will also say “don’t automate this SKU mess yet” if the catalog is the real problem.
Shopify flow, not sure which platform?
Send the stack and a sample order. I’ll say Zapier, Make, or both.