Shopify costs
Headless Shopify cost in 2026: every line on the bill
Headless Shopify costs your Shopify plan, the storefront build and someone to run it. The headless parts cost nothing extra: Hydrogen is MIT, open source, Oxygen hosting comes at no extra charge on every paid plan from Starter to Plus, and the Headless channel that issues your Storefront API keys is free. You don't need Shopify Plus. The money goes on the build, on replacing storefront apps, and on upkeep, because Shopify releases a new version every three months, each stable version supported for at least 12 months.
Prices and plan rules read from Shopify's own pages in October 2026, as shown to a US visitor. Shopify sets plan prices by country.
Disclosure: PandaCodeGen builds headless Shopify storefronts, so we have a commercial interest in one side of this decision. That's why this page lists vendor prices and our own price, but no market price band, speed uplift or payback period.
Hassan Jamal·Published ·Updated ·17 min read
Headless Shopify cost, line by line
Headless Shopify costs your Shopify plan, from $39/mo on Basic, plus the build and the upkeep. Hydrogen, Oxygen hosting and the Headless channel add nothing to that bill. Shopify publishes the first four lines below, so you can check them today; the other four depend on your store and your team, which is where quotes differ. Shopify prices are US prices as of October 2026.
| Line | What you pay | What to know |
|---|---|---|
| Shopify plan | Basic $39/mo ($29/mo billed yearly), Grow $105/mo ($79/mo billed yearly), Advanced $399/mo ($299/mo billed yearly), Plus from $2,300/mo | The plan you'd pay for anyway. Hydrogen on Oxygen runs on every paid plan, so it doesn't force a higher tier. |
| Hydrogen | $0 | MIT, open source. You can host it on Oxygen or anywhere else. |
| Oxygen hosting | No extra charge | On Starter, Basic, Grow, Advanced, Plus, and Pause and build. Not on Agentic plans. |
| Headless channel and Storefront API | Free channel | The channel issues your API keys. Shopify sets no fixed request-per-minute limit for buyer traffic. |
| Hosting outside Oxygen | Vercel Pro $20 a month, plus usage | Only if you build in Next.js or another framework. What Vercel really costs breaks down the usage side. |
| Storefront apps | Varies | Apps that draw on the theme need replacing or rebuilding. Audit the app bill first. |
| The build | Your written quote | Ours starts at the Scale tier, $5,000. A store with its own content system, search, accounts and migration is quoted after a scoping call. |
| Upkeep | Your team's or a supplier's time | At least one API upgrade a year, plus security updates, monitoring and releases. |
Do you need Shopify Plus to go headless?
No. Shopify offers Oxygen hosting at no extra charge on Starter, Basic, Grow, Advanced, Plus, and Pause and build, and the Headless channel is free on the App Store. Plus starts at $2,300/mo, and choosing it is a decision about your sales volume and the features you need, not a condition of going headless.
One planning catch: development stores and trial plans can build and test a Hydrogen storefront, but they get no public environments, so their preview links always need a store login. The number of public environments differs by paid plan, so check that limit before you promise anyone a shareable preview.
Hydrogen on Oxygen or Next.js on Vercel: the running cost
On Oxygen, hosting costs nothing extra, and you work inside Oxygen's limits: 10 MB per worker, 30 seconds of CPU time per request and 128 MB of memory, and Oxygen doesn't support a proxy in front of a deployment. On Vercel, a Next.js storefront starts at the Pro plan's $20 a month (platform fee including one deploying seat and $20 a month of usage credit; added seats and usage beyond the credit are extra), and you choose the framework, the content system and the rest of the stack yourself.
Next to the build and the upkeep, that hosting gap is small. Pick by the team that will run the storefront: Hydrogen keeps you on Shopify's conventions and release tooling, and Next.js suits a team that already ships one or needs to bring in other systems. Both talk to the same Storefront API, and both send shoppers to the same Shopify checkout.
The 2026 decision in one view
Stay on a theme unless a named requirement forces you off it. If something does force you off, the two headless paths differ mainly by how much wiring your team wants to own: Hydrogen gives you Shopify's conventions and less choice, a custom Storefront API client gives you framework freedom and more integration work. And whichever you pick, search, analytics, consent and checkout are inside the migration scope rather than afterthoughts.
- ✓Stay on a theme if it already does what you need and your team would rather run one system than two.
- ✓Choose Hydrogen when Shopify's official React stack and its commerce conventions fit the team.
- ✓Build your own Storefront API client if you genuinely need to pick your own framework, and your team is willing to do the wiring.
- ✓Your search traffic, analytics, accessibility, consent banner, checkout and day-to-day running are part of the migration, not afterthoughts.
Four parts of your business to check before replacing the storefront
Score a headless proposal on all four of these or it will look better than it is. Commerce mostly stays where it is, which is the reassuring part. Experience is what you are buying. Discovery is what you can lose if the migration is careless. Operation is the one that keeps costing after launch, and it is the dimension quotes leave out.
Commerce
What you sell and how people buy it.
Experience
The pages themselves, and who edits them.
Discovery
Whether Google and shoppers can still find you.
Operation
Keeping it safe, shipping changes, and who owns it.
One dated dependency to check before you scope anything: if your operation ran on Stocky for purchase orders or demand forecasting, Shopify made it unavailable after August 31, 2026. See our guide to that deadline for what stopped working, and export what you still need before a replatform starts.
Is headless Shopify worth it?
For most stores, no. We build headless storefronts, so take that as a filter, not modesty. Headless converts a configurable store into a software project. The build is the smaller half. Whether it was worth it comes down to who maintains it, deploys it and is on call for it in year two.
Before costing a headless build, price the alternative honestly. Online Store 2.0 (sections on every template, app blocks and metafields) closed a large part of the gap that originally justified going headless. A well-built 2.0 theme on a disciplined app stack is the right answer for a great many stores that are currently being quoted for Hydrogen.
What you give up is specific, and it is worth writing down before anyone signs:
- ✓The theme editor. Merchandisers lose drag-and-drop layout control over the storefront. Every layout change becomes a developer ticket and a deploy, which is a staffing change disguised as a technical one.
- ✓One-click app installs for storefront features. Apps that inject storefront UI through theme app extensions don't carry over, so reviews, loyalty, upsell and search widgets each need an integration decision, not an install.
- ✓Native previews and the safety of theme duplication. Testing moves into your own staging and release process, which you now own.
- ✓Shopify's own defaults for storefront analytics and consent. These become architecture you configure, not settings you toggle. The analytics section below covers them.
The revenue threshold you will see quoted, usually "not under a few million a year", comes from practitioner forums rather than from Shopify, and we do not repeat it as a rule. The question that decides it: do you employ or retain someone who will own the frontend after launch? A ten-million-dollar store without that person is a worse candidate than a two-million-dollar store with an engineering team. If nobody will own it, the right call is a better 2.0 theme, and the sections below show when it isn't.
What going headless on Shopify changes
Your storefront team takes over how pages render, how routing works, what the interface does, how content gets in, and most of the analytics and deployment. Shopify keeps running the commerce: products, collections, pricing, the cart, checkout, and the operations behind them. Write that boundary down feature by feature, because nobody remembers it under pressure. If you are still settling the terminology, what headless commerce means in practice covers the architecture in plainer terms first.
This page gives Shopify's published prices and ours, but no industry band for a headless build and no predicted ranking or conversion gain. Both depend on what you ask for, what you connect it to and who runs it afterwards, so one figure would tell you nothing about your project. Headless isn't automatically faster either: Shopify ties performance to how well the storefront is built, and moving rendering into your own frontend moves that responsibility onto you. Scope the work against your requirements, then measure the build you ship.
What can a Shopify theme not do?
The case for headless is a requirement a theme cannot meet, not a theme somebody dislikes. Five requirements qualify, and they share one property: each needs control over rendering, routing or composition that Liquid and sections do not hand you. If your reason is not on this list, a theme project is the cheaper answer.
- ✓A differentiated interaction model that is impractical within accepted theme constraints.
- ✓A storefront that combines multiple commerce, content or product systems.
- ✓Consistent experience logic across web, app, kiosk or other supported channels.
- ✓Release independence needed by an established product and engineering team.
- ✓Rendering, caching or personalization control supported by a clear operating model.
If the real problem is one slow page, look at the theme, the apps, the images and the third-party scripts first. A separate frontend can reproduce every one of those problems and add some of its own. Start with diagnosing a slow Dawn theme and the wider Shopify store speed optimization guide, and see why a Shopify Plus store can still be slow before assuming the plan is the constraint.
Hydrogen, Next.js or a Shopify theme: which path?
Three paths are available, and the difference between them is how much integration work your team owns afterwards. A Shopify theme leaves almost all of it with Shopify, Hydrogen splits it, and your own Storefront API client puts every decision on your side. Pick by the team you have rather than the stack you admire.
| Path | Best fit | Responsibility |
|---|---|---|
| Shopify theme | Requirements fit Liquid, sections and platform extensibility | Lower separate-frontend burden |
| Hydrogen | Custom React storefront using Shopify's official headless framework | Custom app plus Shopify integration and release operation |
| Custom API client | A justified framework or runtime requirement | More integration decisions owned by the implementation team |
Shopify lists Hydrogen as its React framework and the Storefront API Client as its recommended lightweight JavaScript client for custom storefronts outside Hydrogen. The API is versioned, which means quarterly releases, upgrades and things being removed. Put that in your maintenance plan, not in a footnote. If the choice is still open between staying native, going headless or leaving the platform, work through our Shopify and custom website decision framework.
Which Shopify apps break when you go headless?
Apps that render through the theme break, because a headless storefront has no theme for them to render through: reviews widgets, upsell blocks, cookie banners, chat launchers and page builders. Apps that work through the Shopify admin, such as order management, fulfillment and accounting sync, keep working. Inventory what the store does today across these six areas; the last one decides the budget.
- ✓Products, variants and collections, with the stock, prices and discounts that go with each market you sell into.
- ✓How the cart behaves, how it hands off to checkout, and how express payment and accounts work.
- ✓Search and recommendations, plus anything bolted on: subscriptions, bundles, loyalty, reviews, wish lists.
- ✓Tax, shipping, click and collect, returns, answering customers, and getting orders out.
- ✓Selling to businesses, selling abroad, other languages, and making it usable for everyone.
- ✓Whether each app works with the new storefront: can it exchange the required data, display its customer-facing features and still respond correctly to orders and checkout actions.
App compatibility is where the rework tends to hide, so inventory what each app does and what it charges before you commit. How to read your real monthly Shopify app bill gives you a method for the second half of that.
How does headless Shopify change analytics and consent?
A custom storefront doesn't inherit the analytics your theme did. Shopify documents a migration path for custom headless analytics, and says in the same place that the custom setup is not officially supported. Hydrogen has its own supported path. Decide this before framework selection, especially after the 2026 cookie changes.
- ✓Decide what each consent category covers, and what the site is allowed to do before someone consents, region by region.
- ✓List every event Shopify, your ad platforms, your email tool and your own analytics fire, and say who owns each one and what it means.
- ✓Check that an event is recognized once and not twice, that attribution still works, and that the handoff to checkout holds.
- ✓Write down what your server sends, what the browser sends, how long each is kept, who processes it, and how it gets deleted.
Advertising measurement belongs in the same scope, not in a later task. Our guide to repairing Meta ad tracking in 2026 covers the server-side event work that a storefront change usually disturbs.
Will headless Shopify hurt your SEO?
Headless isn't better or worse for SEO by itself. The implementation controls the output. Google warns that significant site changes can produce temporary ranking fluctuations while URLs are recrawled and reindexed. Build an evidence-backed migration plan instead of promising ranking retention.
- ✓Crawl the store first and keep the record: every URL, its status code, its canonical, its metadata and headings, its content, where it links, and whether it can be indexed.
- ✓Map every changed URL to a relevant destination and test permanent redirects.
- ✓Render crawlable navigation, product content, canonicals and directives in the delivered HTML.
- ✓Keep product price, availability, variants, structured data and Merchant Center feeds consistent.
- ✓Generate accurate robots and sitemap output and verify production Search Console properties.
- ✓Monitor crawl errors, indexed pages, queries, templates and server capacity after launch.
What a migration does to search visibility expands on the monitoring side of this list. The same product data also feeds agentic shopping surfaces, which we cover in what Google's universal commerce protocol means for a store.
What speed should a headless Shopify store hit?
Agree a written lab target before the build, with its test conditions attached: we contract for a 90+ Lighthouse acceptance target on the pages named in the scope. Without the conditions the number means nothing, because the same build scores differently on another device, network or cache state. Six things make it a target you can hold a supplier to.
- ✓A real example of each: the home page, a collection, a product, search, the cart, and any campaign pages you agree on.
- ✓Mobile and desktop profiles with device, network, geography, cache and consent state recorded.
- ✓Three consecutive tests per agreed page and profile, reported without selecting only the best run.
- ✓Functional, accessibility, SEO, analytics and error guardrails.
- ✓Field Core Web Vitals monitored after enough real traffic exists.
- ✓A written remedy if the contracted target is not met under the accepted conditions.
PandaCodeGen can contract for a 90-plus Lighthouse acceptance target under documented test conditions. That is a delivery criterion, not a promise that every visitor, route, date or third-party state will permanently produce the same score. Core Web Vitals explained sets out the field metrics that acceptance criterion is measured against later.
What keeps costing after launch?
The build is one line in a headless budget, and rarely the one that decides whether the project was worth doing. Six cost categories run for as long as the storefront does, and two of them arrive on Shopify's schedule, not yours: security updates, and API upgrades, because Shopify releases a new version every three months, each stable version supported for at least 12 months. Price the whole column.
- ✓Working out what you need, designing it, building it, moving the data, and the content work.
- ✓Your Shopify plan, hosting, the CMS, search, email, monitoring, and whatever else you pay monthly.
- ✓App replacement, API limits, integrations and vendor support.
- ✓Security updates, framework and API upgrades, incident response and recovery.
- ✓Merchandising workflow, preview, localization, training and documentation.
- ✓Internal product, design, analytics and engineering time.
Our published Scale tier starts at $5,000. A headless storefront with its own content system, search, customer accounts and migration usually goes beyond Scale and is quoted after a scoping call. That's our price, not an industry benchmark. Final scope, third-party costs, ownership, support and acceptance terms are agreed in writing before work starts. See the ecommerce development service and the pricing page for what each tier covers.
The migration sequence, in order
A headless Shopify migration runs in six steps, in this order, because two of them are cheap before you build and expensive after.
- ✓Audit what the theme currently does. Every template, every app that renders on the storefront, every script, every custom section. This is the inventory the rest of the plan is priced from, and skipping it is one reason headless quotes vary so widely.
- ✓Create the Shopify custom app and grant Storefront API access. This is the connection the new frontend reads products, collections and carts through, and getting the scopes right early avoids rework later.
- ✓Build the frontend against real data, not fixtures. Product, collection, search, cart and any content routes, using the actual catalog, so pagination, variant edge cases and out-of-stock states surface during the build rather than at launch.
- ✓Handle images and third-party scripts deliberately. The theme was doing both for you. Decide what loads on first render and what defers, because this is where a headless rebuild can land slower than the theme it replaced.
- ✓Deploy with URLs mapped and pre-generation decided. Every old address needs a documented destination, and which routes are pre-built versus rendered on request is a decision, not a default.
- ✓Keep checkout on Shopify. It's what you want Shopify to keep owning, and it is where PCI scope, fraud tooling and payment integrations already live.
One rule answers a lot of the app-compatibility questions and saves a lot of discovery time: apps that talk to the Shopify admin generally keep working, and apps that inject themselves into the theme generally stop existing. Order management, fulfillment, accounting sync and anything operating behind the scenes is unaffected because it never touched the storefront. Reviews widgets, upsell blocks, cookie banners, chat launchers and page builders all rendered through the theme, so on a headless storefront they have to be rebuilt, replaced with an API-based equivalent, or dropped. Run your app list through that question before anyone quotes the work.
Can you roll back a headless Shopify launch?
A launch is reversible only if the rollback criteria were written down before anyone was under pressure to keep going. Six items make that possible, and the one most often skipped is naming who decides. Settle in advance what evidence would send you back, because at two in the morning nobody wants to be the person who called it.
- ✓Content, URL and data freezes with named exceptions.
- ✓Production-like staging and a complete acceptance checklist.
- ✓Load, security, accessibility, browser and device testing.
- ✓Written steps for DNS, redirects, cache, webhooks, secrets and who owns each provider account.
- ✓Rollback criteria, decision owner and tested recovery path.
- ✓Post-launch monitoring for commerce, SEO, analytics and performance.
For a commerce build delivered under this kind of plan, see our MyCustomPatches project.
Related reading
On the storefront performance side, read testing storefront speed against conversion data and how to tell whether a slow store is costing sales.
Tell us what you have
We will map URLs, commerce requirements, app dependencies, data flows, test conditions and ownership before recommending Hydrogen, a custom storefront or a Shopify-native solution.
Primary sources
- Shopify: headless benefits, tradeoffs and fit
- Shopify pricing (US)
- Shopify: Hydrogen and Oxygen fundamentals, supported plans
- Shopify App Store: Headless channel
- Shopify API versioning
- Shopify Storefront API reference
- Vercel pricing
- Shopify Hydrogen and Oxygen getting started
- Shopify: SEO for Hydrogen
- Shopify: custom headless analytics migration
Questions & answers
Frequently Asked Questions
How much does headless Shopify cost?
Do you need Shopify Plus to go headless?
Is Shopify Oxygen hosting free?
How often does a headless Shopify store need upgrades?
What is headless Shopify?
How much faster is headless Shopify than a theme?
Is headless Shopify worth the investment?
Can I still use Shopify apps with headless?
Related Articles
Slow Shopify Store Losing Sales? Build an Evidence Model
Join route-level field performance to your funnel, build bounded opportunity scenarios, test the least disruptive remedy and separate measured outcomes from assumptions.
Shopify Dawn Theme Slow? Diagnose the Store, Not the Name
Use Shopify field reports and controlled previews to isolate media, apps, third parties, customization and theme code before choosing a rebuild.
Shopify App Costs in 2026: Audit the Real Bill
Reconcile Shopify-billed charges, external subscriptions, usage, workflows, data and performance before you keep, replace or remove an app.