E-Commerce·9 MIN READ
Headless Commerce: What It Is and When It Makes Sense
An understandable introduction to headless commerce: advantages, disadvantages, and who this architecture is really worth it for.
By Martin Ogris
Founder & Managing Director·21 December 2025·9 min read
Headless Commerce is one of the most discussed concepts in e-commerce. But behind the buzzword lies a concrete architectural decision: frontend and backend are separated and communicate exclusively via API. What this concretely means, when it makes sense for DACH merchants, and what it truly costs – we address all of this without sugarcoating.
Traditional vs. Headless: The Difference
In a classic shop system – such as a Shopify theme or a WordPress WooCommerce setup – the frontend (what the customer sees) and backend (product data, order logic, admin) are tightly interlinked. This has advantages: faster setup, lower complexity, many immediately usable features. The downside: design freedom and performance eventually hit system-imposed limits.
Headless resolves this coupling. The backend – for example Shopify as the commerce engine – provides all data via a GraphQL or REST API. The frontend, such as a Next.js or Remix project, consumes this data and renders pages completely independently.
Architecture Comparison at a Glance
| Feature | Traditional | Headless | Composable |
|---|---|---|---|
| Frontend/Backend coupling | Tightly connected | Decoupled | Fully modular |
| Design freedom | Template limits | Fully free | Fully free |
| Time-to-market | Fast (weeks) | Slow (months) | Very slow (months+) |
| Initial costs | Low–medium | High (from €20k) | Very high (enterprise) |
| Maintenance effort | Low | High | Very high |
| Multi-channel | Limited | Well suited | Optimal |
| Internal dev team needed | No | Yes | Yes (multiple) |
When Does Headless Really Pay Off?
Headless is not an end in itself. The honest answer: for many DACH merchants an optimized Shopify theme is the better choice. Headless specifically pays off when several of the following criteria apply:
Headless makes sense when …
- Multi-channel strategy: The same product data should serve website, mobile app, kiosk terminals, and B2B portal.
- Performance as competitive advantage: Core Web Vitals are demonstrably conversion-relevant and theme limits have been reached.
- Highly complex UX: Product configurators, 3D previews, individualized catalogs – requirements no theme system can handle.
- B2B portal with custom logic: Customer-specific prices, approval workflows, roles – a separate interface on the same commerce backend.
- Revenue from approx. €2M: Only at this scale is the ROI of the higher initial investment realistically achievable.
- Standard D2C without special requirements: A classic shop without multi-channel typically gains nothing from headless except costs.
- No internal dev team: Without React/Next.js expertise, every change becomes an agency request – these add up.
Shopify Hydrogen & Oxygen
Shopify has developed Hydrogen, a React-based storefront framework built directly on the Shopify Storefront API. The runtime environment is Oxygen – Shopify's edge hosting network included in the Shopify plan, distributing pages globally. The result: load times under 100 ms in the DACH region are realistic.
Hydrogen uses Remix as the routing framework with Server Side Rendering by default – meaning SEO readiness is given from the first line of code. The typical engagement flow:
Discovery & Scope
Requirements analysis, architecture decision, technical scope – fixed price after completion
Live Prototype in the Browser
Clickable prototype instead of static designs – immediate feedback in real browser context
Hydrogen Build
React components, GraphQL integration, CMS connection, checkout extensions
Oxygen Deployment
CI/CD pipeline, edge hosting, global CDN – production-ready on Shopify infrastructure
Discovery & Scope
Requirements analysis, architecture decision, technical scope – fixed price after completion
Live Prototype in the Browser
Clickable prototype instead of static designs – immediate feedback in real browser context
Hydrogen Build
React components, GraphQL integration, CMS connection, checkout extensions
Oxygen Deployment
CI/CD pipeline, edge hosting, global CDN – production-ready on Shopify infrastructure
Headless CMS: Contentful, Sanity, Storyblok
A commerce backend like Shopify manages products, variants, and orders. For editorial content – magazine articles, lookbooks, guide pages, landing pages – a separate headless CMS is needed. The three most important in the DACH mid-market:
CMS Comparison for DACH Merchants
- Contentful: Enterprise-ready, strong ecosystem, structured content modeling. Costs rise noticeably above approx. 25 users – good for large teams.
- Sanity: Flexible schema, real-time collaboration, GROQ query language, transparent pricing. Our standard recommendation for DACH mid-market.
- Storyblok: Visual editor with live preview – particularly suited when marketing teams maintain content without developer support. Easiest editor onboarding.
- When no headless CMS is needed: Pure product catalogs without content marketing work fine with Shopify metafields and pages.
Composable Commerce: The Evolution
Headless separates frontend and backend. Composable Commerce goes one step further: all functions run as interchangeable, independent services. The conceptual framework is called MACH – Microservices, API-first, Cloud-native, Headless.
Commerce Engine
Shopify / commercetools – products, prices, orders, B2B
Headless CMS
Sanity / Contentful / Storyblok – editorial content, translations, media
Search & Discovery
Algolia / Elasticsearch – product search, faceted filters, recommendations
Payments & Checkout
Stripe / Adyen / Shopify Payments – SEPA, EPS, Klarna, credit card
Commerce Engine
Shopify / commercetools – products, prices, orders, B2B
Headless CMS
Sanity / Contentful / Storyblok – editorial content, translations, media
Search & Discovery
Algolia / Elasticsearch – product search, faceted filters, recommendations
Payments & Checkout
Stripe / Adyen / Shopify Payments – SEPA, EPS, Klarna, credit card
MACH is the enterprise standard for those seeking maximum flexibility and vendor independence. For DACH mid-market with revenue under €20M, the pragmatic approach – Shopify Hydrogen + Sanity + Stripe – is typically sufficient and considerably cheaper to operate.
TCO: What Headless Actually Costs
The most common mistake when deciding for headless is looking only at development costs. The true Total Cost of Ownership consists of several components:
| Cost block | Shopify Theme | Headless (Hydrogen) | Composable (MACH) |
|---|---|---|---|
| Initial build | €8k–€25k | from €20k | €80k–€250k+ |
| Hosting/month | included in plan | €0 (Oxygen) to €300 (self-hosted) | €500–€2,000+ |
| CMS costs/month | included | €0–€500 (Sanity/Storyblok) | €500–€3,000 (Contentful Enterprise) |
| Maintenance/month | €140–€500 (retainer) | from €1,700 (retainer) | €3,000–€8,000+ |
| Internal dev team | optional | recommended (1 FE dev) | required (2–4 devs) |
All figures indicative; actual costs depend on scope, integrations, and internal capacities. Discovery clarifies the concrete numbers for your setup.
Conclusion: Who Headless Is Right For
Headless commerce is a powerful architecture – but not a silver bullet. Our team with merchant background (we have operated shops ourselves) advises: evaluate first whether Shopify Plus with a customized theme covers your requirements. If multi-channel, performance obsession, highly complex UX, or a B2B portal on the same commerce backend are the drivers, headless is the right choice.
What we do not do: give performance guarantees or take on GDPR legal advice – that is your lawyer's job. What we do: honest assessment from a merchant perspective, concrete numbers in the discovery phase, and clean technical implementation – whether Shopify Plus, Hydrogen, or classic theme.
Is Headless Right for You?
We analyze your requirements honestly and recommend whether headless, Shopify Hydrogen, or a classic stack delivers more leverage.
Schedule a No-Obligation Call