Headless commerce
Frontend decoupled from backend, communication via API. When it really makes sense.
Definition
Headless commerce is an ecommerce architecture where the frontend (user interface, mobile app, physical kiosk) is completely separated from the backend (products, orders, cart, checkout). The two layers communicate via REST or GraphQL API.
Monolithic vs headless architecture
| Aspect | Monolithic (standard) | Headless |
|---|---|---|
| Frontend | Platform theme | React, Vue, Next.js, custom |
| Backend | WooCommerce/Shopify/Magento | Same (via API) |
| Time-to-market | 1-6 weeks | 3-6 months |
| Initial cost | €2,000-€10,000 | €20,000-€80,000+ |
| Performance | Good with caching | Exceptional (static) |
| Maintenance | 1 stack | 2 stacks (frontend + backend) |
| Multi-channel | Difficult | Native |
When headless makes sense
Headless commerce is cool but it's also more expensive and complex. It makes sense only when:
- Multi-channel: you sell on the same catalog via web + native mobile app + physical kiosk + smart TV.
- Critical performance: projects with extreme speed SLAs (sub-1s loading time) use prebuilt static frontend.
- Extreme UX customization: frontend must do things no standard theme can (3D configurators, AR product viewers).
- Multi-touchpoint brands: enterprise with native apps, B2B partners with their frontend.
- Large frontend team: makes sense to decouple if you have 5+ dedicated frontend developers.
When it does NOT make sense
- Small/medium ecommerce: under 5,000 products monolithic has hugely better cost/benefit.
- Tight budget: headless costs 5-10x equivalent monolithic.
- Small team: without dedicated frontend team, managing 2 stacks becomes burden.
- Fast time-to-market: WooCommerce monolithic launches in weeks, headless in months.
- SEO / editorial content: WordPress monolithic unmatched for blog + ecommerce in one installation.
Typical headless stacks
- Headless WooCommerce: WooCommerce + GraphQL (WPGraphQL) + Next.js or Nuxt. Good cost/flexibility tradeoff.
- Headless Shopify: Shopify Storefront API + Hydrogen or Next.js. Most widespread DTC mode in EU/USA.
- Headless Magento: Magento + native GraphQL + PWA Studio or custom Vue/React.
- Composable commerce: headless evolution with distributed backend (Commercetools, Stripe payments, Algolia search). Enterprise only.
Our honest opinion
Headless commerce is powerful tech but is often oversold to clients who don't need it. For most projects under €100K budget we recommend monolithic: WooCommerce, Shopify standard, PrestaShop. The cost/benefit ratio is hugely better.
When a client asks us for "headless" out of tech fashion rather than real business need, we honestly advise against it — even at the cost of losing the project.
Related service
For projects where headless effectively makes sense (multi-channel enterprise, critical performance, extreme UX customization), we deliver it. See code programming for custom backend projects and app development for multi-channel.
See also: GEO · server-side tagging · Conversion API · glossary index