DEV Community: Alexandr M.

What the Built for Shopify Badge Certifies, and What It Doesn't

Alexandr M. — Wed, 30 Sep 2026 07:48:15 +0000

If you build Shopify apps, the Built for Shopify badge is a status you may be working toward, and one your users use to shortlist apps. This write-up goes through what the published criteria certify (speed limits and a traction floor), how the badge affects App Store search ranking, and what it leaves out. The original has an interactive verdict table; here it is a plain table.

Everything below was read on Shopify's own pages on September 12, 2026 unless a different date is given.

The quick verdict

Use the badge to shorten a list, not to make the final call. Shopify's help page for merchants describes badged apps as tested for performance, design and integration. For an app that renders on a storefront, the badge shows it reduced the storefront Lighthouse score by no more than 10 points in Shopify's own before-and-after test, so measuring your own store before and after installing still applies.

An app can't qualify until it has 50 net installs from active paid-plan stores and five reviews, and badged apps rank higher in App Store search, so a top result is partly the badge's effect. Fit, pricing and support stay your checks, because none of the Shopify pages on the badge that were read on September 12, 2026 promises them.

Situation	Answer	Why
Two apps do the job equally well, and only one carries the badge	Take the badged one	Shopify's merchant help page describes badged apps as tested for performance, design and integration
The app adds something to the storefront, such as a widget or a popup	Weigh the badge, then measure	The badge shows the app met the 10-point storefront Lighthouse limit in Shopify's own test; your own before-and-after check shows what it does to your store
The app that does the job best has no badge	Keep it on the list	An app can't qualify before it has 50 net installs from active paid-plan stores and five reviews
Picking from the top of App Store search	Don't treat rank as proof	Shopify's documentation says badged apps appear higher in search rankings
You need to know about fit, price or support	Check those yourself	Neither Shopify's merchant help page nor its developer overview, read September 12, 2026, promises any of the three

What the badge certifies

It certifies that an app passed Shopify's own testing for performance, design and integration, according to Shopify's help page for merchants. Shopify calls the underlying status the highest level of recognition an app can reach. On September 12, 2026, the App Store listed 1,654 badged apps, a live count, not a fixed figure.

Built for Shopify is a status Shopify grants to apps in its App Store, and the badge is how that status shows up to merchants. In the Built for Shopify documentation, Shopify writes:

Built for Shopify status is the highest level of recognition and achievement that an app can reach.

For merchants, Shopify's Help Center section on the Built for Shopify badge describes badged apps as having passed its testing across three areas: performance, design and integration. The badge appears on an app's card wherever that card shows up in the App Store, and search and category pages carry a Built for Shopify filter that narrows the results to badged apps.

How common is the badge? On September 12, 2026, Shopify's Built for Shopify collection listed 1,654 apps. That is a live count, not a fixed figure, and the page does not state how many apps the App Store holds in total, so it cannot tell you what share of apps carry the badge. Neither the requirements page nor Shopify's Partners update publishes that share.

For a sense of what badged listings look like, the Judge.me and StoreSEO listings both showed the badge when checked on September 13, 2026. That is a dated snapshot of two listings, not a recommendation and not a complete list.

What an app has to pass to earn the badge

An app earns the badge by meeting Shopify's published requirements. Shopify publishes the bar on its Built for Shopify requirements page, and two groups of criteria on it are worth pulling apart: traction and speed.

Can a new app carry the badge?

Only once it clears the traction floor. To qualify, an app needs:

At least 50 net installs, counted only from active shops on paid plans.
At least five reviews.
A minimum recent rating in the Shopify App Store. The requirement exists, but none of the three sources checked (the requirements page, the shopify.dev overview and the Help Center section on the badge) gives the number behind it.

That makes the badge partly a signal of traction, not only of quality. However carefully a team builds an app, it cannot carry the badge until it clears those counts.

What the speed thresholds actually measure

For the status, an app that touches the storefront must not lower its Lighthouse score by more than 10 points in Shopify's own before-and-after test. The LCP, CLS and INP limits of 2.5 seconds, 0.1 and 200 milliseconds measure the app's own admin screens, and shipping-rate apps must answer within 500 ms at p95.

Threshold	Limit	What it measures	Applies to apps that
Largest Contentful Paint (LCP)	2.5 seconds or less	Loading speed of the app's own pages inside the Shopify admin	Run inside the Shopify admin
Cumulative Layout Shift (CLS)	0.1 or less	Visual stability of the app's admin pages	Run inside the Shopify admin
Interaction to Next Paint (INP)	200 milliseconds or less	Responsiveness of the app's admin pages	Run inside the Shopify admin
Storefront Lighthouse performance score	Reduced by no more than 10 points	The app's effect on the storefront Lighthouse score in Shopify's before-and-after test of home, product and collection pages	Touch the storefront
Carrier rate requests	p95 of 500 ms or less, with a 0.1% failure rate	How fast and how reliably the app answers shipping-rate requests at checkout	Provide carrier shipping rates

Limits and their scope were read on the Built for Shopify requirements page (sections 2.1 to 2.3) on September 12, 2026; the home, product and collection test method comes from Shopify's storefront performance guide on shopify.dev. Each limit is a condition an app must meet for the status.

Three of the five limits measure the app's own screens inside the Shopify admin. They speak to the tool a merchant's team works in, not to what shoppers see. The other two rows reach shoppers. The storefront row is a ceiling on damage rather than a promise of speed: Shopify measures it as a weighted average of home, product and collection page Lighthouse scores before and after the app is installed. The carrier-rate row sits under checkout performance in the requirements. Because each limit covers a different kind of app, the badge should weigh differently by app:

For a reviews widget, a popup or anything else that renders on a storefront, the storefront row is the one that applies, and the badge confirms the app met it in Shopify's own test.
For a tool that lives only in the admin, the badge speaks to the merchant team's experience more than to customers'.
For an app that provides carrier shipping rates, the request row is the one that applies.

Can an app lose the badge?

Yes. As of September 2026, Shopify's developer documentation says badged apps are reviewed annually against the Built for Shopify standards, and an app can lose the status after it is granted if it fails to meet certain criteria on an ongoing basis. It states that "Apps are reviewed annually to ensure they continue to adhere to the Built for Shopify standards." A badge is a status an app keeps by continuing to qualify, not a medal it earned once.

The standard itself also moves. Shopify has changed what the badge requires more than once since it launched:

Jul 26, 2023: badges arrive in the App Store. Shopify's changelog introduced the badge with one line of meaning: "This badge means that an app has met our high standards for quality and performance."
Dec 11, 2024: new design requirements added. Shopify added new design requirements to the requirements page, including that an app's UI "should demonstrate a good faith effort to leverage common UX best practices and meet a high bar for design quality." Apps needed to meet that requirement starting in January 2025.
Aug 1, 2026: updated requirements for fulfillment services apps. Shopify updated three requirements for fulfillment services apps: the required completion rate for assigned fulfillment orders, the response window and response rate for fulfillment requests, and the response window for cancellation requests. Apps in other categories aren't affected, and the entry does not state the new figures.

In practice, check the badge on the live App Store listing on the day you install, not in a roundup or a screenshot from last year.

Do badged apps rank higher in App Store search?

Yes. Shopify's developer documentation says Built for Shopify apps appear higher in App Store search rankings, above other boosted apps, and that the boost isn't exclusive to them. In Shopify's words:

Built for Shopify apps appear higher in Shopify App Store search rankings.

The same documentation page adds that Built for Shopify apps are ranked higher than other apps with search ranking boosts, and that a search ranking boost isn't exclusive to Built for Shopify apps. The ranking lift is not the only placement the status brings. Shopify names these surfaces for badged apps:

Additional promotion in the App Store, and eligibility for promotion on what Shopify calls other key merchant surfaces.
Recommendations in the App Store homepage header, according to a Shopify Partners blog update on Built for Shopify read in September 2026.
Priority placement in Recommended for you sections across category pages, according to the same update.

The same update tells developers that badged apps see "an average increase of 49% new installs in just 14 days of achieving status", which is Shopify's own average across apps, addressed to developers, not a forecast for any single app and not a measure of quality.

Search order is not independent evidence. A badged app sits near the top partly because it is badged, and its install count can climb partly because of that placement. An unbadged app near the top may hold a search ranking boost from another Shopify achievement. The badge filter shortens a list; the choice still rests on what the badge does not measure.

What the badge doesn't tell you

Nothing in Shopify's merchant help page, developer overview or blog post on Built for Shopify, read September 12, 2026, promises that a badged app fits a given store, is priced well for it or keeps good support. Shopify's help page names merchant reviews as one of the best ways to judge fit.

Question	What the badge tells you	Where to look instead
Will it slow the storefront?	If the app touches the storefront: it met the 10-point Lighthouse limit in Shopify's before-and-after test of home, product and collection pages	Your own before-and-after measurement, badge or not
Is the app established?	At least 50 net installs from active shops on paid plans, and at least five reviews	Recent reviews, for how the app behaves now
Does it do the exact job?	Nothing found in the Built for Shopify pages read	Reviews from merchants whose stores look like yours
What will it really cost?	That features gated by a plan must be disabled and clearly indicated in the app	The app's own pricing terms, before installing
Will support hold up?	Nothing on the pages read; status is reviewed annually	Recent reviews and how problems in them were handled
What store data can it read?	Not covered by the criteria in this article	Whether the badge means an app is safe with customer data

A cell that reports nothing found on the pages read records an absence in that reading, not a rule Shopify publishes.

For the question the badge cannot settle, whether the app does a particular job, Shopify itself points elsewhere. From its Help Center:

Reviews from other merchants are one of the best ways to evaluate if an app is right for your business.

Reviews are the start of the check, not the whole of it. The check for evaluating an app before you install it covers the permissions an app asks for, its pricing model, support signals and the cost of leaving.

What was looked for and not found, all read on September 12, 2026:

The number behind the minimum recent rating: not found on the Built for Shopify requirements page, the Built for Shopify overview on shopify.dev, or the Help Center section on the Built for Shopify badge.
A promise that the badge means fit for a store, fair pricing or long-term support: not found in that Help Center section, the shopify.dev overview, or Shopify's blog post on Built for Shopify apps. The blog post does say the badge "guarantees that an app has been built to Shopify's highest standards" and names value alongside speed, security and usability, but it promises a standard, not a fit, a price or support.
An official share of App Store apps carrying the badge: not found on the requirements page, the Shopify Partners update on Built for Shopify, or the App Store's Built for Shopify collection.

If Shopify publishes any of these, the absence is what changes.

When an app without the badge is the right pick

Pick an unbadged app when it does the job better, including when it lacks the installs and reviews the traction floor asks for. A missing badge does not say why it is missing. An app can be missing the badge for any of these reasons, and the first two say nothing about the app's quality at all:

It has not applied. The status is something a developer applies for.
It has not reached the traction floor. Without 50 net installs from active paid-plan shops and five reviews, it cannot qualify.
It is waiting out a suspension. Shopify's developer documentation says an application that fails the same criterion three times in a row is suspended, and the developer cannot apply again for three months.
It lost the status. An app that stops meeting certain criteria on an ongoing basis can lose a badge it was granted.

Familiar names can lack the badge too: when checked on September 12, 2026, the Klaviyo and TikTok App Store listings showed no Built for Shopify badge. No conclusion is drawn about why.

A missing badge does not mean a missing speed limit. Shopify's performance guide for app developers says an app published in the Shopify App Store "must not" reduce storefront Lighthouse performance scores by more than 10 points, Shopify's App Store best practices say an app "shouldn't", and the Built for Shopify requirements list the same ten-point limit as a must-not criterion. What the badge adds is confirmation that the app met the criteria Shopify evaluates for the status, including this limit for an app that affects the storefront directly, which Shopify checks with a before-and-after Lighthouse test. Run the same kind of check on your own storefront, before you install and again after.

The bottom line

Use the Built for Shopify badge to shorten your list, not to make the final call. It shows an app met Shopify's performance, design and integration bar, including, for storefront apps, the ten-point Lighthouse limit in Shopify's test, and it lifts the app in App Store search. Fit, price and support stay your checks.

Filter for the badge, then decide on fit. Among apps that do the job equally well, take the badged one. When the app that does the job best has no badge, don't discard it: read its recent reviews, check its pricing terms, and measure the storefront before and after installing it.

Frequently asked questions

What does the Built for Shopify badge mean?

It means the app holds Built for Shopify status, which Shopify's developer documentation calls the highest level of recognition an app can reach. Shopify's help page for merchants describes badged apps as tested for performance, design and integration. It is a quality bar with a traction floor attached, not a ranking of which app fits a store best.

How does an app get Built for Shopify status?

A developer applies, and the app must meet Shopify's published requirements. Those include at least 50 net installs from active shops on paid plans, at least five reviews, a minimum recent rating, and speed limits for its admin screens, its storefront impact and, for shipping-rate apps, its rate requests. Apps that hold the status are reviewed annually.

Do Built for Shopify apps rank higher in the App Store?

Yes. Shopify's developer documentation states that Built for Shopify apps appear higher in App Store search rankings and receive additional promotion, and a Shopify Partners update read in September 2026 extends their recommendations to the App Store homepage header and to Recommended for you sections. A badged app's high search position is partly the badge's own effect, not independent proof of fit.

Can an app lose its Built for Shopify badge?

Yes. As of September 2026, Shopify's developer documentation says apps with the status are reviewed annually, and an app can lose the status after it is granted if it fails to meet certain criteria on an ongoing basis. The requirements also change over time, so check the badge on the live App Store listing on the day you install.

What is the minimum rating for Built for Shopify?

The requirements say an app must meet a minimum recent app rating threshold in the Shopify App Store, but none of the three pages checked on September 12, 2026 publishes the number: the requirements page, Shopify's Built for Shopify overview and its Help Center section on the badge. Treat any specific star figure quoted elsewhere as unconfirmed by those pages.

How many apps have the Built for Shopify badge?

On September 12, 2026, the App Store's Built for Shopify collection listed 1,654 apps. That is a live count rather than a fixed figure, and the page does not show how many apps the App Store holds in total, so it gives no share. That page, the requirements page and Shopify's Partners update were read that day, and none of them publishes an official share.

Will a Built for Shopify app slow down my store?

For an app that touches the storefront, the requirements say it must not reduce the storefront Lighthouse performance score by more than ten points; Shopify's storefront performance guide describes a before-and-after test of home, product and collection pages. The badge's LCP, CLS and INP limits cover the app's admin screens instead. Measure your own storefront before and after installing, badge or not.

Should I avoid Shopify apps without the badge?

No. A missing badge can mean the developer has not applied, the app does not yet have 50 net installs from active paid-plan shops and five reviews, or it failed the same criterion three times in a row, which bars reapplying for three months. Klaviyo's and TikTok's listings showed no badge on September 12, 2026. Judge unbadged apps on fit and reviews.

How do I find Built for Shopify apps in the App Store?

Look for the Built for Shopify badge, which appears on an app's card wherever that card shows up in the App Store. On search and category pages, Shopify's Help Center says you can use the Built for Shopify filter option to display only certified apps. Then read merchant reviews, which Shopify calls one of the best ways to judge fit.

Does the Built for Shopify badge guarantee good support or fair pricing?

No page checked on September 12, 2026 promises either: not Shopify's Help Center section on the badge, its Built for Shopify overview, or its blog post, which says the badge "guarantees that an app has been built to Shopify's highest standards" and lists value with speed, security and usability, promising no price. The published criteria cover performance, design, integration and traction, so check pricing terms and recent reviews yourself.

What do the LCP, CLS and INP limits in Built for Shopify measure?

They measure the app's own pages inside the Shopify admin: Largest Contentful Paint of 2.5 seconds or less, Cumulative Layout Shift of 0.1 or less, and Interaction to Next Paint of 200 milliseconds or less. They speak to how the tool performs for a merchant's team, not to the storefront; apps that touch the storefront face a separate ten-point Lighthouse criterion.

When did the Built for Shopify badge start?

Shopify's changelog introduced Built for Shopify badges in the App Store in a post dated July 26, 2023, describing the badge as meaning an app has met Shopify's high standards for quality and performance. Since then, Shopify added design requirements in December 2024, some required from January 2025, and a changelog entry dated August 1, 2026 updated three requirements for fulfillment services apps.

Originally published at shopify.ecom-store.pro.

Disclosure: this article is AI-generated.

Can you use a Google Sheet as a Shopify webhook URL? What has to sit in between

Alexandr M. — Wed, 30 Sep 2026 07:48:09 +0000

If you want Shopify events to land in a Google Sheet, the webhook URL field looks like the obvious place to paste a spreadsheet link. It is not that simple: each event arrives as a request that something has to receive and answer first. This post covers the two receivers that work (a connector or an Apps Script web app), the response-code trap with Apps Script, and the Shopify Flow route that skips the webhook entirely. Everything below was checked against the Shopify and Google pages linked inline, read September 25, 2026.

Short answer

Not directly. Route the event through a connector that writes the row (Zapier on paid plans, Make or n8n) or a Google Apps Script web app you test first. On Basic, Grow, Advanced or Plus, Flow's own Add row to spreadsheet action writes the row without a webhook URL.

Caveats at a glance:

Zapier's webhook trigger. Webhooks by Zapier isn't available on Zapier's Free plan.
Apps Script replies. A TextOutput reply from Apps Script is a redirect, not a 200; test that the admin webhook survives.
A receiver that keeps failing. Repeated non-200 responses get the admin webhook subscription deleted automatically.
Flow's own Sheets action. On Basic, Grow, Advanced or Plus, Flow's Add row to spreadsheet action writes the row without a webhook URL.
Flow's Send HTTP request. It needs Shopify Plus, Advanced or Grow; it counts 2XX or 3XX as success.
Self-hosted n8n. Shopify lists localhost among the URLs webhooks can't be returned to.

What a Shopify webhook needs at the other end

An admin webhook is created under Settings > Notifications > Webhooks: you pick an event, a format (JSON or XML) and a URL. The Shopify Help Center tells you to enter the URL "where you want data to be stored", which is why a spreadsheet link looks like the right answer. Shopify then sends the event's data to that address, so something there has to take the request.

None of the Google pages read for this post describes a spreadsheet taking an incoming webhook by itself (see the boundaries at the end). Google calls the Sheets API "a RESTful interface that lets you read and modify a spreadsheet's data", which is a way for code to work with the sheet. An Apps Script web app can accept an incoming request through its doPost function, so the sheet sits at the end of the route, behind a go-between.

The no-code route: a connector that writes the row

Zapier documents both halves. A Zap with a webhook trigger gets "a brand new URL for your use" from Webhooks by Zapier; you paste it into Shopify's URL field, and it triggers on a POST, PUT or GET request. The Zapier Google Sheets action Create Spreadsheet Row adds the row, and Create Multiple Spreadsheet Rows handles line items.

Webhooks by Zapier isn't available on Zapier's Free plan, only on Professional, Team and Enterprise.

Make and n8n cover both halves too. Make's custom webhooks "allow you to create a URL to which you can send any data", and its Google Sheets module has an Add a Row action that "Appends a new row to the bottom of the table." n8n's Webhook node can "receive data from apps and services when an event occurs", and its built-in Google Sheets node has an Append Row operation that creates a new row.

If you self-host n8n, keep it off your own machine's address: Shopify lists localhost among the URLs webhooks can't be returned to.

The build-it route: a Google Apps Script web app

If you would rather write a little code than add another service, deploy an Apps Script project as a web app. It gets its own URL, and Google's web apps guide describes what runs when a request arrives:

"When a program sends the app an HTTP POST request, Apps Script runs doPost instead."

Google for Developers, Apps Script web apps guide, read September 25, 2026

The request body reaches the function through its e parameter, in e.postData.contents, and doPost has to return an HtmlOutput or TextOutput object. Writing the row is a separate step with Apps Script's spreadsheet service; none of the Apps Script guides read for this post pairs doPost with SpreadsheetApp.appendRow, so expect to combine the web apps guide with Apps Script's Sheets guide.

Choose Execute the app as me so the script writes as you, and open access to anyone, signed in or not. Google's deployment reference calls that access level ANYONE_ANONYMOUS, "Any user, logged in or not". It is the only one of its access levels that doesn't require a login; the level named ANYONE means "Any logged in user".

Then test before you rely on it. Google says content returned by its Content service "is redirected to a one-time URL at script.googleusercontent.com", so a TextOutput reply is a redirect, not a 200. For app webhooks, Shopify's developer docs treat "any response outside the 200 range, including 3XX codes" as an error.

The admin webhook page read for this post says nothing about redirects, but it does say a destination that repeatedly returns a non-200 status gets the subscription automatically deleted. Place a test order, then check that the row appeared, then look for the webhook again after later orders. Shopify removes a failing webhook without an email.

Does Shopify Flow change the answer?

It adds a route with no webhook at all. Flow's Add row to spreadsheet action "adds a single row of data to a Google Sheets spreadsheet": Flow calls the Google Sheets API itself. You connect Flow to a Google account with edit access to the sheet first, and the action works with any trigger. Flow itself is a free app on the Basic, Grow, Advanced and Plus plans.

Flow's Send HTTP request action changes the sender, not the receiver: its URL field is simply "The URL of the server to which the HTTP request is sent.", so the other end is still a connector trigger or an Apps Script web app. Send HTTP request is only available on the Shopify Plus, Advanced or Grow plans.

What Send HTTP request does change is the success rule. Flow marks a request as a success on a 2XX or 3XX response; on 4XX, 5XX and 429 errors it does what you configured: retry for up to 24 hours, fail the run, or ignore the error.

Set beside the redirect above, the Send HTTP request page doesn't say whether Flow follows a redirect. Whether a Send HTTP request wrote the row is still yours to confirm, and a failed request shows up in Flow's run log, where you can retry the run.

What was looked for and not found

Read September 25, 2026.

A spreadsheet receiving a webhook by itself: Google's Sheets API concepts, values and authorizing guides, the Apps Script web apps and quotas pages, and the Google Sheets product page.
One page pairing doPost with appendRow: the Apps Script Sheets, web apps and triggers guides, and the Apps Script product page.
Redirects: Shopify's Help Center pages on admin webhooks and Flow's Send HTTP request.

Originally published at shopify.ecom-store.pro.

Disclosure: this article is AI-generated.

Shopify's ChatGPT and Claude Connectors: What They Expose and Where the Limits Are

Alexandr M. — Wed, 30 Sep 2026 07:24:09 +0000

If you build tools around AI assistants, or you are deciding whether to let one touch a production store, the useful question is not "does it work" but "what exactly can it call, and what is walled off". Shopify's Help Center now documents three official integrations for ChatGPT, Claude and Perplexity.

This write-up walks through what each connector exposes, the action tiers (read, write, blocked), the batch limits, how access and data ownership work, and what is still undocumented. The connector facts below come from Shopify's Help Center pages as read on September 13-14, 2026.

The original article carries an interactive step-by-step safety checklist with saved progress; here it is a plain list in the section "Connecting it safely".

As of September 2026, Shopify's Help Center documents three ways to run a store from a chat window: the Shopify plugin for ChatGPT, the Shopify connector for Claude and the Shopify connector for Perplexity. All three connect to a store you own, and the section that documents them is explicit that shoppers who buy through AI assistants are a different topic.

That makes this three decisions rather than one: which connector, given the assistant you already pay for and whether the store exists yet; what to let it change, since some actions are read-only by design and some are blocked outright; and what stays in your admin whatever you approve.

The quick verdict

Pick by what you already have: the assistant you pay for and whether the store exists. Every connector manages a store you own with the same core. It can create and change products, collections and inventory, create percentage-off discount codes and change an unpublished theme, and it reads orders, customers and analytics without changing them. The full action table is further down. The capability gaps are the few actions named in that section and Perplexity's text-only answers.

Situation	Answer	Why
You already pay for ChatGPT and run a store	Shopify plugin for ChatGPT	Manages your store from the chat and can also build one from a preview; no extra Shopify fee
Your team works in a Claude workspace	Shopify connector for Claude	The same store actions except attaching a photo in the chat, plus Claude's own access controls per conversation or workspace owner
You use Perplexity and already own a store	Shopify connector for Perplexity	Manages an existing store only, with text-only answers; no preview and no claim
No store yet	A ChatGPT or Claude preview, then claim it	The claimed store starts a free trial, currently 4 months as of September 2026; Perplexity can't build one
You want it to refund, cancel, publish a theme or change payments, taxes or domains	Your Shopify admin	Those actions are blocked even when you approve write access

Key takeaway: Pick the connector for the assistant you already pay for. The ChatGPT plugin and the Claude connector manage a store you own and can build one from a storefront preview, with no extra Shopify fee, while the Perplexity connector manages an existing store only. Refunds, order changes and your live theme stay in your admin.

What are Shopify's ChatGPT, Claude and Perplexity connectors?

Shopify documents three official integrations: the Shopify plugin for ChatGPT, the Shopify connector for Claude and the Shopify connector for Perplexity. All three manage a store you already own; as of September 2026, ChatGPT and Claude can also build one from a storefront preview. None is on the App Store.

The names are Shopify's own (plugin for ChatGPT, connector for Claude and Perplexity) and they matter when you search, because none of the three is listed on the Shopify App Store. The Help Center pages for the ChatGPT plugin, the Claude connector and the Perplexity connector each say you install the integration directly from the AI tool, and Shopify asks you to use that official integration rather than create an API access token or build your own.

"The Shopify plugin for ChatGPT and the Shopify connector for Claude can build a store from a storefront preview and manage a store that you own. The Shopify connector for Perplexity manages an existing store only."

Shopify Help Center, Connecting AI tools to your store

Where the three differ is in what happens before a store exists, and in how answers come back:

Connector	Manages a store you own	Builds a new store from a preview	How analytics come back	Assistant subscription paid to
Shopify plugin for ChatGPT	Yes	Yes: preview, then claim	Tables and charts	OpenAI
Shopify connector for Claude	Yes	Yes: preview, then claim	Tables and charts	Anthropic
Shopify connector for Perplexity	Yes	No: existing store only	Text only	Not stated on its Shopify page, as read on September 13, 2026

Source: Shopify Help Center pages for each connector, read September 13-14, 2026. Every connector also works through the Shopify Admin API for pages, blogs, menus, metafields, markets and translations, asking you to confirm first.

For the Claude route, Shopify's own Learn With Shopify channel on YouTube walks through both halves in one 2026 video: building a store from a preview, then connecting Claude to run it day to day. It is a walkthrough, not the source for anything on this page; the limits above come from the Help Center.

Can ChatGPT or Claude build a store from a preview?

Yes. In ChatGPT or Claude you generate a storefront preview and then claim it. Claiming makes you the store owner and starts the free trial, currently 4 months as of September 2026. The tool isn't connected to the new store until you authorize access, and the preview is finished in your admin.

A preview is not yet your store. Shopify's setup page for AI-created stores says the store is created on Shopify before you have an account for it and starts as a trial store you can look at before taking ownership. Claiming connects it to your Shopify account and makes you the owner, and the free trial, currently 4 months as of September 2026, begins when you claim the store, not when it was generated.

The connection does not carry over automatically. The Help Center is explicit that a store built from a preview is a new store the tool has not yet been authorized on:

"If you created the store from a preview in an AI tool, such as the Shopify plugin for ChatGPT or the Shopify connector for Claude, then the tool isn't connected to your new store yet. Authorize access to the new store before the tool can make changes to it."

Shopify Help Center, Setting up a store created with an AI tool or vibe code partner

The preview also ships unfinished by design. Shopify's ChatGPT and Claude pages describe it as a starting point rather than a finished store, with a theme that matches the preview you chose and possibly sample content, and they tell you to review product names, descriptions, images, prices, store policies, shipping and payment settings and domain settings in your admin before you sell.

Perplexity has no preview or claim flow at all, so this route is ChatGPT and Claude only.

What these connectors are not

Three neighbouring things share the words and are not these connectors: vibe code partners that create a store for you and stay installed after the claim, agentic commerce where shoppers buy through AI assistants, and the Shopify CLI connector for developers. These connectors are for you, working on a store you own.

What it is	Who uses it	What it touches	Where it's covered
The ChatGPT, Claude and Perplexity connectors	You, on a store you own	Products, collections, inventory, orders, customers, discounts and analytics; a preview and claim for ChatGPT and Claude	This guide
Vibe code partners: Lovable, Manus, Replit, v0 by Vercel	You, before or after you have a store	Create a store for you; the partner's app stays installed after you claim it	Not covered here
Agentic storefronts, Selling on ChatGPT, the Agentic plan	Shoppers who use AI assistants	Whether your products are discoverable to AI-assisted buyers	Agentic commerce guide (linked below)
Shopify CLI connector	Developers	API access for an AI tool on a local device; not a chat, no preview or claim	Shopify Help Center

The difference from the partner route is who builds and what stays connected: a partner's app stays installed once you claim, while a store from a ChatGPT or Claude preview isn't connected until you authorize it.

The other confusion runs the opposite way: the connectors put you in the chat, agentic commerce puts your shopper there. For products discoverable to AI-assisted buyers the Help Center points to agentic storefronts, Selling on ChatGPT and the Agentic plan, and selling through AI assistants and agentic commerce has its own guide.

Developers have a fourth thing with a similar name: the Shopify CLI connector authorizes an AI tool on a local device to reach the Shopify API for a store from the command line. It is API access and nothing more: not a chat interface, and no storefront preview or claim flow.

What can a connected AI tool actually do in your store?

A connected AI tool works in three tiers. It reads orders, customers and analytics but never changes them; once you approve write access it creates and updates products, collections and inventory, creates percentage-off discount codes and changes an unpublished theme; refunds, order changes, your live theme and plan, payment, tax or domain settings stay blocked.

Shopify publishes the full table of actions for each connector: 29 actions for ChatGPT, 28 for Claude and 24 for Perplexity, as counted in the Help Center tables on September 14, 2026. The gap is the two storefront-preview actions, the claim and the sample-product actions Perplexity lacks, plus an image-upload action only ChatGPT has; the store-management core is the same on all three.

Find your task in the table, then read the tier it sits in:

Your task	What the tool does	Access	Limit
Create a product	Title, description, price, variants, options and inventory tracking	Write	none
Update a product	Title, description, status, images, variant prices or SKUs	Write	none
Change product status in bulk	Active, draft or archived, by naming products or choosing a collection	Write	Up to 50 per batch
Collections	Create manual or smart collections; update title, description, image, sort order or rules	Write	none
Inventory	Check stock per variant across locations; set a quantity at a location with a reason	Write	none
Orders	List recent orders with customer, totals, payment and fulfillment status; read one order	Read only	Up to 50 per list
Customers	Reads customer records	Read only	none
Analytics	Answers questions about sales, orders, products, customers and fulfillment	Read only	Perplexity returns text only
Discount codes	Creates percentage-off codes	Write, create only	No edits to existing codes; no fixed-amount discounts
Theme	Changes a theme that isn't published	Write	Can't edit the live theme, publish or delete one
Pages, blogs, menus, metafields, markets, translations	Works through the Shopify Admin API and asks you to confirm first	Write	No dedicated action
Refunds, cancelling or capturing orders, marking orders as paid, returns, gift cards	Nothing: these actions are blocked even when you approve write access	Blocked	Your admin only
Plan, payments, taxes, domains	Nothing: a connected AI tool can't change these settings	Blocked	Your admin only

Source: Shopify Help Center pages for the ChatGPT plugin, the Claude connector and the Perplexity connector, and the considerations page, read September 14, 2026. The rows are the same on all three connectors.

What stays blocked even with write access

Refunds, cancelling or capturing orders, marking orders as paid, returns and gift cards are blocked on every connector even when you approve write access, and so are your plan, payments, taxes and domains. The tool can change only an unpublished theme, and some actions stay read-only by the provider's design.

Money and order state are the clearest line. Shopify's considerations page for connected AI tools lists the actions that stay off limits no matter what access you approve:

"A connected AI tool can't issue refunds, cancel or capture orders, mark orders as paid, process returns, or create and adjust gift cards. These actions are blocked even when you approve write access."

Shopify Help Center, Considerations for connecting AI tools to your store

Blocked regardless of access:

Refunds, cancelling or capturing orders, marking orders as paid, processing returns, creating or adjusting gift cards
Settings such as your plan, payments, taxes or domains
Your live theme: a connected tool can change an unpublished theme but can't edit the live one, publish a theme or delete one

Two more limits sit underneath. Some connector actions are read-only by design, which the AI tool's provider controls, and Shopify says your admin is still required for payments, taxes, domains and launch readiness. The connector helps with some tasks; it doesn't replace the admin.

Why a big batch can stop halfway

Because a connected tool changes items one at a time, a large batch can stop partway, and some actions cover a limited number of items: product status changes take up to 50 products per batch and order lists return up to 50 at a time. An unfinished batch is completed in your Shopify admin.

Shopify warns that a connected AI tool changes items one at a time, so a large batch can stop partway, and that some actions cover only a limited number of items. The two published limits are the ones in the table: up to 50 products per status change and up to 50 orders per list.

The instruction for an unfinished batch is short: finish it in your Shopify admin. For a catalog of hundreds of products that means planning the work in batches you can check, rather than one long chat instruction.

Who controls what the tool can see and change?

You control access in two ways: the data access scope you approve when you install, and the permissions of the staff account the tool acts through. A user who can't edit product data can't give the tool that ability. Lowering the scope later means uninstalling, and each connector holds one store at a time.

Shopify's page on authorizing AI tool access describes two levers, the data access you approve and the user permissions of whoever operates the tool, and six rules follow from them:

Rule	What Shopify says
Data access is what you approve	The tool can read data but not change it unless you approve write access when you connect.
Never more than the staff account	Users who interact with the tool are limited by their own permissions; someone who can't edit product data can't give the tool that ability.
Some actions are read-only by design	Orders, customers and analytics are read but never changed; some actions are read-only by design, which the AI tool's provider controls.
Lowering access means uninstalling	To decrease the data access scope after you approve it, you have to uninstall the integration.
Uninstalling revokes everything	Uninstall the integration from your Shopify admin and the tool can no longer read or edit your store data.
One store per connector at a time	Each integration connects one store at a time, even if your stores are in the same organization.

The second lever is the one to plan around. The tool acts through a staff account, and that account's permissions are its ceiling, so the question before you connect is which account it should be: the owner's, or a narrower staff seat built for the job. How Shopify staff permissions are organized is the map for that decision.

On the Claude side there is one control more: its Help Center page says Claude applies its own access controls as well, so a connection can be limited to specific conversations or restricted by whoever owns your Claude workspace.

Reducing access later is not a slider. Shopify's wording is unambiguous:

"To decrease the data access scope after you approve it, you have to uninstall the integration."

Shopify Help Center, Authorizing AI tool access to your store

Where your store data goes after you connect

Once you grant access, the data the tool receives is no longer processed by Shopify, and how the AI company uses, retains or processes it isn't controlled by Shopify. Under Section 9.9 of Shopify's Terms of Service that use is your responsibility: review the tool's terms, meet your legal obligations, monitor its changes.

The considerations page draws the boundary in one sentence: after you provide access to the third-party AI tool, that data is no longer processed by Shopify, and how the tool uses, retains or processes it after it is shared isn't controlled by Shopify. That includes customer records, which the connectors read.

Responsibility follows the data. Under Section 9.9 of the Shopify Terms of Service you're responsible for your use of third-party services, including the data you share and your obligations to customers under applicable laws. Shopify names the GDPR and the CCPA as examples, not as the full list. Its page lists three things it expects of you:

Reviewing the terms and privacy policy of the AI tool that you connect to before activating the integration.
Ensuring that your use of connected AI tools meets your obligations to your customers under applicable laws.
Monitoring your store for any changes that a connected AI tool makes.

One question the section doesn't answer is training. No page in the connecting-AI-tools section read on September 13, 2026 (the considerations, authorizing-access and index pages) states whether OpenAI, Anthropic or Perplexity trains models on store data; the only statement is that Shopify no longer controls it. That makes the first duty above, reading the tool's privacy policy, the place where that answer lives.

What happens if the tool makes a wrong change?

You are responsible for the change; actions a connected AI tool takes on your behalf aren't reviewed or approved by Shopify. Shopify asks you to review any action you ask the tool to take for accuracy and to monitor your store for changes; a stopped batch is finished in your admin, and uninstalling revokes access.

Shopify's answer is blunt: if an AI tool makes an incorrect change to your store, you're responsible for that change, because actions connected AI tools take on your behalf aren't reviewed or approved by Shopify. There is no Shopify-side review between the chat and your catalog.

What the documentation gives you instead is already in your hands: reviewing any action you ask the tool to take for accuracy, monitoring your store for changes a connected tool makes, finishing a batch that stopped partway in the admin, and uninstalling the integration to end the tool's ability to read or edit anything.

Whether the tool itself keeps a change log or an undo is a question for its provider, not for Shopify: the connector pages send issues with ChatGPT, Claude or Perplexity to OpenAI, Anthropic or Perplexity AI, and issues with your Shopify account or your store to Shopify Support.

What does it cost to connect ChatGPT or Claude to Shopify?

Nothing extra on Shopify's side for ChatGPT or Claude. Standard Shopify plan pricing applies to a store you create or run through the ChatGPT plugin or the Claude connector, and you pay the assistant's subscription to OpenAI or Anthropic. The Perplexity page, as read on September 13, 2026, states no pricing terms.

Both the ChatGPT and the Claude pages answer the cost question in the same two sentences, and the answer is that Shopify's side doesn't change:

"Standard Shopify plan pricing applies to a store that you create or run this way, and there's no extra Shopify fee for using the plugin. You pay any ChatGPT subscription costs to OpenAI rather than to Shopify."

Shopify Help Center, Shopify plugin for ChatGPT

So the Shopify part of the bill is the plan you would pay anyway. For a new store from a preview, the subscription is billed after the free trial ends and you choose a paid plan; for an existing store, nothing changes. As of September 2026, Basic is $39 a month billed monthly or $29 a month on annual billing, in USD.

Which assistant tier you need is a question for the assistant's own pricing page, not the Help Center: Shopify's pages name no amounts, and the Perplexity page, as read on September 13, 2026, carries no pricing sentence at all.

Cost line	Who bills you	What Shopify's page says
Your Shopify plan	Shopify	Standard plan pricing applies; no extra Shopify fee for the ChatGPT plugin or the Claude connector
ChatGPT subscription	OpenAI	"You pay any ChatGPT subscription costs to OpenAI rather than to Shopify"
Claude subscription	Anthropic	The same sentence, with Claude and Anthropic
Perplexity subscription	Not stated on the Shopify page	No pricing sentence on the connector page, as read on September 13, 2026

Connectors vs Sidekick: do you need both?

You may well use both. Sidekick is the AI assistant inside your Shopify admin; the ChatGPT, Claude and Perplexity connectors work from outside it, and Shopify says plainly that a connector doesn't replace your admin or Sidekick. Use a connector for the tasks in the table, and the admin for everything else.

Each connector page carries a version of the same disclaimer (the Perplexity page drops the line about starting a store), and the disclaimer settles the "which one" question by refusing it:

"Your Shopify admin is the main place to manage your business. The plugin can help you start a store and handle some tasks, but it doesn't replace your Shopify admin, and it doesn't replace Sidekick, which is the AI assistant inside your Shopify admin."

Shopify Help Center, Shopify plugin for ChatGPT

The practical split is where you are working. A connector brings the tasks in the table into ChatGPT, Claude or Perplexity; Sidekick lives inside the admin, next to the settings the connectors can't touch. If you already run a store and don't work in ChatGPT, Claude or Perplexity, a connector adds a new place to do those tasks: the products, collections, inventory, discounts and analytics in the table are also managed in your admin.

Practical limits before you connect

Five limits apply first: one store per connector at a time; installation from the AI tool, never the App Store or your own API token; a desktop browser for setup; support split between the assistant's company and Shopify; and text-only answers from Perplexity. No page read on September 13, 2026 names Plus or POS.

One store at a time per connector, even if your stores are in the same organization; the action tables include switching to another store you own.
Installed from the AI tool, not the App Store. Shopify asks you to use the official integration rather than create an API access token or build your own; using one means agreeing to the Shopify API Terms.
A desktop browser for setup. Whether the plugin or connector is available on a mobile device depends on ChatGPT, Claude or Perplexity.
Support is split. OpenAI, Anthropic or Perplexity AI for issues with the tool itself, Shopify Support for issues with your account or your store.
Perplexity answers in text only. No storefront previews, tables or charts, no sample product browsing, and no way to generate a preview or claim a new store from it.

Plan and channel compatibility is a gap in the documentation rather than a rule. None of the six pages in the section read on September 13, 2026 mentions Shopify Plus or Shopify POS in the context of the connectors, so if either is your setup, the honest next step is to ask Shopify Support before you build a workflow on it.

Shopify's own pages carry no launch date for any of the three. No changelog.shopify.com or shopify.com/news entry found on September 13, 2026 names one, and the only first-party date to point to is that Anthropic's connector directory lists the Claude connector as added in April 2026, a date for the directory card, not necessarily for the feature.

What was looked for and not found. Several statements here are absences: the Perplexity page's silence on pricing, the section's silence on Shopify Plus and POS, the lack of any statement on whether the AI company trains on store data, the lack of any change log or undo for the tool's actions, and the lack of an official launch date. Each rests on the same reading: the Shopify Help Center pages for the ChatGPT plugin, the Claude connector and the Perplexity connector, the considerations and authorizing-access pages and the section index, read on September 13 and again on September 14, 2026, plus a search of changelog.shopify.com and shopify.com/news for the launch date.

Connecting it safely: seven steps

Seven steps keep a connector safe: read the tool's terms and privacy policy, pick the staff account it acts through, decide read-only or write before you approve, install from the AI tool on a desktop browser, start with a small batch and an unpublished theme, monitor every change, and know that uninstalling revokes access. Steps one to four happen before you connect and decide what the tool can ever do; five to seven are how you keep it safe afterwards.

Read the tool's terms and privacy policy. Shopify puts reviewing the AI tool's terms and privacy policy on you before activating the integration, because data you share is no longer processed by Shopify. Read its privacy policy, including what it says about retention, and accept that data shared with the tool is handled outside Shopify.
Pick the staff account it will act through. The tool never gets more than that account's permissions, so choose the account whose rights match what you want the tool to do, and check its permissions against the tasks you plan to hand over.
Decide read-only or write before you approve. The tool reads by default and changes data only if you approve write access; lowering the scope later means uninstalling the integration and reconnecting.
Install from the AI tool, on a desktop browser. The official integration is installed from ChatGPT, Claude or Perplexity, not from the Shopify App Store, and Shopify says not to build your own connection with an API token. Don't create an API access token for it.
Start with a small batch and an unpublished theme. Changes run one item at a time and product status changes are capped at 50 per batch; the tool can change only a theme that isn't published. Keep the first task within one batch of 50 or fewer items and point theme work at an unpublished copy, never the live theme.
Monitor every change and finish batches in your admin. Monitoring your store for changes the tool makes is your obligation; Shopify doesn't review the tool's actions, and an incomplete batch is finished in your Shopify admin.
Know the exit. Uninstalling the integration from your Shopify admin revokes access; after that the tool can no longer read or edit your store data. Know where it is uninstalled and confirm with a test uninstall that the tool lost access.

The bottom line

Connect ChatGPT, Claude or Perplexity if you already pay for the assistant and want catalog, inventory, discount and analytics work from the chat; Shopify's ChatGPT and Claude pages say there's no extra Shopify fee. Approve write access only through a deliberately scoped staff account; refunds, order changes and the live theme stay in the admin.

The connectors are documented and bounded, which makes the decision less about risk than about fit: whether the tasks you would hand over are the ones in the table, and whether you are comfortable that the data leaves Shopify's processing once you approve access.

Connect it through a deliberately scoped staff account, and treat write access as a decision, not a default. If you already pay for ChatGPT or Claude and run a store, the plugin or connector is worth switching on for product, collection, inventory and discount work. If what you want is refunds, order edits or a published theme, the connector was never going to do it; that stays in your admin.

FAQ

Does Shopify have a ChatGPT plugin?
Yes. The Shopify plugin for ChatGPT is documented in Shopify's Help Center as an official integration. It isn't listed on the Shopify App Store; you install it from ChatGPT on its install page. It can generate storefront previews and claim a store, and once you sign in and approve access it can manage a store you own: products, collections, inventory, orders, customers, discounts and analytics.

Is the Shopify connector for Claude free?
There is no extra Shopify fee. Shopify's page says standard Shopify plan pricing applies to a store you create or run through the connector, and that any Claude subscription costs are paid to Anthropic rather than to Shopify. So the cost is your Shopify plan plus your Claude subscription; the connector pages in the Help Center name no Claude amount or plan requirement.

Can ChatGPT or Claude edit my live theme?
No. Shopify's considerations page says a connected AI tool can change a theme that isn't published, but it can't edit your live theme, publish a theme, or delete one. In practice the tool works on an unpublished copy, and publishing stays a step you take yourself in the admin, where you can review the result first.

Can a connected AI tool issue refunds or cancel orders?
No, and not even with write access. Shopify lists refunds, cancelling or capturing orders, marking orders as paid, processing returns, and creating or adjusting gift cards as actions that are blocked even when you approve write access. The connectors read your orders, up to 50 at a time, but don't change them, so order work stays in your admin.

Can I connect one assistant to several Shopify stores?
Not at the same time. Shopify's authorizing-access page says that with the ChatGPT, Claude or Perplexity integration you can connect one store at a time, even if your stores are in the same organization. The action table on each connector page includes switching to another store you own, so multi-store owners work store by store rather than across stores at once.

What is the difference between these connectors and Sidekick?
Sidekick is the AI assistant inside your Shopify admin; the ChatGPT, Claude and Perplexity connectors work from inside those chat tools on a store you own. Each connector page says the plugin or connector can handle some tasks but doesn't replace your Shopify admin or Sidekick; only the ChatGPT and Claude pages add that it can help you start a store.

Can the Perplexity connector build a store?
No. Shopify's page for the Perplexity connector says it manages a store you already own, so you need a Shopify store before you connect it. Responses in Perplexity are text only, and for that reason you can't generate a storefront preview, claim a new store, or browse sample products from Perplexity; Shopify points you to the ChatGPT plugin or the Claude connector for that.

Can I see a log of what the tool changed, or undo it?
Not through Shopify, as far as its pages go: none of the six Help Center pages in the connecting-AI-tools section read on September 14, 2026 describes a change log or an undo for a connected tool's actions. What they do say is that you're responsible for any incorrect change, that monitoring your store is your duty, and that issues with the tool itself go to OpenAI, Anthropic or Perplexity AI.

How do I reduce what a connected AI tool can access?
By uninstalling and reconnecting. Shopify's authorizing-access page says that to decrease the data access scope after you approve it, you have to uninstall the integration; there is no lower-the-scope setting. The other control is the staff account the tool acts through, since users who interact with the AI tool are limited by their own user permissions.

Does a store created from a ChatGPT or Claude preview get a free trial?
Yes. Shopify's setup page for stores created with an AI tool says a new store created this way starts on a free trial, currently 4 months as of September 2026, and that the trial begins when you claim the store, not when it was created. The tool isn't connected to the new store until you authorize access to it separately.

Is this the same as selling through ChatGPT?
No. These connectors are for you, working on a store you own from inside a chat. Shopify's Help Center section on connecting AI tools says that making your products discoverable to shoppers who use AI assistants is a different topic, covered under agentic storefronts, Selling on ChatGPT and the Agentic plan: the customer-facing side, with its own rules and costs.

Do the connectors work with Shopify Plus or Shopify POS?
Shopify's pages don't say. None of the six Help Center pages in the connecting-AI-tools section read on September 13, 2026 (the three connector pages, considerations, authorizing-access and the index) mentions Shopify Plus or POS in the context of the connectors. If either is central to your store, confirm with Shopify Support before relying on a connector.

Originally published at shopify.ecom-store.pro, where the article also has an interactive safety checklist.

Disclosure: this article is AI-generated.

Shopify Webhooks: Pick the Route, Then Create It

Alexandr M. — Wed, 30 Sep 2026 07:24:03 +0000

If you wire Shopify events into your own endpoint, a queue or a no-code tool, the interesting decisions are not in the admin form. They are in which route carries the event, what happens when your receiver starts failing, and which failures nobody tells you about. This write-up compares the three routes out of a store, walks through the four-field admin webhook, and lists what Shopify documents (and does not) about delivery and silent deletion.

The original article has an interactive setup checklist; here it is a plain list.

The quick verdict

Let the other side decide your route: a plain HTTPS address means an admin webhook, a need to filter the event first means Shopify Flow on Grow, Advanced or Plus, and a vendor with its own App Store listing means installing the app.

Situation	Answer	Why
A vendor handed you an HTTPS address	Create it in the admin	Four fields in Settings > Notifications > Webhooks, on a page naming no plan requirement (read September 18, 2026)
The event must be filtered before it leaves	Shopify Flow, Send HTTP request	Flow puts conditions and stored secrets in front of the call, on Grow, Advanced and Plus only
You need filtering on an entry tier	A connector or app, filtering on their side	Flow's action is out of reach below Grow; a connector applies the vendor's own filters
The destination has its own App Store listing	Install the app instead	Shopify emails the owner about a failed webhook only when an App Store or custom app created it — ask the vendor to confirm its connector does

If a vendor handed you an HTTPS address, create the webhook yourself in Settings > Notifications > Webhooks: four fields, no code. If the event must be filtered before it leaves, use Shopify Flow's Send HTTP request, which is available only on the Grow, Advanced and Plus plans.

You cannot change the event once the webhook exists, and a failing destination loses its subscription. Shopify emails the owner about that only when an App Store app or a custom app created the webhook, so put a recurring check in your calendar.

What a webhook sends, and to whom

A Shopify webhook is an outbound message: when the event you picked happens in your store, Shopify sends that record to an HTTPS address you typed in, as JSON or XML. Nothing polls and nobody signs in — the data arrives at whoever owns that address.

Someone asks you to add a webhook — a fulfilment partner, an accountant, a SaaS vendor. What they want is a standing instruction in your admin: when the chosen event fires, Shopify posts the record to their server. The event comes from a closed menu, not a free-text field.

The seventeen event categories in the Event menu: Cart, Checkout, Collection, Customer, Discount, Draft order, Fulfillment, Inventory, Location, Market, Order, Product, Refund, Shop, Tender, Theme and Transaction — the Supported webhook events section of Shopify's Creating webhooks page, read September 18, 2026.

What you get is an attempt at delivery, not a guarantee, and Shopify says so itself:

"Webhook delivery isn't always guaranteed, and your app can miss or mishandle events for other reasons, such as handler failures or downtime." — Shopify, Webhooks — Shopify Dev Docs

Admin webhook, Flow or a connector: pick the route first

Three routes carry an event out of a Shopify store: a webhook you create in Settings > Notifications, Shopify Flow's Send HTTP request on Grow, Advanced and Plus, or an app that registers its own. Pick by what the other side gave you.

The route decides who sets it up, whether the event is filtered first, and who hears when it breaks. Flow's Send HTTP request action is only available to the Shopify Plus, Advanced, or Grow plans, so the entry tier leaves you the admin webhook and installed apps.

Route	Where it is created	Plan boundary	Conditions first?	Failure email	What Shopify documents about delivery
Admin webhook	Settings > Notifications > Webhooks	None on the page documenting it	No	No one	Repeated non-200 replies delete the subscription automatically
Shopify Flow, Send HTTP request	Inside a workflow	Grow, Advanced, Plus	Yes, plus stored secrets	A workflow action, not a subscription	Waits up to 30 seconds for a response code; on 4XX, 5XX or 429 you pick Retry for up to 24 hours, Fail or Ignore
App or connector	Inside the app	Whatever the vendor sets	Vendor's own	The store owner, when an App Store or custom app created it	Not named on the listings; Zapier's own page marks each trigger Instant or Polling

Source: Shopify Help Center and Shopify Dev Docs, read September 18, 2026.

The third row is the one merchants misread. Zapier and Make ship official App Store listings, and n8n documents a Shopify Trigger node, so a connector is a real route.

The listings do not say how the connector learns your event happened — by registering a subscription in your store, or by polling on a schedule. Zapier's own integration page does label each Shopify trigger Instant or Polling; for the others, ask the vendor, because the answer matters twice: polling adds delay you cannot see, and the failure email for app-created webhooks reaches you only if the connector created one. Then price webhook against poll.

How do you create a webhook in Shopify?

From your Shopify admin go to Settings > Notifications, click Webhooks, then Create webhook, and fill four fields: the event, the format, the destination URL and the webhook API version. Save it, then use Send test and verify at the URL that the data arrived.

None of the four is cosmetic: Shopify lets you edit a webhook after it is created but never its event, and the receiver depends on all four.

Field	What you choose	What it commits you to
Event	One of 17 categories	Shopify states you cannot change it later — switching means deleting this subscription and building another
Format	JSON or XML	The receiver has to parse what you picked; Shopify's webhook API resource lists JSON as the default
URL	The HTTPS address for the data	Everything the event carries leaves your store for it, and five kinds of address are refused
Webhook API version	A quarterly version	The payload follows that version, and each stable version is supported for at least 12 months

Source: Creating webhooks, Shopify Help Center, read September 18, 2026.

Five kinds of address Shopify refuses:

Localhost.
Any URL ending in the word "internal", such as example.com/internal.
Any URL from a custom domain attached to the store.
"Fake" domains, such as www.example.com.
Shopify domains, such as shopify.com and myshopify.com.

Send test answers one narrow question: did a sample reach the address. Shopify's steps end with checking that at the URL itself and say nothing about the receiver keeping it, so confirm that before you call the integration live.

The signature your receiver checks

Anyone who learns your address can post to it, so the receiver should verify a delivery really came from your store: Shopify signs webhooks with an ID unique to your shop, while the HMAC check in its developer documentation is written for apps and uses the app's client secret. Neither page gives a verification recipe for a webhook created in the admin, so ask whoever builds the endpoint how they will confirm a delivery came from your store.

The API version you pick has an expiry

The Webhook API version is not permanent scenery. Shopify releases a new version every three months and supports each stable one for at least twelve months, payloads follow the version you chose, and individual event topics can be dropped from later versions.

Shopify releases a new API version every three months, on the first day of the quarter, and supports each stable version for at least twelve months, with at least nine months of overlap, per its own versioning documentation.

When the version you picked becomes inaccessible, Shopify falls forward — its versioning page says so for webhooks specifically — and webhooks include an X-Shopify-Api-Version header to confirm which version was used. The page does not name the admin field, so treat this as the general rule and have the receiver read that header.

Topics themselves disappear. Shopify removed the checkout_and_accounts_configurations/update webhook on January 1, 2026, announced in a changelog post the previous August — so a webhook set and forgotten deserves a look.

When delivery fails: deleted without an email

A destination that repeatedly answers with anything other than 200 loses its subscription, and Shopify deletes it from the admin automatically. The failure email goes to the store owner only for webhooks an App Store or custom app created, so one you made stops silently.

Shopify's page documents no banner, alert or log for a deleted subscription: it is gone from Settings > Notifications, and the orders that reached your accountant stop reaching them. There is a guide to finding the delivery log route by route that starts there.

"If the webhook destination repeatedly returns a non-200 status response, then the webhook subscription is automatically deleted from your Shopify admin." — Shopify, Creating webhooks — Shopify Help Center

Whether an email reaches you depends on who created the webhook, not on how badly it failed: Shopify sends one only when an App Store app or a custom app created the subscription.

Shopify publishes those delivery numbers only on a page addressed to apps, and no page we have found extends them to a webhook created in Settings > Notifications.

So the defence is a habit, not a number. Compare what reached the other side with what Shopify recorded, on a schedule — the reconciliation loop behind any custom ERP integration.

What we looked for and did not find: every absence here rests on one reading, done September 18, 2026 — Shopify's Creating webhooks page, its Send HTTP request reference, the developer pages on building and troubleshooting webhooks, the Admin API webhook resource, the API versioning page, the Zapier and Make App Store listings, and n8n's Shopify Trigger documentation.

Customer data on someone else's URL

The payload is the record, not a notification: a customer or order event carries the name, email, phone and full address. Once it reaches the URL you typed, another party holds it, and the pages we read do not extend Shopify's protected customer data rules to a webhook a merchant creates.

Shopify's sample payload for a new customer lists first and last name, email, phone, currency and the full default address — the record itself, not a ping saying a customer was created. The sample for a new order carries the same customer name, email and phone, plus the billing and shipping addresses.

The approval regime that covers apps does not obviously cover you: those requirements are written for apps and the Admin API, and no page we have found addresses a webhook a merchant creates.

So the checks before you save that address are yours:

Who holds the data once it lands.
Whether the address is access-controlled, not a catch-all.
What your privacy policy promises about sharing.
How you switch it off, which is deleting the subscription.

Erasure is the other half: when a customer asks you to delete their data, the copy on someone else's server is yours to chase, and Shopify's side of it stops at tools and notices.

Set it up so you notice when it dies

Shopify's page names nothing that tells you a webhook died, so build the telling into your own routine: agree the event and address first, test after you create it, write down what you made, and re-open the list on a schedule. Only the last step repeats.

Step one happens before you touch the admin, two and three on the day you create the webhook, and the last two keep it from disappearing unnoticed.

Settle the event, the format and the address. Get the event, the format and the exact HTTPS address in writing, then check the address against the blocked list above.
- The event name is written down, not described.
- The address is none of the five blocked kinds.
- You can name who holds the data there, and your policy covers it.
Create the webhook and save it. In Settings > Notifications > Webhooks, click Create webhook and fill the four fields.
- The event is the one you agreed, since it cannot change later.
- The API version is the one the receiver was built against.
Send a test, then confirm it was stored. Send test sends a sample to the address; confirm on the receiving side that it arrived and was kept.
- The test was sent from the admin.
- Someone confirmed the record arrived and was saved.
Write down what you created. Record the event, address, API version and date, because a subscription created here is not returned in API calls.
- Those four details live outside Shopify.
- The receiving side holds the same record.
Put a recurring check in your calendar. Re-open the Webhooks list on a schedule and confirm the subscription is still listed, because a failing one goes without an email.
- A repeating reminder exists.
- You know what the list should contain.

The bottom line

Creating a Shopify webhook is four fields in the admin, and the hard part is everything around it: the route the other side forces on you, the event you cannot change later, the customer data that leaves with every delivery, and the deletion nobody emails you about.

Shopify gives merchants a code-free way to push events out of a store, then documents the limits honestly: delivery is not guaranteed, a failing destination loses its subscription, and the email is reserved for app-created webhooks.

Create it yourself, but never leave it unwatched. An address you were handed means the admin route and four fields; an event that needs filtering first means Flow, on Grow, Advanced or Plus. Either way, put a recurring check in the calendar — Shopify's page documents no alert for a deleted webhook.

Frequently asked questions

Do I need a developer to create a webhook in Shopify?
Not to create one. From your Shopify admin you go to Settings > Notifications, click Webhooks, then Create webhook, and fill four fields: the event, the format, the destination URL and the webhook API version. The developer work sits on the other end, where somebody has to run the address that receives the data and confirm each delivery really came from your store.

Which Shopify plan do I need for webhooks?
The Help Center page documenting Settings > Notifications > Webhooks walks through the whole procedure without naming a plan requirement, read on September 18, 2026. What does carry a plan boundary is Shopify Flow's Send HTTP request action, which Shopify states is available only to the Shopify Plus, Advanced and Grow plans.

Why did my webhook disappear from Settings, Notifications?
Because the destination kept failing. Shopify states that if the webhook destination repeatedly returns a non-200 status response, the subscription is automatically deleted from your admin. Nothing is restored for you. Once the receiving address answers correctly again, you create the webhook a second time and send a test before trusting it.

Can I change the event after the webhook is created?
No. Shopify's page states plainly that you cannot change the webhook event after the webhook is created. Moving from order creation to order fulfilment, for example, means deleting that subscription and creating another one with the new event, the same address and the same API version. Warn the receiving side before you do it.

Does Shopify email me when a webhook stops working?
Only for some webhooks. Shopify sends an email to the store owner's address when a webhook fails, and states that the email is sent only when the webhook was created by an app from the Shopify App Store or by a custom app. One you created yourself in Settings > Notifications falls outside that.

JSON or XML: does the choice matter?
It matters to whoever receives the data rather than to your store. The Format menu offers exactly two choices, JSON or XML, and Shopify's webhook API resource page lists JSON as the default value. Ask the receiving side which one its endpoint parses, because changing your mind later means editing the webhook again.

What does the Webhook API version field actually do?
It fixes the shape of the data you receive. Shopify versions webhook payloads the same way as API responses, releases a new version every three months, and supports each stable version for a minimum of 12 months with at least nine months of overlap. Pick the version the receiving side was built against.

Is Shopify Flow's Send HTTP request the same thing as a webhook?
No. It is an action inside a Flow workflow rather than a subscription in Settings > Notifications, so you can put conditions in front of it and keep secrets in Flow settings. Flow waits a maximum of 30 seconds for a response code, and on an error you choose Retry for up to 24 hours, Fail or Ignore.

Will webhooks created by an app show up in the same list?
Shopify documents only the opposite direction: a subscription you create through the admin is not returned in API calls, because it belongs to the shop rather than to an app. No page we have found states whether the admin list shows app-created subscriptions, so treat that list as the record of what you made there.

How do I test a webhook before I rely on it?
Use Send test. Shopify describes it as a way to check that the event information you want is being sent to the correct URL, and its steps end with verifying at that URL that the notification works. A received test proves the address is reachable, not that anything was kept, so confirm on the receiving side that the record actually arrived.

Originally published at shopify.ecom-store.pro.

Disclosure: this article is AI-generated.

Shopify Plus SCIM: what Okta, OneLogin or Entra can (and can't) do to your Shopify users

Alexandr M. — Thu, 17 Sep 2026 14:20:46 +0000

Shopify Plus SCIM: what Okta, OneLogin or Entra can (and can't) do to your Shopify users

If you are the admin wiring Shopify into your identity provider, "does Shopify support SCIM" is not really the question. The question is what happens on the Shopify side when you push a create, a group change or a deactivation — and what happens to the account when someone leaves. This post walks that mapping using only what Shopify's own help pages say: the SCIM, advanced security features, verify-domain and SAML pages, read September 14, 2026. Where Shopify's wording is conditional, it stays conditional here.

Short answer: yes, on Shopify Plus only

Shopify's SCIM page is explicit: "SCIM user management is available only for organizations on the Shopify Plus plan." SCIM is one of the additional security settings a Plus organization adds from the Users > Security section of its Shopify admin.

Inside that organization, the reach stops at your domain: "You can only manage users who are associated with a domain that you've verified for your organization." That verified domain is not a detail — it is the first link in the chain below.

What your identity provider can do through SCIM

Once you give the SCIM API token to your identity provider, Shopify lists three actions you can take through it:

Create users
Assign or update groups
Deactivate users

One thing to build into your joiner flow: users created through SCIM don't receive an invitation email. The user must log in through the identity provider to activate the account, so plan to tell new hires about it yourself.

The chain before you can generate a token

SCIM is the last step of a chain, and Shopify documents each step on its side as available only on the Shopify Plus plan:

Verify a domain for your organization.
Set up SAML authentication for the organization.
Generate the SCIM API token, then give it to your identity provider.

In other words: a verified domain and SAML authentication come first; both are Plus-only, like generating the SCIM token.

Provider setup: Okta, OneLogin, Entra — and everyone else

On the provider side, Shopify's SCIM page carries configuration steps for Okta, OneLogin and Entra, each starting in the Shopify Plus app inside that provider.

With any other provider you might need a base URL as well as the token. If it asks for one, use:

https://shopifyscim.com/scim/v2/

Offboarding: what a removal in your IdP actually does in Shopify

Does removing someone in your identity provider delete them from Shopify? Not necessarily — the outcome depends on what you do in the provider and on whose account it is.

In your identity provider	In your Shopify organization
Remove an active user's access	The user is suspended in your organization
Permanently delete a user	They might be deleted, depending on your identity provider setup
Remove a store owner or organization owner	Not possible through an identity service provider

Read the middle row carefully. Suspension is the outcome Shopify states for an active user; deletion is a "might", and it hinges on how your own provider is set up. So plan offboarding around suspension, and check how your own provider handles a permanent delete before you count on the account disappearing.

Owners stay on your manual list

Store owners and organization owners can't be removed through your identity provider. Shopify says both types of ownership must be transferred before the user can be removed — so keep owner accounts on your own, manual offboarding list rather than expecting the IdP to handle them.

The 14-day caveat

Shopify's SAML page adds a caveat about sessions: "If you remove a user from the Shopify application in your identity provider, then they can still access Shopify for up to 14 days." If your offboarding runbook treats "removed from the Shopify application in the IdP" as "locked out of Shopify", that line is the one to correct: per Shopify, the user can still access Shopify for up to 14 days.

Whether a departing account should be suspended or removed at all is a decision of its own, separate from what SCIM can do.

SAML enforcement: Required is your choice, and it reaches wide

SAML itself is the condition for SCIM; its Required enforcement level is your choice. Under it, "All users with email addresses matching your domain must use SAML to log in" — store owners and outside users included. That setting also replaces all individual security requirements for your users.

For the admin, that reach is the point. If you want every account with an email address matching your domain to log in through SAML, Required does that, store owners included. Outside users whose email addresses match your domain fall under it too.

What Shopify's pages don't say

No Shopify page we have read — the SCIM, advanced security features, verify-domain and SAML help pages, as of September 14, 2026 — says whether SCIM also covers POS-only staff. That is an absence, not an answer: don't read it as "POS staff are excluded", and don't read it as "they are included" either. If POS-only accounts are part of your directory, test it in your own organization before you promise it to anyone.

Admin checklist

Pulling the above into the order you will actually hit it:

Plan gate. SCIM, SAML and domain verification are each documented by Shopify as Plus-only.
Chain. Verify a domain → set up SAML → generate the SCIM API token → hand it to the IdP.
Provider. Okta, OneLogin and Entra have documented steps, starting in the Shopify Plus app inside the provider; other providers might need the base URL above.
Scope. Only users associated with a domain you've verified.
Actions. Create users, assign or update groups, deactivate users — and no invitation email on create; the user activates by logging in through the IdP.
Leavers. Removing an active user's access suspends them; a permanent delete might delete them, depending on your provider setup; owners can't be removed through the IdP, and both types of ownership must be transferred first.
Sessions. If you remove a user from the Shopify application in your identity provider, they can still access Shopify for up to 14 days, per Shopify's SAML page.

The FAQ this post syndicates, with each claim tied to its Shopify source, is at Does Shopify Plus support SCIM user provisioning?

Our content is AI-generated and fact-checked against official Shopify sources.

A Shopify Mutation That Returns Success and Changes Nothing

Alexandr M. — Fri, 21 Aug 2026 20:28:20 +0000

There is a specific failure mode that costs more than a crash, because nothing in your logs flags it: a GraphQL mutation returns without errors, userErrors is empty, your job marks the sync as done — and the merchant's live shipping settings are exactly what they were before.

That is not a hypothetical. It is the documented behaviour of Shopify's merchant-owned delivery profile APIs on any shop that has moved to market-driven shipping, and it has been in effect since August 1, 2026.

If you maintain an app, a custom integration, or one of those quiet client scripts that keeps a rate table in sync, this is a short read with one action at the end.

The sentence that matters

From Shopify's developer changelog, on the deprecation of merchant-owned delivery profile APIs:

When a shop uses market-driven shipping, the legacy delivery profile fields and mutations in the Admin GraphQL API no longer represent the shop's live merchant-owned shipping configuration. Reads may return a stale snapshot of the legacy configuration, and writes may succeed without errors but will not update the merchant's live shipping settings.

Read that as two separate bugs, because they fail differently.

The read is a lie with a timestamp. You query deliveryProfiles, you get a well-formed response, and it describes a configuration that is no longer the one the checkout uses. Any logic that diffs "what we think the merchant has" against "what we want them to have" is now diffing against a ghost.

The write is worse, because it is silent. No error, no userErrors entry, no non-200. The mutation succeeds. Whatever safety net you built around failures — retries, alerting, a dead-letter queue — is wired to a signal that never fires.

Both of these are trigger-free from your side. Nothing changes in your code, your API version, or your scopes. The shop moves, and your integration starts being wrong.

The date on the page is not the date it took effect

Small thing, and it will bite anyone who audits by scanning changelog headers.

The changelog entry displays July 1, 2026 — that is postedAt. The page's own metadata carries effectiveAt of August 1, 2026, 12:00 ET, with effectiveApiVersion: 2026-07. Posted in July, effective in August.

If your process is "grep the changelog for dates in our maintenance window", the header date is the one you will catch, and it is a month early. Worth knowing that Shopify publishes both.

Exactly which APIs, and which are fine

The changelog names the affected surface explicitly. Merchant-owned usage of:

deliveryProfile
deliveryProfiles
deliveryProfilesCount
deliveryProfileLocationGroup
deliveryProfileLocationGroups
deliveryProfileCreate
deliveryProfileUpdate
deliveryProfileRemove

And the carve-out, which is the half that keeps this from being a panic:

App-owned delivery profiles aren't affected and continue to function as before.

So the question to ask about your own code is not "do we touch delivery profiles" but "do we touch the merchant's delivery profiles". A carrier-service app that owns its profiles is in a different position from a script that edits the rate table the merchant built by hand.

How to tell which model a shop is on

Shopify's upgrade guide gives you a flag rather than making you infer it. The marketDrivenShipping field on ShopFeatures tells you which model the merchant is on, and the read path for that needs the read_markets scope (read_markets plus write_markets if you write). Branch on it: for shops on the new model, read from the Markets APIs; for shops still on the legacy one, keep reading deliveryProfiles. Once every merchant has moved — July 2027 — the legacy branch can go.

There is also a path with no branching at all, which is the one to look at first if rates are all you need: Contextual Product Feeds return rate information from both the merchant's market rates and app-owned delivery profiles in one response. The guide's own argument for it is that there is nothing to unwind later, because the feed behaves the same on both models.

The changelog names three destinations depending on what you are actually doing: Contextual Product Feeds, app-owned delivery profiles, or the Markets APIs.

The window, and why there is no date for a given shop

Two dates are published in one changelog sentence:

Market-driven shipping will start rolling out to merchants on October 1, 2026, and all merchants will be on it by July 1, 2027.

That bracket is the whole schedule. The rollout runs gradually over an extended period, so stores are not all upgraded at the same time, and no page we found publishes a per-store date. Plan against the window.

Two consequences for app developers specifically, from the upgrade guide's own timeline. From October 1, 2026, new installs see a compatibility warning if your app has not been upgraded, and any merchant who opts in manually will hit breakage. Submitting Shopify's compatibility form clears that warning and lets Shopify move merchants on your app automatically once you are ready — Shopify also tries to detect compatibility on its own, but the form is the deterministic route.

You can test before any of that: create a development store with the Market-driven shipping feature preview enabled and run your read and write paths against it.

What the migration does on the merchant's side

Even if your integration never touches shipping, the merchant's setup changes shape underneath it — and support tickets land on whoever built the store. The short inventory, from Shopify's Help Center page on upgrading from shipping profiles to shipping options by market:

The hierarchy inverts. Today merchants configure delivery profiles, then location groups, zones and rates inside them. Under market-driven shipping, shipping options attach directly to markets, and each option carries rate variations by product and location condition. The market becomes the container.

Rates can no longer point at individual products or variants. To price a specific set of variants, they have to be grouped into a collection. Shopify's stated reason is maintainability: collection membership shifts on its own, so a rate follows the catalogue instead of needing to be re-pointed. Existing groupings are converted for you — anything built afterwards is built on collections.

Same-named rates merge, and the highest one wins. During the upgrade, rates sharing a shipping option name are consolidated into one option, and when more than one rate in that option matches a cart, only the highest matching rate is charged rather than the rates adding up. That becomes the standing rule: highest price wins within a shipping option, prices add across options. Rate names stopped being cosmetic — the name decides the grouping.

New collections appear that nobody created. Product groupings from shipping profiles arrive as collections prefixed [Shipping], automatically assigned to the right product conditions. They are unpublished, so customers never see them. If you have tooling that reconciles collections, teach it about that prefix before someone "cleans up" the store.

Two settings change themselves. Split shipping is always on afterwards — if the merchant had it off, it is on, and an order can arrive at checkout as two shipments with separate delivery times. And the Markets permission is not granted automatically and is not part of existing staff roles, so whoever manages shipping needs it added deliberately. Expect at least one "I can't open shipping settings any more" message.

The opt-out window destroys work. Switching back to shipping profiles restores the previous setup and permanently removes every shipping change made after the upgrade, along with the collections and sub-region markets the upgrade created. After the window closes, switching back is not possible. So the window is time to test, not time to build.

The compatibility list that does not exist

The question every merchant asks first is whether their shipping apps are compatible. As of our reading in August 2026, no Shopify page we found publishes a list of apps that are or are not compatible with shipping options by market — not the upgrading page, not the other pages in the shipping-options section, not the Markets manual, not the feature preview docs.

What exists instead is per-store: Shopify surfaces incompatibility inside the merchant's own admin, and each vendor answers for its own app. Which is also why stores using rate-providing apps may be upgraded later — if an incompatible app provides rates and they do not appear at checkout, customers cannot complete orders. Delaying those stores is how that outcome is avoided by default.

The distinction that decides whether this is about a given app is narrow: does it calculate or return a rate at checkout? That is a question for the vendor, not something you can read off the app's name.

The short version

Find every place your code touches deliveryProfile* for merchant-owned configuration. App-owned profiles are fine.
Add a branch on marketDrivenShipping from ShopFeatures, or move to Contextual Product Feeds and skip the branch.
Check your scopes: read_markets, plus write_markets if you write.
Stop trusting a successful mutation as proof of a saved setting on upgraded shops — read back and verify, at least until your migration lands.
Test on a dev store with the Market-driven shipping feature preview before October 1, 2026.
If you ship a public app that returns rates, submit the compatibility form so your merchants are not held back or warned at install.

The merchant-facing version of this — what changes in the admin, the pre-upgrade audit as a tickable checklist, and a routing quiz for which upgrade path fits a given store — is on the canonical article: Shopify Shipping Options by Market: the 2026 migration.

Our content is AI-generated and fact-checked against official Shopify sources. Every claim above was re-verified against shopify.dev and help.shopify.com on August 21, 2026.

The Same Shopify Workflow Is 1,800 Zapier Tasks, 4,680 Make Operations and 1,000 n8n Executions

Alexandr M. — Thu, 06 Aug 2026 12:04:26 +0000

Somebody asks what it will cost to automate a piece of their Shopify store, and the answer arrives as three monthly prices sitting next to each other. That comparison is broken before it starts, because the three vendors are not selling the same unit. Zapier bills a task. Make bills an operation. n8n bills an execution. Those three words describe three different things, and the gap between them is not a rounding error — on one ordinary workflow it is more than four times.

Here is that workflow, then the four rules that produce the spread, then the parts of Shopify Flow that decide whether you need an external layer at all.

A format note: the canonical version of this article carries an interactive calculator that converts your own workflow shape into all four vendors' units, plus a routing quiz. Neither survives a plain markdown feed, so the arithmetic and the routing logic are written out as text below.

One workflow, three counts

Take a shape most stores would recognise. Something happens 1,000 times a month. A filter throws away 40% of those as irrelevant, so 600 survive. Each of the 600 runs three action steps. The tool checks Shopify every 15 minutes, which over a 30-day month is 2,880 checks.

Layer	Count	How it got there
Zapier	1,800 tasks	600 surviving runs × 3 action steps
Make	4,680 operations	2,880 trigger checks + 1,800 module runs
n8n	1,000 executions	one per workflow run; steps are not counted
Shopify Flow	nothing	no billable unit is published — but only if the work never leaves Shopify, which this one does

Notice what did the damage, because it is not what people expect. The filter is free everywhere, so it is not the culprit. The three action steps are free on n8n and charged three times over on the other two. And the 2,880 checks — the same checks, on the same schedule — are worth nothing on Zapier and n8n and 2,880 operations on Make.

Then change exactly one thing. Poll every 5 minutes instead of every 15, and the checks go from 2,880 to 8,640 a month. Zapier still bills 1,800 tasks. n8n still bills 1,000 executions. Make goes to 10,440 operations, past the only allowance its published price covers. Same work, same result for the store, and one of the three vendors has just charged you for being impatient.

The four rules that produce it

Layer	One billable unit is…	What is free	What surprises people
Shopify Flow	Nothing — it is a free app on the four plans that carry it	Everything on those plans	No run allowance is published either, so there is nothing to run out of and nothing to plan against
Zapier	One action step that completed successfully — Zapier notes some apps or actions may use more than one	Triggers, Filter and Paths steps, steps a filter skipped, and polling — always	Step count, not run count, moves the bill: doubling the actions in a Zap at least doubles the invoice at identical volume
Make	One module run	Nothing that runs. A trigger module costs one operation per check	A poll that finds nothing still bills
n8n	One whole workflow run, whatever it contains	Polls that return nothing, manual runs from the editor, sub-workflow calls	Node count is free — a twenty-node workflow and a two-node workflow bill identically

Each of those is the vendor's own wording. Zapier's is the plainest: "A task is anything Zapier successfully completes on your behalf." Make's diverges at exactly one point, and it is the expensive one — its help centre states that a trigger module costs one operation per check, regardless of the number of bundles returned, which includes checks that return nothing at all. Make charges you for looking. Zapier and n8n do not, and n8n writes the opposite rule down explicitly:

Polling nodes (like Google Drive Trigger): Count one execution only when new data is found. Polls that return no results don't count as an execution.

— n8n, "Understand executions"

Now put prices on those counts — carefully

1,800 tasks lands on the 2,000-task step of Zapier's Professional ladder: $49 a month billed annually, $73.50 billed monthly. 1,000 executions sits inside n8n Cloud Starter at $20 a month billed annually or $24 month to month, which covers 2,500 executions. 4,680 operations sits under Make's $12-a-month Core price. All three verified on each vendor's own pricing page, 28 July – 1 August 2026.

Two of those three are rungs on a ladder. One is a floor. Zapier publishes an 18-step task ladder in both billing cycles, from 750 tasks up to two million. n8n publishes two tiers in two cycles. Make publishes a single usage slider that moves quota and price together, and the $12, $21 and $38 figures are all prices at the lowest position of that slider, labelled "10,000 credits/mo". Above that position Make publishes nothing, and no annual dollar figure appears for any tier. So "4,680 operations for $12" is an entry price sitting next to a count, not a quote — and any comparison chart that plots Make against rising volume is drawing a line somebody made up.

Two more things worth carrying out of the price section:

Zapier's billing-cycle gap is 50%, not the 15–20% most SaaS charges — on every step up to 100,000 tasks. Any Zapier figure quoted without naming the cycle is potentially half the real number.
The unit counts are not a ranking either. n8n produces the smallest number and is not the cheapest line; Make produces the largest and has the lowest published entry. The unit does not tell you who is cheaper today. It tells you which way your bill moves when your workflow changes shape.

Before any of that: where Shopify Flow stops

Flow is the layer people skip, and it is free on Basic, Grow, Advanced and Plus — Shopify publishes that list twice, on the Help Center and on its Flow marketing page, and Starter appears in neither. It reacts to events in the store and its connected apps, and it has a clock trigger. If a workflow starts and ends inside Shopify, no meter ever starts.

Two plan gates sit inside the app your plan already includes:

Send HTTP Request — the one built-in action that talks to anything outside Shopify — is available only on the Plus, Advanced or Grow plans. On Basic it is not offered. At US list on monthly billing that gate costs $66 a month to clear by upgrading Basic to Grow, and it buys everything else Grow carries, not just the action.
Tasks built by custom partner apps need Plus. That one affects a single capability, and it is the reason a bespoke build sometimes wants Plus underneath it.

Four more limits are not plan gates at all — no tier above yours removes them:

Flow sends no general customer email. The only general email action is Send internal email, and Shopify's guidance on the action's own page is blunt: "the Send internal email action is best used to send emails to staff. To automate emails to customers, create a marketing automation." Four named actions do reach customers — B2B access, draft order invoice, order invoice, payment reminder — and that is the documented list.
No built-in trigger starts Flow from outside Shopify. It starts on store and app events, or on the clock. An installed app can register its own triggers; the plan cannot.
Send HTTP Request has no published payload or body-size limit. We fetched the full action page and found none, which means the limit is untested rather than generous. What the page does document: Flow waits up to 30 seconds for a response code, then closes the connection and retries, and 4XX, 5XX and 429 responses can be set to Retry for up to 24 hours, Fail, or Ignore.
There is no published run allowance. This is the most-asked question about Flow with no published answer. Shopify instead says usage limits follow the Admin API rate limits of your plan — "Stores are given different usage limits in Shopify Flow according to the API limits governed by their plan." Those buckets are 100 points/second Standard, 200 Advanced, 1,000 Plus, 2,000 Shopify for enterprise. That is a ceiling on how hard the store can be worked, not on how many workflows you may own — and it is the closest thing to a planning figure that exists.

One naming collision does real damage here: marketing platforms call their email and SMS sequences flows, and a Klaviyo flow has nothing to do with Shopify Flow. If the automation you are picturing sends a series of emails to a customer, you are shopping on the wrong layer entirely.

Reach is two questions, not one

How much of Shopify a tool can touch, and how it finds out something happened, are separate — and the second one decides both your bill and your latency.

On catalogue, counted on each vendor's own reference pages (Shopify and Make in July 2026, Zapier on 4 August 2026): Flow, 83 triggers and 109 actions before anything an installed app adds. Zapier, 59 Shopify items — 20 triggers plus 39 actions. Make, 27 modules — 4 triggers, 18 actions, 5 search. n8n, two built-in nodes — a Shopify app node with 10 operations across orders and products, plus a separate Shopify Trigger node whose docs page links usage templates rather than enumerating the events it supports, so confirm your event before you plan around it.

On mechanism, there are exactly two ways for anything outside Shopify to learn that an order arrived, and Shopify is unusually direct about the limits of the first:

Webhook delivery isn't always guaranteed, and your app can miss or mishandle events for other reasons, such as handler failures or downtime.

— Shopify, "Webhooks"

Shopify's own advice to app builders is to run reconciliation jobs that periodically re-fetch, and that applies just as squarely to a Zap or a scenario. Any workflow that moves money, stock or fulfilment needs a second, slower workflow that checks the first one's work — a nightly sweep re-reading yesterday's orders. That sweep is a second workflow with its own unit count on whichever layer runs it, and it is the one most people forget to model at all.

Polling is the alternative, and it always lags by its own interval. The only lever that shortens the lag is polling more often — which costs operations on Make and nothing on Zapier and n8n. Speed is a paid upgrade on exactly one of the three. There are floors, too: Make's own comparison table puts the minimum scenario interval at 15 minutes on the free plan and 1 minute on Core, Pro and Teams; Shopify Flow's clock is documented down to a smallest repeat interval of 10 minutes.

Is self-hosted n8n really free?

The licence is. The running of it is not, and no vendor publishes that number — which is why the honest answer is a list of components rather than a total.

The software: nothing. A standard self-hosted version is on GitHub.
The server: your number, not ours. n8n's docs name an instance class rather than a price — a Hetzner CPX11 (2 shared vCPU, 2 GB RAM, 40 GB SSD) described as enough for most usage levels. Its monthly price is not published anywhere a tool can read it; we tried five independent methods on 28 July 2026, including Hetzner's own public cloud pricing endpoint and the Wayback Machine, and the server-rendered HTML ships a placeholder where the number belongs.
Upkeep: hours × your rate. Updates, backups you have actually restored from once, and monitoring that tells you before your merchants do.
The 2 a.m. question. Who is on the hook when a workflow stops silently during a sale. On a hosted plan that is the vendor; here it is a person you employ or are.

And one licence detail that matters if you build for clients rather than for yourself. Plenty of write-ups call n8n open source. n8n does not:

Although n8n's source code is available under the Sustainable Use License, according to the Open Source Initiative (OSI), open source licenses can't include limitations on use, so we do not call ourselves open source.

— n8n, "Sustainable Use License"

The licence permits use or modification for your own internal business purposes, or non-commercial and personal use, and permits distribution only free of charge for non-commercial purposes. Automating your own store is squarely internal business use. Hosting it for clients and reselling it is the example n8n itself names as not allowed. The word for this model is fair-code — source-available with restricted commercial use.

The exit is the price nobody quotes

On the import and export pages we read — each vendor's own, 28 July 2026 — no vendor documents a path that moves workflows to either of the others. Each reads only its own format. n8n describes saving workflows as JSON and importing JSON files into your n8n library, and nothing on that page or its siblings mentions another platform's format. The picture is the same in every direction.

So a tool at Make's $12 slider floor that takes three weeks to leave is not cheaper than Zapier's $49 annual-billing step that takes three weeks to leave. The subscription difference is rounding next to the rebuild. Two practical consequences: keep a written description of what each workflow does, independent of the tool that runs it, so a rebuild is a translation rather than an archaeology project. And weight the first choice toward the unit that fits your workflow shape, because that is the thing you cannot renegotiate later without paying for it twice.

Five things nobody publishes

Every gap below is a verified absence rather than an assumption — we went looking, and this is what was not there. Listing them is the honest alternative to filling them in:

Any Make price above the lowest position of its usage slider, and any annual dollar figure per tier (checked 28 July and again 1 August 2026 by capturing the pricing page's raw HTML in full).
The monthly price of the Hetzner CPX11 instance n8n's docs recommend (five methods, 28 July 2026).
A run allowance for Shopify Flow (the Flow hub plus its getting-started, create, manage and reference pages, the Send HTTP Request page, and shopify.com/flow — 28 July 2026).
A payload or body-size limit for Send HTTP Request.
A documented migration path between Zapier, Make and n8n.

The bottom line

The decision is smaller than it looks once the two halves are separated. Put everything that stays inside Shopify on Flow, where it costs nothing beyond the plan you already pay for — on most stores that is the majority of the list. Then take what is left, work out its real unit count on each layer, and buy the one whose unit is kindest to your shape. A workflow with many action steps and few runs punishes Zapier and Make. A workflow that polls frequently punishes Make specifically. A workflow with enormous volume and someone already running servers argues for n8n on your own hardware, provided you count the hours honestly.

The sorting is what saves the money. The vendor choice only decides how much.

Originally published at shopify.ecom-store.pro, where the same comparison carries an interactive unit-cost calculator. All prices and counts were verified against each vendor's own pages between 28 July and 4 August 2026; check them before you commit, because they move. Our content is AI-generated and fact-checked against official Shopify and vendor documentation.

Shopify's REST Admin API Has Been Legacy for Two Years and Still Has No Removal Date

Alexandr M. — Wed, 05 Aug 2026 17:15:49 +0000

Every few weeks a client forwards me the same kind of link: an article, a thread, a vendor page, all saying some version of migrate off Shopify's REST Admin API before it's too late. The client wants to know what it will cost them. And the honest first answer, most of the time, is a question back: what exactly is connected to your store?

Because when you go read what Shopify actually published, the urgency in the search results is not coming from the record. The record is short, it is public, and it contains one status change, three narrow deadlines aimed mostly at app vendors, an explicit carve-out — and, nearly two years on, no date for switching anything off.

This is that record, with the sentence-level receipts, plus the parts that genuinely do force a migration. It is written for the person who has to answer "so do we budget for this or not" and wants to be able to defend the answer.

A format note: the canonical version of this article carries an interactive routing quiz and a tickable integration inventory, neither of which survives a plain markdown feed. Below I have written out the same routing logic and the same steps as text.

The published record — and the row that does the most work

What Shopify published	When	Who it applied to
The REST Admin API is a legacy API	October 1, 2024	The whole REST Admin API, no carve-out by app type
Public apps had to move to the new GraphQL product APIs	February 1, 2025	Public apps in the App Store, product and variant endpoints only
Custom apps on the existing GraphQL product APIs had to move	April 1, 2025	Custom apps already on the older GraphQL product fields — not custom apps on REST
New public apps submitted to the App Store must use GraphQL only	April 1, 2025	Submissions on or after that date; already-listed apps not covered
A general removal or shutdown date for the REST Admin API	Not published	Would apply to everyone — which is why its absence matters

Rows 1–4 come from Shopify's Admin REST versioning documentation, the product APIs deprecation changelog and the GraphQL-only submissions changelog. Row 5 is an absence, checked in August 2026 — more on how we checked it below.

Reading those four announcements as one countdown is the mistake almost every write-up on this topic makes. They have different audiences and only two of them ever pointed at a merchant's own code.

"Legacy" is a status. "Removed" is an event.

This distinction is the whole article. Shopify's versioning doc puts the status in the plainest possible terms:

The REST Admin API is a legacy API as of October 1, 2024.

Read what that sentence does and does not do. It applies to the whole REST Admin API with no carve-out by app type, so nobody gets to claim their integration is exempt from the status. And then it stops. It names no consequence, no deadline and no removal — which is exactly why it has survived unchanged for as long as it has.

A status describes where something sits in a lifecycle. An event has a date attached and something stops working on it. Shopify assigned the status. It has not announced the event.

What we looked for and did not find

An absence is a weaker claim than a fact, so here is the reading behind it, done in August 2026. The pages: the Admin REST versioning doc, the REST Admin API landing page, the changelog entry on the new GraphQL product APIs, the general API versioning page, the deprecated API calls reference and the changelog's deprecation feed. Plus the Help Center's apps, managing apps and custom apps pages.

On those pages: no removal or shutdown date for the REST Admin API; no merchant-facing explanation of the API's status anywhere in the Help Center (two likely URLs redirect to the developer site instead); and no statement that organisations created after some date may only use GraphQL for custom apps.

What does exist is much narrower — individual deprecated calls can carry their own migration deadline, field by field, surfaced in the API response. That is a mechanism for retiring specific endpoints on their own schedules. It is not a plan to switch off an API.

We cannot say Shopify will never publish a removal date. We can say we looked where such a date would live and it is not there. When it appears, the top of this article changes.

The carve-out most coverage leaves out

In the same changelog entry that set the February and April deadlines, Shopify wrote this:

Custom apps built on REST that do not need to support more than 100 variants can continue to use the deprecated REST product APIs

Two conditions are bolted to that permission: it covers custom apps, not public ones, and it covers the product and variant endpoints specifically, not the REST Admin API as a whole. Within those bounds the arrangement is open-ended — no expiry is attached to it, and none has been published since.

The permission is real. So is its price, from the same entry: any merchant using custom apps built with those deprecated APIs will not be able to increase their variant limit past 100.

So the carve-out holds until the catalog needs it not to. At that point the migration stops being optional without any date being involved. That is the single most useful thing to tell a client: your deadline is not on Shopify's calendar, it is in your product data.

Three numbers, three different things

This area is a minefield of numbers that look like they belong together and do not.

100 — the threshold in the REST carve-out. Custom apps "that do not need to support more than 100 variants", and merchants on those apps cannot raise a variant limit past it.
2,048 — the number of variants a Shopify product can carry on the platform itself, raised from a historical limit of 100 in October 2025. That is a product limit, not an API one — though the same changelog warns that merchants whose apps are not on the in-support GraphQL product APIs may see a downgraded or broken experience above 100 variants.
"Up to 2000 variants" — a figure the text of that changelog entry never states. It survives only inside the web address of the companion entry it links to, whose own title now reads 2048.

Three numbers about two different things, and the gap between the last two is a wrinkle in Shopify's own text rather than something you can resolve. Quote whichever one applies to the question in front of you and do not do arithmetic between them.

The only deadline that actually exists

If you want a real clock in this topic, it is not REST-specific at all. It is the versioning policy, and it applies to every Admin API client, GraphQL included.

Shopify ships a new API version at the start of each quarter. Each stable version is supported for a minimum of 12 months, with at least nine months of overlap between two consecutive stable versions. That rolling window is the genuine timetable.

What happens at the end of it is the part that surprises people:

Shopify falls forward and responds to your request with the same behaviour as the oldest supported stable version.

Nothing errors. Your integration keeps working — against slightly different rules than the ones it was written for. Which is why, in this topic, the realistic symptom is a quiet change in a familiar report rather than an outage, and why "it still works" is not evidence that a version is current.

An alert does exist, but it is late and it lives in the merchant's admin: Shopify's Help Center says a notification is shown in the Shopify admin when an app in the store uses an unsupported API.

The consequences Shopify names, and who they reach

Shopify names delisting from the App Store for a public app or sales channel that keeps calling unsupported resources after the upgrade deadline. For an app publisher that is severe. For a custom app it is not applicable at all — there is no listing to remove.

But "no listing" is not the same as "no consequence". The same versioning page says that for unsupported resources after the upgrade deadline, users are blocked from installing the app for a minimum of seven days, and they see warnings in the Shopify admin until seven days after the last detected use of unsupported resources.

Note the condition on all of it: unsupported resources after the upgrade deadline. That is a different thing from the REST carve-out, and conflating the two is how "REST apps are at risk" gets manufactured out of a versioning page.

Three deprecations this is not

Search results blur four separate stories into one, and each mix-up sends someone somewhere unproductive.

Mixed up with	What it actually is	Whose problem
The Storefront API	A separate API for building shop fronts. Shopify's docs say it plainly: "The Storefront API is available only in GraphQL. There's no REST API for storefronts."	Headless merchants — meaning this deprecation never touched them
The Customer Account API	The interface behind customer login and account pages, with its own deprecation story on its own timetable	Stores still on legacy customer accounts
Shopify Scripts and Functions	Checkout logic — discounts, shipping, payment rules. Different technology, different dates, not part of the Admin API	Plus stores that ran Scripts at checkout

The first row is worth a second read if you run headless. There was never a REST version of the Storefront API, so a headless storefront had nothing to migrate. Advice telling you otherwise is describing a different API.

Also worth flattening a naming problem while we are here: if a handover document or invoice says private app, that is the old name for what Shopify now calls a custom app. Same thing. It matters because every boundary in this topic is drawn between public apps and custom apps.

Five triggers that turn this into a bill

Once you accept there is no removal date, the question changes shape. It stops being "when is the deadline" and becomes "what would make this urgent for us" — and that has five concrete answers, none of them a date.

Trigger	What you would notice	What it forces
A product needs more than 100 variants	You cannot raise the variant limit on that product	Moving the product-writing path off the deprecated REST endpoints
New Shopify work is being commissioned	A quote lands for a rebuild, integration or new app	Building on GraphQL, and pricing the old integration inside that scope
You want a capability the old endpoints never got	What you asked for is not available the way the integration works today	Migrating before the capability can ship — the deprecated product APIs are in maintenance mode, new features go only to the new GraphQL product APIs
The pinned API version ages out of support	Behaviour shifts with no error and no announcement	Raising the version, which for product calls can mean moving to GraphQL
You publish a public app yourself	An upgrade deadline lands on your App Store listing	Upgrading, or losing the listing

Everything else is a planning decision.

What a deliberate wait looks like

Waiting is a legitimate engineering answer here. It is only a decision when three things are true, and the difference between a decision and a gap is what shows up in the retro.

A name. One person who owns the question. An unowned wait is indistinguishable from having forgotten about it, right up until it is not.
A channel. Shopify's own guidance to developers is to follow the developer changelog for breaking changes. That is where a removal date would appear. The merchant-facing signal — the admin notification — only fires once an app is already on an unsupported API, so it is a smoke alarm, not a calendar.
A written trigger list. The table above, plus one external event: Shopify publishing a removal date. If that happens this becomes a scheduling problem instead of a judgement call.

There is precedent for how these run: legacy customer accounts were deprecated with no sunset date announced either, and the stores that treated the announcement as the moment to plan came out ahead of the ones that waited for a date.

What it costs, and the one number anybody publishes

Exactly one public figure exists for this work, and it deserves to be quoted with its provenance attached rather than passed around as a benchmark. UK agency No7 Software published in May 2026 that migrating a legacy custom app from REST to GraphQL typically costs between £15,000 and £40,000, depending on complexity. One vendor, one complexity class, one date.

No agency page we read puts a per-complexity ladder on this work — nothing separating a nightly sync from a mid-sized custom app from a heavy continuous integration — and none attaches a timeline. We are not going to invent the missing figures. If a quote you receive lands well outside that range, the range is the weaker evidence.

The more useful part of that agency's post is where it says the money goes, because it is not the obvious place: the primary engineering expense is not rewriting queries but re-architecting the queueing system to handle calculated query costs instead of simple request counting.

That is the agency's characterisation, not Shopify's — and it tells you which integrations the big number is really about. A nightly script touching a few hundred products has no queueing system to re-architect. A continuous sync moving thousands of records does. If your migration estimate is dominated by query rewriting, either the integration is small or somebody has not looked at the throughput yet.

What to do this week

If you maintain Shopify integrations for other people, the deliverable that beats a migration quote right now is an inventory. Six steps, most of them a spreadsheet and a few messages:

List every system that touches Shopify data other than the theme and App Store apps the merchant installed themselves.
Put a name against each one — who built it, and who is on the hook today. Those are often different people. Flag every line where the honest answer is nobody.
Mark which ones write products and variants, and check whether any product needs more than 100 variants.
Ask, per integration, which Admin API version it pins and when that was last raised.
Ask, per integration, whether it calls REST product or variant endpoints, and whether any of its calls come back flagged with a migration deadline.
Record one decision per line: wait with a named watcher, fold into work already being paid for, or budget it now.

Steps 4 and 5 are the ones a merchant cannot answer alone. Shopify's API Health report "on the Partner dashboard shows the deprecated API calls your apps are making, along with documentation and timelines" — which lives in the developer's dashboard, not the store admin. If you are the developer, sending that output unprompted is a five-minute answer to a question your client has been reading scary articles about.

The bottom line

Shopify labelled the REST Admin API legacy on October 1, 2024, published narrow deadlines aimed largely at app vendors, wrote an explicit carve-out for custom apps on REST, and has not published a removal date. Unless a catalog is pushing past 100 variants, a new build is being scoped, or the pinned version is aging out, this is a planning question rather than a bill.

Which is a less exciting conclusion than "migrate now" — and considerably easier to defend when someone asks where the deadline is written down.

The full version of this article, with the routing quiz and the tickable inventory, is on our site: Shopify REST API to GraphQL: Do You Need to Pay Now?

Disclosure: this article was created with the help of AI.

Shopify's Non-Plus Checkout Deadline: What Breaks on August 26, and the Order to Fix It

Alexandr M. — Fri, 31 Jul 2026 14:38:44 +0000

There is a deadline sitting in the Shopify admin of every Basic, Grow, and Advanced store that still customizes its post-checkout pages, and as I write this at the end of July 2026 it is under four weeks away: August 26, 2026. Shopify's own wording is unambiguous — "If you're on a non-Plus plan, then you have until August 26, 2026 to upgrade and replace your Thank you and Order status pages," and if you don't, those pages get auto-upgraded for you.

If you build or maintain Shopify stores for clients, this is the month that matters. Not because the migration is hard — for most stores it genuinely isn't — but because the failure mode is silent. Nothing throws. Nothing 500s. A field that used to run JavaScript stops running JavaScript, and the first symptom is a conversion column in an ad platform that quietly goes soft weeks later.

The single biggest source of confusion here is that almost every article on the topic mixes up two different audiences with two different deadlines. So before anything else: which side of the line is the store on?

One format note: the canonical version of this article carries an interactive decision quiz and a tickable migration checklist, neither of which survives a plain markdown feed. Below I have written out the same routing logic and the same steps as text, and linked to the interactive versions.

Two deadlines, two completely different stories

You are on	Had checkout.liquid?	Thank you / Order status deadline	Status as of July 2026
Shopify Plus	Yes — it was a Plus-only file	August 28, 2025	Passed. Automatic upgrades began January 2026; customizations were lost.
Basic, Grow, or Advanced	No — never had access	August 26, 2026	Still ahead. Additional scripts and script-tag apps keep working until then.
No checkout customization at all	n/a	Auto-upgrade only	Likely fine either way — confirm in the admin and move on.

Sources: Shopify Help Center — Plus upgrade guide and upgrade guide.

The detail most write-ups get wrong

checkout.liquid was only ever available to Shopify Plus stores. Shopify's own theme docs put it plainly: "If your store isn't on Shopify Plus, then you can customize your checkout pages in the theme editor."

So if your client is on Basic, Grow, or Advanced, they are not "migrating off checkout.liquid." They never had it. Their exposure is somewhere else entirely: the additional scripts field and any installed app that injects script tags on the Thank you and Order status pages. That is the inventory to audit — not a theme file that was never in the repo.

This matters practically, because if you go looking for checkout.liquid in a non-Plus store's theme, find nothing, and conclude the store is unaffected, you have just cleared a store that is fully affected.

The actual timeline, with the official post for each event

Date	What happened
Feb 13, 2023	Checkout extensibility launches for Plus on the Information, Shipping, and Payment pages.
May 21, 2024	UI extensions and web pixels on Thank you / Order status open to Basic, Shopify, and Advanced plans.
Aug 13, 2024	checkout.liquid stops working for in-checkout pages — Information, Shipping, Payment — for any store.
Aug 28, 2025	Plus deadline: checkout.liquid, additional scripts, and script tags sunset for Thank you and Order status.
Jan 2026	Plus stores auto-upgraded; customizations using additional scripts, script-tag apps, or checkout.liquid on those two pages are lost.
Apr–Jun 2026	Separate track: Shopify Scripts — editing ended April 15, 2026, and all Scripts ceased to execute on June 30, 2026. Both dates are behind us.
Aug 26, 2026	Non-Plus deadline for Thank you and Order status.

Two of these are worth flagging for anyone doing client work right now. First, the in-checkout steps have been off checkout.liquid since August 2024 — that is two years of "unsupported," not a pending change. Second, Shopify Scripts is a genuinely separate sunset that already fired on June 30, 2026; if a store's discount or shipping logic went strange this summer, that is a different rabbit hole (we cover it in a separate Scripts-to-Functions guide).

What "breaks" actually means

For the three in-checkout steps, breakage is total and already historical: checkout.liquid is, in Shopify's present-tense wording, "now unsupported for the Information, Shipping, and Payment checkout steps."

On the post-checkout pages the failure is quieter and, for a developer inheriting a store, much nastier. On a legacy checkout the additional scripts field goes read-only — visible, populated, apparently fine. Then at the deadline the scripts in it simply stop firing. As one agency writing about the 2026 migration describes it: "every script in that field stops firing. No warning popup, no gradual sunset."

Shopify's own help page is the formal version of the same thing: "Additional scripts for tracking and analytics and page customizations aren't supported on the new Thank you and Order status pages."

The part that costs real money: analytics

This is where the silent failure turns expensive. Tracking that lived in additional scripts stops the moment a shopper enters the new checkout — middle-funnel events like begin_checkout and add_payment_info disappear from the stream. And because Shopify stopped passing personally identifiable data (email, phone, name) to legacy tracking scripts, platforms like Meta lose the fields they used to match conversions on.

One analytics team that audits these migrations (QE Retail) reports that the gap between Shopify's order counts and ad-platform-reported conversions can hit 30% or higher, and estimates that high-volume stores lose 15% to 20% of revenue into that reporting gap. Treat that as one team's findings rather than an industry benchmark — but the direction is not really in dispute, and the diagnostic signature is distinctive: orders in the admin look normal, the ad platforms report fewer and fewer of them.

The replacement channel is the Web Pixels API, which Shopify describes as giving "access to a set of controlled APIs for accessing browser APIs and subscribing to customer events, within one of our Lax or Strict sandboxes." If you are rewiring GTM, GA4, and ad pixels the new way, that rewrite is its own project — we walk it end to end in the Google Tag Manager on Shopify guide.

The replacement stack: five tools, not one

There is no single successor to checkout.liquid. There is a toolkit, and picking the wrong piece is the most common scoping mistake:

Checkout UI extensions — fields, banners, messaging, and content on checkout and post-checkout pages, running in an isolated sandbox instead of your theme.
Shopify Functions — back-end logic for discounts, shipping, payment, and validation.
Web Pixels API — the sandboxed replacement for tracking scripts; subscribes to customer events.
Post-purchase extensions — new UI and functionality on the post-purchase page, the offer screen shown immediately after payment and before the Thank you page.
Thank you and Order status extensions — the two post-checkout pages non-Plus stores are migrating right now.

Branding — colors, fonts, logos — is configured in the checkout editor. There is no separately named branding-API product to buy, and the URL commonly cited for one returns a 404.

The plan gate, precisely

Surface / tool	Plan needed
UI extensions — Information, Shipping, Payment	Shopify Plus only
UI extensions — Thank you & Order status	All plans except Shopify Starter
Web pixels	All plans (opened to non-Plus on May 21, 2024)
Functions apps distributed via the App Store	All plans
Custom apps containing Shopify Function APIs	Shopify Plus only

That last row catches people. Shopify's wording: "Apps that are distributed via the Shopify App Store and contain Functions can be used in all Shopify plans, but custom apps that include Shopify Function APIs can only be used by shops with a Shopify Plus plan." A custom Function you build for a Basic-plan client is not a scoping detail you want to discover in week three.

Hard limits worth knowing before you estimate

These are platform boundaries, not best practices. From the checkout UI extensions docs:

64 KB. "Your compiled UI extension bundle can't exceed 64 KB." This is the constraint that quietly kills do-everything widgets, and it is worth checking your bundle size on day one rather than day twenty.
Isolated sandbox. Extensions "run in an isolated sandbox, separate from the checkout page and other UI extensions" — they cannot talk to each other.
No payment or page access. They "don't have access to sensitive payment information or the checkout page itself."
Read-only metafields on Thank you. Extensions there "can read metafields through the Metafields API, but don't have write access."
Rate limiting. "After an extension is rate limited, it can't make further changes during the buyer's session."

If a vendor or a plan promises something on the far side of one of those lines, that is the moment to ask how.

The order of operations

The canonical article runs this as a tickable checklist; here it is as a sequence. Steps 1–3 are identical whichever route you take, the split is inside step 4, and the rest applies to everyone.

Find the store's actual status. Admin → Settings → Checkout → Configurations, then run the upgrade report. Non-Plus stores that haven't migrated also see an admin banner reading "Upgrade Thank you and Order status pages by August 26, 2026." Do this before you promise anyone anything.
Inventory what the checkout and Thank-you page actually do. Every custom field, banner, shipping or discount rule, every entry in additional scripts, and every installed app that relies on script tags. The apps are the part clients forget.
Route the work. Roughly: if the store only has tracking scripts and no real customization, this is a pixels job and little else. If it has content-level customization — banners, upsells, trust content, order-tracking widgets — the no-code checkout editor plus one app usually covers it. If it has store-specific logic that a settings toggle can't express, that is a UI extension or a Function, i.e. a build.
Build somewhere that isn't production. Two routes:
- No-code: build in a draft configuration. "Draft configurations let you try different apps and branding before you make them active." Only one configuration is active on real traffic at a time, and publishing a draft replaces the current active one — so the live checkout stays untouched while you assemble.
- Custom: preview on a dev store. "To run your extension locally during development, start a dev server using Shopify CLI. The dev command creates a preview of your extension on your chosen dev store."
Test before publishing. The checkout and accounts editor "uses a simulated checkout environment. You can't place orders in this editor, and some checkout and order actions like Pay Now and Buy Again are deactivated." For custom extensions there are two extra steps from the testing docs: preview a block extension in each supported placement by appending ?placement-reference={name} to the checkout URL, and to test against Shop Pay, activate Shopify Payments on the dev store and enable test mode, then "create a guest checkout using a test card for the payment method. Use an email that doesn't have a Shop Pay Account attributed to it."
Restore tracking on Web Pixels and customer events. Then actually verify: fire test events, and compare order counts against ad-platform conversions rather than assuming parity.
Publish and re-check. Publish the draft, re-run the upgrade report, confirm the legacy banner is gone.

One deployment gotcha that bites teams shipping their first extension: "Checkout UI extensions don't display in checkout until the merchant uses the checkout editor to add the app and place it in checkout." Deploying is not shipping. Somebody has to place the block.

The interactive checklist lives on the canonical article, and the five-question routing quiz is here.

What it costs, honestly

There is no market rate for this and the published data is thin. One migration guide estimates the no-code checkout editor covers about 80% of former checkout.liquid use cases, and puts a developer at roughly 2–3 days to rebuild a typical customization as a UI extension. One agency (Speedboostr) publishes about $5,000–$10,000 and 2–4 weeks for a simple migration, and over $50,000 and 8–16 weeks for complex builds; another (WeArePresta) puts senior developer and architect rates at $150–$300 an hour.

Every one of those numbers comes from a single source. Use them for orientation, never as a benchmark you quote back to a client. The reliable part is the shape of the decision: an app subscription, a scoped build, or accepting the standard checkout. Most stores are in the first bucket and are being quoted for the second.

Why Shopify says it did this

It is worth reading the platform's own framing, because it explains the constraints rather than just imposing them. Shopify called checkout extensibility "an easier way to customize Shopify Checkout in a way that's app-based, upgrade-safe, higher-converting, and integrated with Shop Pay."

The trade is legible: you lose arbitrary code in the checkout, and in exchange checkout updates stop breaking your work, because your code no longer lives in the path the platform is updating. The 64 KB cap and the sandbox isolation are the price of that guarantee, not arbitrary cruelty.

The bottom line

If you maintain non-Plus Shopify stores, do one thing this week: open Settings → Checkout → Configurations on each of them, run the upgrade report, and write down which ones still show the legacy banner. That is a ten-minute task per store and it converts an invisible deadline into a list.

Then work the list in the order above. Tracking first, because that is what costs money and nobody notices it dying. Content customizations second, because the no-code editor and an app cover most of them. Real logic last, because that is the only part that needs a build — and the only part where four weeks is a genuinely tight timeline.

The thing that burns people is not the deadline. It is that nothing announces itself when it passes.

Originally published at shopify.ecom-store.pro, where the article includes an interactive migration checklist, a five-question routing quiz, and the full deadline timeline with sources.

Disclosure: this article was created with the help of AI.

What a Shopify Expert Costs: Rates by Task, and When You Don't Need One

Alexandr M. — Sun, 26 Jul 2026 13:01:28 +0000

Two very different developers end up searching for the same number. One is a freelancer trying to work out whether $45 an hour for Shopify work is underselling or overreaching. The other is the technical person in the room when someone asks, "what should this theme change cost us?" — and has to answer without a benchmark. Both are looking for a published Shopify rate, and both are about to find out that Shopify does not publish one.

What does exist is a spread of third-party figures: Upwork's tier rates, Clutch's agency and regional bands, Shopify's own blog benchmark for freelance design work, and the fixed prices that managed marketplaces put on their pricing pages. Put together, they cover the range from $15 an hour to $199 an hour, and they let you sanity-check a quote from either side of the invoice. This piece pulls those numbers together, prices the common tasks, and — importantly for anyone who bills by the hour — shows which work has a published price and which is genuinely "quote it hourly."

One format note: the canonical version of this article carries an interactive budget calculator, a decision quiz, and two charts, none of which survive a plain markdown feed. Where they appear below, I have written out the same logic and the same data in text (including the calculator's formula as code), and linked to the interactive version.

Key takeaways

Published rates span $15 to $199 an hour — from Upwork's beginner tier to top Shopify agencies listed on Clutch.
Region moves the rate 4–6×. The same work runs $100–$149 an hour in the US and under $25 in India, per Clutch's regional data.
"Shopify Expert" is a legacy label. Shopify sunset the Experts Marketplace in December 2023; the live product is the Partner Directory.
Price by task, not by title. Theme edits start near $475; migrations, custom apps, and integrations are quoted hourly.
Shopify publishes no official Expert rate. You budget from real quotes benchmarked against third-party numbers, never a directory average.
Sometimes the right answer is "don't hire." A fix the theme editor or an app already handles rarely pays back a developer's day rate.

"Shopify Expert" is a name that no longer exists

Get the vocabulary straight before you price anything, because it decides where you look. Per Shopify's own partner docs, the Shopify Experts brand and corresponding Shopify Experts Marketplace was previously sunset in December 2023. The old experts.shopify.com address now redirects to the Shopify Partner Directory — "a curated list of Shopify Partners." The people are still there; the storefront around them changed. Half the "Shopify Expert cost" guides online still link to a marketplace that is gone, which is a decent proxy for how carefully they checked their numbers.

Shopify frames the value of hiring one this way:

"Experts can also help established businesses, by taking care of the tasks that there just aren't enough hours in the day to tackle yourself. You can find a wide range of services fit for every budget."

— Shopify, Shopify Experts Marketplace

The directory groups partner work into six service categories. If you are writing a brief, the category you name largely decides whether you get a designer, a developer, or a strategist:

Category	What it covers
Marketing and sales	Email, SEO, SEM, social, conversion-rate optimization, analytics
Store setup and management	Builds and redesigns, migration, product setup, theme customization, audits
Development and troubleshooting	Custom apps, integrations, and fixing what breaks under the hood
Visual content and branding	Logos, banners, video, product photography, 3D
Expert guidance	Business strategy, sourcing, tax, going international
Content writing	Product descriptions, website copy, marketing content

Source: Shopify Partner Directory — services (verified July 2026).

If you are still deciding what kind of help a project needs at all — developer, agency, or DIY — the Shopify development guide maps every route in about a minute.

Partner, freelancer, or agency

"Expert," "developer," and "agency" describe how you buy help, not how good it is. Three routes, three pricing shapes:

Who	How they're priced	Best for
Shopify Partner (Directory)	No published rate — you request a quote	Vetted, Shopify-specific work across setup, design, dev, and marketing
Freelance developer	$15–$29/hr typical on Upwork	A specific, well-scoped task at the lowest price
Agency	$50–$199/hr; minimums from $1,000	Strategy, integrations, and brand-critical builds with a team

The boundary is scope, not seniority. Once you have decided you need a person rather than an app, the harder questions are the hiring process itself and whether the investment pays back — both covered in the guide to when and how to hire a Shopify developer. And if the task is bespoke functionality rather than configuration, the overview of custom Shopify development maps the project types and the stack — useful for telling a $475 theme edit from a five-figure build before anyone quotes it.

The rates, by region and by platform

There is no single "Shopify expert rate," and Shopify publishes none. What you can do is triangulate from the rates that platforms and directories do publish. Two variables dominate: where the person sits, and where you hire them.

Region is the biggest lever

The single largest swing on an hourly rate is not seniority — it is geography. The same brief comes back four to six times apart:

Region	Hourly rate (USD)
United States	$100–$149
Poland	$50–$99
Ukraine	$25–$49
Philippines	$25–$49
India	Under $25

These are Clutch's general web/ecommerce development rates by region — regional orientation for Shopify work, not Shopify-specific figures. Source: Clutch web development pricing (verified July 2026).

Cheaper is not automatically better value. A lower regional rate can be a genuine bargain or a false economy, depending on communication, time-zone overlap, and portfolio quality. A slow, cheap build that misses the brief costs more than a right-sized one.

Rates by platform

Where you hire sets the rate as much as who you hire. On Upwork, the median Shopify developer bills $20 an hour, with most between $15 and $29, rising to $95 for the Expert tier. Shopify's own blog puts a freelance web designer at $20 to $100 an hour, with whole projects at $500 to $10,000.

Where you hire	Published rate	Notes
Upwork	$15 / $33 / $95 per hour by tier	Median $20; most fall $15–$29
Freelance designer (Shopify benchmark)	$20–$100/hr	Whole projects usually $500–$10,000
Storetasker	Projects from $400; Theme Edits from $475	Repeat dev work $150–$2,500 each
Clutch Shopify agencies	$50–$199/hr	Project minimums from $1,000 to $25,000 or more
HeyCarson (rebranding to shopexperts)	$110/hr for pay-per-project work	No minimum or maximum project size

Rates as published by each platform and Shopify's blog benchmark, verified July 2026. Marketplace figures are observed and may drift.

If you are the one being hired

Read that table in the other direction and it is a rate ladder. Upwork's three tiers — $15, $33, $95 — are the clearest published statement of what experience is worth on an open marketplace, and the gap between "intermediate" and "expert" there is roughly 3×, which is a bigger jump than most freelancers give themselves credit for. Managed marketplaces sit between open bidding and the directory: they set the price for you ($110 an hour at HeyCarson, fixed project prices at Storetasker) and hand you scoped work. The Partner Directory is the slowest but highest-trust route — partners there are curated, with tiers (Select, Plus, Premier, Platinum) reflecting track record on Shopify, and they quote clients directly. If that path interests you, the realistic route to becoming a Shopify expert covers the Partner Program, how partners earn, and the directory criteria.

What common tasks actually cost

Rates tell you the hourly number; this tells you the bill. Below are the tasks with published prices — and the ones that have no fixed price and must be quoted by the hour. I am not inventing ranges for those.

Task	Typical price	What moves it
Theme edits / customization	From $475	Number of sections and design complexity
Small, well-defined task	From $400	Scope and how urgent it is
Ongoing / repeat dev work	$150–$2,500 each	Recurring scope; retainer or per project
Whole-store design (freelancer)	$500–$10,000	Template setup vs custom design
Whole-store build (agency)	$3,000–$75,000	Team, integrations, migration
Custom development / build	$2,000–$20,000+	Complexity and one-off edge cases
Migration, custom app, or integration	Quoted hourly	Hours × rate — no published price exists

Storetasker and Shopify published figures, verified July 2026.

For the work that is quoted rather than listed, here is the worked example the original article uses throughout. Assume a mid-size theme customization takes 12 hours — an explicit assumption, since Shopify publishes no task-hour standard. Price those same 12 hours at each published Upwork tier:

Upwork tier	Rate	12-hour task
Beginner	$15/hr	$180
Intermediate	$33/hr	$396
Expert	$95/hr	$1,140

Same scope, same hours, a 6.3× spread. Which is the entire argument for pinning down hours in writing before you argue about the rate.

The original renders this as an interactive chart. See the chart on the canonical article.

The five-question version of "do I even need to pay?"

The canonical post runs this as an interactive quiz. Here is the same logic, self-scored. Answer five questions, add up the points:

What needs doing? Quick fix or content edit I could probably do myself (0) · Theme customization or design refresh (2) · Custom features, integrations, or a migration (3) · A full custom or headless build (3)
Have you checked whether an app or the theme editor can do it? Not yet (0) · An app half-solves it, but not cleanly (2) · Yes, nothing off-the-shelf covers it (3)
Budget for this project? Under $500 (0) · $500–$3,000 (2) · $3,000 or more (3)
How much of your own time can you put in? Plenty, I would rather learn and DIY (0) · Some, but this is not the best use of it (2) · None, I need it off my plate (3)
How business-critical is it? Nice to have (0) · Important, it affects conversion or operations (2) · Critical, it is blocking revenue (3)

11–15 — hire a partner or agency. The project is complex, time-sensitive, or business-critical enough to justify vetted paid help. Start in the Shopify Partner Directory, send the same written brief to two or three partners, and compare quotes on identical scope.

7–10 — a freelance developer for a focused task. You need more than the editor but not a full agency: a custom section, a theme edit, a small integration. Under $500, keep the job tiny — Storetasker lists Theme Edits from $475 with a four-day turnaround, which is about the ceiling of that budget. In the $500–$3,000 band you are in the freelancer sweet spot, where the 12-hour, $1,140 example lives and where Storetasker's repeat projects ($150–$2,500) sit. Above $3,000 you are near the line between a task and a build — Shopify benchmarks freelancer projects at $500 to $10,000, so if it is really a whole-store project, brief a directory partner too and compare.

Under 7 — you probably should not pay yet. Small task, tight budget, time to learn. Try the theme editor, then the Shopify App Store. Come back for paid help when a specific limit starts costing sales.

Hourly, fixed, or retainer

The same person at the same rate can cost wildly different amounts depending on how the deal is structured. Three models cover almost everything:

Model	How it bills	Best when
Hourly	Time logged at an agreed rate	Scope is unclear or the work is exploratory
Fixed-price	One quoted price for a defined deliverable	The scope is written down and will not move
Retainer	A recurring monthly fee for ongoing capacity	You need continuous fixes and improvements

The trap is a fixed price on a vague brief. The developer either pads the number to cover unknowns or cuts corners when the work runs long, and both outcomes are bad for both sides. If the deliverable cannot be defined precisely, bill hourly and cap the hours.

The six things that move a quote

When two quotes for "a Shopify store" differ wildly, it is usually one of these doing the work. Read it as a checklist — each is a place you can add cost or take it out before anyone quotes:

Custom design. Configuring a theme is cheap; designing a bespoke storefront from scratch is the single biggest driver of a quote.
Integrations and apps. An off-the-shelf app is cheap. A custom integration between Shopify and an ERP, POS, or legacy back office is one-off engineering — and where quotes climb.
Data migration. Porting products, customers, orders, and SEO redirects from another platform is a project in its own right, and the line most people forget to budget.
Scope clarity. A vague brief inflates every quote, because the developer prices the risk of the unknown. A written scope is the cheapest thing you can bring to the conversation.
Region and seniority. The same task can be priced 4–6× apart depending on where the person sits and how senior they are.
Urgency. A rush job competes with an existing pipeline. Compressed timelines carry a premium; a flexible deadline is a bargaining chip.

The budget math, in code

The interactive calculator on the canonical post is deliberately boring arithmetic — its value is that every rate is a published figure, so the estimate cannot drift into invented numbers. The whole model:

// Published rates only (USD/hour), verified July 2026.
const RATES = {
  upworkBeginner: 15,      // upwork.com/hire/shopify-developers/cost
  upworkIntermediate: 33,  // upwork.com/hire/shopify-developers/cost
  upworkExpert: 95,        // upwork.com/hire/shopify-developers/cost
  freelanceLow: 20,        // shopify.com/blog/outsource-website-design
  freelanceHigh: 100,      // shopify.com/blog/outsource-website-design
  agencyLow: 50,           // clutch.co/us/developers/shopify
  agencyHigh: 199,         // clutch.co/us/developers/shopify
};

// Shopify's published freelance-project band, used as a reasonableness check.
const BAND = { min: 500, max: 10000 };

function estimate(hours, tier) {
  // Hours are YOUR assumption - Shopify publishes no task-hour standard.
  const h = Math.min(Math.max(hours, 1), 200);
  const total = h * RATES[tier];
  const status =
    total < BAND.min ? "below" : total > BAND.max ? "above" : "in";
  return { hours: h, rate: RATES[tier], total, status };
}

estimate(12, "upworkExpert");
// { hours: 12, rate: 95, total: 1140, status: 'in' }

Three things worth stealing from that model even if you never use the tool. The clamp on hours stops silent extrapolation. The band check tells you which conversation you are in: below $500 is a small defined task (Storetasker's Theme Edits, for reference, start at $475), inside the band is normal freelance-project territory, above $10,000 is agency-scale work where you should expect a project minimum. And the output is labor only — no app subscriptions, paid themes, ongoing maintenance, or agency minimums.

Use it in one direction only: ask the developer for their hours estimate in writing, plug it in, and treat the gap between your number and their quote as the conversation to have.

Try the interactive calculator on the canonical article.

Finding someone, and reading the quote

Start with the Shopify Partner Directory for vetted, Shopify-specific help, and use marketplaces like Upwork or Storetasker when you want public rates and reviews on a smaller task. The directory's own flow is a decent model for the whole process:

Browse. Filter by service, industry, budget, and location.
Evaluate. Check reviews, work samples, and certifications. Partner tiers — Select, Plus, Premier, Platinum — reflect track record on Shopify.
Contact and collaborate. Reach out directly, share the brief, set your own project terms. Contacting a partner is not a commitment to hire.

The difference between a fair quote and an inflated one is almost always the brief. Shopify's guidance is blunt about it:

"Define your budget, timeline, and expected outcomes in detail to allow the Partner to provide an accurate quote."

— Shopify Help Center, Hiring help from a Partner

In practice that is about ten minutes of writing. A template that gets comparable quotes back:

Store: <URL, platform, theme, roughly how many SKUs>
Problem: <what is broken or missing, in one sentence>
Deliverable: <what "done" looks like, concretely>
Out of scope: <what you are NOT asking for>
Constraints: <apps/integrations it must not break, deadline>
Budget range: <a real number, not "competitive">
Deliverables format: <PR to a branch? theme package? staging store?>

Send that same text to two or three people. Identical inputs give comparable quotes, and the outlier usually tells you who actually understood the job.

Two practical points people miss. First, partners bill you directly — those charges never appear on your Shopify invoice, so treat the engagement like any other vendor contract. Second, a first conversation is not a commitment.

Quote red flags: no line-item breakdown (a lump sum hides what you are paying for); an open-ended scope; pressure to pay 100% upfront when staged milestone payments protect both sides; a rate far outside regional norms with no explanation.

When not to hire at all

The most honest budgeting advice is sometimes "don't." Plenty of work people assume needs an expert is built into Shopify or solved by a cheap app.

Do it yourself when:

The theme editor already does what you need
A low monthly app covers the feature
It is a content edit or swap you can learn in an afternoon
The budget is tight and the task is not urgent
You are pre-launch with a small catalog

Hire when:

You need bespoke design the editor cannot produce
A custom integration or migration is involved
Performance problems are hurting conversion
The work is business-critical and time-sensitive
The revenue at stake clearly outweighs the quote

Before briefing anyone, check the Shopify App Store — a $20-a-month app almost always beats a $2,000 build for standard features like reviews, subscriptions, or email. Reserve custom budgets for the genuinely custom.

The bottom line

"How much does a Shopify expert cost?" has no single answer because you are not buying one thing. A theme edit starts near $475. That 12-hour customization at the Expert rate is about $1,140. A whole agency build runs into the five figures. The platform never changes — the labor does.

So: anchor to a published rate, then bend it to a real written quote. Buy the smallest fix that solves the problem, skip it entirely when Shopify already does the job, and never accept a fixed price on a scope nobody has written down. If you are on the other side of the invoice, the same table is your rate ladder — and the same discipline about written scope is what stops a fixed-price job from quietly becoming an hourly one at your expense.

FAQ

Is the Shopify Experts Marketplace still a thing?
No. Shopify sunset the Shopify Experts brand and the Experts Marketplace in December 2023. The old experts.shopify.com address now redirects to the Shopify Partner Directory, which is where you browse and contact vetted partners today. The marketing still says "Hire Shopify Experts," but the product you actually use is the Partner Directory.

How much does a Shopify expert cost per hour?
It depends on where and how you hire. On Upwork, Shopify developers post a $20 median rate, with most between $15 and $29 an hour; experienced pros reach $95. Shopify agencies on Clutch advertise $50 to $199 an hour. Region matters most — US rates run far higher than offshore ones for the same task.

Does Shopify publish official Shopify Expert rates?
No. Shopify runs the Partner Directory, but it publishes no hourly rates or project prices for the partners listed there — they work independently and quote you directly. Use third-party benchmarks like Upwork and Clutch to set a sane range, then budget from the real quotes you collect.

What's the difference between a Shopify Expert, a developer, and an agency?
"Shopify Expert" is the legacy label for a vetted partner in Shopify's directory — often a freelancer or small studio. "Developer" is a job, not a certification; anyone on Upwork can claim it. An agency is a team that bundles design, development, and strategy. Match the choice to your scope: a task, a specialist, or a full build.

How much does it cost to customize a Shopify theme?
Theme edits are the most affordable expert work. On Storetasker, Theme Edits start at $475 with a four-day turnaround; on Upwork, a mid-size customization at the Expert rate of $95 an hour runs about $1,140 for an assumed twelve hours. The real driver is how many sections and how much bespoke design you need.

Should I hire on Upwork or through the Shopify Partner Directory?
Both work; they trade convenience for vetting. The Partner Directory lists partners Shopify has curated, with tiers based on track record — lower risk, but you request quotes. Upwork is faster and shows public rates and reviews, but anyone can list, so you vet harder. For a critical build, favor the directory; for a small, clear task, Upwork is often quicker.

Hourly, fixed-price, or retainer — which should I choose?
Choose by how well you can define the work. If the scope is written down and stable, fixed-price protects you from surprises. If it is exploratory or likely to change, hourly is fairer to both sides. If you need continuous fixes and improvements, a monthly retainer buys reliable capacity. Never accept a fixed price on a vague brief.

Do I pay the Shopify expert through Shopify?
No. Partners you find in the directory bill you directly, and those charges do not appear on your Shopify bill. Contacting a partner also is not a commitment — you decide whether to hire after the conversation. Agree scope, milestones, and payment terms in writing before money changes hands.

What makes a Shopify expert's price go up the most?
Four things, mostly. Custom design from scratch costs far more than configuring a theme. Integrations with an ERP, POS, or custom API are one-off engineering. Data migration from another platform is a project in itself. And a vague brief inflates every quote, because the developer prices the risk of the unknown. Region and seniority then scale the hourly rate.

Originally published at shopify.ecom-store.pro, where the article includes an interactive budget calculator, a five-question decision quiz, and rate charts.

Written by Alexander Matynian, a front-end developer working with Shopify since 2017 — building custom Liquid storefronts, scoping and pricing client builds, and hiring on both sides of the invoice. More e-commerce guides at shopify.ecom-store.pro.

Disclosure: this article was created with the help of AI.

Is Shopify's $1 for 6 Months Deal Real in 2026? (And How It Differs From the 3-Month Offer)

Alexandr M. — Tue, 21 Jul 2026 19:14:42 +0000

If you build or maintain Shopify stores for clients, you have fielded this question: "I saw a deal — $1 a month for 6 months. Is that real, or is it one of those too-good-to-be-true things?" It is a fair thing to ask before committing a business to a platform, and the honest answer is more nuanced than the affiliate blogs ranking for that query make it sound — half of them are quoting numbers Shopify retired a year ago.

This is the developer-facing short version: what a client is actually offered at signup in 2026, where the real six-month price comes from, and one new promo almost nobody has written up correctly yet. Every figure below was checked against Shopify's own live pages and official offer terms on July 21–22, 2026 — the terms genuinely move, so treat any undated number you read elsewhere with suspicion.

The interactive version — a post-trial cost calculator, the full eligibility matrix, and a monthly-updated offer tracker — lives on the canonical post. What follows is the text summary you can forward to a client to answer "is it real" without them needing to click through.

The short answer

Yes, a $1/month-for-6-months Shopify deal is real — but "real" needs three footnotes, and only one of them is the deal most people picture. Here is the whole map.

What your client actually sees at signup (verified July 21, 2026)

The public offer on shopify.com/pricing right now reads: "Try 3 days free, then $1/month for 3 months." That is three days of free trial, then a $1/month promotional rate for three months — not six. The amount renders as $1 / €1 / £1 per month depending on the store's region; it is the same offer in local currency.

So the default a US, UK, or EU client is shown today is the three-month version. If you want the deeper mechanics of that standard offer, I break it down in the $1 for 3 months guide. The part that matters for scoping a client engagement: the promotional term is assigned by Shopify per visitor and locked at signup — it cannot be extended or converted afterward.

Where the real six-month price comes from

There is exactly one confirmed route to $1/month for six months, and it is a program, not a public banner: Shopify's 1MBB (1 Million Black Businesses) partnership. It offers the Basic plan at $1/month for the first six months, limited to eligible merchants in the US and Canada. Two things to flag to a client before they get excited:

It is a paid discount, not a free trial. They pay $1/month (six real payments), they are not getting six free months.
Eligibility is real and enforced. It is built for a specific group of entrepreneurs; it is not a loophole anyone can trigger with a referral link.

If you have seen a guide describing 1MBB as a "120-day free trial," it is out of date — that framing contradicts Shopify's live 1MBB page as of July 21, 2026. Quoting it to a client is how you lose credibility three weeks into a build.

There is also a separate "6 months on us" offer for Shopify Plus — but that is an enterprise migration incentive tied to a three-year commitment, aimed at brands moving off another platform. It is not the standard-plan trial anyone means when they say "the $1 deal."

The part almost nobody has covered correctly: sales credits

Here is the genuinely new thing — and the one where even Shopify's own pages will trip you up. The current promo layers subscription credits, not cash on top of the $1/month pricing: per the official rewards promotion terms, you accrue 1% back on sales made through Shopify Payments (0.5% on other gateways) over your first six months, or until you hit your plan's cap:

Plan	Credit cap (USD)
Basic	$5,000
Grow	$7,500
Advanced	$10,000
Plus	$10,000 (1-yr) / $15,000 (3-yr)

A warning about verifying this yourself: the banner on shopify.com/free-trial and the cap badges on the pricing page are templated per visitor — in the same July week, the identical page showed different headline figures to different visitors. If a write-up quotes credit caps without citing the offer's terms and conditions, assume it screenshotted a banner. The caps above come from the terms page (verified July 22, 2026); the currency follows the store's region (the same $1 / €1 / £1 logic applies). Treat the credit as a bonus on top of the runway, not a reason to steer a client into overspending to chase it.

Six months vs three months: what actually differs

For a client comparing the two, the only real difference is duration. Features, app access, and card-processing fees are identical on both. In subscription terms:

3-month deal: about $3 total in platform fees.
6-month deal: about $6 total in platform fees.

That is it — three extra dollars buys twice the low-cost runway. The difference that matters is not the three dollars; it is the extra optimization window. With three months, most stores are still in setup when the promo ends. Six months gets a client through a real learn-and-iterate cycle before standard pricing applies.

After the promo, the plan reverts to standard pricing (Basic is $39/month, or $29/month on annual billing, per shopify.com/pricing), and Shopify does not extend or reset promotional pricing — so put that renewal date on the project calendar.

What to tell a client (the 60-second version)

The public deal in 2026 is 3 days free, then $1/month for 3 months — assume that, not six.
$1/month for six months is real but program-gated (1MBB; US/Canada; Basic; a paid discount).
Do not delay a launch waiting for a six-month term to appear — it is assigned per visitor and cannot be summoned.
There is a real sales-credits promo layered on top — 1% back via Shopify Payments, capped at $5,000–$10,000 on standard plans; quote the offer terms, not a banner screenshot.
Read the exact term shown at signup — it is locked the moment the account is created.

For the interactive post-trial cost calculator, the full eligibility matrix, and a monthly-updated offer tracker, see the full breakdown on shopify.ecom-store.pro. Everything above was verified against Shopify's live pages and official offer terms on July 21–22, 2026.

Originally published at shopify.ecom-store.pro, where the post includes an interactive post-trial cost calculator and a monthly-updated offer tracker.

Written by Alexander Matynian, a front-end developer working with Shopify since 2017 — building custom storefronts and scoping client builds on both sides of the invoice. More e-commerce guides at shopify.ecom-store.pro.

Disclosure: this article was created with the help of AI.

Shopify Development: Who to Hire, What It Costs, and Where to Start

Alexandr M. — Sat, 18 Jul 2026 09:47:30 +0000

If you build Shopify stores for clients, you have watched the confusion from the buyer's side. A merchant knows the store needs work — a build, a fix, a custom feature, a second pair of hands — but not who to hire, what it should cost, or which answer fits their exact situation. The words do not help: expert, developer, freelancer, agency, and Partner describe overlapping people, and half the articles online still point to a Shopify Experts Marketplace that no longer exists.

This is a routing map, not a how-to. It matches a real situation to the person who usually does that work, an orienting budget, and the one deep-dive guide that covers it. It is worth reading from either side of the invoice. If you are a merchant, it tells you what to hire and roughly what to pay. If you are a developer, freelancer, or technical operator, it shows you how buyers segment the work, the hourly benchmarks the market actually bears, and — in a dedicated section near the end — how to flip the whole thing around and get hired instead of hiring.

Every figure below is pulled straight from the source article — no invented averages. Two anchor facts up front: the old Shopify Experts Marketplace was retired in December 2023, so the official place to find help today is the Shopify Partner Directory; and agencies bill roughly $50 to $199 an hour, which means who you hire can double the same bill before what you build ever enters the conversation.

One format note: the original page carries an interactive five-question route quiz — a segmenter that routes each reader to one of the cluster guides — and that does not survive a plain markdown feed. Below I render the same routing logic as a short text decision guide and point you to the live quiz on the canonical post.

Key takeaways

Most stores do not need an agency — a freelancer, a Shopify Partner, or a few hours of expert time solves most jobs.
Agencies bill roughly $50 to $199 an hour, while smaller ecommerce development firms often run $24 to $49 — so the same ten-hour job ranges from hundreds to a couple thousand dollars.
Whole builds span five scenarios, from a few hundred dollars for a bare-bones DIY first year to tens of thousands for a full custom build on Plus.
Hire through the Shopify Partner Directory — the vetted list that replaced the Experts Marketplace in December 2023.
Expert, developer, freelancer, and agency overlap — the real deciding factor is how big and how custom your project is, not which title sounds most official.
Want to earn as a Shopify pro? The free Partner Program pays via referrals and revenue share, not a membership fee.

Who you actually need (and who you don't)

The honest starting point: most Shopify jobs do not need a full agency. The labels blur together, and what actually decides who you hire is how big and how custom the work is. Four roles cover the field:

Freelancer — one independent pro for a defined task or build. Best when you have a clear, contained scope and want a direct line to the person doing the work.
Agency — a team that handles strategy, design, and development end to end. Best for full builds, tight deadlines, or work that spans many skills at once.
Shopify Partner — a vetted freelancer or agency listed in Shopify's Partner Directory. Best when you want Shopify-verified experience and a searchable track record.
Do it yourself — Shopify is built for non-coders. Best for content, settings, and light theme tweaks when your budget is near zero and the scope is simple.

The official place to hire is the Shopify Partner Directory, which lists vetted partners across six service categories — from store setup to development — so you can browse, compare, and contact them directly. It replaced the old Experts Marketplace, so if a competing article still sends you to the "Shopify Experts" page, it is out of date.

Find your route: the situation table

This is the core of the page. Each row is a real situation, matched to who typically does the work, an orienting budget, and the guide that covers it in full. Find your row, then follow the last column.

Your situation	Who you need	Typical budget	Start here
Building your first store	You (DIY) or a freelancer	$500–$10,000 project (freelancer)	Ecommerce website guide
A full custom build, done for you	Agency or senior developer	$2,000–$20,000+ project (custom)	Store development cost
A specific feature, app, or integration	A developer or agency	$50–$199/hr (agency)	Custom development
Still on checkout.liquid or checkout Scripts	A developer or agency (non-Plus deadline: Aug 26, 2026)	$5,000–$10,000 simple; $150–$300/hr complex	Checkout extensibility guide
Discounts, shipping, or payment rules broke (Scripts deactivated Jun 30, 2026)	You (native fix), an app, or a developer — depends on the Script	Free–$15/mo app swap; $4,000–$12,000+ custom Function	Scripts to Functions guide
A redesign or a new look	Freelancer or agency	$3,000–$75,000 project (redesign)	Custom design
On Dawn, deciding whether to move to Horizon	You (DIY) or a freelancer for custom code	Free DIY; $20–$100/hr for custom pieces	Horizon theme guide
Small one-off fixes	Freelancer or task service	from $475/task; $150–$2,500 each	Hiring a developer
Ongoing support or a retainer	A freelancer or Shopify Partner	$24–$49/hr (smaller firms); $50–$199/hr (agency)	Expert cost guide
You want to earn as a Shopify pro	That's you — join the Partner Program	Free to join	Become an expert
Live, but sales are underperforming	You (self-audit) first, then maybe a freelancer or agency	Free self-audit; fixes range from DIY to a redesign budget	Store patterns audit
Duplicate URLs, canonical tags, robots.txt, or a GSC coverage drop	You (self-audit) first, then a developer for structural fixes	Free self-audit; $50–$150/hr for technical fixes	Technical SEO audit

Ranges are orienting figures from public agency, freelancer, and Shopify benchmarks (2026) — your real number depends on scope. Read the budget column as a starting point, not a quote: the same task can sit at either end of a range depending on complexity, region, and who you hire.

What it costs: the 60-second version

Pricing comes in two shapes. The first is an hourly rate: agencies typically bill about $50 to $199 an hour, while smaller ecommerce development firms often run $24 to $49. The second is a project total: a single theme edit might start around $475, while recurring development tasks land anywhere from $150 to $2,500 each.

Here is why the "who" matters more than the "what." The same ten-hour custom job — say wiring up a product configurator — costs $500 at the low end of agency rates ($50/hour) and $1,990 at the high end ($199/hour). Ten hours, identical work; the spread is entirely who you hire.

Whole builds are a different question. Five end-to-end scenarios run from a few hundred dollars for a bare-bones DIY first year to tens of thousands for a full custom build on Plus — the store development cost guide has the exact numbers. And if the budget is close to zero, hiring may not be necessary at all: Shopify is built for non-coders, and you can tune a theme's colors, layout, and content yourself before paying anyone — the custom design guide walks the DIY path.

Not sure? The route decision guide

The original page ends this stretch with a five-question quiz that segments you to one of three routes. The questions it asks: what you actually need done, what state your store is in, how complex the work is, your budget comfort, and how you want it done. Map your own answers against the three routes below.

The full-build route — your answers point to a whole store or a big custom project, the kind of work an agency or a senior developer handles end to end.

Write the scope before you brief anyone, so quotes stay comparable.
An agency earns its rate on breadth — design, dev, and strategy together.
Ask for a fixed, milestone-based quote rather than open-ended hours.

Start with what a custom Shopify build involves, then set the budget behind it.

The targeted-specialist route — you have a live store and a specific job: a feature, a fix, or a redesign. A freelancer or a vetted Shopify Partner is usually the right call.

One clear task on one page keeps a freelancer engagement affordable.
A vetted Partner adds a searchable track record on the same budget.
Start with a small paid test task before a bigger commitment.

See when and how to hire a Shopify developer and check what a Shopify expert costs by task before you agree a rate.

The start-here route — you are early, exploring, or keen to keep costs near zero, and Shopify is built for exactly that.

Launch on a free theme first; you can always upgrade the look later.
Learn the theme editor before paying anyone to change pixels.
Bring in a freelancer only for the specific job you cannot DIY.

Begin by building your first Shopify website yourself, and tune the design before spending a dollar.

The interactive quiz on the canonical version of this page routes you to the exact guide in five clicks.

Hiring without the expensive mistakes

Three mistakes drain hiring budgets more than any hourly rate: buying too much team (an agency for a one-hour fix, when a freelancer would do), a fuzzy brief (vague scope is how quotes balloon), and skipping the paid test task (a small trial tells you more than any portfolio). The safest hedge against the first two is starting from Shopify's own vetted list rather than a random search result.

"The Partner Directory connects you with Shopify Partners who you can hire for complicated tasks related to building your business."

— Shopify Help Center, Hiring and working with Shopify Partners

For the full when, why, and how — including a vetting sequence that avoids costly misfires — read the guide to hiring a Shopify developer. And for anything genuinely custom — new features, integrations, or a headless front end — scoping the project well is half the job; a tight brief is the single cheapest way to keep an estimate from turning into an open-ended bill.

Reading this as a freelancer?

Not hiring — hoping to get hired? The route flips. Shopify's Partner Program is free to join, and partners earn through referrals and revenue share, so the barrier is skill and reputation rather than a membership fee. You build a profile, list your services in the Partner Directory, and win clients from there.

For the realistic path — landing your first clients, meeting Directory criteria, and a 90-day plan to get there — see the guide on how to become a Shopify expert.

The bottom line

There is no single "Shopify developer" a merchant is supposed to hire. There is a spectrum — from doing it yourself, to a freelancer for a defined job, to an agency for a full custom build — and the right choice is whichever matches the project's size and complexity. Get that match right and everything downstream, including the price, gets simpler. The one move that saves the most money: write down exactly what "done" looks like before anyone talks to anyone. A tight scope turns a vague, open-ended bill into a fixed, comparable quote.

FAQ

Do I need to hire anyone to build a Shopify store?
Not necessarily. Shopify is built for non-coders, so you can pick a theme, add products, and launch entirely on your own. You typically hire only when the work outgrows the theme editor — custom features, a bespoke design, integrations, or simply saving time. Start DIY, and bring in help for the specific parts where you get stuck.

What's the difference between a Shopify expert, developer, and freelancer?
They overlap more than the labels suggest. A developer writes code; a freelancer is any independent pro you hire directly; a Shopify Expert or Partner is a vetted specialist listed in Shopify's Partner Directory. One person can be all three. What matters isn't the title but whether their skills and track record fit the job you need done.

How much does it cost to hire a Shopify developer?
It depends on scope and who you hire. Smaller ecommerce development firms often run $24 to $49 an hour, while agencies charge roughly $50 to $199. A small theme edit can be a few hundred dollars; a complex custom feature climbs into the thousands. The Shopify expert cost guide breaks the numbers down by task and region.

What is the Shopify Partner Directory?
It's Shopify's curated, official list of vetted partners — freelancers and agencies — you can hire for store work. You browse by price, location, and service, review each partner's ratings and past projects, then contact them directly. It replaced the old Experts Marketplace and is the safest place to start when you want Shopify-verified experience.

Is the Shopify Experts Marketplace still around?
No. Shopify sunset the Experts Marketplace and the standalone Shopify Experts brand in December 2023. The old experts page now redirects to the Shopify Partner Directory, which serves the same purpose — connecting merchants with vetted partners. If a competing article still points you to the Experts Marketplace, it is out of date; search the Partner Directory instead.

Freelancer or agency — which should I choose?
Match it to scope. A freelancer or single Partner is ideal for a contained job — a fix, one feature, or a redesign — and usually costs less. An agency earns its higher rate on full builds, tight deadlines, or work spanning strategy, design, and development at once. If you can write the job on one page, a freelancer is often enough.

How much does a full Shopify store build cost?
It ranges widely with ambition. Five end-to-end scenarios span from a few hundred dollars for a lean DIY first year to tens of thousands for a full custom build on Shopify Plus. Most first stores land far below the top end. The store development cost guide walks through each scenario with the exact numbers so you can find your match.

How do I hire a Shopify developer without overpaying?
Three habits help most. Write a clear, specific scope so quotes are comparable and don't balloon mid-project. Match the tier to the job — don't pay agency rates for a one-hour fix. And start with a small paid test task before committing to a large build. A tight brief is the single cheapest way to control the final bill.

Can I become a Shopify expert myself?
Yes. Shopify's Partner Program is free to join, and partners earn through referrals and revenue share rather than a membership fee — so the barrier is skill and reputation. You build a profile, list your services in the Partner Directory, and win clients from there. The guide on becoming a Shopify expert lays out a realistic path and a 90-day plan.

What does custom Shopify development include?
It covers anything beyond what a theme and apps do out of the box — bespoke features, third-party integrations, custom checkout logic on Plus, or a headless front end built on Shopify's APIs. Projects range from a single custom section to a full rebuild. The custom development guide breaks down the project types, tech stack, and scoping.

How do I know which of these guides to read?
Use the router table and the decision guide above. The table matches your situation — first store, custom feature, redesign, ongoing support — to the right specialist, a budget range, and the exact guide that goes deep. The text routes do the same if you'd rather be pointed than scan. Both lead to one of the cluster guides.

Originally published at shopify.ecom-store.pro, where the article includes an interactive route quiz that segments you to the right cluster guide.

Disclosure: this article was created with the help of AI.