5.0 stars on OMR Reviews. Server location EU. BFSG-ready. In use by Symfony teams that want to launch faster.
Feel free to reach out to one of our partners for your e-commerce frontend built on Laioutr.
5/5
OMR Reviews
70+
E-commerce components
Lighthouse 100
Performance from day 1
Made in EU
GDPR-compliant, servers in Germany
What does headless mean for Sylius?
Headless for Sylius separates the frontend — everything your customers see — from the Sylius backend with products, channels, orders, and checkout. The frontend connects via the Sylius API Platform (REST and GraphQL) and can be designed freely, without Twig theme limits and with full performance control.
1. The backend stays Sylius
Sylius continues to manage products, channels, customer hierarchies, orders, taxes, and checkout. You use the Symfony-based admin interface unchanged, with all the familiar workflows and plugin extensions.
2. The frontend is chosen
You have four options: keep the Twig storefront, custom build (Next.js or Nuxt), Vue Storefront with Sylius integration, or a Frontend Management Platform like Laioutr. Each option has pros and cons.
3. Data flows via the API Platform in real time
No data duplication, no sync conflicts. Laioutr talks directly to the Sylius API Platform (REST and GraphQL), including multi-channel, customer-group, and Sylius Plus support.
Benefits
What frontend options do you have for Sylius?
Unlike Shopify or commercetools, Sylius has no official headless frontend product. That puts the frontend question on the table for every composable Sylius project. Four options are established in the market.
1. Twig storefront (default)
The storefront shipped with Sylius, Symfony-based with Twig templates and Bootstrap. Solid for standard setups, but the performance ceiling and theme limitations become noticeable beyond a certain size. Sensible for small shops or as a transitional solution.
2. Custom build (Next.js or Nuxt)
Maximum control, maximum effort. A six- to twelve-month build phase, ongoing maintenance by an internal Symfony and React or Vue team. It makes sense if frontend engineering is your strategic core competency.
3. Vue Storefront with Sylius integration
An open-source PWA frontend with a community-maintained Sylius connection. An active community, but no official Sylius product and no direct enterprise support network. It makes sense if you have a Vue team and open source is strategically important.
4. Laioutr DXP
A Frontend Management Platform with a visual builder, 70+ components, EU hosting, and multi-backend support. Fastest time-to-launch, lowest learning curve, backend optionality for the future. It makes sense if you want to go live fast, without a custom-build investment.
USE CASES
What you build with Laioutr for Sylius
Laioutr is designed for Sylius setups that need to change fast and scale globally. From the multi-channel storefront for brand portfolios to the B2B configurator frontend with Sylius Plus.
Multi-channel storefronts on a single Sylius backend
Multiple Sylius channels (brands, markets, sales channels) on a single instance with independent frontends, their own domains, their own brand identity. One component pool, multiple brand presences.
B2B portals with Sylius Plus customer hierarchies
Sylius Plus provides customer hierarchies, customer pools, loyalty programs. Laioutr calls the Sylius API directly and renders customer-group-specific prices, assortments, approval workflows.
Configurator-driven PDPs
Industrial goods, customization workflows, B2B specifications. Complex state-management logic is solved at the Laioutr component level, while Sylius API calls stay cleanly separated.
International storefronts with dedicated channels per market
One Sylius instance, many channels. Languages, currencies, layouts, and assortments can be controlled per channel, compatible with the Sylius channels concept.
Replatforming from Twig to headless without touching the backend
An existing Sylius stack to be renewed on the frontend side, without touching the backend configuration. Migration in phases, with a clear rollback plan.
Greenfield storefronts on new Sylius projects
A new Sylius project, a fresh start. With Laioutr themes and the UI library, this goes into production in weeks, instead of investing months in a custom build.
Laioutr vs. custom build for Sylius
The honest comparison
Sylius has no official headless frontend product. The most common frontend decision is therefore: custom build in Next.js or Nuxt, or a Frontend Management Platform like Laioutr. A custom build gives maximum control, but costs a six- to twelve-month build phase and ongoing maintenance. Laioutr delivers Studio, 70+ components, and hosting in the plan, with full code extensibility for edge cases. Both work with Sylius Community and Plus.
Compare differences | Laioutr DXP | Custom Build (Next.js / Nuxt) |
|---|---|---|
Builder und Komponenten Was Sie aus der Box bekommen und was Sie selbst aufbauen müssen. | ||
Visueller Page Builder Drag-and-Drop-Editor für Marketing- und Content-Teams. | Inklusive (Studio) Live-Preview, komponentenbasiert | Nicht enthalten Eigenbau oder externes CMS |
E-Commerce-Komponenten Vorgefertigte UI-Bausteine für Storefronts, Produkt- und Landingpages. | 70+ Komponenten Design-Token-basiert, anpassbar | Selbst aufbauen Komplette UI-Bibliothek selbst entwickeln |
Themes und Vorlagen Startpunkt für neue Storefronts ohne Greenfield-Aufwand. | Vorgefertigte Themes Sofort einsatzbereit, voll erweiterbar | Greenfield Designsystem komplett selbst aufbauen |
Hosting Wo das Frontend ausgeliefert wird und wer es betreibt. | Inklusive (EU-CDN) Laioutr Cloud, kein separater Deploy | Selbst hosten Vercel, AWS, eigene Infrastruktur |
Architektur und Compliance Wie flexibel die Plattform ist und was Sie regulatorisch mitbekommen. | ||
Backend-Flexibilität Welche E-Commerce-Backends sich anbinden lassen. | Multi-Backend Sylius, Shopware, commercetools, Shopify | Backend-spezifisch Code an Sylius API gebunden, Wechsel teuer |
Performance und Core Web Vitals Wie viel Aufwand für Lighthouse-100-Niveau nötig ist. | Out of the box Lighthouse 100 als Default-Ziel | Manuelles Tuning Performance-Engineering durch Team |
BFSG und WCAG 3.0 Konformität mit Barrierefreiheitsstärkungsgesetz und WCAG 3.0. | Im Standard WCAG 3.0, BFSG, EN 301 549 | Eigenverantwortung Audit separat erforderlich |
Datenschutz und Serverstandort Wo Daten verarbeitet werden und welche EU-Verträge gelten. | EU und Deutschland EU-Standardvertrag, deutschsprachiger Support | Hosting-abhängig Je nachdem, wo Sie deployen |
Team und Wirtschaftlichkeit Wer mit der Plattform produktiv ist und was es Sie über die Zeit kostet. | ||
Lernkurve Wie schnell ein neues Teammitglied produktiv wird. | Niedrig Marketing onboardet in Tagen | Hoch React/Vue plus Symfony plus Sylius-API |
Time-to-Launch Realistische Zeitspanne bis zum Live-Gang einer neuen Storefront. | Wochen Mit Themes und UI-Bibliothek | Monate Sechs- bis zwölfmonatige Build-Phase |
Ideales Team-Setup Wer mit der Plattform arbeiten kann und wer arbeiten muss. | Cross-funktional Marketing, Design und Dev gemeinsam | Engineering-only Drei plus React- oder Vue-Engineers |
Preismodell Wie sich Kosten zusammensetzen, Software plus Betrieb plus Entwicklung. | SaaS (planbar) Transparente Pläne, Hosting inklusive Preise ansehen | Engineering-Kosten Build plus dauerhafte Wartung |
All data is based on publicly available information, experience from sales conversations with DACH e-commerce brands, and our own platform testing. As of April 2026. Sylius features may have evolved since.
SYLIUS
When a custom build is the right choice
You have a dedicated React or Vue team with Symfony and Sylius experience, at least three engineers. You're building exactly one Sylius storefront with extremely specialized requirements. Frontend engineering is your strategic core competency. Classic use case: a DTC brand with its own engineering team and a demand for pixel-level control.
LAIOUTR
When Laioutr is the right choice
You want weeks instead of months to go-live, marketing should build pages independently, you serve multiple Sylius channels or brands, you want to keep your backend optionality open, and BFSG as well as WCAG 3.0 must be handled without a separate audit. Classic use case: a mid-market or enterprise Sylius shop that wants to scale without a double-digit engineering investment.
You don't have to do this alone. Our certified composable partners have delivered commercetools frontend projects with Laioutr, from greenfield setups to Frontastic migrations.
FAQ