DEV Community: Alexandr M.

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.

Custom Shopify Development: The 5 Types, the Full Stack, and How to Scope a Build

Alexandr M. — Tue, 14 Jul 2026 08:22:13 +0000

If you have ever been handed a Shopify store and asked to "just add a custom feature," you already know that the phrase custom development hides an enormous range. It can mean a ten-minute CSS override or a six-month headless rebuild on Hydrogen — and the two live on the same platform, priced an order of magnitude apart. The hard part of a Shopify build is almost never the platform. It is deciding how much custom code the problem actually deserves.

This piece is written for the developer, freelancer, or technical operator who has to either build custom Shopify work or scope it before someone else does. We will map the five types of custom development from simplest to most complex, walk the full modern stack (Liquid, CLI, Storefront and Admin APIs, Checkout Extensions, Functions, Hydrogen, Theme App Extensions), cover how to scope a project so the estimate holds, look at costs and timelines with concrete mid-range numbers, and settle the two decisions people get wrong most often: theme versus app, and monolithic versus headless. Every figure below is pulled straight from the source article — no invented averages.

The single most useful habit before any of this: the question is not "can we build it?" — it is "should we build it?" Every custom feature adds maintenance cost and surface area. The best developers push back when a $20/month app solves the same problem as a $5,000 custom build. That discipline is worth more than any framework choice.

One format note: the original article carries two interactive charts and a set of expandable components that do not survive a plain markdown feed — a stack-adoption bar chart and a timeline-versus-cost chart. Where those appear below I render the same data as tables and point you to the interactive version on the canonical post.

Key takeaways

Five development types — theme tweaks, custom sections, private apps, API integrations, and headless builds.
Costs range $500–$50K+ — theme mods start low; headless Hydrogen builds exceed $50K.
Liquid powers most stores — it remains the core skill; headless is for high-scale use cases.
Scoping saves 40% of budget — clear requirements and acceptance criteria prevent scope creep.
Headless is not for everyone — unless you need sub-second loads at scale, Liquid themes deliver better ROI.
Staging and QA are non-negotiable — test every change on a dev store before touching production.
Developer rates vary widely — freelancers run $30–$150/hr, agencies $100–$250/hr; match complexity to the right model.

What custom Shopify development actually is

Shopify gives you a powerful foundation: hosted commerce, secure checkout, payment processing, and a drag-and-drop theme editor. For many stores, that is enough. Custom development starts where the built-in tools stop — and "custom" does not always mean "expensive" or "complex." It is a spectrum:

Low complexity: tweaking CSS, adjusting Liquid templates, adding a custom font or animation.
Medium complexity: building custom sections, creating unique product page layouts, integrating a third-party API.
High complexity: developing private apps, building checkout extensions, or creating a headless storefront with Hydrogen.

Worth drawing a hard line here: theme customization means using Shopify's built-in editor to adjust colors, fonts, sections, and layouts — no code. Custom development means writing code (Liquid, JavaScript, React) to build functionality the editor cannot produce. If you are not sure which side of that line your task falls on, the companion guide to theme setup versus a developer build maps the two paths and what each costs.

If you want the full walkthrough of theme development end to end, there is a solid video introduction that covers architecture, Liquid basics, and building custom sections from scratch.

Buy vs build: App Store or custom development?

The first question is not "who should I hire?" — it is "do I need to hire at all?" The Shopify App Store has over 13,000 apps, and many solve problems that would cost $3,000–$10,000 to build custom.

Use an existing app when:

The feature is common (reviews, upsells, loyalty, subscriptions).
A well-rated app with 100+ reviews exists for your need.
The monthly cost ($10–$100/mo) is less than custom dev amortized over two years.
You do not need deep integration with your ERP or custom workflows.

Build custom when:

No app exists for your specific workflow.
Available apps cannot integrate with your existing systems (ERP, CRM, WMS).
You need full control over data, performance, or the user experience.
App subscription fees would exceed custom dev cost within 12–18 months.
Security or compliance requirements prohibit third-party data access.

For most stores under $500K annual revenue, the optimal strategy is the 80/20 rule: use apps for 80% of functionality and invest in custom development only for the 20% that creates competitive differentiation — unique product experiences, proprietary flows, or integrations no off-the-shelf solution handles.

The 5 types of custom Shopify development

Not all custom development is equal. Here are the five categories, ordered simplest to most complex:

Theme modifications — CSS tweaks, layout changes, custom fonts, color schemes, and minor Liquid edits. The most common type: modifying an existing theme to match your brand without building from scratch.
Custom sections & templates — building new Liquid sections (custom product pages, landing pages, mega-menus, comparison tables) using Online Store 2.0 architecture. Reusable, merchant-editable blocks.
Private app development — custom Shopify apps for unique business logic: automated pricing rules, B2B portals, custom loyalty systems, or workflow automation no public app handles.
API integrations — connecting Shopify to ERPs (NetSuite, SAP), CRMs (Salesforce, HubSpot), warehouses (ShipBob), POS systems, or custom internal tools via REST or GraphQL APIs.
Headless / Hydrogen builds — decoupling the frontend from Shopify's backend. Hydrogen (React + Remix) or Next.js with the Storefront API for fully custom frontends with maximum performance control.

Type	Skill level	Typical cost	Timeline
Theme modifications	Junior–Mid	$500–$3,000	1–2 weeks
Custom sections	Mid	$1,000–$5,000	2–4 weeks
Private apps	Mid–Senior	$3,000–$20,000	4–12 weeks
API integrations	Mid–Senior	$2,000–$10,000	2–6 weeks
Headless builds	Senior	$15,000–$60,000+	10–20+ weeks

Most stores need types 1–2; types 3–5 are for specific business requirements. For understanding the Liquid language that powers types 1–2, see the Shopify Liquid explainer; for when to hire versus DIY, the hiring guide.

The Shopify development stack

Shopify's development platform has expanded significantly since Online Store 2.0 launched in 2021. Here is the full stack a modern Shopify developer works with:

Liquid — Shopify's template language. Powers every theme: product displays, collections, cart logic, dynamic content. The essential skill for any Shopify developer.
Shopify CLI — command-line tool for theme development, app scaffolding, and local preview with hot reload against your actual store data.
Storefront API (GraphQL) — read-only API for building custom storefronts. Powers headless commerce, mobile apps, and custom buy experiences outside the standard theme.
Admin API (REST/GraphQL) — full read/write access to products, orders, customers, and inventory. Used for app development, migrations, and backend integrations.
Checkout Extensions — customize checkout with UI extensions, payment customizations, and delivery options. Replaces the deprecated checkout.liquid approach.
Shopify Functions — server-side logic running on Shopify's infrastructure: custom discounts, payment methods, delivery rates, and cart validation.
Hydrogen + Oxygen — Shopify's React-based headless framework (Hydrogen) with built-in hosting (Oxygen). Full frontend control with Shopify's backend handling commerce.
Theme App Extensions — embed app functionality into themes without touching theme code. Merchants add blocks via the editor — no code conflicts.

"Theme app extensions allow merchants to easily add dynamic elements to their themes without having to interact with Liquid templates or code. For example, dynamic elements can include product reviews, prices, ratings, or interactive 3D models of products. Theme app extensions can integrate with Online Store 2.0 themes."

— Shopify Developers, Theme app extensions — Shopify.dev

The original article visualizes stack adoption as a bar chart. Here is the same data as a table — an editorial estimate of usage among active Shopify developers in 2026 (based on Shopify developer documentation, job postings, and community surveys as of Q1 2026), not a hard survey:

Stack tool	Estimated developer adoption
Liquid	95%
Shopify CLI	78%
Theme App Extensions	55%
Storefront API	42%
Checkout Extensions	35%
Shopify Functions	28%
Hydrogen	18%

The shape is the point: Liquid is the universal skill; everything else is specialized. If you only need theme modifications, do not pay for headless expertise.

How to scope a custom Shopify project

The number-one reason custom Shopify projects go over budget is not bad developers — it is poor scoping. A five-step process protects both budget and timeline:

Define business objectives. Start with the "why": increase conversion rate, reduce bounce, automate a workflow, support a new channel. Every technical decision flows from a business goal.
Document requirements. List every feature, page, and behavior. Use wireframes or annotated screenshots. Separate must-have from nice-to-have. Include edge cases (mobile, empty states, error handling).
Define acceptance criteria. For each feature, write testable success conditions: "Product filtering loads results within 500ms," "Cart upsell appears on products over $50," "Email triggers within 5 minutes of order."
Set milestones & budget. Break the project into phases with deliverables. Allocate a 15–20% buffer for unexpected complexity. Never pay 100% upfront — use milestone-based payments (30/40/30 is standard).
Plan testing & launch. Require a staging/development store for all work. Define a QA checklist (cross-browser, mobile, checkout, page speed). Plan a soft launch before going fully live.

A concrete sample scope keeps this honest. For a custom product page:

Objective: increase product page conversion rate from 1.8% to 2.5%.
Budget: $3,000–$4,500 (including a 15% buffer).
Deliverables: custom product page section (OS 2.0), image zoom with video support, size guide modal, dynamic upsell block, mobile-first responsive design.
Acceptance criteria: page loads under 2s on mobile (3G), all elements editable via theme editor, works on Chrome/Safari/Firefox, keyboard navigable.

Cost & timeline by development type

The five-type table above gives ranges. The original article also plots single mid-range point estimates per type — useful when you need one number to anchor a first conversation (editorial assessment based on the Shopify Partner Directory, freelancer platforms, and agency pricing as of Q1 2026):

Development type	Mid-range timeline	Mid-range cost
Theme tweak	1 week	$500
Custom sections	3 weeks	$3,000
Full theme	8 weeks	$12,000
Private app	6 weeks	$8,000
API integration	4 weeks	$5,000
Headless build	14 weeks	$35,000

These are mid-range estimates; actual costs move with four levers:

Developer location — US/UK developers charge 2–3× more than developers in Eastern Europe or South Asia.
Complexity — a "custom section" with simple HTML costs less than one with real-time API calls and animations.
Urgency — rush projects (under two weeks) typically carry a 25–50% premium.
Ongoing maintenance — budget 15–20% of initial cost annually for updates, Shopify API version upgrades, and bug fixes.

One plan caveat: certain development types — native B2B catalogs, advanced Checkout Extensions (payment and delivery customizations), Shopify Functions for advanced discount logic, and multi-storefront setups — are only available on Shopify Plus ($2,300/mo). Confirm your plan supports the features you need before scoping; upgrading mid-project adds both cost and delays.

"Shopify Functions enable you to customize Shopify's backend logic by running custom code during the checkout process. You can create functions to implement specialized features that aren't available natively."

— Shopify Developers, Function APIs — Shopify.dev

Custom theme vs custom app vs headless

One of the most common mistakes is choosing the wrong type of development for the problem. Custom themes solve visual and layout needs. Custom apps solve business logic and automation. Headless builds solve performance and multi-channel needs. Here is the decision framework side by side:

	Custom Theme	Custom App	Headless
Purpose	Visual customization	Business logic & automation	Full frontend control
Technology	Liquid + CSS + JS	Node.js/Ruby + APIs	React + Storefront API
Timeline	1–8 weeks	2–12 weeks	8–20+ weeks
Cost range	$500–$15K	$2K–$20K	$15K–$60K+
Maintenance	Low (theme updates)	Medium (API changes)	High (full stack)
Best for	Brand differentiation	Unique workflows	Max performance at scale

Quick rules of thumb:

Choose a custom theme when you need a unique brand look, existing themes cannot produce your layout, you want merchant-editable sections, and budget is under $15,000.
Choose a custom app when you need unique business logic, no public app handles your workflow, you need ERP/CRM integration, or you want to automate operations.
Choose headless when you need sub-second page loads at scale, you serve web + mobile app + kiosk, you have $1M+ annual revenue, and you have a React team on staff.

Headless Shopify: when it actually makes sense

"Going headless" is the most hyped — and most misunderstood — term in Shopify development. The mechanics are simple. In the traditional (monolithic) model, Shopify handles everything: theme (Liquid) → backend → checkout. It is simpler, cheaper, and easier to maintain, at the cost of less frontend control. In the headless (decoupled) model, a custom frontend talks to the Shopify backend: React (Hydrogen) → Storefront API → checkout. You get full control, speed, and multi-channel reuse — at 3–5× the cost, plus React developers and more maintenance.

"Get all the power of Shopify under the hood, with complete control over the frontend. Start building quickly with Hydrogen, Shopify's official headless framework, or add Shopify APIs to your existing tech stack."

— Shopify Developers, Build headless commerce — Shopify.dev

Go headless if revenue exceeds $1M/year with high traffic, you need the same backend for web and a native app, page speed is a proven competitive differentiator, your content model exceeds Shopify's CMS, and you have (or can hire) a React/TypeScript team.

Stay monolithic if revenue is under $500K/year, your team has no frontend developers, you want to manage content via the theme editor, budget is under $15,000, or you value simplicity over maximum performance.

The trap worth naming: headless is not a performance silver bullet. A poorly built Hydrogen storefront can be slower than a well-optimized Liquid theme. Headless gives you control over performance, not automatic performance. If your current theme loads in under two seconds on mobile, headless likely will not deliver meaningful speed gains.

How to vet a Shopify developer

Finding a developer is easy; finding the right one is the hard part. Evaluate on Shopify-specific experience — not just general web dev.

Green flags:

Portfolio with live Shopify stores you can visit and test.
Experience with Online Store 2.0 architecture.
Uses version control (GitHub/GitLab) and the Shopify CLI.
Works on a development store first, never on production.
Provides a written scope document before starting.
Offers milestone-based payments (30/40/30).
Can explain trade-offs between approaches clearly.

Red flags:

No live Shopify stores in the portfolio.
Still building on pre-OS 2.0 theme architecture.
Wants admin login instead of collaborator access.
No version control — edits theme files directly.
Demands 100% payment upfront.
Cannot explain why they chose a specific approach.
No post-launch support period in the contract.

Where to find qualified people: the official Shopify Partner Directory (filter by location, services, budget), general freelance platforms like Upwork or Toptal, and curated marketplaces such as Storetasker that match you with pre-vetted specialists by project type.

A professional developer delivers more than working code. Your deliverables should include:

Deliverable	Why it matters
Working code on your store	Deployed, tested, and live — not "it works on my machine"
Source code access (GitHub)	You own the code — full repository access, not locked to one developer
Technical documentation	How custom features work, how to update them, known limitations
Theme editor instructions	How your team uses custom sections/blocks without touching code
Post-launch support period	30–90 days of bug fixes included; anything beyond is a new scope
IP ownership confirmation	Written agreement that you own all custom code created for your project

On that last row: by default the developer may retain intellectual property rights unless your contract states otherwise. Always include an IP assignment clause — upon final payment, all custom code, designs, and assets become your exclusive property. It protects you if you ever need to switch developers.

Managing a custom development project

How you run the project matters as much as who builds it. Use a five-phase approach:

Kickoff & setup — create a development store, grant collaborator access, set up version control (GitHub), agree on communication channels and meeting cadence.
Design & prototyping — review wireframes or Figma before any code is written; approve mobile and desktop layouts. This is the cheapest phase to make changes — 10× cheaper than changing code.
Development sprints — work in 1–2 week sprints with demo reviews. Each sprint delivers testable, visible progress. Use a shared task board (Trello, Notion, or Linear).
QA & testing — test on real devices, not just browser resizing. Check page speed (target under 2s), cross-browser (Chrome, Safari, Firefox), checkout, search, filtering, and every interactive element.
Launch & handover — go live during low-traffic hours, monitor analytics for 48 hours, get documentation on what was built and how to maintain it, and confirm a 30–90 day post-launch support period.

A short project-management checklist keeps everyone honest. Before starting: signed contract with scope and milestones, development store created, collaborator access granted (not login sharing), design files approved, content (copy, images) prepared. During development: weekly demo/review meetings, a shared task board, version control for all code, testing on real devices after each sprint, and change requests documented formally.

6 common mistakes and how to avoid them

Skipping the scoping phase. Jumping into development without clear requirements leads to scope creep and features nobody asked for. Spend 20% of project time on planning — it saves 40% in rework.
Choosing headless too early. Headless adds 3–5× the cost and ongoing maintenance. Unless you are doing $1M+/year with specific performance or UX requirements, a well-optimized Liquid theme delivers better ROI.
Not using Online Store 2.0. Building on pre-2021 theme architecture creates technical debt. OS 2.0 with JSON templates and sections everywhere is the standard — reject any developer who does not build on it.
Ignoring mobile from the start. 79% of Shopify traffic is mobile. Designing desktop-first and "making it responsive later" always produces poor mobile UX. Start mobile-first, then enhance for desktop.
No staging environment. Changing a live store directly risks breaking checkout, search rankings, or the customer experience. Always use a development store or duplicate theme for testing.
Over-customizing checkout. Shopify's native checkout converts better than most custom solutions. Use Checkout Extensions for minor tweaks, but do not rebuild checkout unless you are on Plus with a specific, data-backed reason.

The bottom line

Custom Shopify development is a spectrum from $500 tweaks to $50K headless builds. Match the development type to your actual business need, start with the simplest solution that works, measure results, and escalate complexity only when the data justifies it. The best custom development is invisible — customers do not care whether your store runs on Liquid or Hydrogen; they care about fast load times, intuitive navigation, and a checkout that works. Choose the simplest technology that delivers those outcomes.

Still deciding whether custom development is even your route — versus a theme tweak or a ready-made app? The Shopify development guide sorts that out in about a minute. And if you are building checkout customizations specifically, the checkout extensibility deadlines guide covers exactly which plan needs which UI extension and by when.

FAQ

What is custom Shopify development?
Building functionality beyond what pre-built themes and public apps offer — from Liquid template modifications to full headless commerce builds using Hydrogen. Scope ranges from simple CSS tweaks costing a few hundred dollars to complex API integrations exceeding $50,000, depending on your business needs and growth trajectory.

How much does custom Shopify development cost?
Common ranges: theme modifications $500–$3,000, custom sections $1,000–$5,000, full custom themes $5,000–$15,000, private apps $3,000–$20,000, and API integrations $2,000–$10,000, up to $60,000+ for full headless builds. Developer geographic location and overall project complexity significantly affect final pricing within each category.

What programming languages does Shopify use?
Themes use Liquid, HTML, CSS, and JavaScript. App development typically uses Node.js or Ruby with REST and GraphQL APIs. Headless storefronts use React with the Hydrogen framework. Shopify Functions run custom backend logic using Rust or JavaScript compiled to WebAssembly. Most store owners only need a developer proficient in Liquid and JavaScript.

Should I build a custom theme or customize an existing one?
Customize an existing theme in most cases. Premium themes ($320–$400+) with professional setup deliver roughly 80% of custom results at 20% of the cost. Build custom only when your brand requires a layout no existing theme supports, or your revenue comfortably justifies the $5,000–$15,000 investment in a ground-up build.

What is headless Shopify and when do I need it?
Headless separates the frontend from Shopify's backend using the Storefront API. You likely need it when annual revenue exceeds $1M with high traffic, you serve multiple channels simultaneously (web, mobile app, kiosk), or page speed is a proven competitive differentiator. Most stores under $1M annual revenue do not benefit enough to justify the cost.

What is Shopify Hydrogen?
Hydrogen is Shopify's official React-based framework for building headless storefronts, built on top of Remix. It provides pre-built commerce components, optimized data fetching through the Storefront API, and deploys on Shopify's Oxygen hosting. It requires React and TypeScript developers — a fundamentally different skillset from traditional Liquid theme developers.

What are Shopify Functions and when are they used?
Shopify Functions run custom backend logic directly on Shopify's infrastructure — discount rules, payment method filtering, delivery rate calculations, and cart validation. They replaced the deprecated Script Editor app. Use them when standard Shopify settings cannot handle your business rules, such as tiered pricing, location-based payment restrictions, or complex discount logic.

How long does a custom Shopify project take?
Theme tweaks take 1–2 weeks, custom sections 2–4 weeks, full custom themes 6–12 weeks, private apps 4–12 weeks, API integrations 2–6 weeks, and headless Hydrogen builds 10–20+ weeks. Projects with well-defined scope documents and responsive stakeholders consistently finish 30–40% faster.

What is Online Store 2.0 and why does it matter?
Online Store 2.0 is Shopify's current theme architecture, launched in 2021, using JSON templates and sections on every page. It lets merchants customize any page through drag-and-drop without writing code. Any custom development project in 2026 should use OS 2.0 — building on older architecture creates technical debt and limits future flexibility.

What's the difference between Checkout Extensions and checkout.liquid?
checkout.liquid was deprecated and fully sunset in August 2025. Checkout Extensions are the modern replacement — React-based UI components that run within Shopify's secure checkout sandbox. They are safer, faster, and fully supported going forward. Any developer still referencing checkout.liquid is working with technology that no longer functions on the platform.

Do I need Shopify Plus for custom development?
Not for most projects. Standard Shopify plans support theme customization, custom sections, private apps, and API integrations. You need Plus (starting at $2,300–$2,500/month depending on term length) specifically for native B2B catalogs, advanced Checkout Extensions, Shopify Functions for complex discount logic, and multi-storefront management.

Who owns the code a developer writes for my store?
By default, developers may retain intellectual property rights unless your contract explicitly specifies otherwise. Always include an IP assignment clause stating that upon final payment, all custom code, designs, and documentation become your exclusive property. Ensure you also receive full source code access via GitHub and detailed technical documentation.

Originally published at shopify.ecom-store.pro, where the article includes an interactive stack-adoption chart, a timeline-versus-cost chart, and an expandable FAQ.

Written by Alexander Matynian, a front-end developer working with Shopify since 2017 — building custom Liquid storefronts, scoping and pricing client builds, and integrating stores with external systems. More e-commerce guides at shopify.ecom-store.pro.

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

Shopify Store Development Cost: What You're Paying For and How to Read a Quote

Alexandr M. — Tue, 07 Jul 2026 18:21:49 +0000

If you have ever quoted a Shopify build — or been on the receiving end of three quotes that ranged from $500 to $50,000 for what sounded like the same job — you already know the hard part is not the platform. Shopify's own fee is the one line on the invoice that is fixed, public, and boring. Everything else is labor, and labor is where the number swings by an order of magnitude.

This piece is written for the developer, freelancer, or technical operator who has to either produce a build estimate or read one without getting fleeced. We will break a build budget into its actual line items, put five end-to-end scenarios next to each other, look at what freelancer and agency rates really are (with sources), walk through the four things that make a quote climb, and cover how to scope a project so the estimate holds. Every figure below is pulled from official Shopify pricing pages or Clutch's published benchmarks — no made-up averages.

One format note: the original article carries two interactive pieces that do not survive a plain markdown feed — a budget calculator that takes your own hours, theme, and plan and returns a year-one total, and a regional-rate chart. Where those appear below I summarize the logic in text and point you to the interactive version on the canonical post.

Key takeaways

The platform is the cheap part. Most of a Shopify build budget is labor, not Shopify's own subscription fee.
Five scenarios span a huge range — from a roughly $357 DIY store to a mid-five-figure agency build, all on the same platform.
Who builds it drives the price far more than the platform ever does — DIY, freelancer, and agency are the real cost tiers.
Region moves rates 4–6×. The same scope is $100–$149/hour in the US and under $25/hour in India, per Clutch's regional data.
Shopify publishes no official Expert rates. You budget from real quotes and third-party benchmarks, not a directory number.
Launch is not the finish line. Plan, domain, apps, card fees, and support keep billing every month after you go live.

What you're actually paying for

"How much does it cost to develop a Shopify store?" has no single answer because you are not buying one thing — you are buying a stack of separate line items, and only one of them (the subscription) is fixed and public. The rest scale with how much you outsource and how custom you go. Six components make up almost every build budget:

Component	What it covers
Platform plan	Recurring Shopify subscription — hosting, SSL, CDN, checkout bundled in. The most predictable line, and usually the smallest.
Theme	A free Horizon theme, or a one-time paid theme. The base your storefront sits on, not the custom work.
Design & development	The labor: theme setup, custom design, and code. The biggest variable — the number that separates a $500 build from a $50,000 one.
Apps	Subscriptions for reviews, email, subscriptions, and features Shopify does not include natively. They stack up monthly.
Content & data	Product photography, copywriting, and migrating an existing catalog. Easy to forget, quietly expensive at scale.
Support & maintenance	Ongoing fixes, updates, and improvements after launch — a retainer, ad-hoc hours, or your own time.

Notice what dominates: design and development. Your plan might be $29 a month and your theme free, but the labor to design, build, and integrate is what turns a few hundred dollars into a few thousand — or a few tens of thousands. That is why the same platform can host a weekend DIY project and a six-figure enterprise store.

Budgets by scenario

The fastest way to place your own project is to find the scenario that looks like it. Each row below is a full year-one budget — the one-time build plus twelve months of the plan and a domain — using representative build figures chosen inside Shopify's and Clutch's published ranges.

Scenario	Development (one-time)	Plan	Year-one total	Timeline	Best for
DIY on a free theme	$0 — your own hours	$29/mo (Basic, annual)	$357	Days–2 weeks	First store, tiny catalog, tight budget
Premium theme + pro setup	$1,680 (theme + setup)	$29/mo (Basic, annual)	$2,037	1–3 weeks	A polished launch with light customization
Custom theme build	$5,000 (freelancer)	$79/mo (Grow, annual)	$5,957	3–6 weeks	A distinct brand, moderate complexity
Full custom + integrations	$25,000 (agency)	$299/mo (Advanced, annual)	$28,597	2–4 months	Complex catalog, integrations, migration
Plus-scale enterprise	$60,000 (agency)	$2,300/mo (Plus)	$87,609	3–6 months	High volume, custom checkout, B2B

Plan and domain prices come from Shopify's pricing page; the build figures are representative points within Shopify's and Clutch's published ranges (verified July 2026). The first row is the outlier: a DIY store has essentially no development cost — your time is the investment. Everything above it is the price of buying someone else's hours.

Notice how the totals cluster low and then jump. Most stores are modest, but a handful of large custom builds pull the average up sharply — which is exactly what the aggregate project data shows:

"Based on reviews on Clutch, the average cost for an e-commerce development project is $51,943.13."

— Clutch, E-commerce development pricing

That five-figure average is not the typical store — it is the mean, dragged upward by enterprise projects. The median store spends far less, which is why the scenario you pick matters more than any headline number.

The original post has an interactive budget calculator: plug in who builds it, how many hours, your theme, and your plan, and it returns a one-time build cost, a monthly platform cost, and a year-one total — with every input clamped to a sourced range so it estimates rather than invents. Try the interactive calculator on the original article.

Freelancer vs agency rates

Once you have decided to pay someone, the rate depends on who they are. Three routes, three price bands:

Who builds it	Hourly rate	Where it fits
Do it yourself	$0 — your own time	Tight budget, small catalog, learning the platform
Freelancer	$24–$49/hr typical	A custom look without an agency's overhead
Agency	$50–$199/hr	Strategy, integrations, migrations, brand-critical builds

Freelancer and agency bands are from Clutch (general ecommerce and Shopify-directory rates, verified July 2026). Agencies sit at the top for a reason: you are paying for a team and a process, not just hours. Across Clutch's Shopify directory, advertised rates run $50 to $199 an hour, with project minimums from $1,000 to $25,000 or more. The minimum matters as much as the rate — many agencies simply will not take a small build.

Shopify's own outsourcing benchmark brackets the same spread at the project level: in its guide to outsourcing website design, it puts freelance web designers' total project costs between $500 and $10,000, and agencies often between $3,000 and $75,000.

One gap in the official data is worth being blunt about: Shopify runs a directory of Partners and Experts, but it publishes no hourly rates or project prices for them anywhere on its site. You cannot budget from an official Shopify figure. Use third-party benchmarks like Clutch to set a reasonable range, then budget from the real quotes you collect — never from a number a Shopify page appears to imply.

Why region swings the number so much

The single biggest lever on an hourly rate is not seniority — it is geography. The same scope of work is priced very differently depending on where the builder sits, which is why an identical brief can come 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

Figures are Clutch's general web/ecommerce development rates by region — a 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 bargain or a false economy depending on communication, time-zone overlap, and portfolio quality. Price the builder, not just the rate — a slower, cheaper build that misses the brief costs more than a right-sized one.

The original post renders this as an interactive floating-bar chart. The point is not the exact endpoints — it is the 4–6× spread. See the interactive chart on the original article.

What drives costs up

When two quotes for "a Shopify store" differ wildly, it is usually one of four drivers doing the work. Shopify's own benchmarks bracket the spread: it puts ecommerce-type website design projects at $500 to $10,000, and fully custom design and development at $2,000 to $20,000 or more depending on complexity.

Custom design — usually the single biggest driver. Configuring an existing theme is cheap; designing a bespoke storefront from scratch is not.
Integrations & apps — every system your store must talk to (an ERP, a POS, a warehouse, a subscription engine, a tax service) is custom work and testing. Off-the-shelf apps are cheap; a custom integration between Shopify and a legacy back office is where quotes climb fast, because the edge cases are unique to your business.
Data migration — moving from another platform means porting products, customers, orders, and URLs, and preserving SEO with redirects. A large catalog with variants, metafields, and years of order history is a project in its own right, and it is the line most owners forget to budget for.
Template & page count — a store with one product template and a homepage is quick; one that needs distinct templates for categories, landing pages, lookbooks, and a custom cart is many times the work. A custom Liquid theme is priced by how many of these it contains.

If you are unsure which you actually need, the companion guide to theme setup versus a custom design build maps the two paths and what each costs — most first stores need far less custom design than they assume.

A quiet warning on all four: most overruns are not bad estimates, they are a scope that grew after the quote. "Can we also add..." is how a $5,000 build becomes a $12,000 one. Lock the scope in writing before work starts, and treat every addition as a priced change order, not a favor.

Ongoing costs after launch

A development budget that stops at launch is only half a budget. These are the costs that keep arriving after the store goes live — the recurring floor you carry every month:

Ongoing cost	Typical amount	How it behaves
Shopify plan	$29–$299/mo (annual)	Your recurring floor; Plus starts far higher
Domain	From $9/yr	Auto-renews; includes free WHOIS privacy
Apps	Subscription — varies	No official average; priced by features, usage, or order volume
Payment processing	Per-transaction card rate	A percentage of sales, not a fixed monthly fee
Maintenance & support	Hours × your builder's rate	An optional retainer or ad-hoc fixes

Two of these deserve a caveat. Apps have no official average — they are subscriptions priced by features, usage, or order volume, so a lean store might spend little and an app-heavy one hundreds a month. And a domain is trivial: you can register one through Shopify from $9 a year, renewal and privacy included. Shopify frames the whole recurring picture in a single range:

"Essential ecommerce costs, from domain to hosting to platform fees, typically span from about $29 per month on the low end up to $10,000 as your store grows and adds features."

— Shopify, How much does an ecommerce website cost?

That range is the honest shape of it: cheap to start, and as expensive as your ambitions as you scale. The development spend gets you live; these ongoing costs are what running the store actually feels like month to month.

How not to overpay

The gap between a fair price and an inflated one usually comes down to process, not luck. Run every build through these five steps and you will pay for what you need — no more:

Write the scope down first. Before asking anyone for a price, list the pages, features, integrations, and data you need. A vague brief invites a vague quote — and vague quotes are where overruns hide.
Get three quotes on the same brief. Send the identical written scope to three builders. Comparable inputs give comparable numbers, and the outlier — high or low — usually tells you who understood the job.
Separate one-time build from the retainer. Ask for the build cost and the ongoing support cost as two distinct lines. Bundling them hides the true monthly commitment and makes builders hard to compare.
Check the portfolio and references. Ask for live Shopify stores they built and speak to a past client. A real portfolio of shipped stores beats a slick pitch deck every time.
Agree milestones and acceptance criteria. Tie payments to deliverables, not dates, and define what "done" means for each. Milestone-based contracts protect both sides and keep scope honest.

Some things in a quote or a conversation should make you slow down. Treat these as red flags:

No line-item breakdown — a single lump sum hides what you are actually paying for.
"We'll figure out scope as we go" — open-ended hours are open-ended bills.
Pressure to pay 100% upfront — staged payments tied to milestones protect you.
No named contact or references — you should be able to reach a person and a past client.
Rates far outside regional norms with no explanation — unusually high or low both deserve a question.

For the full step-by-step on finding, vetting, and contracting a builder, the guide to hiring a Shopify developer walks the whole process, contracts and red flags included.

The bottom line

The number that matters is not Shopify's fee — it is the labor. A DIY store costs your time and about $357 in platform and domain for the year; a premium theme with pro setup lands near $2,000; a freelance custom theme runs into the mid-thousands; and a full agency build with integrations reaches the mid-five figures, with Plus-scale projects higher still. Same platform, wildly different labor.

Buy the smallest build that fits, then scale. Start on a theme and DIY if you can; pay a freelancer for polish and an agency only for genuine complexity or migration. Match the scenario to what the store actually needs today, not the one you imagine in two years, and treat every custom feature as a cost to justify against the revenue it unlocks.

FAQ

How much does it cost to develop a Shopify store?
It depends almost entirely on who builds it, not on Shopify. A do-it-yourself store on a free theme costs only the plan and a domain in year one. Hiring a freelancer typically lands in the low thousands, while a full agency build with integrations reaches the mid-five figures or more.

Can you build a Shopify store for $500?
Yes — but only two ways. You can build it yourself, spending your own hours plus a plan and a domain, or you can pay a freelancer for a light theme setup at the very bottom of Shopify's published $500-to-$10,000 build range. What $500 does not buy is a custom-coded, integration-heavy store.

Why do development quotes vary by 10× for the same store?
Three reasons: who builds it, where they sit, and how much is custom. A freelancer in a lower-cost region and a specialist US agency can price the same brief an order of magnitude apart. Custom design, integrations, and migration then widen the gap further. Comparable written scopes are the only fair way to compare.

Does Shopify publish official Shopify Expert rates?
No. Shopify runs a directory of Partners and Experts, but it publishes no hourly rates or project prices for them anywhere on its site. You cannot budget from an official Shopify number — you budget from real quotes, and industry benchmarks like Clutch's give you a reasonable range to sanity-check them against.

Is it cheaper to hire a freelancer or an agency?
A freelancer is almost always cheaper up front and fits polished-but-standard builds. An agency costs more because you are buying strategy, project management, and a team — worth it for complex, integration-heavy, or brand-critical stores. The cheaper option is only cheaper if it actually delivers what you need.

What's the difference between a theme setup and a custom theme build?
A theme setup configures an existing free or paid theme — your logo, colors, and content on a proven template — for hundreds to a few thousand dollars. A custom theme build codes a bespoke storefront from the ground up in Liquid, costing several thousand and up. Most first stores only ever need the setup.

What ongoing costs should I budget after launch?
Your Shopify plan, a domain renewal from $9 a year, app subscriptions, and per-transaction card fees are the recurring floor. On top of that, budget for maintenance — either a retainer with your builder or ad-hoc hours for fixes and improvements. The build is one-time; these costs recur every single month.

What makes a development quote go up the most?
Custom design is usually the single biggest driver, followed by integrations with ERPs, POS, or third-party systems, then data migration from another platform. The number of unique page templates also matters — each custom layout is more design and code. Scope creep during the build quietly inflates every one of these.

Originally published at shopify.ecom-store.pro, where the article includes an interactive budget calculator and a regional-rate chart.

Written by Alexander Matynian, a front-end developer working with Shopify since 2017 — building custom Liquid storefronts, scoping and pricing client builds, and migrating catalogs onto the platform. More e-commerce guides at shopify.ecom-store.pro.

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

Shopify Analytics: What's Built In, What's Missing, and How to Read It

Alexandr M. — Tue, 07 Jul 2026 06:45:26 +0000

If you build or operate on Shopify, you have almost certainly wired up more than one measurement layer: GA4 through a channel, a Meta pixel with the Conversions API, maybe Google Tag Manager, maybe TikTok. Then you open three dashboards on a Monday and none of them agree on how many orders you did. The reflex is to assume something is broken. It usually is not — and the tool that most teams under-read is the one that ships free with every plan.

This is a practical, engineering-minded tour of built-in Shopify Analytics: what is actually inside it by plan, the four metrics worth watching weekly, why ad-platform numbers structurally never match Shopify, what ShopifyQL buys you, and the honest line at which a paid attribution platform (Polar, Triple Whale, Lifetimely) earns its price. It is written for the developer or technical operator who would rather understand the data model than stare at a live-visitor map.

The original version of this article ships a few interactive pieces that do not survive a plain markdown feed — a decision quiz, a live conversion-uplift calculator, an attribution-gap chart, and an embedded dashboard walkthrough. Where one of those appears below, I summarize the logic in text and point you to the interactive version on the canonical post.

Key takeaways

Built-in Analytics covers roughly 80% of reporting — sales, acquisition, behavior, marketing, inventory, and profit. Cohorts and deep LTV are the missing 20%.
Report depth scales with plan. Every plan gets the dashboard and prebuilt reports; the custom report builder and ShopifyQL Notebooks are gated to Advanced and Plus.
Four metrics drive most decisions — conversion rate, AOV, sessions by source, and gross profit per order. Watch them weekly, not hourly.
Shopify credits last-non-direct-click; Meta and TikTok count view-through. The numbers never match, and that is structural — pick one source of truth per decision.
Live View is morale, not steering. Use it for launches and BFCM, not daily operations.
A small CR lift on fixed traffic usually beats a new paid channel — and it is far cheaper to buy.

What Shopify Analytics actually is

Shopify Analytics is not a single screen — it is six tightly connected report clusters under Analytics in the admin. The dashboard is the at-a-glance KPI strip, Live View is the real-time map, and the real work happens inside Reports, where the sales, acquisition, behavior, marketing, inventory, and profit reports live. Most operators only ever open the dashboard and Marketing, and miss two-thirds of the leverage.

The simplest mental model: built-in Shopify Analytics answers operational questions exceptionally well (what sold, where it came from, how much margin it produced) and answers strategic questions (cohort behavior, multi-touch attribution, lifetime-value depth) only at the surface. Knowing where that line sits is the difference between paying for tools you do not need and missing tools you do.

Two baselines worth anchoring on before we go deeper, from Shopify's ecommerce conversion-rate analysis: the global ecommerce conversion rate sits near 1.6% (Statista, Q3 2025), while the ceiling on a well-merchandised store is closer to 3–5%. Your numbers vary by category and traffic mix, but that spread is the space you are operating in.

Reports by plan

The reports themselves do not change between Basic and Plus — what changes is your ability to build new ones. On Basic and Shopify, you read the prebuilt set. On Advanced and Plus, you can edit, save, and create custom reports, plus query data directly with ShopifyQL Notebooks. Picking the right plan for analytics is a question of how often you will modify reports, not whether the reports exist.

Capability	Basic	Shopify	Advanced	Plus
Overview dashboard (KPIs, sales over time)	Yes	Yes	Yes	Yes
Live View (real-time map + KPIs)	Yes	Yes	Yes	Yes
Sales, acquisition, behavior, inventory reports	Yes	Yes	Yes	Yes
Marketing & conversion reports	Yes	Yes	Yes	Yes
Profit reports (margin, COGS-aware)	Yes	Yes	Yes	Yes
Custom report builder	—	—	Yes	Yes
ShopifyQL Notebooks	—	—	Yes	Yes
Shopify Audiences (data signal feed)	—	—	—	Yes

Source: Shopify Pricing. Capabilities reflect the 2026 plan structure; check the live page for any post-publication changes.

The metrics that drive decisions

Shopify will happily show you forty metrics. A handful of them actually drive decisions; the rest are useful when one of those moves and you are trying to understand why — but they should not be a weekly read.

Conversion rate — sessions that turn into orders. The single most leveraged metric on Shopify. The global baseline is near 1.6%; the ceiling on a well-merchandised store is 3–5%. Diagnose CR before you spend a dollar more on ads.
Average order value (AOV) — revenue per order, driven by bundles, free-shipping thresholds, checkout upsells, and PDP price anchoring. A 10% AOV lift on a healthy store typically beats a 10% traffic lift on contribution margin.
Sessions by source — where traffic actually comes from (organic vs. direct vs. paid social vs. email). Watch the trend over weeks more than the absolute split; channel attribution is fuzzy, but the trend is honest.
Gross profit per order — revenue minus COGS at the order level, available in the Profit reports once cost-per-item is set on every variant. This is the number that turns ROAS into a real business metric.
Returning customer rate — share of orders from prior buyers. Under 25% on a year-old store with email in place is a retention problem, not an acquisition problem.
Sessions converted by device — mobile is usually 65–75% of sessions but only 50–60% of revenue. If the gap is wider than that, the mobile PDP and checkout are the highest-leverage things to fix.

The one-number-per-lever discipline: pick one metric for each lever you control — CR for site quality, AOV for merchandising, sessions by source for acquisition, gross profit per order for unit economics. When the lever moves, the metric should move within two weeks. If it does not, the lever is wrong, not the metric.

KPI benchmarks: healthy / watch / fix

Open your Shopify Analytics dashboard, score each row, and you will know within five minutes which lever to pull first. Ranges are directional and category-dependent — a luxury brand at 0.9% CR is normal; a supplement brand at 0.9% is broken.

Metric	Healthy	Watch	Fix
Conversion rate (blended)	2.5–5%	1.4–2.5%	<1.4%
Mobile vs. desktop CR gap	≤ 30%	30–50%	> 50%
Cart-to-checkout rate	50–70%	35–50%	<35%
Checkout-to-purchase rate	70–85%	55–70%	<55%
Returning customer rate (year-old store)	> 35%	25–35%	<25%
Discount-driven share of revenue	<20%	20–30%	> 30%
Gross margin per order	> 60%	40–60%	<40%

Ranges synthesized from Shopify's conversion-rate benchmarks and operational norms for stores doing $30K–$500K/month. Adjust by category and price point.

Live View: useful or noise?

Live View shows real-time visitors on a world map plus a strip of in-the-moment KPIs — sessions, carts, checkouts, orders. It is the most-watched and least-decision-useful screen in Shopify Analytics.

The legitimate use cases are narrow and high-value: confirming a launch landing page is receiving paid traffic, hour-by-hour BFCM monitoring, validating that a UTM-tagged campaign URL is firing inside the first hour, or QA-ing a checkout change in production. Outside those moments it is theatre — operators who watch it daily report that they rarely change anything material because of what they see.

The test: ask "if this number is 30% higher or lower than expected in the next hour, what will I do differently?" If the answer is "nothing," close the tab. The dashboard's daily and weekly trend lines drive better decisions than minute-by-minute dots.

Reading the reports that matter

A weekly ritual that takes 20 minutes and outperforms most third-party dashboards: open the four clusters below, in this order, and write down one observation per cluster. The discipline of writing it down matters more than the tool — most analytics waste comes from looking without recording.

Sales — total sales, returning vs. first-time, by product, by location, by discount. The three views worth opening weekly are Sales by traffic source (fast attribution view), Sales by product variant (your real bestsellers, not your most-viewed), and Sales by discount (the audit on promo dependency). When discount-driven revenue exceeds 30% of total for two consecutive months, you have a margin problem disguised as a sales problem.

Acquisition & behavior — the under-used hero is the Online store conversion over time funnel: added to cart → reached checkout → completed. The two step rates (cart-to-checkout ~50–70%, checkout-to-purchase ~70–85%) tell you exactly where the leak is. If a bucket is below the floor, you have a specific UX or trust problem to fix — not a generic "conversion problem."

Marketing — built on UTM parameters and the attribution model you set in Settings → Customer events. Use it as one signal in a triangulation, not a sole source of truth. Meta, TikTok, and Google will always claim more conversions than Shopify credits them with, often by 2–3×.

Inventory & profit — inventory reports rely on accurate stock levels; profit reports rely on cost-per-item being set on every variant. Both quietly become the highest-ROI reports for any store above ~$50K/month — they convert a revenue dashboard into a real margin dashboard. If the Profit reports show $0 for most rows, the cause is missing cost-per-item data, not a Shopify bug. Bulk-import COGS via CSV before trusting any margin or ROAS calculation downstream.

The original post embeds a 15-minute dashboard walkthrough from a working ecommerce operator, useful if you prefer to see the four clusters opened on screen. Watch the embedded version on the original article.

LTV and cohorts without a third-party tool

Cohort and lifetime-value depth is the most-cited reason merchants jump to a paid analytics tool. The reality: 80% of LTV decisions do not need a cohort heatmap — they need a defensible average. This formula uses three numbers Shopify already exposes:

Estimated 12-month LTV = AOV × Avg orders per customer × Gross margin %

AOV — Analytics → Reports → Sales (last 12 months)
Avg orders per customer — Customers report → Total orders ÷ Total customers
Gross margin % — Profit report (cost-per-item must be set on every variant)

Plug in your last 12 months. A store with $80 AOV, 1.6 average orders per customer, and 55% gross margin has an estimated 12-month LTV of $70.40 per customer. That single number sets the ceiling on customer acquisition cost (CAC) for any paid channel — spend more than that and you are buying revenue at a loss until the second year.

You can also answer three cohort questions without a new tool: (1) is repeat behavior improving? Compare returning-customer rate quarter-over-quarter in the Customers report. (2) Which products drive repeat orders? Sort Sales by product by returning-customer revenue. (3) Is the first-90-day repeat rate moving? Filter the Customers report to "first order in the last 90 days." Three reports, fifteen minutes. Upgrade to Lifetimely or Polar when you need this weekly, not occasionally.

Attribution gaps in 2026

The single most-asked question about Shopify Analytics is some version of "why doesn't Meta match?" The answer is structural, not a bug. Shopify credits the last non-direct click in the customer's session. Meta also counts view-through conversions and a 7-day post-click window. Add iOS 14.5 ATT (which strips much of Meta's deterministic data), Shop Pay logins inflating Shopify's "direct" bucket, and ad blockers deflating both, and a 2–3× gap between the two reports is the norm, not the exception.

"If your conversion rate looks different in every dashboard, it doesn't mean something's broken. Analytics tools don't all measure the same thing. They disagree on what counts as a session, where credit is assigned, which orders are included, and which channels are counted — so the numbers naturally drift. Instead of hunting for a single 'correct' conversion rate, choose one tool as your source of truth."

— Shopify, Ecommerce Conversion Rate: How To Improve Yours

The original article renders a chart illustrating the directional shape of this gap. The point is not the precise percentages — it is that the disagreement is structural and predictable. See the interactive chart on the original post.

The triangulation rule: use Shopify for revenue, AOV, and gross profit; use ad platforms for in-channel optimization (creative, audience, bid); use a unified-attribution app only when spend across channels is large enough that better allocation pays for the tool. Never reconcile the same number across three tools — pick one tool per question.

ShopifyQL and custom reports

On Advanced and Plus, the report builder lets you customize and save reports without code. One step deeper sits ShopifyQL, a query language tuned for commerce data and accessed through Notebooks. A simple example — total sales by product type for the last 90 days, ordered by sales descending:

FROM sales
SHOW total_sales
GROUP BY product_type
SINCE -90d
ORDER BY total_sales DESC
LIMIT 10

That kind of question — slicing across dimensions in ways the prebuilt reports do not — is where ShopifyQL pays off. Below ~$100K/month, the report builder is enough. Above it, ShopifyQL or a third-party warehouse pipe usually replaces a stack of fragile spreadsheets.

Do you need a third-party analytics tool?

The marketing for Polar, Triple Whale, and Lifetimely is excellent — and it is also designed to convince every Shopify merchant they need the tool. Most do not, yet. Here is the honest 10-second view:

Tool	Best at	Weak at	Starts at	Right for
Shopify Analytics (built-in)	Operational reporting, profit, on-store funnel	Cohorts, multi-channel attribution, LTV depth	Free (every plan)	All stores; the default base layer
Google Analytics 4	Traffic patterns, audiences for Google Ads	Order-level revenue accuracy, profit views	Free	Every store, as a complement to Shopify
Lifetimely	LTV cohorts, contribution margin, post-purchase surveys	Daily creative attribution, multi-store	~$49/mo (free tier available)	$30K–$200K/mo, retention focus
Triple Whale	First-party pixel, daily creative attribution, AI insights	Warehouse-grade depth, complex finance views	~$129/mo	$100K+/mo, paid-media heavy
Polar Analytics	Full-funnel custom dashboards, Snowflake-quality data, multi-store	Onboarding effort, price for early-stage	~$300/mo	$250K+/mo, multi-channel, multi-store

Pricing reflects publicly listed entry tiers as of mid-2026 — confirm on each provider's site before committing. The decision heuristic, in plain terms: below ~$50K/month with one or two paid channels, built-in Shopify plus GA4 is enough. Once you cross ~$100K/month with three or more paid channels and active weekly LTV or contribution-margin decisions, a paid attribution platform usually pays back inside a quarter. In between, a free stack (Shopify + GA4 + Lifetimely's free tier) removes the two biggest blind spots without a recurring fee.

The original post has an interactive five-question quiz that maps your revenue, channel mix, cohort needs, reconciliation time, and multi-store setup to one of those rows. Take the interactive quiz on the original article.

Connecting GA4, Meta CAPI, and TikTok cleanly

The right way to connect downstream analytics on Shopify in 2026 is the official sales channel apps for Google, Meta, and TikTok. They install pixels and server-side endpoints through the Web Pixels API, which lives inside Customer Events and respects the customer-privacy state automatically. Anything pasted directly into theme.liquid bypasses that framework, often double-counting events when the official channel is also installed and breaking consent in regulated markets. The install order that avoids the usual foot-guns:

Set customer privacy first. Configure the cookie banner, regional behavior, and consent mode in Settings → Customer privacy. Every downstream pixel relies on Shopify's consent state; skip this and your data flows are non-compliant in the EU/UK and often blocked in the browser.
Install GA4 via the official Google channel. It wires GA4 through Customer Events / Web Pixels, respects consent, and survives theme updates. Avoid pasting the legacy gtag snippet into theme.liquid — it bypasses consent and double-counts events.
Wire up Meta pixel + CAPI through the official Meta channel. It ships both browser pixel and server-side Conversions API and forwards checkout events server-side, recovering 15–30% of attribution lost to ATT and ad blockers. Confirm CAPI events are firing in Events Manager before scaling spend.
Add TikTok through the official app — same pattern. Keep it off until you actually have TikTok spend; an idle pixel adds page weight without any data benefit.
Decide the attribution source of truth. Use Shopify for revenue, COGS, and AOV; ad platforms for in-channel optimization; a unified-attribution app only when the spend across channels exceeds your patience to reconcile.

That is the short version. If you want the full engineering walkthrough — GTM container structure, Consent Mode v2, checkout events, and server-side deduplication so you do not double-fire purchases — that is its own deep dive: installing Google Tag Manager on Shopify without breaking tracking or checkout.

What a conversion-rate lift is actually worth

The conversion-rate lever is the most under-priced lever on Shopify, because the inputs compound. Hold traffic and AOV constant and vary CR, and the revenue line is steep. A quick illustration using the calculator's own arithmetic: on 100,000 monthly sessions at $80 AOV, moving conversion rate from 1.5% to 2.0% takes monthly revenue from $120,000 to $160,000 — a $40,000/month, ~$480,000/year lift (+33%), on the same traffic you already pay for. That is why a half-point CR gain usually beats standing up a new paid channel.

None of the things that drive a real CR lift are analytics work — fast PDPs (under 2.5s LCP), trust signals above the fold, a visible free-shipping threshold, a persistent cart drawer, Shop Pay enabled, a mobile-optimized checkout, and discount logic that does not fight the AOV strategy. But the analytics tells you which one to fix first.

The original post has a live calculator — plug in your real sessions, AOV, and current/target CR to size your own annual lift. Try the interactive calculator on the original article.

Six mistakes that wreck reporting

Most "Shopify analytics is wrong" complaints trace back to one of these. Each is operational, fixable inside an hour, and quietly costs more in bad decisions than any analytics app would cost to install.

Trusting a single attribution model. The "right" marketing number depends on the model you set in Customer events. Switching from last-click to data-driven can re-cut paid social by 40% with the same underlying sales. Pick a model, document it, compare like-for-like.
Not setting cost-per-item on variants. Empty COGS makes the Profit reports useless and ROAS meaningless. Bulk-import COGS via CSV before you trust any margin dashboard; re-audit quarterly.
Reading Live View as a KPI. It is for moments — launches, flash sales, BFCM, debugging a campaign URL — not a daily decision surface.
Pasting raw gtag/pixel into theme.liquid. Hand-installed pixels bypass Customer Events and double-count purchases when the official channel is also live. Always go through Web Pixels; Shopify dedupes and respects consent.
Building dashboards in sheets nobody opens. If a dashboard takes more than two minutes a week to update, it dies inside a month. Use saved custom reports (Advanced+) or a real tool — avoid the half-built spreadsheet middle.
Comparing periods without seasonality. Week-over-week during a Q4 swing tells you about the calendar, not your store. Compare to the same week last year — the year-over-year toggle exists precisely for this.

The bottom line

The Shopify Analytics stack that wins 90% of decisions is unglamorous: the built-in dashboard plus the four core report clusters, GA4 installed via the official Google channel, Meta and TikTok pixels installed via their official channels with server-side enabled, and cost-per-item set on every variant so the Profit reports work. Read four metrics weekly. Pick one source of truth per decision. Stop trying to make Shopify and Meta agree. Layer in a paid attribution platform only when the cost of bad weekly decisions has overtaken the tool's price tag.

FAQ

Is Shopify Analytics free on the Basic plan?
Yes. Every plan — Starter, Basic, Shopify, Advanced, and Plus — includes the analytics dashboard, Live View, and the core sales, acquisition, behavior, marketing, inventory, and profit reports. The custom report builder and ShopifyQL Notebooks are gated to Advanced and Plus, but the operational reports most merchants check daily are available on Basic.

Why don't Shopify and Meta Ads numbers match?
They use different attribution. Shopify credits the last non-direct click; Meta also counts view-through and 7-day post-click conversions. Add iOS 14.5 ATT, Shop Pay logins inflating direct, and ad blockers, and a 2–3× gap is normal. Pick one source per decision, document it, and stop trying to reconcile every week.

What is ShopifyQL and who needs it?
ShopifyQL is Shopify's commerce-tuned query language for building custom reports inside Notebooks (Advanced and Plus). It is worth learning when the prebuilt reports stop answering your questions — typically multi-channel, multi-cohort, or contribution-margin analysis. For most stores under $100K/month, the report builder is enough; ShopifyQL pays off above that.

Should I install Google Analytics 4 alongside Shopify Analytics?
Yes, in almost every case. GA4 adds traffic-pattern depth, audience signals for Google Ads, and free retention reports Shopify does not ship. Install via the official Google channel — never paste raw gtag into theme.liquid, which bypasses consent mode and double-counts purchases when the channel is also live.

How do I see profit per order in Shopify?
Set cost-per-item on every product variant (Products → variant → cost). Once costs are set, the Profit reports under Analytics → Reports calculate gross profit, margin, and net revenue per order automatically. Without cost-per-item, profit reports show $0 and ROAS calculations are flying blind. Bulk-import COGS via CSV to backfill.

When should I switch to Polar, Triple Whale, or Lifetimely?
When you spend on three or more paid channels and lose 2+ hours a week reconciling reports — or when you need cohort LTV and contribution-margin views Shopify does not ship. Below ~$50K/month, built-in plus GA4 is enough. Above $100K/month with multi-channel spend, the attribution upgrade usually pays back inside a quarter.

What is the average conversion rate on Shopify?
Global ecommerce conversion rate sits near 1.6% per Statista's Q3 2025 data, with category averages spreading from ~0.9% in luxury to ~6% in food and beverage. Healthy stores land in the 2–4% range and exceptional ones clear 5%. Mobile typically converts about half as well as desktop — usually a checkout-flow or PDP-trust problem, not a traffic-quality one.

Do I need a custom data warehouse to run a Shopify business?
Almost never below $1M/year revenue. Shopify reports + GA4 + a paid attribution app cover 99% of operational and strategic decisions under that line. A real warehouse (BigQuery, Snowflake) earns its complexity once you have multi-store, multi-region, finance, and marketing all asking conflicting questions of the same data.

Originally published at shopify.ecom-store.pro, where the article includes an interactive quiz, a live conversion-uplift calculator, attribution and conversion charts, and an embedded dashboard walkthrough.

Written by Alexander Matynian, a front-end developer working with Shopify since 2017 — building custom storefronts, wiring up analytics and Customer Events pixels, and helping merchants read their own data. More e-commerce guides at shopify.ecom-store.pro.

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

What Is Shopify Liquid? Syntax, Use Cases, and Limitations

Alexandr M. — Mon, 06 Jul 2026 19:35:23 +0000

If you have ever cloned a Shopify theme into your editor and stared at a wall of {{ }} and {% %} tags, this is the language you were looking at. Liquid is the template layer that sits between a store's data and the HTML a browser finally renders. Before you can safely change a single line in a theme, it helps to understand what Liquid actually does, and — just as importantly — what it refuses to do.

This guide is written for the developer or tech-savvy merchant who wants to customize a theme rather than fight the visual editor. We will walk through the three building blocks (objects, tags, filters), the theme file structure, real code you will actually ship, where Liquid's sandbox draws the line, and what Liquid work costs when you hand it to someone else. Every code sample below is copy-paste ready.

One framing note up front: Liquid is intentionally limited. It renders pages; it does not run your backend. If you are coming from a general-purpose language, the mental-model shift is the whole game, so this piece is explicit about the boundaries. Some of the original article's interactive pieces (a capability radar chart, a cost chart, an embedded video tutorial) do not translate to a plain markdown feed — where that happens, I point you to the interactive version on the original post.

Key takeaways

Liquid is Shopify's template language — it connects your store data to the HTML that customers see in the browser.
Open-source and stable — created by Shopify in 2006, written in Ruby, and used by millions of stores worldwide.
You do not need Liquid for most changes — the theme editor handles colors, fonts, layout, and sections without code.
Liquid developers cost $25–$150/hr — simple edits run $150–$500; custom sections or cart logic run $500–$2,000+.
Three building blocks — objects output data, tags control logic, and filters transform output.
Wrong Liquid breaks visuals, not the server — it is sandboxed, but bad code can show wrong prices or break mobile layouts.

What Is Shopify Liquid?

Liquid is Shopify's template language — a set of simple code instructions that tell Shopify how to display your store's data (products, prices, collections, customer info) inside HTML pages. When a customer visits your store, Shopify processes the Liquid code in your theme files, replaces it with real data, and sends the final HTML to the browser.

Created by Shopify co-founder and CEO Tobias Lütke in 2006, Liquid was designed to be safe and easy to read. It is an open-source template language written in Ruby with over 11,800 stars on GitHub. Unlike general-purpose programming languages, Liquid runs in a sandbox — it cannot access the server's file system, make network requests, or execute arbitrary code. That is what makes it safe for theme developers to write code that runs on Shopify's infrastructure.

"Liquid is a template language created by Shopify. It's available as an open source project on GitHub, and is used by many different software projects and companies."

— Shopify Developer Documentation, Liquid reference

A few numbers on where Liquid stands, per the Shopify/liquid repository on GitHub: in production at Shopify since 2006, 11,800+ GitHub stars, and 193 contributors worldwide.

Here is the key distinction: Liquid is the code behind your theme, not something merchants interact with directly. When someone uses the theme editor to change colors or rearrange sections, they are adjusting settings that Liquid code reads and applies. Liquid is the engine; the theme editor is the steering wheel.

Do You Need Liquid?

Most store owners never need to write Liquid. Whether it is relevant to you depends entirely on your role and how often the store changes.

Your role	Learn Liquid?	Why
Store owner (1 store)	No — hire when needed	One-off developer tasks cost $150–$500; learning Liquid takes weeks.
Store owner (frequent changes)	Learn basics	Basic Liquid saves $200–$500/month in developer fees for minor tweaks.
Marketing manager	Learn to read	Understanding Liquid helps you brief developers more effectively.
Freelance developer	Yes — essential	Liquid is the core skill for Shopify theme development work.
Agency team	Yes — essential	Every Shopify agency project involves Liquid at some level.

If you are a developer reading this on dev.to, you are almost certainly in the bottom two rows: Liquid is the price of admission for Shopify theme work.

How Liquid Works: Objects, Tags, and Filters

Every Liquid file in a Shopify theme is a mix of HTML and Liquid code. Shopify processes the Liquid parts on its servers, replaces them with real data, and sends pure HTML to the customer's browser. The customer never sees Liquid code — only the final rendered page.

"A template language allows you to create a single template to host static content, and dynamically insert information depending on where the template is rendered. For example, you can create a product template that hosts all of your standard product attributes, such as the product image, title, and price. That template can then dynamically render those attributes with the appropriate content, depending on the current product being viewed."

— Shopify Developer Documentation, Liquid reference

Liquid has exactly three building blocks:

Objects — output data. Objects are wrapped in double curly braces: {{ product.title }}, {{ cart.total_price | money }}. They pull live data from your store and display it on the page. Think of them as placeholders that Shopify fills with real values.
Tags — control logic. Tags use {% %} syntax: {% if product.available %}, {% for product in collection.products %}. They control what appears, loop through items, and handle conditional logic — without outputting anything themselves.
Filters — transform output. Filters modify objects using the pipe character: {{ product.price | money }}, {{ 'hello' | upcase }}. They format numbers, dates, strings, URLs, and more — chained left to right.

Here is a practical example that ties all three together. This Liquid code displays a product's title and formatted price, but only if the product is available for purchase:

{% if product.available %}
  <h1>{{ product.title }}</h1>
  <p class="price">{{ product.price | money }}</p>
  <button>Add to Cart</button>
{% else %}
  <p>This product is currently sold out.</p>
{% endif %}

In this example, {{ product.title }} is an object that outputs the product name. {% if product.available %} is a tag that checks availability. | money is a filter that formats the raw price integer into a currency string like "$29.99". For the full list of available objects, tags, and filters, see the Liquid documentation.

Where Liquid Lives: Theme File Structure

Liquid code is organized into specific directories within a Shopify theme. Knowing this structure helps you know where to look (or where to tell a developer to look) when you need changes.

Directory	Contains	Role
`layout/`	`theme.liquid`	Master wrapper — header, footer, global scripts
`templates/`	JSON files	Define which sections appear on each page type
`sections/`	`.liquid` files	Modular page blocks added via the theme editor
`snippets/`	`.liquid` files	Reusable code fragments (price display, badges)
`assets/`	CSS, JS, images	Static files served to the browser
`config/`	`settings_schema.json`	Theme-wide settings visible in the editor
`locales/`	`.json` files	Translation strings for multi-language stores

Source: Shopify Theme Architecture.

The original post embeds a full 45-minute Liquid tutorial video walking through this file structure and building custom sections from scratch. Watch the embedded version on the original article.

Liquid vs No-Code: When You Need Each

The theme editor handles the bulk of everyday customization. Liquid is for what it cannot reach — conditional logic, custom sections, dynamic data, and performance work.

Customization	Theme editor	Liquid code
Change colors & fonts	Yes	No
Rearrange page sections	Yes	No
Add/remove sections	Yes	No
Edit text & images	Yes	No
Create entirely new section types	No	Yes
Show/hide elements based on conditions	No	Yes
Display metafield data on product pages	No	Yes
Custom price formatting	No	Yes
Dynamic inventory badges	No	Yes
Custom cart modifications	No	Yes
Performance optimization	No	Yes
Multi-template product pages	Yes	Yes

The original article includes an interactive radar chart comparing theme-editor reach against Liquid across capability dimensions. Try the interactive version on the original post.

The rule of thumb: for most stores, the theme editor plus a well-chosen Shopify theme covers roughly 80% of what you need. The remaining 20% — unique sections, conditional logic, metafield-driven content — is where Liquid comes in. Do not reach for Liquid until you have exhausted what the editor can do.

What You Can Do with Liquid

These are the most common real-world use cases where stores reach for Liquid customizations:

Custom sections — build unique page sections (testimonials, product tabs, size guides) that merchants can add, configure, and reorder through the theme editor.
Conditional product logic — show "Low Stock" badges when inventory drops below a threshold, display "Pre-Order" buttons for upcoming products, or hide prices for logged-out visitors.
Dynamic content — pull metafield data into product pages (care instructions, size charts, ingredient lists) without installing apps.
Multi-currency / language — display localized content, format prices for different markets, and show region-specific shipping information.
Performance optimization — lazy-load images, conditionally load scripts, preload critical assets, and minimize DOM elements for faster page loads.
Custom cart & checkout — add gift wrapping options, delivery date pickers, upsell blocks, and free-shipping progress bars to the cart page.

Each of these can typically be implemented in 2–8 hours depending on complexity.

Real Liquid Code Examples

You do not need to understand every line — the point of these examples is to show what is possible and give you a concrete starting point. All examples follow Shopify's theme development documentation.

1. Low Stock Badge

Shows a "Low Stock" badge when inventory drops below a threshold. Uses Liquid objects to access inventory data:

{% if product.selected_or_first_available_variant.inventory_quantity <= 5
    and product.selected_or_first_available_variant.inventory_quantity > 0 %}
  <span class="badge badge--low-stock">
    Only {{ product.selected_or_first_available_variant.inventory_quantity }} left
  </span>
{% endif %}

2. Metafield Content on a Product Page

Pulls custom data (like care instructions) from a product metafield:

{% assign care = product.metafields.custom.care_instructions %}
{% if care != blank %}
  <div class="care-instructions">
    <h3>Care Instructions</h3>
    <p>{{ care.value }}</p>
  </div>
{% endif %}

3. Free Shipping Progress Bar

Displays how much more the customer needs to spend for free shipping. Uses Liquid filters for math and currency formatting:

{% assign threshold = 7500 %}  {%- comment -%} $75.00 in cents {%- endcomment -%}
{% assign remaining = threshold | minus: cart.total_price %}

{% if remaining > 0 %}
  <p>Add {{ remaining | money }} more for free shipping!</p>
  {% assign progress = cart.total_price | times: 100 | divided_by: threshold %}
  <div class="progress-bar">
    <div class="progress-bar__fill" style="width: {{ progress }}%"></div>
  </div>
{% else %}
  <p>You qualify for free shipping!</p>
{% endif %}

4. Custom Section with Schema Settings

A reusable section where merchants configure content through the theme editor using schema settings:

<section class="announcement-bar" style="background: {{ section.settings.bg_color }}">
  <p>{{ section.settings.text }}</p>
</section>

{% schema %}
{
  "name": "Announcement Bar",
  "settings": [
    { "type": "text", "id": "text", "label": "Message", "default": "Free shipping on orders over $75" },
    { "type": "color", "id": "bg_color", "label": "Background Color", "default": "#000000" }
  ]
}
{% endschema %}

5. Collection-Based Product Tabs

Dynamically generates product tabs based on a collection handle using Liquid tags for looping:

{% for collection in section.settings.collections %}
  <div class="tab-content" data-tab="{{ collection.handle }}">
    {% for product in collection.products limit: 8 %}
      <a href="{{ product.url }}">
        <img src="{{ product.featured_image | image_url: width: 400 }}"
             alt="{{ product.title }}" loading="lazy" />
        <h4>{{ product.title }}</h4>
        <p>{{ product.price | money }}</p>
      </a>
    {% endfor %}
  </div>
{% endfor %}

Shopify maintains an official Liquid Cheat Sheet with a searchable reference of every object, tag, and filter. Bookmark it.

Hiring a Liquid Developer: Costs and What to Expect

If Liquid work is best left to a professional, here is what the market looks like: freelancers charge roughly $25–$150/hour, agencies $100–$250/hour, and a small task typically turns around in 2–5 days.

Task	Cost range	Timeline
Add a banner or announcement bar	$150–$300	1–2 days
Custom product section	$300–$800	2–4 days
Cart page customization	$500–$1,500	3–5 days
Mega navigation menu	$400–$1,000	2–4 days
Product page redesign	$800–$2,500	5–10 days
Full custom theme	$3,000–$15,000+	4–12 weeks

The original post includes an interactive chart of these cost ranges by task type. Try the interactive version on the original article.

Where to find Liquid developers: the Shopify Partner Directory lists vetted agencies and freelancers. For a deeper breakdown of pricing, contracts, and red flags, see the guide to hiring a Shopify developer.

A word of caution when vetting: not all "Shopify developers" know Liquid well. Ask to see theme work specifically — not just Shopify app development, which uses React/Node rather than Liquid. Request a code sample or a link to a live store they have customized. A competent Liquid developer should know sections, blocks, schema settings, and Online Store 2.0 architecture.

Common Liquid Mistakes to Avoid

Whether you are writing Liquid yourself or managing a developer, these five mistakes cause the most damage — and they are all preventable:

Editing the live theme directly. Always duplicate your theme before making Liquid changes. One syntax error can break the entire storefront for every visitor.
Not using Shopify CLI for local development. Editing code in the browser admin is slow and error-prone. Use the Shopify CLI with hot reload for real-time previews and version control.
Hardcoding values instead of using settings. Do not hardcode colors, text, or URLs. Use section schema settings so merchants can update content through the theme editor.
Ignoring Liquid's sandboxed nature. Liquid cannot access external APIs, write to databases, or execute arbitrary Ruby. For backend logic, use Shopify Functions or custom apps.
Over-customizing a theme you might replace. Heavy Liquid customizations do not transfer between themes. If you plan to switch themes within a year, keep customizations minimal or build reusable snippets.

The Bottom Line

Liquid is the invisible engine behind every Shopify storefront. It has been in production since 2006, it is open-source, and it is not being replaced anytime soon. For a business, the practical question is not "should I learn Liquid?" — it is "do I need Liquid-level customizations, and if so, should I hire a developer or learn the basics myself?"

If you are still picking a starting theme, the guide to Shopify themes covers what is editable without code, and the custom design playbook walks through when Liquid work is genuinely needed. Where to go next depends on your role:

Store owner — start with the theme editor; hire a developer only for specific Liquid tasks.
Want to learn — start with the Liquid basics docs, then practice editing the current flagship theme, Horizon, in a development store.
Need a developer — find a vetted Liquid expert through the Shopify Partner Directory.

Whether you are customizing the Horizon theme or building from scratch, Liquid gives Shopify the flexibility to match any brand's vision — without sacrificing the platform's security and reliability.

FAQ

What is Shopify Liquid in simple terms?
Liquid is the template language Shopify uses to display dynamic content on your online store. It acts as a bridge between your store's data (products, collections, customer info) and the HTML that visitors see in the browser — a set of instructions that tell Shopify what information to show and how to format it.

Do I need to know Liquid to run a Shopify store?
No. Most store owners never touch Liquid code. Shopify's theme editor lets you customize colors, fonts, layouts, and page content without any coding. Liquid becomes relevant only when you need customizations the editor does not support — like conditional product badges, custom sections, or dynamic content based on metafields.

Is Liquid a programming language?
Liquid is technically a template language, not a full programming language. It can output data and control what appears on a page (loops, conditionals), but it cannot access databases directly, make API calls, or perform complex computations. It is intentionally limited for security — it runs in a sandbox, so broken Liquid code cannot crash the server or expose sensitive data.

What is the difference between Liquid and HTML/CSS?
HTML defines the structure of a page (headings, paragraphs, divs). CSS styles it (colors, fonts, spacing). Liquid is the layer on top that inserts dynamic data into that HTML — product titles, prices, cart contents, collection names. A Shopify theme file typically contains all three.

Can Liquid code break my Shopify store?
Liquid runs in a sandboxed environment, so it cannot crash Shopify's servers or corrupt your data. However, incorrect Liquid code can break your store's visual appearance — showing wrong prices, hiding products, breaking mobile layouts, or creating infinite loops that slow down pages. Always test changes on a duplicate theme before publishing.

How long does it take to learn Shopify Liquid?
Basic Liquid (reading objects, simple conditionals, filters) can be understood in a few hours with Shopify's documentation. Building functional sections and snippets takes 2–4 weeks of practice. Advanced Liquid (complex metafield logic, performance optimization, custom schema settings) takes 2–3 months of hands-on work with real store projects.

What is the difference between Liquid and Shopify's theme editor?
The theme editor is a visual, no-code interface for customizing your store. Liquid is the underlying code that powers the theme. The editor exposes settings that theme developers defined using Liquid's schema system. When you change a color in the editor, you are updating a value that Liquid code reads and applies.

Can I use JavaScript with Liquid?
Yes. Shopify themes commonly combine Liquid and JavaScript. Liquid renders the initial HTML with dynamic data, and JavaScript adds interactivity (dropdown menus, image sliders, AJAX cart updates). You can also pass Liquid data to JavaScript variables using the json filter.

How much does a Liquid developer charge?
Shopify Liquid developers typically charge $25–$150/hour depending on experience and location. Simple tasks (adding a banner, modifying a section) cost $150–$500. Medium complexity work (custom sections, conditional logic) runs $500–$2,000. Complex projects (full custom theme builds) range from $3,000–$15,000+. Freelancers are generally 30–50% cheaper than agencies.

Is Liquid used outside of Shopify?
Yes. Liquid is open-source and used by other platforms including Jekyll (GitHub Pages), Zendesk, Salesforce, and many other web applications. However, Shopify's implementation includes Shopify-specific objects (product, collection, cart) that do not exist in the standard Liquid library. The syntax transfers between platforms; the available objects differ.

Originally published at shopify.ecom-store.pro, where the article includes interactive charts and an embedded video tutorial.

Written by Alexander Matynian, a front-end developer specializing in Shopify since 2017 — building custom Liquid themes, optimizing storefront performance, and integrating third-party apps. More e-commerce guides at shopify.ecom-store.pro.

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