"Go headless" is a common pitch to growing Shopify stores. It sounds like an upgrade. It is a different way of building a storefront, and it brings costs that are easy to miss. Owners who say yes without understanding it can end up paying for a custom front end they did not need.
This article explains headless in plain words, sets out what Shopify's own developer pages and blog say about when it makes sense, and ends with a decision list and a set of questions to put to any agency that proposes it. The pages were read on 3 November 2026. Shopify updates them, so check the dates before you rely on a detail.
What headless means for a store owner
A normal Shopify store uses a theme. Shopify's developer pages describe a theme as a set of templates that Shopify renders and hosts, so you run no server. Your team edits content in the theme editor.
A headless store splits the shop into two parts. The front end is what shoppers see. The back end holds products, carts, customers and orders. In a headless build, you or your agency create and host the front end, and Shopify's interfaces (APIs) supply the commerce data. Shopify's Storefront API page says the API hands customers off to checkout, and Shopify's blog says checkout stays on Shopify.
The pieces Shopify offers
Ask your agency which of these it plans to use. The names come up in proposals.
- Storefront API. A GraphQL interface for products, collections, search and the cart. The page says real buyer traffic has no fixed requests-per-minute limit, but automated traffic and checkout creation are limited. Versions are dated, and the page listed 2026-10 as the latest on 3 November 2026.
- Customer Account API. Handles sign-in, orders, addresses and profiles.
- Hydrogen. Shopify's toolkit for building a storefront. A Hydrogen post dated 14 October 2026 says it is now a library that works with any JavaScript framework, and that existing Hydrogen storefronts keep working. The post says Hydrogen was previously a framework built on React Router, and Shopify's legacy Hydrogen page, which covers versions 2026-04 and earlier, describes Hydrogen projects as React Router apps. Ask which version your agency means.
- Oxygen. Shopify's hosting for Hydrogen. Shopify's blog says it is included at no extra charge on supported paid plans, within runtime and usage limits, and the Hydrogen post calls it still free. Shopify's developer page on Hydrogen and Oxygen lists the plans, so check it for yours. You can also host elsewhere.
- Headless channel. The admin area where you manage storefronts and their access tokens.
There are lighter options too. Shopify lists Buy Button JS and storefront web components for adding products to an existing site, a WordPress plugin, and a Checkout Kit for native mobile apps. If you only need to sell a few products inside a site you already have, these may be all you need.
What Shopify says about when to choose headless
Shopify's developer overview recommends headless only when your needs cannot be met by its sales channels, themes and apps. It says a headless storefront costs more to build and run than a theme. It lists reasons to consider it:
- You want an experience that existing tools cannot support easily.
- Your web stack does not use Liquid, Shopify's theme language.
- You are adding Shopify commerce to systems you already run.
- You sell on channels Shopify does not support out of the box.
- You need to connect a content management system.
Shopify's blog, updated 17 October 2026, also says when a theme is likely the better fit: existing themes and apps meet your needs, your team relies on the visual editor, the deadline or budget is tight, or speed problems can be fixed inside the theme. That is Shopify's own view, so treat it as one input and test any proposal against it.
What you take on
These are the costs owners tend to miss. Every one comes from Shopify's own pages.
- Build time. Shopify says a custom build adds development and integration work before launch, and its checklist calls for time to schedule integration, migration and testing. Themes usually shorten the first set-up.
- Running costs. Shopify advises budgeting separately for development, integrations and maintenance, and for headless CMS subscriptions, paid apps and any external hosting.
- Maintenance. Your team owns the front-end application, its software updates, API compatibility, speed monitoring and bug fixes. With a theme, Shopify manages hosting and infrastructure. The Storefront API uses dated versions, so ask how your agency will track them. The Storefront API page I read does not say how long old versions stay supported, so ask your agency.
- Apps. Shopify tells teams to check how subscriptions, reviews, loyalty programs and analytics will work before committing. Shopify's blog suggests asking partners which existing apps need custom integration or replacement. Make a list of every app you use today and ask what happens to each.
- Content editing. A theme gives your marketers a visual editor. In a headless build, Shopify says to plan how content is created, previewed and published, and a headless CMS gives marketers a separate workspace that also appears as a cost line.
- Search and speed. A Shopify blog post from June 2026 says both approaches can support technical SEO and fast load times, and that results depend on the quality of the work, not on the architecture alone. So headless is not automatically faster. If your product addresses differ from Shopify's standard product address pattern, Shopify says you need server-side redirects. Read redesigning without losing SEO and Core Web Vitals for Shopify stores for how to measure this.
- Testing. Shopify says the team must test front-end changes for accessibility, security and API compatibility before release. Private API tokens must stay on the server, not in the browser.
A decision list
Answer each line yes or no. This is a thinking aid, not a score.
Signs that point toward headless
- You can name a specific shopper experience that no theme or app can deliver, and you can say why it matters to revenue.
- You already run a CMS, product information system or app that must drive the storefront.
- You sell through a native mobile app or another channel, and want one commerce back end behind all of them.
- You have developers in house, or a retained agency, to maintain the front end after launch.
- You have budget for the build and for ongoing work, not only for the launch.
Signs to stay on a theme
- Your plan depends mostly on apps that install into a theme.
- Your team edits pages and campaigns itself, with the visual editor.
- The main complaint is a slow or cluttered store, which a clean-up may fix.
- You have a hard launch date or a fixed budget with no room for upkeep.
If most answers sit in the second list, a theme is the lower-cost route that Shopify's own overview points to, and Shopify solutions for a theme build or clean-up can start there. Shopify also says retailers can mix headless and theme storefronts.
A middle path: start with one market or channel
Shopify's blog says a retailer can mix headless and theme storefronts. It describes keeping a theme for the main store and building a headless storefront for a single market or channel, then widening it if the pilot justifies it. For an owner this limits the risk. You learn what maintenance really takes before the whole business depends on it.
Questions to ask before you sign
A headless storefront is custom software, so treat the proposal like any custom software project.
- Which exact Shopify pieces will you use: Hydrogen, the Storefront API directly, Oxygen or other hosting?
- Which version of Hydrogen and the Storefront API, and who will upgrade them, and when?
- What will you do with each app we use today?
- How will my team edit pages? Which CMS, who pays for it, and who trains us?
- What is the redirect plan for every old address, and how will you check search traffic after launch?
- How do you test accessibility, speed and security before launch?
- What monthly or yearly costs will I pay for hosting, the CMS and support?
- Who owns the code and the accounts? See who owns the code in a software project.
- Is the build priced as a fixed fee or by time? See fixed price or time and materials, and how to read a custom software quote.
- Can we start with one market or channel first?
This is general information, not legal or tax advice. Check the current rules or ask a qualified adviser before you decide.
ESTASOFT works on Shopify solutions and custom software from offices in Dubai, Erbil and London. If you are weighing a theme build against a custom front end, read about our Shopify work and custom software, then send a short brief on the contact page.
Sources
- Build headless commerce: definition, build options, and when Shopify recommends headless (checked 3 November 2026)
- Headless overview: trade-offs, redirects and cart permalinks, API tokens (checked 3 November 2026)
- Storefronts overview: themes, headless and storefront APIs, and guidance on choosing (checked 3 November 2026)
- Storefront API reference: what the API covers, tokens, limits and dated versions (checked 3 November 2026)
- Hydrogen and Oxygen fundamentals: older Hydrogen description and Oxygen hosting (checked 3 November 2026)
- Hydrogen 2026-10 now available: post dated 14 October 2026 (checked 3 November 2026)
- Manage the Headless channel: storefronts, access tokens and permissions (checked 3 November 2026)
- Headless commerce: definition, benefits and costs: cost, trade-offs, apps, who it suits, updated 17 October 2026 (checked 3 November 2026)
- Headless commerce vs traditional commerce: cost, launch time, maintenance, content editing, pilot approach, updated 23 October 2026 (checked 3 November 2026)
- Headless commerce: benefits, trade-offs and when to use: SEO, speed and maintenance view, published 2 June 2026 (checked 3 November 2026)