OpenAI's ChatGPT Instant Checkout and Shopify's own agentic commerce fee are reportedly land…
Sylius Storefront Uses Twig Templates: the Decoupled Frontend Path
Yes, Sylius renders its storefront server-side with Twig, the Symfony templating layer, paired with Bootstrap for styling and Symfony UX for interactivity. That ties every visible frontend change to the Sylius release cycle. The built-in API Platform bundle lets you decouple the storefront, but from there the entire frontend build is your own effort unless a dedicated frontend layer sits on top.
What "Sylius uses Twig templates" actually means
Sylius is a full-stack Symfony project. The native storefront is a Twig theme structure: category, product, and checkout pages live as Twig templates inside theme bundles, the visual scaffolding is Bootstrap, and the pockets of interactivity (cart updates, filters, forms) run on Symfony UX with Turbo, Stimulus, and in places Live Components. Changing the theme means overriding Twig files, rebuilding the bundle, and redeploying the Symfony app.
That is a solid, proven setup for a Symfony team. The part most Sylius shops feel only once they grow: frontend and backend are wired to the same deploy cycle. A marketing team that wants a new landing page or a campaign variant needs a Symfony developer and a release slot in the same window as every backend update.
The problem a lot of Sylius teams have right now
Two things collide. First, every Sylius upgrade (say, from 1.x to 2.x) can touch the Twig theme structure, because bundle conventions and template hooks move with it. A backend upgrade quietly turns into a frontend project. Second, marketing teams have no visual editor. Every section change, every A/B test, every new campaign page runs through a developer ticket, because Twig templates are code, not an editable layout.
Sylius itself recognizes this and answers it with the API Platform bundle for teams that want to move off server-side rendering: REST and GraphQL endpoints for products, categories, cart, and checkout. That is the right technical foundation for a decoupled storefront. What API Platform does not ship is a storefront on top of it. Teams that take this step on their own end up rebuilding routing, SEO, caching, checkout UX, and a component library from scratch, usually with a dedicated Next.js or Nuxt project and a dedicated team to run it.
How Laioutr solves this, without replacing Sylius
Laioutr is an official Sylius Technology Partner. That partnership is the basis for the positioning here: Sylius stays your backend, your product catalog, checkout logic, order management, and admin area keep running unchanged. Laioutr becomes the frontend layer on top, connected through the exact API Platform interface Sylius already ships.
Concretely: Laioutr talks to your Sylius REST and GraphQL endpoints directly, with no custom glue code, and delivers PDP, PLP, cart, and checkout components as a ready composable stack. Marketing gets Studio, our visual editor, to build landing pages, campaign variants, and section changes without a developer ticket, directly in the live storefront rather than an isolated preview.
The effect in one sentence: you leave the Twig release train, frontend changes are no longer tied to Sylius minor or major releases, and you gain a visual editor the native Twig storefront never had. A comparable pattern plays out for Headless Frontend for Sylius: A Composable Storefront for the Symfony Open-Source Backend, where the same API Platform connection carries a broader composable rollout.
What you gain
- Time. With the native Twig storefront: Landing-page changes need a dev ticket and a Symfony deploy. With Laioutr on Sylius API Platform: New landing pages and campaign variants in Studio, no dev ticket.
- Money. With the native Twig storefront: Every Sylius upgrade risks becoming a Twig theme project. With Laioutr on Sylius API Platform: Frontend release cycle decoupled from the Sylius upgrade window.
- Quality. With the native Twig storefront: Performance and accessibility depend on the state of the theme. With Laioutr on Sylius API Platform: Core Web Vitals and WCAG-ready components as a platform property.
FAQ
Does Sylius support headless commerce? Yes, through the API Platform bundle Sylius exposes REST and GraphQL endpoints. What is missing is a ready storefront on top of that API, and that is the part Laioutr delivers.
Do we have to replace Sylius to decouple? No. Laioutr is a Sylius Technology Partner and sits as a frontend layer on top of your existing Sylius backend, with no replatforming involved.
How long does the switch typically take? Usually four to six weeks to your first production Sylius storefront on Laioutr, depending on the scope of your API Platform setup and the number of storefront sections.
Next steps
If your Sylius storefront is starting to hit the limits of the Twig theme structure, the next step is a 30-minute demo where we map your API Platform setup against the Laioutr composable stack. Book a Sylius frontend demo.
More from the Laioutr Platform
About the author: Marcel Thiesies is CEO & Co-Founder of Laioutr. He works directly with Sylius teams on separating the storefront from the backend release cadence without giving up their existing Symfony investment.