What "headless" means in 2026
A headless commerce stack separates the storefront (Next.js, Astro, mobile app) from the commerce engine (Shopify, Medusa, Commerce Layer, BigCommerce). Everything in between is APIs. The point is freedom — to change the storefront without rebuilding the backend, and vice versa.
The default 2026 reference stack
- Storefront: Next.js 15 with React Server Components, deployed on Vercel or self-hosted on Node.
- Commerce engine: Shopify Plus or open-source Medusa for full control.
- CMS: Sanity, Storyblok or Payload — APIs everywhere.
- Search: Algolia or Meilisearch with semantic embeddings.
- Payments: Stripe + a local processor for the markets that need it.
- Analytics: Plausible or PostHog (privacy-first), plus your own warehouse.
Why brands are switching
- Page speed. A static Next.js storefront easily beats a themed monolith on Core Web Vitals — and Google ranks accordingly.
- Reuse across channels. The same APIs power your iOS app, your in-store kiosk and your B2B portal.
- Vendor independence. Swap your CMS or search provider without touching the storefront.
Where headless hurts
- Initial cost. A headless build is 2-4x more expensive up front than a Shopify theme.
- Ops surface. You now have four vendors and a custom storefront to keep alive.
- Editor experience. Out-of-the-box theme editors are nicer than most CMS preview flows.
When a monolith still wins
If you are doing under roughly $1M GMV per year, are happy with theme-level customisation, and do not have a dev team — stay on a managed monolith. The economics do not flip until you have either real scale or real customisation needs.
API integration: the part nobody warns you about
The hardest part of a headless project is rarely the storefront. It is the dozen integrations behind it — ERP, 3PL, tax, address validation, fraud, loyalty. Plan for this upfront with a tiny integration layer in your stack (often a small Node.js service or an MCP server) so each vendor only talks to that.
We build headless commerce stacks and own the integration layer end-to-end. See our API integration services.