Photo: free stock photography (Unsplash licence) — see imprint
What headless actually gives you
Headless decouples the storefront from Shopware and talks to it over the Store API. That gives you total freedom over UX, app-like navigation and the ability to serve a website, a mobile app and a kiosk from one commerce backend. It does not, by itself, make anything faster.
What it costs you
You now own a second application: routing, SEO, caching, image handling, checkout state, translations and every admin preview feature that Twig gave you for free. Budget for it honestly — a headless build is typically 1.5–2× the frontend effort of a Twig theme.
The four questions
Do you need more than one channel from the same catalogue? Is your UX genuinely unlike a normal shop? Do you have a frontend team who will still be there in three years? Is the SEO risk of client-side rendering acceptable, or do you need SSR? Two yeses and headless starts to make sense.
The honest middle road
For most B2B shops the answer is a well-built Twig theme with a few Vue islands for the configurator and the cart. You get 90% of the perceived speed for 40% of the cost, and any Shopware developer can maintain it after you.
- Headless buys freedom, not speed.
- Budget 1.5–2× the frontend effort.
- Twig + Vue islands beat headless for most B2B shops.
Frequently asked questions
Not by itself. Headless decouples the storefront from Shopware; it does not make anything render quicker. You can build a fast headless shop and a very slow one, exactly as with Twig. If speed is the goal, measure what is actually slow first — usually images, uncached queries or one bad plugin. None of those get fixed by a rewrite.
Four questions decide it. Do you need more than one channel from the same catalogue? Is your UX genuinely unlike a normal shop? Will you still have a frontend team in three years? And is the SEO risk of client-side rendering acceptable, or do you need SSR? Two clear yeses and it starts to pay off. One or none, and you are buying freedom you will never spend.
Plan for roughly one and a half to two times the frontend effort of a Twig theme, and be honest about why: you now own a second application. Routing, SEO, caching, image handling, checkout state, translations and every admin preview feature Twig gave you for free are yours to build and maintain. The commerce backend is the cheap half of the project.
Yes, and for most B2B shops it is the right answer: a well-built Twig theme with a few Vue islands where the interaction genuinely is app-like — the configurator, the cart, a quick-order form. You get most of the perceived speed for a fraction of the cost, and any Shopware developer can maintain it after we are gone.
We do this for a living — Shopware, Node.js, React, ERP integration and automation for B2B.
Talk to an engineer