What is headless commerce and when it is worth it for your store
Headless means decoupling the frontend from the backend. A simple explanation of what it is, what you gain, and when it is NOT worth the complexity.
"Headless" is everywhere in e-commerce discussions but rarely explained in merchant terms. Let's clear it up without jargon: what it is, what you actually gain, and — just as important — when it's not worth it.
What headless means, briefly
A classic store (PrestaShop, Magento, WooCommerce) is a "monolith": the same application handles both the business logic (products, prices, orders) and how the site looks. "Headless" means you separate the two: the backend (Sylius/Symfony) handles data and rules and exposes them through an API, while the frontend (Next.js) is a separate, fast application that consumes that API and renders the store.
"Head" = the visible part (frontend). "Headless" = the backend stays, but the frontend is free, decoupled.
What you actually gain
- Speed — the Next.js frontend serves static/pre-rendered pages, near-instant. That means green Core Web Vitals and better conversions, especially on mobile.
- Design flexibility — you're not limited by a platform theme; you build exactly the experience you want.
- Scalability — frontend and backend scale independently; large catalogs and peak traffic are easier to handle.
- Independence — you own the (open-source) stack, with no platform lock-in and no transaction fees.
- Omnichannel — the same backend can power the site, an app, a kiosk or a marketplace.
Why Sylius + Next.js
Sylius is a mature open-source e-commerce core built on Symfony (PHP) — API-first by design, ideal as the store's "brain". Next.js is the de facto standard for fast frontends, with static/ISR rendering and excellent SEO. Together they give a store you fully own, fast and extensible. That's how we build headless stores.
When headless is NOT worth it
Honestly: headless adds complexity. It's not worth it if:
- You have a small catalog and modest sales, and a SaaS platform covers your needs painlessly.
- You don't have budget for custom development and technical maintenance.
- You have no real customization, performance or integration needs the current platform can't meet.
Headless pays off when you outgrow the platform: large catalog, growing traffic, poor mobile speed, complex B2B needs or rising SaaS costs.
How to tell if it's time
Clear signals: red mobile Core Web Vitals, a slow admin on a large catalog, fees/subscriptions that grow with sales, or customization needs you "just can't do on the current platform". If you tick a few, it's worth a conversation. Start with a free speed test to see where you stand today.