Photo: free stock photography (Unsplash licence) — see imprint
What it saves you
The unglamorous 60% of a headless build: URL resolution, CMS page rendering, cart and checkout state, customer session, i18n. Rebuilding that yourself is three months you will not get back and will not enjoy.
What it costs you
You adopt someone else's structure and upgrade cycle. When your requirement does not fit the shape, you are patching a framework instead of writing your feature. Read its assumptions before you commit, not after.
SEO is still your problem
Composable does not mean crawlable. Server-side rendering, canonical URLs, structured data and the redirect map from your old shop are all still work you must do. A beautiful client-rendered storefront with no rankings is an expensive brochure.
Who it is genuinely for
Teams with a real frontend competence who need custom UX across several channels. If your shop is one channel and your team is two Shopware developers, a Twig theme will make you happier and richer.
- Frontends saves the boring 60% of headless.
- You inherit its structure and its upgrade cycle.
- Composable is not automatically crawlable.
We do this for a living — Shopware, Node.js, React, ERP integration and automation for B2B.
Talk to an engineer