The headless commerce market is real: $1.74 billion in 2025, projected $7.16 billion by 2032 (22.4% CAGR). But “headless” has become the “microservices” of e-commerce — a technically sound architecture that gets recommended far more often than it should be.
| Signal | Headless makes sense | Headless is overengineering |
| Revenue scale | >€10M ARR with frontend bottleneck | <€5M ARR with standard needs |
| Dev team | Strong in-house React/Node/Python | No frontend developers |
| Storefronts | 5+ brands/regions from single backend | 1–2 storefronts |
| Checkout needs | Completely custom flow impossible in platform | Standard cart → checkout |
| Channel expansion | Web + app + kiosk + voice simultaneously | Web only for foreseeable future |
| Who asked | Engineering team solving real frontend constraint | Consultant recommended it |
Revenue scale
Yes>€10M ARR with frontend bottleneck
No<€5M ARR with standard needs
Dev team
YesStrong in-house React/Node/Python
NoNo frontend developers
Storefronts
Yes5+ brands/regions from single backend
No1–2 storefronts
Checkout needs
YesCompletely custom flow impossible in platform
NoStandard cart → checkout
Channel expansion
YesWeb + app + kiosk + voice simultaneously
NoWeb only for foreseeable future
Who asked
YesEngineering team solving real frontend constraint
NoConsultant recommended it
The back-migration pattern
A significant portion of headless Shopify projects in 2025–2026 involve migrating back to native Shopify. Not because headless is wrong, but because the organisation could not maintain it long-term, content updates slowed down, and the cost/value gap never closed. The original build was theoretical, not driven by real needs.
Total cost of ownership
Enterprise headless averages $2.6 million (platform, dev, integration, migration). Mid-market implementations run $300K–$800K. The hidden “integration tax” arrives 6–24 months post-launch: API orchestration complexity grows non-linearly with vendor count, marketing team autonomy is lost, and DevOps overhead compounds. Legacy-heavy organisations spend nearly 60% of IT budget on upgrades and maintenance — making the “headless is more expensive” argument moot when you are already drowning in tech debt.
The headless platforms
MeMedusa — the fastest-growing open-source option
Copenhagen-based, MIT licensed, 32,300+ GitHub stars growing at 33.4%/month. The key differentiator: zero GMV fees — pricing is infrastructure-only ($29–$299/month on Medusa Cloud). At scale, this saves tens of thousands monthly versus Saleor Cloud (0.8%+ GMV). Fully modular architecture with 17 built-in commerce modules. Used by Eight Sleep ($1B+ valuation, built in 6 months with a single engineer) and Matt Sleeps (24x revenue growth in 3 years).
SaSaleor — enterprise multi-channel
Polish origin, Python/Django, GraphQL-first with the most mature headless GraphQL schema. Zalando is a strategic investor. Multi-channel is the flagship feature: each channel has independent pricing, stock, currency, payment methods, tax, and shipping. Used by Lush Cosmetics (£690M turnover, 869 shops, 50 countries). But: GMV-based Cloud pricing (0.8%+ on Starter) gets expensive at scale, Python requirement means a separate hiring pool from the React frontend, and GraphQL-only means no REST.
VnVendure — TypeScript-native B2B
German company (Vendure GmbH), self-funded, NestJS architecture. The strictest TypeScript typing end-to-end. Enterprise customers include IBM and Swile. Made a bold pivot in February 2026: closing their €3M/year Elevantiq agency business to go all-in on product. No managed cloud yet (announced but not GA) — use Medusa Cloud or Saleor Cloud if you need managed hosting today.
For Rails teams specifically
SoSolidus — forked from Spree in 2015, maintained by Nebulab (Italian agency). Installed as gems in a standard Rails app. All ActiveRecord, ActiveJob, Rails conventions — zero context switching. Best for: clean, highly-customised DTC or B2B Rails stores. Added reverse charge VAT fields in v4.6 for EU compliance. But: not API-first by design, default frontend is dated ERB templates.
SpSpree — 15,000 GitHub stars, 865 contributors, the largest Rails e-commerce community. Spree 5 (April 2025) was a transformation: headless-native API-first architecture, modern JavaScript admin UI, no-code storefront builder, native multi-vendor marketplace, Price Lists engine for B2B. But: the AGPL-3.0 license change (v4.10+) means all modifications must be open-sourced if distributed — commercial licence from Vendo required for proprietary use.
| Your team | Platform | Why |
| Rails | SoSolidus or SpSpree | All Rails conventions, ActiveRecord, gems. Solidus for MVC; Spree for API-first + marketplace. |
| TypeScript / Node.js | MeMedusa or VnVendure | Medusa for best DX + fastest community. Vendure for B2B complexity + NestJS teams. |
| Python / Django | SaSaleor | Best multi-language + multi-currency. Mature GraphQL. Enterprise-grade (Lush, Breitling). |
| No dev team | Shopify | Managed infrastructure, no hosting decisions, ship in days. Graduate when you hit real limits. |
Rails
PlatformSoSolidus or SpSpree
WhyAll Rails conventions, ActiveRecord, gems. Solidus for MVC; Spree for API-first + marketplace.
TypeScript / Node.js
PlatformMeMedusa or VnVendure
WhyMedusa for best DX + fastest community. Vendure for B2B complexity + NestJS teams.
Python / Django
PlatformSaSaleor
WhyBest multi-language + multi-currency. Mature GraphQL. Enterprise-grade (Lush, Breitling).
No dev team
Platform
Shopify
WhyManaged infrastructure, no hosting decisions, ship in days. Graduate when you hit real limits.