Headless Commerce: When a Webshop Actually Needs It
By CodexierPublished 5 min read
Headless commerce is pitched as the modern way to build a webshop: faster pages, total design freedom, content from anywhere. All of that can be true. What the pitch leaves out is that you trade a finished storefront, maintained by the platform, for a custom one that you must build and maintain yourself. This guide explains what headless is, what it really gives, what it costs, and how to tell whether you have outgrown a theme or simply need a better one.
What headless commerce means
In a traditional setup, Shopify or WooCommerce handles everything: products, cart, checkout and the pages customers browse, rendered through a theme. In a headless setup, the platform keeps products, inventory, orders and usually checkout, while a separately built front end, often in a framework such as Next.js or Shopify's own Hydrogen, fetches data through the platform's API and renders the pages. Content can come from a separate content management system at the same time.
Speed and design freedom
The two main arguments are speed and freedom. A headless front end can be very fast, because you control exactly what loads on each page and can serve pre-built pages from the edge. And you are no longer limited by what a theme's sections allow: complex product configurators, editorial content woven into product pages or one experience across web, app and in-store screens all become possible.
Real gain
Full control over page weight and loading, which matters for large catalogues and mobile-heavy traffic.
Often overstated
Speed. A lean theme with few apps is fast too. Many slow shops are slow because of app scripts and oversized images, which headless does not fix by itself.
Genuine freedom
Custom experiences that would fight a theme at every step, and content from several sources in one front end.
Before choosing headless for speed, measure where the time goes today. Our guide to Core Web Vitals explains the metrics; if the culprit is third-party scripts, the fix is removing them, not rebuilding the storefront.
Costs and developer dependency
| Area | Theme-based shop | Headless shop |
|---|---|---|
| Initial build | Theme setup and adjustments | A custom front end built from scratch |
| Apps and plugins | Install from the app store; most render in the theme automatically | Many storefront apps do not work without integration work |
| Content changes | Staff edit in the theme editor | Depends on the content system chosen; layout changes need developers |
| Hosting | Included in the platform | Separate hosting for the front end |
| Maintenance | Platform updates the theme engine | You maintain framework, dependencies and API version changes |
| Supplier dependency | Many agencies can take over | Fewer can take over a custom front end |
The recurring cost is the one that surprises people: a headless storefront is software you own and must keep up to date.
Everything the marketing team could do in the theme editor needs thinking through again. A headless build can give them a good editor, but only if it is designed and paid for. See what a webshop costs to build and run for the baseline you are comparing against.
Signs you have outgrown a theme
- You sell in several markets or channels and want one front end with shared components across them.
- Your product experience needs logic a theme cannot express, such as a complex configurator or bundles built from many sources.
- Content and commerce must be deeply mixed, for example editorial stories with shoppable components throughout.
- You already have developers in-house or on contract, and the storefront is a strategic asset you want to control.
- You have measured that the theme and its apps are the speed limit, and removing apps has not solved it.
If only one of these fits, the answer is usually custom sections or an app inside the existing theme, which gives you most of the benefit at a fraction of the cost and keeps the platform's maintenance working for you.
Who should wait
A new shop still validating its range, a small team without a developer, or a shop whose main problem is traffic or conversion should not go headless. The money is better spent on product pages, checkout and marketing. Headless also adds risk during a platform migration, so change one thing at a time.
When not to buy headless from us: if your goals fit in a theme, we will recommend a theme and custom sections instead. Our custom e-commerce features service covers both custom theme work and headless builds where they are justified; see pricing or book a call and bring what you want the shop to do that it cannot today.
Frequently asked questions
Is headless faster than a normal Shopify theme?
It can be, but not automatically. A lean theme with few apps is fast. Headless gives you more control over what loads, which matters most for large catalogues and custom experiences.
Does headless work with Klarna and Swish?
Usually yes, because checkout typically stays on the platform, where the payment methods are configured. If you build a custom checkout as well, each payment method must be integrated, which adds work and risk.
Can we go headless later?
Yes. Products, customers and orders stay in the platform, so you can replace the front end later without migrating data. Starting on a theme and moving when you have a clear reason is the lower-risk route.
What does headless mean for SEO?
A well-built headless front end renders pages on the server and can be excellent for SEO. A badly built one that renders only in the browser can hurt rankings, so server rendering and redirects must be part of the plan.
Theme, custom sections or headless?
Tell us what your shop needs to do that it cannot today. In fifteen minutes we can tell you which level of build fits, and often that it is less than you feared.
Book a free 15-minute call