Shopify Headless Development
Gencer Karakaya builds headless Shopify storefronts with Hydrogen, Next.js, and the Storefront API, for merchants whose requirements a Liquid theme genuinely cannot meet. Headless buys you full control of the front end and the freedom to pull in data from any system, and it costs more to build and more to maintain. Most stores should stay on a theme. This page is about the cases where the tradeoff pays for itself, and how to tell them apart.
What headless Shopify actually means
On a normal Shopify store, the storefront your customers browse is a Liquid theme that Shopify renders and hosts. Headless replaces that theme with a separate application you own, which asks Shopify for products, collections, and cart state through the Storefront API and renders the pages itself.
Shopify still runs the commerce engine underneath: catalog, inventory, cart, discounts, checkout, orders, payments. What changes is the layer your customers see, and who is responsible for it. You gain complete control over the interface and the ability to combine Shopify data with any other system. You also take on hosting, deploys, dependency updates, and the engineering time to keep it all working, which Shopify handles for you on a theme.
When headless makes sense
Headless earns its cost when a specific requirement cannot be expressed in a theme. In practice that usually looks like one of these:
- A configurator, quote builder, or booking flow with real business logic between the product and the cart
- Content, pricing, or availability that has to come from an external CMS, PIM, or ERP as the page renders
- One front end serving a storefront and a mobile app or kiosk from the same codebase
- A catalog whose search and filtering exceeds what the theme and its apps can do at your size
- An interface that is genuinely a web application rather than a catalog, where the theme's page model fights you at every step
When you should stay on a theme
If your storefront is a catalog, product pages, a cart, and some content, a theme is the better engineering decision. A well built Online Store 2.0 theme is fast, cheap to change, and lets your team edit pages in the theme editor without booking developer time. Headless takes all of that away and hands you a codebase.
Going headless to fix speed is usually the wrong fix. Most slow Shopify stores are slow because of apps, third-party scripts, oversized images, and bloated theme code, and repairing those costs a fraction of a rebuild while keeping the store your team knows how to run. If speed is the goal, start with a performance audit, not an architecture change.
Headless is also a staffing decision, not just a build. Once the storefront is code you own, it needs someone to maintain it: dependency updates, deploys, API version bumps, and the bugs that follow. If there is no budget for that after launch, headless will degrade.
What this includes
- Hydrogen storefronts on Oxygen, or Next.js / React on Vercel or Cloudflare, built on the Storefront API
- Custom cart, checkout handoff, and customer account flows that a theme cannot express
- Content and data from outside Shopify: headless CMS, PIM, ERP, subscription and loyalty systems, custom pricing logic
- Core Web Vitals work built into the architecture (server rendering, caching, image and font strategy) rather than bolted on
- SEO parity with a theme build: server-rendered markup, canonicals, hreflang, structured data, and sitemaps that actually get crawled
- Incremental migration paths, so you can move one template at a time instead of rebuilding the whole storefront at once
- A written assessment first: if a theme will serve you better, that is what the assessment says
Headless vs a Shopify theme
| Shopify theme | Headless storefront | |
|---|---|---|
| Front end | Liquid, rendered and hosted by Shopify | Your application, hosted by you |
| Merchant editing | Full control in the theme editor | Limited to what the build exposes |
| Build cost | Lower, from $5,000 for a custom theme | Higher, from $15,000 |
| Ongoing cost | Shopify maintains the platform layer | Hosting plus your own engineering time |
| Checkout | Shopify checkout | Shopify checkout, handed off from your cart |
| Speed ceiling | High when the theme is built carefully | Higher, but only with deliberate work |
| External data | Through apps and metafields | Directly, at render time, from any API |
| Best for | Most stores, including large catalogs | Storefronts a theme genuinely cannot express |
Scroll the table sideways to compare
Both columns describe well executed builds. A careless headless storefront is slower and more expensive to run than the theme it replaced.
Investment
Headless assessment
A written recommendation on whether headless fits, before you commit to a build.
Headless storefront
Hydrogen or Next.js on the Storefront API, built and launched.
Ongoing development
Feature work and maintenance after launch.
Prices are in USD and are starting points. Final pricing depends on scope and complexity, and you get a written estimate before any work starts.
Frequently asked questions
What is headless Shopify?
Headless means Shopify keeps running your products, cart, checkout, and orders, while the storefront your customers see is a separate application that talks to Shopify through the Storefront API. Because the front end is no longer a Liquid theme, you can build any interface you want and pull data from any system. You also take on hosting, deployment, and maintenance that Shopify otherwise handles for you.
When is headless Shopify worth it?
When something specific about your storefront cannot be built in a theme. Common cases: a product configurator or quoting flow with real business logic, content and pricing that must come from an external CMS, PIM, or ERP, an interface shared with a mobile app, or a catalog whose filtering and search a theme cannot handle at your scale. If your reason is that headless sounds faster or more modern, it is not worth it.
When should I not go headless?
If your storefront is a reasonably standard catalog, product page, and cart, stay on a theme. A well built Online Store 2.0 theme is fast, cheap to change, and lets your team edit pages without a developer. Going headless to fix speed is usually the wrong fix too: most slow Shopify stores are slow because of apps, scripts, and images, and that is far cheaper to repair than a rebuild.
Is headless Shopify faster than a theme?
Not automatically. Headless gives you control over rendering and caching, so a carefully built headless storefront can be very fast, but a poorly built one is slower than the theme it replaced. A tuned theme beats a careless headless build. Speed comes from the decisions, not from the architecture.
Do I need Shopify Plus for headless?
No. The Storefront API is available on standard Shopify plans, so you can build headless without Plus. Plus matters for checkout customization, B2B, and higher API limits, which some headless projects need and others do not.
What happens to checkout if I go headless?
Checkout stays on Shopify. That is deliberate: Shopify-hosted checkout handles payments, fraud, taxes, and PCI compliance, and it converts well. A headless storefront hands the cart to Shopify checkout, and on Plus you can customize it with Checkout Extensibility.
Can I move to headless gradually?
Usually yes, and it is often the better plan. Moving one template at a time (product pages first, for example) keeps the rest of the store on the theme, limits the blast radius, and lets you judge the results before committing the whole storefront.
How much does a headless Shopify project cost?
Headless builds here start at $15,000, and ongoing development is $45/hr. Agency quotes for comparable work commonly land between $20,000 and $50,000, and enterprise builds go far beyond that. The build is only part of it: budget for hosting and ongoing engineering, because a headless storefront needs maintenance that Shopify would otherwise do for you.