Shopify Flow vs Make: Which Automation Tool to Pick in 2027

Short answer: pick by where the automation has to reach

Shopify Flow and Make are different kinds of product, so the decision turns on reach more than on feature lists. Workflow automation is a set of triggers, conditions and actions that run without a person clicking through each step. Shopify Flow is Shopify's own app for building those workflows around events in your store, and its listing names Shopify as the developer (Shopify app listing). Make is a separate visual automation platform that connects Shopify to other apps and services.

Settle one fact first. Make is the renamed Integromat. Make's announcement page says Integromat evolved into Make, which it calls the name of its brand, business and flagship platform, and it says support for Integromat would end in 2023 (Make announcement).

Our answer: start with Shopify Flow when both the trigger and the action live in Shopify or in the apps Flow lists. Evaluate Make when the flow has to reach a tool outside that list, and accept per-credit billing plus a separate platform to monitor. TL;DR: Flow handles in-store logic at no app fee on eligible Shopify plans, and Make handles cross-app flows you pay for by the credit.

Key Takeaways

• Shopify Flow suits workflows that start and finish inside Shopify or its listed apps, and it adds no app fee beyond your Shopify plan.

• Make suits workflows that must reach outside tools, but it bills per credit and runs as a separate platform you have to monitor.

• Neither tool removes the need for an owner. Someone has to read failed runs and decide exceptions.

• Shopify publishes hard ceilings, including a workflow count and a per-section execution limit, so high-volume designs need a check before you build.

• Make's error recovery is a feature you configure, while Shopify retries transient errors by default.

• Before you commit, price a realistic order volume and name the person who reviews failures.

How we evaluated these tools

We weighted six criteria against the decisions a small ecommerce operator actually makes. The weights are our judgment, not vendor data. Vendor and government figures appear only where we read them on a page we opened, and our analysis is labeled "Our read" so you can separate the two.

The weighting favors reach and error handling because those are where small stores most often pay for a wrong choice later. A flow that cannot reach a needed tool forces a rebuild, and a flow that fails silently can hold up orders. E-commerce is also a large channel. The U.S. Census Bureau reported E-commerce sales: $340.2 billion in Q2 2026 according to U.S. Census Bureau (2026), seasonally adjusted and not adjusted for price changes, equal to 17.1 percent of total retail sales. A small rule error repeats on every order it touches.

Feature matrix: what each tool publishes

The matrix uses only what each vendor's own pages state, placed side by side on the same rows. Where a page did not state a point, the cell says so rather than filling the gap.

Our read: Flow's advantage is that it sits where the orders already are. Make's advantage is reach beyond Shopify and more explicit error routing. The trade is that you own the credit math, the error routes and the monitoring.

Limits and error handling: where workflows break

The Shopify column below comes from the usage-limit and monitoring pages cited in this section. The Make column comes from Make's help and listing pages.

Shopify publishes hard limits you should plan around: Workflow limit per store: 1,000 according to Shopify (2026). The same page sets 40 wait steps per workflow, a 36-hour execution ceiling for each workflow section, and a 90-day cap on total wait time. It also limits error notifications to one per workflow version every 7 days, so repeated failures may not each raise an alert.

Retry behavior differs in kind between the two tools. Shopify retries transient errors, meaning temporary failures, until they succeed or reach a timeout. A permanent error, such as one that cannot be retried, fails the workflow. Shopify also warns that a step which keeps hitting the same transient error across runs may need reconfiguration. Make's help center says the Retry error handler stores incomplete executions and enables automatic or manual retries (Make help center). That is a design you configure, not a default you inherit.

Shopify keeps run records for 14 days after completion, and its Recent runs search reaches back only that far (Shopify monitoring guide). A longer audit trail has to live outside Flow.

Take a hypothetical store that books 1,200 orders a month and wants each new order to tag the order, post to Slack and write one row to a sheet, which is three action steps after the trigger. The Shopify Admin API names the order-creation topic ORDERS_CREATE, which is the event an outside build would listen for (Shopify developer docs). Spread over a 30-day month, 1,200 orders is 40 runs a day (1,200 ÷ 30). That is far below the workflow-count limit, but Flow's total work is still capped by API rate limits, which the usage page does not quantify. On Make, the credit rule is Credit rule: 1 credit per trigger run according to Make (2026), and each action module uses 1 credit per input bundle it processes. The design therefore costs 4 credits per order (1 trigger plus 3 actions), or 4,800 credits a month (1,200 × 4). Make's Shopify trigger also fires when an order is updated, so edits would add credits (Make Shopify integration). The listing does not state Core's credit allowance, so confirm that 4,800 credits fits before you pick a plan.

A proposed US Tech Automations workflow for holding high-value orders would be a configured design, not a live deployment. The trigger is a new order from Shopify's order-created topic. The condition checks an order value threshold you set. The action adds a hold tag and posts a review task. The output is a log row with order ID, timestamp and reviewer decision. Prerequisites are Admin API access scoped to orders and tags, a log destination you own, and a named reviewer. The human review point is that only a person releases a hold, and any step that still fails after the retry window goes to the operations lead rather than retrying indefinitely.

What it costs at a small store

Pricing checked November 13, 2026. Shopify Flow is listed as a free app with a 4.7 rating from 15,539 reviews, according to Shopify (2026). Flow carries no app fee, so the real cost is the Shopify plan you already pay for, which this comparison does not price.

Make's Shopify listing shows Core plan on Make: $10.59 per month according to Make (2026), with the Pro plan at $18.82 and the Teams plan at $34.12 per month on the same listing.

The Make figures come from the listing cited above. The twelve-month column is our arithmetic on those figures, not a published price. The listing says a free plan is available, but it does not state the allowance, and the Core credit allowance is not stated there either. The Enterprise plan has no public price on the pages we read.

Where each tool fits

Shopify Flow

Best fit: stores on eligible Shopify plans whose automations start and finish inside Shopify, such as tagging orders, routing an order for review, or alerting staff on a stock condition. The listing names integrations with Shopify Admin, Asana, Email, Google Sheets, Klaviyo, Slack and Trello (Shopify app listing).

Limitations: the published ceilings above apply, and some actions are plan-gated. Shopify's help page says the Send HTTP Request action is available on the Grow, Advanced and Plus plans, and custom partner-app tasks are limited to Plus (Shopify Flow help). The pages we read do not document a human approval step.

Implementation: install the free app from the Shopify App Store, and note that staff need Flow permissions both to open the app and to turn on workflows (Shopify Flow help). Plan a review of the Recent runs list on a fixed schedule, because the record window is short.

Make

Best fit: operators whose flows cross into outside systems and who will own credit math. Make's Shopify listing names triggers Watch orders, Watch products and Watch events, and actions including Create product, Create fulfillment and Adjust an inventory level, with the note that the list may be incomplete (Make Shopify integration). The listing says the app is supported and maintained by Make.

Limitations: credits are billed per action bundle, so a branching design can cost more than its trigger count suggests. Make is part of Celonis. According to Diginomica (2026), in an October 2026 article, Celonis is Make's parent company, and forthcoming capabilities will pause workflows so a person can make a decision. That means the human approval step is not a feature you can rely on today.

Implementation: connect Shopify through the app, build the scenario, and design the error route before you turn it on. Make's credit usage is visible per scenario run, so check it on a few real orders before you choose a plan.

Building it yourself, and where a proposed design fits

The alternative most buyers weigh is building the flow themselves, in Zapier, Make, n8n or in-house code. Those tools can support run histories, retries, error branches and audit evidence when they are configured. The buyer must still design and own observability, idempotency (so a retried order is not processed twice), escalation, access controls and maintenance. Our read is that the hard part is rarely the first trigger. It is the failure path six months later.

A proposed US Tech Automations design for refund approvals would be configured differently from a standard build. The trigger is a refund event. The condition checks a refund amount you set. The action posts an approval request to a named Slack channel. The output is a logged decision with the approver's name and time. Prerequisites are API access for refunds and order reads, a Slack channel with a named approver, and a retention rule for the log. Review points: a person approves every refund in this design, a transient Slack failure is retried, and a permanent error, such as a deleted channel, stops the run and alerts the owner.

Who this is for

Shopify Flow fits an owner or operations lead whose automations start and end inside Shopify and who can name the person who reads failed runs. Make fits a lead whose flows cross into outside systems and who accepts per-credit billing and a separate platform to monitor.

Red flags: you cannot name an owner for failed runs; your flow needs an approval step nobody has designed; or you have not estimated credits per order before choosing a plan.

When NOT to use US Tech Automations: if every automation you need is one in-store rule, such as tagging orders over a threshold, Shopify Flow on your existing plan is simpler and adds no app fee. If you need one app-to-app connection with no error branches, a native integration or Make's free plan can handle it without a designed review step. If you already run engineering with logging, idempotency and on-call coverage, your own code may cost less to operate than a managed design.

If you are weighing Zapier as well, our Zapier alternatives guide for Shopify stores covers those options separately.

Glossary

• Trigger: the event that starts a workflow, such as a new order.

• Action: a step that changes data or sends a message.

• Condition: a rule that decides whether later steps run.

• Transient error: a temporary failure that Shopify retries until it succeeds or times out.

• Permanent error: a failure that cannot be retried, so the workflow fails.

• Credit: Make's billing unit, consumed by trigger runs and by action modules per bundle.

• Incomplete execution: a stored Make run that can be retried after an error.

• Idempotency: designing a step so a repeated run does not double-process an order.

Decision checklist

• Confirm every trigger and action sits inside Shopify or a Flow-listed app. If one does not, evaluate Make.

• Name the person who reads failed runs each week, before you build.

• Check that your Shopify plan supports the actions you need, such as HTTP requests on Grow and up.

• For Make, estimate credits per order and confirm the plan allowance before you buy.

• Decide where run logs live, since Shopify's run record window is short.

• Name every human approval point in writing before the flow goes live.

Questions buyers ask before they switch

Is Shopify Flow free to use?

Yes, Shopify Flow is a free app on the Basic, Grow, Advanced and Plus plans, but your Shopify plan itself is a separate cost (Shopify Flow help).

Can Make replace Shopify Flow entirely?

Make can run Shopify-triggered flows through its Shopify app, but most stores keep Flow for in-store rules because Flow adds no app fee.

Which tool handles failed steps better?

Neither is hands-off: Shopify retries transient errors until they succeed or time out, and Make's Retry error handler stores incomplete executions for automatic or manual retries.

Does Make cost more than Flow?

Usually, yes, because Make is a separately billed platform with paid plans, while Flow is a free app on eligible Shopify plans.

Do I need a developer?

For single in-store rules, no. For cross-app flows with error routes and stored credentials, plan for someone who owns the build and its upkeep.

What if we already use Zapier?

Keep it until you have measured run volume and error rates, and then compare the options on those numbers.

The bottom line

Pick Shopify Flow when the work stays inside Shopify and you have someone to read failed runs. Pick Make when the flow must reach outside tools and you will track credits from the first week. Before you commit to either route, see how this workflow is configured so you can compare the approval and logging design against your own order volume.