Every "what is headless commerce" article is written by someone with something to sell. Vue Storefront wants you to buy Vue Storefront. commercetools wants you to buy commercetools. The headless-commerce agencies want you to buy their 400-hour build project. Even the "neutral" explainers are usually ghostwritten by marketing teams at the vendors who benefit if you believe headless is the future.
I have shipped headless stores on Shopify Hydrogen, built custom Next.js frontends on top of Shopify APIs for mid-market clients, and told dozens of founders — honestly — "you don't need headless, keep your Shopify Plus theme." After 500+ ecommerce builds across 19 years, I can tell you the honest answer: headless is right for about 10% of ecommerce businesses, and wrong for the other 90%. This article is the explainer without the vendor spin.
The 30-second answer
Headless commerce means your storefront (what customers see — the website, mobile app) is built separately from your commerce engine (what handles products, cart, checkout, orders), connected via APIs. Traditional platforms like Shopify or WooCommerce bundle both; headless splits them.
You need it if: you're at $5M+ annual revenue, you have specific frontend performance or UX requirements a traditional theme can't deliver, you serve commerce across multiple channels (web + app + kiosk), or you have a full-time frontend developer.
You don't need it if: you're under $2M revenue, you don't have an in-house developer, your frontend requirements are standard DTC, or your marketing team needs admin-level content control.
Everything else in this article is the detailed reasoning behind those two paragraphs.
What is headless commerce — the long answer
Traditional ecommerce platforms have two parts bundled together:
- The storefront (the frontend): the pages customers browse, the product listings, the cart, the checkout form. Built with the platform's theme system.
- The commerce engine (the backend): the systems that store products, calculate shipping, handle inventory, process payments, manage orders.
In a traditional setup, these two are tightly coupled. You pick a Shopify theme and it's locked to Shopify's commerce engine. You install WooCommerce on WordPress and the theme talks directly to the Woo database. The admin, the storefront, the APIs, and the frontend templates are all one system.
Headless commerce decouples these. The storefront becomes a separate codebase — typically a modern frontend framework like Next.js, Remix, Nuxt, or SvelteKit — that talks to the commerce engine over APIs (REST or GraphQL). The storefront can be hosted anywhere (Vercel, Netlify, Cloudflare), built with any tech stack, and iterated on independently of the commerce backend.
The commerce engine still handles everything commerce-related: product catalog, cart state, inventory, checkout, payments, orders, customer accounts, taxes, shipping rules. It just doesn't render the pages customers see anymore.
The analogy: think of a traditional ecommerce platform like a bundled smartphone that comes with its own fixed camera. The camera's quality is set, you can't swap it. Headless is like a professional camera system — the body (commerce engine) and the lens (frontend) are separate, each can be upgraded independently, but you need more expertise to use the full system.
What's the difference between headless and composable commerce?
Two terms that get confused because the industry uses them loosely.
Headless describes the architecture: frontend split from backend, connected via APIs. One commerce engine (Shopify, BigCommerce, Magento, commercetools) can serve a headless frontend.
Composable describes the strategy: building your commerce stack from multiple best-in-class vendors rather than one monolithic platform. Composable architectures are headless by necessity (because you're combining services), but headless architectures aren't always composable.
Example of headless but not composable:
- Commerce engine: Shopify
- Storefront: Shopify Hydrogen on Oxygen
- Search: Shopify's native search
- Reviews: Judge.me
- Email: Klaviyo
This is headless (Hydrogen is a separate frontend) but not composable (Shopify is still the primary platform for most functions).
Example of composable (also headless):
- Commerce engine: commercetools
- Storefront: Next.js on Vercel
- Search: Algolia
- Reviews: Yotpo
- Email: Braze
- CMS: Contentful
- Payments: Stripe (via commercetools)
- Shipping: ShipStation (via commercetools)
This is both headless and composable — multiple best-in-class vendors, each handling one piece, connected via APIs.
The industry's shorthand "MACH" (Microservices, API-first, Cloud-native, Headless) is composable's marketing acronym, pushed hard by the MACH Alliance since 2020. Treat it as useful framing, not a shopping requirement.
When does my business actually need headless commerce?
The honest four-scenario list.
1. Frontend performance is mission-critical
If your conversion rate materially depends on sub-1-second page loads, 100 Lighthouse scores, and specific Core Web Vitals targets your traditional theme can't deliver, headless gives you the control to hit those numbers.
Real example: a $20M/year beauty brand I audited in 2024 was on Shopify Plus with a premium theme. Mobile Lighthouse was 62, LCP was 3.1 seconds. After going headless on Hydrogen + Oxygen, mobile Lighthouse was 94, LCP was 0.9 seconds. Conversion rate lifted 11% in the first 60 days. For a $20M business, 11% is $2.2M/year — the $90k headless build paid back in 15 days.
But this works because the brand was already at scale, already had conversion-rate data to measure against, and already had the engineering team to execute. For a $500k/year store, the same build would still cost $90k and the performance improvement might only translate to $50k/year in incremental revenue. The math doesn't work.
2. Multi-channel commerce
If you sell through more than one channel — website + mobile app + in-store kiosk + voice + social commerce — maintaining one commerce engine with multiple frontends is cleaner than maintaining multiple separate storefronts.
Real example: a retail brand I worked with runs a website, iOS app, Android app, and 40 in-store kiosks. All four touchpoints need to see the same inventory, the same prices, the same promotions. Headless with Shopify as the backend + 4 separate frontends (web Next.js, iOS Swift, Android Kotlin, kiosk Electron) was the only architecture that worked. Trying to maintain 4 separate Shopify stores would have broken operations within a quarter.
3. Specific frontend requirements traditional themes can't deliver
Unusual UX patterns, heavy custom animations, complex personalization at every page, bespoke merchandising experiences, or interactive product configurators.
Real example: a bespoke tailoring brand with a 3D product configurator. Customers rotate a shirt, choose fabric by hovering, see live stitching previews. Zero traditional themes handle this; a custom frontend was non-negotiable. Shopify handled the commerce engine; Next.js + Three.js handled the frontend.
4. Enterprise scale ($5M+ annual revenue)
At enterprise scale, the flexibility gains of headless compound. The ability to A/B test every element, deploy custom experiences by segment, integrate with any marketing stack, and iterate without replatforming justifies the complexity cost.
Below $2M annual revenue, these gains compound slower than the complexity cost grows. The math works at scale, not before.
What does headless commerce cost compared to Shopify Plus?
The honest numbers from real projects.
Shopify Plus with premium theme (traditional)
| Line item | Cost |
|---|---|
| Shopify Plus (platform) | $2,300/mo = $27,600/yr |
| Premium theme (one-time) | $350 |
| Theme customization | $8,000–$25,000 one-time |
| Apps (Klaviyo, Judge.me, ReCharge, etc.) | $300–$800/mo = $3,600–$9,600/yr |
| Ongoing maintenance | $500–$2,000/mo = $6,000–$24,000/yr |
| Year 1 total | $45,550–$86,550 |
| Year 2+ ongoing | $37,200–$61,200/yr |
Headless on Shopify Hydrogen + Oxygen
| Line item | Cost |
|---|---|
| Shopify Plus (commerce engine) | $2,300/mo = $27,600/yr |
| Hydrogen frontend build (one-time) | $35,000–$120,000 |
| Oxygen hosting | $0 (included with Plus) |
| Apps (headless-compatible subset) | $300–$1,000/mo = $3,600–$12,000/yr |
| Frontend developer (part-time or full-time) | $3,000–$15,000/mo = $36,000–$180,000/yr |
| Year 1 total | $102,200–$339,600 |
| Year 2+ ongoing | $67,200–$219,600/yr |
Fully composable (commercetools, Algolia, Contentful, Stripe, etc.)
| Line item | Cost |
|---|---|
| commercetools (commerce engine) | $20,000–$75,000/yr |
| Next.js frontend build | $50,000–$200,000 one-time |
| Vercel or Netlify hosting | $240–$3,600/yr |
| Algolia (search) | $500–$5,000/mo = $6,000–$60,000/yr |
| Contentful (CMS) | $300–$2,000/mo = $3,600–$24,000/yr |
| Multiple vendor fees | $20,000–$80,000/yr |
| Frontend developer | $60,000–$200,000/yr |
| Year 1 total | $170,000–$650,000 |
| Year 2+ ongoing | $120,000–$450,000/yr |
For a mid-market DTC brand doing $5M/year, the Shopify Plus traditional setup costs 1–2% of revenue. The Hydrogen headless setup costs 2–7% of revenue. The fully composable setup costs 3–13% of revenue. The gains need to justify the cost gap, which they do at scale and rarely do below $5M.
For the companion view on Shopify Plus specifically, see when NOT to pick Shopify and what a Shopify store really costs per month.
What breaks when you go headless?
The honest list of what gets harder.
The admin disconnect. In a traditional Shopify theme, your merchandising team edits a product in admin and sees the change on the storefront within seconds. In headless, the frontend fetches via API — depending on caching, changes may take 1–30 minutes to appear. Instant admin feedback is gone.
Theme-based apps lose compatibility. Dozens of Shopify apps work by injecting code into the theme (reviews widgets, popup builders, upsell overlays). On a headless frontend, these apps need custom API integration. Some apps don't support headless at all; others require 10–40 hours of integration work.
Checkout customization is still constrained. On Shopify, checkout is the one piece Shopify guards tightly. Headless Hydrogen stores still use Shopify's hosted checkout. Only Shopify Plus with Checkout Extensibility gives real checkout customization — and that's a separate learning curve.
Preview and staging workflows become developer-heavy. A merchandiser making seasonal landing page changes on a traditional theme uses the Online Store editor. On a headless setup, those changes typically require a developer or a well-integrated headless CMS (Contentful, Sanity, Storyblok) with marketer-friendly editing.
SEO complexity. Headless requires server-side rendering (SSR) or static site generation (SSG) to be SEO-friendly. A badly-built headless site renders JavaScript-only and gets poor Google crawling. Shopify Hydrogen handles SSR by default; custom builds don't always.
Deployment overhead. Traditional Shopify changes are instant via admin. Headless changes go through Git, CI/CD, build, deploy — minutes to hours depending on setup. Hotfixes require developer involvement.
Hiring and team ramp. Shopify theme development has a known hiring market. Headless developers are rarer and more expensive. If your frontend developer leaves, replacing them takes 1–3 months vs 2–4 weeks for a Shopify Partner.
Shopify Hydrogen, commercetools, Medusa — which should you pick?
The real options in 2026, honestly compared.
Shopify Hydrogen
The default headless choice for stores already on Shopify. Hydrogen is React-based, deploys to Shopify's Oxygen platform (free with Plus), has first-party support, and benefits from Shopify's checkout and payment infrastructure. The strongest path if your commerce engine will stay Shopify.
Who it fits: Shopify Plus stores wanting headless performance; brands valuing a single-vendor commerce stack; teams with React experience.
commercetools
Enterprise-grade MACH platform with GraphQL APIs, strong B2B features, and multi-regional capabilities. commercetools is the choice for enterprise brands building composable stacks, often replacing Magento or SAP Commerce Cloud.
Who it fits: $20M+ brands; enterprises with complex B2B or multi-market requirements; teams with budget for 6-figure annual platform costs.
Elastic Path
B2B-focused composable commerce platform. Elastic Path targets enterprise B2B where complex pricing, catalogues, and workflows matter.
Who it fits: mid-market and enterprise B2B; brands coming off Magento Commerce; teams willing to invest in a specialized platform.
Medusa
Open-source headless commerce engine. Medusa is a Node.js-based self-hostable alternative to Shopify, free as software, growing community.
Who it fits: developer-heavy teams who want full control; brands with regulatory or data-sovereignty requirements that prevent SaaS; projects with time to invest in open-source.
Saleor
Open-source GraphQL-first commerce platform. Saleor is Python-based, well-architected, and used by brands wanting modern APIs without vendor lock-in.
Who it fits: developer-led teams; brands prioritizing API quality and open-source stewardship.
Custom build on Shopify Storefront API
For stores that want headless flexibility but don't want to commit to a specific framework like Hydrogen. Build a Next.js or Remix frontend that talks to Shopify's Storefront API directly. More work than Hydrogen, but no Hydrogen-specific lock-in.
Who it fits: teams with strong Next.js preference; brands wanting portable frontend code.
The pragmatic 2026 recommendation
For 80% of businesses considering headless, Shopify Hydrogen is the right first choice because:
- Your commerce engine stays Shopify (one vendor, less complexity)
- Hydrogen is first-party, well-supported, and feature-complete
- Oxygen hosting is included with Shopify Plus
- The React ecosystem is familiar to most frontend developers
- Migration back to a traditional theme is easier than from commercetools
Pick commercetools, Elastic Path, Medusa, or Saleor only if your business shape forces it — enterprise B2B complexity, open-source requirements, or specific MACH strategy.
The 5-year lens
Where will headless be in 2031?
The honest prediction. Headless as the universal future didn't happen. The MACH Alliance predicted most mid-market brands would be composable by 2025; the reality is that traditional platforms (Shopify, BigCommerce) added so much flexibility that most brands never needed to go composable. Shopify's checkout extensibility and 2.0 themes closed much of the "headless or stay basic" gap.
Headless remains the right answer for enterprise, multi-channel, performance-critical, and composable-strategy use cases. It's unlikely to replace traditional ecommerce for mid-market in the next 5 years.
For the broader platform landscape view, see best ecommerce platform in 2026.
The 6 scenarios where headless is the wrong choice
Being honest where the vendors won't be.
You're under $2M annual revenue. The complexity rarely pays back below this threshold. Stay on Shopify or BigCommerce with a well-built traditional theme.
You don't have an in-house developer. Headless requires ongoing frontend engineering. Without a developer on team or on retainer, headless becomes an operational burden.
Your marketing team edits pages often. If your business runs on frequent landing page updates, seasonal promotions, and admin-controlled content changes, headless adds developer dependency where you don't want it.
Your frontend requirements are standard DTC. If what you need is a well-themed Shopify Plus store with Judge.me reviews, Klaviyo email, and a decent checkout, headless adds cost and complexity for marginal gain.
Your SEO strategy depends on frequent content updates. Content agility is harder on headless unless you've invested in a headless CMS with good authoring UX.
You're exploring headless because of a vendor pitch. Decisions driven by a Hydrogen launch blog, a MACH alliance deck, or a vendor demo rarely survive the first year of production. The right reasons to go headless are internal (your business shape forces it), not external (someone sold you on it).
The honest conclusion
Headless commerce is a real architecture that solves real problems. It's also been dramatically oversold since 2020, with vendors and agencies pitching it as the inevitable future when it's actually a specialized solution for about 10% of ecommerce businesses.
If your business is in that 10% — enterprise scale, multi-channel, performance-critical, or specifically composable — headless is worth the investment. Start with Shopify Hydrogen unless something specific forces another choice.
If you're in the other 90% — mid-market or smaller, single-channel website-first, standard DTC — a well-built traditional Shopify or BigCommerce theme will deliver 95% of the business result at 25% of the cost and complexity.
If you're unsure which 10/90 bucket you're in, that's exactly what a 90-minute paid Strategy consultation at $249 is for. We review your current stack, your frontend requirements, your team shape, and the real cost math — then tell you honestly whether headless is right. No commission from any headless vendor. If traditional is the right answer, we'll say so.
For related platform decisions, see Shopify vs BigCommerce 2026, when NOT to pick Shopify, and the pillar best ecommerce platform in 2026.
FAQs
What is headless commerce in one sentence? Headless commerce is an architecture where the storefront is built separately from the commerce engine, connected via APIs — giving you frontend flexibility at the cost of more complexity.
What's the difference between headless commerce and composable commerce? Headless describes the architecture (frontend split from backend). Composable describes the strategy (multiple best-in-class vendors). Every composable architecture is headless; not every headless architecture is composable.
When does my business actually need headless commerce? Four scenarios: frontend performance is mission-critical, multi-channel commerce (web + app + kiosk), specific frontend requirements traditional themes can't deliver, or enterprise scale ($5M+ revenue).
What does headless commerce cost compared to Shopify Plus? 2–5× more in Year 1 ($102k–$340k vs $45k–$87k for Hydrogen). 1.5–2× more ongoing. Fully composable can cost $170k–$650k Year 1.
What breaks when you go headless? Admin disconnect, theme-based app compatibility, checkout customization constraints, developer-heavy preview workflows, SEO complexity, deployment overhead, harder developer hiring.
Is Shopify Hydrogen the best headless option in 2026? For stores already on Shopify, yes. For stores considering a full platform replacement, commercetools or Elastic Path for enterprise, Medusa or Saleor for open-source preference.
Can I go headless without rebuilding my whole store? Partially. Hybrid approaches (custom Next.js homepage + Shopify theme for product pages) give 60–70% of the benefit at 30–40% of the cost.
When is headless commerce the wrong choice? Under $2M revenue, no in-house developer, frequent marketing-team edits, standard DTC requirements, SEO-heavy content strategy, or decisions driven by vendor pitches.
About the author
Dharmendra Asimi is the founder of Aapta Solutions, established in 2007 and now serving SMBs and growing brands across India, the United States, the United Kingdom, and the UAE. Over the past twenty years he has shipped WordPress builds, Shopify and WooCommerce stores, managed cloud hosting, and SEO programmes for hundreds of businesses — from single-product boutiques to multi-region brands handling Black Friday peaks.
He is the creator of Aapta GEO (a free 30-second AI-readiness scan) and Aapta SEO AI (a monthly tracker for how ChatGPT, Claude, Perplexity, and Gemini cite your content). His writing on ecommerce platforms, AI-search visibility, and store economics is read by founders, marketing teams, and SEO managers across three time zones.
Areas of expertise: ecommerce architecture across Shopify, WooCommerce, BigCommerce, Wix, Magento, and headless · platform migration · payment gateway integration (Stripe, Razorpay, Checkout.com, Paystack) · technical SEO and Generative Engine Optimization (GEO) · AI-search citation tracking · managed cloud hosting (AWS, GCP, Azure, Cloudflare) · brand strategy and visual identity for commerce brands.
Connect: LinkedIn · X · Instagram · personal site · About · Contact
This article is maintained as part of Aapta's content quality programme. If any data point looks stale or incorrect next time you read this, tell us and we will verify and update within 48 hours.
