BareStack
← Blog
tutorials

Headless Shopify Costs vs Standard Shopify in 2026

Headless Shopify cost in 2026: the plan price, card and third-party fees, hosting at $0 to $20 a month, plus the build work a standard theme does not need.

·11 min read
Headless Shopify Costs vs Standard Shopify in 2026 — illustration

TL:DR: Headless Shopify cost is the same Shopify subscription plus a front end you pay for separately. Shopify's own Basic plan is £25 per month billed monthly or £19 billed yearly, and that price does not change when you go headless, because the Storefront API comes with the plan. What changes is everything around it: hosting at $0 to $20 per month, a one-off development project Shopify does not sell, and a codebase someone has to maintain, which is why Shopify's own documentation says a headless storefront costs more to build and run than a theme. The trade-off is control: you get page speed, markup and design freedom, and you give up the zero-maintenance theme layer.

A Shopify theme is a subscription. A headless storefront is a subscription plus a software project, and most cost comparisons hide that by quoting only the plan price on both sides.

It is not free, and it is not as expensive as the agency quotes suggest. The real number has four parts: the Shopify plan, the payment fees, the hosting and the build. Three are published. The fourth is a quote, and this post treats it as one.

Headless Shopify cost compared with a standard Shopify plan on a laptop

What "headless Shopify cost" actually means in 2026

Headless means the storefront and the commerce backend are separate systems. Your front end runs anywhere you like, and Shopify supplies products, collections, cart, checkout and payments through its APIs. Shopify's own headless overview describes the split plainly: you choose the stack, framework and hosting for the frontend, and Shopify handles the commerce underneath.

That structure creates the cost model. The Shopify subscription stays, because the APIs are part of the plan. A second hosting bill appears, because the front end no longer lives on Shopify's servers. A development cost appears, because somebody has to build and then maintain a storefront that a theme would have given you for the price of a licence.

The part that never appears in a quote is maintenance. Shopify ships theme updates and platform changes continuously, and a theme absorbs them. A headless storefront does not: it is a codebase with dependencies, and it needs an owner.

Cost lineStandard Shopify themeHeadless Shopify
Shopify plan£25/mo Basic, £19 yearlySame plan, unchanged price
Front-end hostingIncluded in the plan$0 Hobby to $20/mo Vercel Pro, or from EUR 5.99 on Hetzner
BuildTheme licence or a theme customisationA development project, quoted per store
MaintenanceShopify handles platform updatesYour codebase, your dependency upgrades
CheckoutShopify checkoutShopify checkout, with custom steps on Plus only
API accessNot neededStorefront API included, Admin API 100 points/second on standard plans

What Shopify charges either way

Shopify's UK pricing page, read on 9 November 2026 and quoted in GBP, lists Basic at £25 per month billed monthly or £19 per month billed yearly, Grow at £65 or £49, Advanced at £344 or £259, and Plus from £1,800 per month, per Shopify's pricing page. New stores get a three-day trial and £1 per month for the first three months.

Card rates move with the plan: 2 percent plus 25p on Basic, 1.7 percent plus 25p on Grow, 1.5 percent plus 25p on Advanced and 1.3 percent plus 25p on Plus for standard online card payments. Those are the rates when you use Shopify Payments. Use a third-party payment provider instead and Shopify adds a transaction fee on top: 2 percent on Basic, 1 percent on Grow, 0.6 percent on Advanced and 0.2 percent on Plus.

None of that changes when you go headless. A headless store on Basic pays £25 a month, the same as a themed store on Basic, because the Storefront API is part of the plan rather than an add-on. What the higher plans buy is a lower card rate and, in the pricing table's own words, API rate limits that go up to 2x on Advanced and up to 10x on Plus for select APIs.

If your reason for going headless is catalog size rather than design, check the API line before assuming Basic is enough. Admin API calls are limited by calculated query cost, with a restore rate of 100 points per second on Standard, 200 on Advanced, 1000 on Plus and 2000 on Enterprise, per Shopify's GraphQL Admin API rate limit documentation.

What the front end adds in hosting

Hosting is the cheapest line and the easiest to get wrong in the other direction. A statically generated storefront serves most pages from a CDN, so the bill is small until traffic arrives in bursts.

Vercel lists Hobby at $0 for personal, non-commercial use, and Pro at $20 per month per user with $20 of included usage credit, per Vercel's pricing page. Usage beyond the credit is metered.

The other end of the market is a server you own. Hetzner's cloud range starts at EUR 5.99 per month excluding VAT for a cost-optimized instance, per Hetzner's cloud pricing, and a statically built Next.js storefront plus a small API runs on the cheapest tier. That is the pattern behind this five-dollar-a-month website build, and it is why the hosting line in a headless quote should be the smallest number on the page.

The hidden cost is not the server. It is the build pipeline, the preview environments, the image optimisation and the monitoring that a managed platform includes and a bare VPS does not. Comparing Coolify with Vercel covers that trade in detail.

Headless Shopify cost includes development work on a custom storefront build

What the build costs, and why Shopify has no line for it

There is no Shopify line item for a headless build, because Shopify does not build it. That is the honest answer to the question, and it is why every "headless Shopify cost" article that quotes only plan pricing is missing the largest number.

Shopify's own documentation is direct about it: "A headless storefront costs more to build and run than a theme. Before you commit, make sure that the merchant accepts the added cost and complexity, and has developers to maintain the storefront after launch," per the headless overview on shopify.dev. That sentence is on Shopify's site, not an agency's.

What you are buying is a front end built to your design and wired to the Storefront API, with the SEO markup and page structure a theme cannot give you. BareStack built that for Knurle, a supplement brand: a statically generated Next.js storefront reading the Storefront API at build and revalidation time, with checkout handed to Shopify's native checkout on a subdomain, as described in the Knurle storefront case study. That post is the closest thing to a public cost breakdown, and it describes the trade-off rather than quoting a figure.

The variables that move a quote are catalogue size, template count, how much content lives in a CMS, and whether the brand needs search, bundles or subscriptions. A single-brand store with 30 products is a small project. A multi-market store with B2B pricing and 4,000 SKUs is not.

The API limits, quoted correctly

Most headless cost articles warn that Storefront API rate limits will throttle your traffic. That is out of date. Shopify's Storefront API documentation states that requests from real buyers are not subject to a fixed request-per-minute limit, that rate limiting for buyer traffic is "none", and that what is limited is automated traffic and checkout creation.

The same page sets out the real constraints. Bots and crawlers are limited, most strictly when unsigned, with Web Bot Auth signatures available for higher limits. Checkout creation is throttled per minute and returns a throttled error when it trips. Tokenless access has a query complexity limit of 1,000. Malicious-looking requests get a 430 security rejection, so the buyer IP header has to be forwarded correctly.

That distinction matters for cost. If buyer traffic were rate limited, you would need a caching layer and an on-call engineer. Because it is not, the API is a build-time dependency rather than a scale problem.

When headless is worth the money

Shopify lists the conditions that justify headless, and they are narrower than the marketing suggests: when the experience cannot be built with sales channels, themes and apps; when the frontend stack does not use Liquid; when you want to add Shopify commerce to infrastructure you already run; when you sell on channels Shopify does not support; or when a CMS has to drive storefront content, per the same headless overview.

  • If you sell 20 products, use a paid theme and your pages load in under two seconds on mobile, stay on the theme. Headless buys nothing you can measure.
  • If organic traffic is the growth channel and your theme's app scripts are what break Core Web Vitals, headless pays for itself in rankings. The median mobile home page shipped 632 KB of JavaScript in July 2025, per the Web Almanac page weight chapter. Headless does not make that number zero, but it puts the budget under your control. This analysis of why DTC supplement stores lose to page speed makes the same argument for retail.
  • If your storefront has to live inside an existing app, a membership site or a content platform, headless is the only route that does not involve fighting Liquid.
  • If you need a checkout flow that differs on the information, shipping or payment step, note that checkout UI extensions for those steps are available only to stores on Shopify Plus, per Shopify's checkout UI extensions documentation. Headless does not unlock them; Plus does.
  • If you have no frontend developer and no plan to retain one, the maintenance line will eat the gains. A theme that Shopify keeps working is worth more than a codebase nobody updates.

The realistic answer for most small stores is a theme, and the realistic answer for a brand whose growth depends on organic search and page experience is headless with a static front end.

Integrating with the rest of your stack

A headless front end is only worth the money if it removes work elsewhere. The usual win is data: products, content, orders and customers in systems that talk to each other instead of being copied between apps.

Start with what the front end reads. If product facts live in one file or one CMS rather than in 30 duplicated theme sections, a formulation or price change propagates everywhere at once. That is how the Knurle build handles dosing and purity data, and it is the difference between a storefront you can update in an afternoon and one that needs a developer for every product change.

Then look behind the store. Orders and customer records are where headless projects usually stall, because the front end is new and the back office is still a spreadsheet. BareStackOS, BareStack's free open-source CRM, takes an order webhook and a customer record without a per-seat licence, described on the BareStack features page.

The cost test that matters is total ownership, not the first invoice. Add the Shopify plan, the payment fees, the hosting, the build amortised over three years and an honest maintenance estimate, then compare that to a theme plus the apps it needs to match the result. The BareStack comparison page applies that test across the tools a small store runs, and the FAQ covers how self-hosted components handle backups.

If hosting is the line you want to shrink, the Hetzner and AWS cost comparison puts numbers on both, and the guide to running business apps on one server covers the operational side.

Bottom line

Headless Shopify cost is the Shopify plan you were already paying, plus hosting at $0 to $20 per month, plus a development project that Shopify does not sell and does not price, plus the maintenance of a codebase you now own. On a Basic plan the subscription is £25 per month billed monthly or £19 billed yearly either way, so the decision is never about the plan price. It is about whether page speed, markup control and design freedom are worth a build and an owner, and for a small store with a good theme the answer is usually no.

FAQ

Does going headless change my Shopify plan price?

No. The Storefront API and the Customer Account API come with the plan, so a headless store on Basic pays the same £25 per month billed monthly, or £19 billed yearly, as a themed store on Basic, per Shopify's pricing page. What can change is which plan you need, because higher tiers carry higher API limits and lower card rates.

How much does a headless Shopify store cost to build?

There is no published price, because Shopify does not build it and each store is a separate project. The variables are catalogue size, template count, CMS integration and whether the store needs search, bundles or subscriptions. Treat any figure quoted without those details as a placeholder, and ask for the maintenance cost per year alongside the build cost.

Is the Shopify Storefront API rate limited?

Not for buyer traffic. Shopify's documentation states that requests from real buyers are not subject to a fixed request-per-minute limit, and that what is limited is automated traffic, checkout creation and tokenless queries above a complexity of 1,000, per the Storefront API documentation. Bots and crawlers are limited, and signing requests with Web Bot Auth raises those limits.

Do I need Shopify Plus for a headless store?

No. Shopify supports headless storefronts on its standard plans through two channels: one where you host the front end yourself, including Hydrogen deployed anywhere, and one where Hydrogen runs on Shopify's Oxygen hosting, per the headless overview. Plus matters for checkout customisation, not for headless itself.

What does headless hosting cost per month?

Between nothing and about $20 for most small stores. Vercel lists a free Hobby tier for non-commercial use and Pro at $20 per month per user with $20 of included usage credit, per Vercel's pricing page. A self-hosted front end on Hetzner starts at EUR 5.99 per month excluding VAT, per Hetzner's cloud pricing.

Can I go back to a Shopify theme after going headless?

Yes, and the data survives because products, orders and customers live in Shopify either way. What you lose is the front end, so the cost of going back is a theme purchase and a template rebuild. Keep the Shopify plan active throughout, because cancelling it is the step that makes a return expensive.


Photo by Shixart1985 via Wikimedia Commons, licensed CC BY 2.0.

Photo via Rawpixel, public domain (CC0).

About the author

Anirudh Prashant · Founder & Lead Engineer, BareStack

Founder of BareStack. Builds custom, no-bloat software, self-hosted tooling, and AI automations for solopreneurs and small teams.