Unlock limitless creativity and commerce performance with Laioutr
OMR Reviews
E-commerce components
Performance from day 1
GDPR-compliant, servers in Germany
Vendure is headless from the ground up: the TypeScript backend, with products, channels, orders, and checkout, is already decoupled from the frontend and accessed via the Vendure Shop API (GraphQL). Here, headless means you build the frontend, everything your customers see, freely on top of the GraphQL layer, without being tied to a predefined storefront stack and with full performance control.
Vendure continues to manage products, channels, customer groups, orders, taxes, and checkout. You use the Vendure dashboard, the plugin architecture, and the familiar business tools unchanged, with all your established workflows and extensions.
You have four options: adopt a storefront starter, a community storefront with a Vendure connection, a custom build (Next.js or Nuxt), or a Frontend Management Platform like Laioutr. Each option has its pros and cons.
No duplicated data, no sync conflicts. Laioutr talks directly to the Vendure Shop API (GraphQL), including support for multi-channel, customer groups, and B2B.
Vendure is headless-first and ships storefront starters and a documented Shop API (GraphQL) as building blocks, but not a finished frontend product that non-developers can operate. That puts the frontend question on the table for every Vendure project. Four options are established in the market.
The storefront examples and starters provided by Vendure, typically Remix- or React-based. An ideal starting point for learning and for proofs of concept, but as a production storefront you develop the design system, components, and page logic yourself. A good fit for small shops or as a transitional solution.
Open-source frontend frameworks with a community-maintained Vendure connection. An active community, but no official Vendure product and no direct enterprise support net. A good fit if you have a suitable frontend team and open source matters strategically to you.
Maximum control, highest effort. A six- to twelve-month build phase and permanent maintenance by an in-house Node and React or Vue team that orchestrates the Shop GraphQL API itself. A good fit when frontend engineering is your strategic core competency.
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.
Laioutr is built for Vendure setups that need to change fast and scale globally. From a multi-channel storefront for brand portfolios to a B2B configurator frontend with complex assortments.
Multiple Vendure channels (brands, markets, sales channels) on a single instance with standalone frontends, their own domains, and their own brand identity. One pool of components, many brand experiences.
Vendure delivers customer groups, group-specific prices, and B2B workflows via plugins. Laioutr calls the Shop API directly and renders customer-group-specific prices, assortments, and approval processes.
Industrial goods, customization workflows, B2B specifications. Complex state-management logic is solved at the Laioutr component level, while Shop API calls stay cleanly separated.
One Vendure instance, many channels. Languages, currencies, layouts, and assortments can be controlled per channel, compatible with the Vendure channels concept.
An existing Vendure frontend needs an overhaul without touching the backend configuration. Migration in phases, with a clear rollback plan.
A new Vendure project, a fresh start. With Laioutr themes and the UI library, you go live in weeks instead of investing months in a custom build.
Vendure is a headless-first framework and delivers a Shop API (GraphQL) and storefront starters, but not a finished frontend product for non-developers. The most common frontend decision therefore comes down to: a 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 permanent maintenance. Laioutr delivers Studio, 70+ components, and hosting in the plan, with full code extensibility for edge cases. Both work with Vendure B2C and B2B.
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 Vendure, commercetools, Shopware, Shopify | Backend-spezifisch Code an Vendure Shop API (GraphQL) 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 Node/NestJS plus Vendure GraphQL 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.
You have a dedicated React or Vue team with Node and Vendure experience, at least three engineers. You're building exactly one Vendure 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.
You want weeks instead of months to go-live, you want marketing to build pages on its own, you serve multiple Vendure channels or brands, you want to keep backend optionality open, and BFSG and WCAG 3.0 must be handled without a separate audit. Classic use case: a mid-market or enterprise Vendure shop that wants to scale without a double-digit engineering investment.