Vendure x Laioutr

Headless for Vendure, without the custom-build effort

Built for Growth, Designed for Scale

Unlock limitless creativity and commerce performance with Laioutr

App vendure

Feel free to reach out to one of our partners for your e-commerce frontend built on Laioutr.

Best it
5/5

OMR Reviews

70+

E-commerce components

Lighthouse 100

Performance from day 1

Made in EU

GDPR-compliant, servers in Germany

100% Match

What does headless mean for Vendure?

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.

1. The backend stays Vendure

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.

2. The frontend is chosen

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.

3. Data flows in real time via the Shop API (GraphQL)

No duplicated data, no sync conflicts. Laioutr talks directly to the Vendure Shop API (GraphQL), including support for multi-channel, customer groups, and B2B.

Benefits

What frontend options do you have for Vendure?

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.

1. Storefront starter (Remix / React)

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.

2. Community storefront with a Vendure connection

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.

3. Custom Build (Next.js or Nuxt)

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.

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 can build with Laioutr for Vendure

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.

Multi-channel storefronts on one Vendure backend

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.

B2B portals with Vendure customer groups

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.

Configurator-driven PDPs

Industrial goods, customization workflows, B2B specifications. Complex state-management logic is solved at the Laioutr component level, while Shop API calls stay cleanly separated.

International storefronts with dedicated channels per market

One Vendure instance, many channels. Languages, currencies, layouts, and assortments can be controlled per channel, compatible with the Vendure channels concept.

Replatforming to headless without touching the backend

An existing Vendure frontend needs an overhaul without touching the backend configuration. Migration in phases, with a clear rollback plan.

Greenfield storefronts on new Vendure projects

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.

Laioutr vs. custom build for Vendure

The honest comparison

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.

Pricing Plans Comparison
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.

VENDURE

When a custom build is the right choice

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.

LAIOUTR

When Laioutr is the right choice

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.

get started fast - build
BLUEPRINTS

Start with a Blueprint instead of from scratch

Discover our Blueprints: pre-composed frontends for your industry, ready to customize on the spot and, when in doubt, a match for your Vendure setup too. Pick a starting point and go live faster.

UI PREVIEW

What you can build with Laioutr for Vendure

Product launch pages, home pages, product detail pages, product list pages, sales pages, blogs, content pages, and more.

UI Demo

You don't have to do this alone. Our certified composable partners have delivered Vendure frontend projects with Laioutr, from greenfield setups to storefront-starter migrations.

Bit Expert
FAQ

Frequently asked questions about headless for Vendure

Yes. Laioutr uses the Vendure Shop API (GraphQL), which is available for both B2C and B2B scenarios. B2B features such as customer groups, group-specific prices, and approval workflows (via plugins) are also supported, provided the corresponding API operations are available.

A custom build typically costs a six- to twelve-month engineering investment plus ongoing maintenance by an internal React or Vue team. Laioutr delivers Studio, 70+ components, and hosting in the plan. Time-to-launch drops from months to weeks, and the total cost of ownership is typically well below.

The storefront starter is a code example to build on yourself: you develop the design system, components, and page logic and maintain them across ongoing upgrade cycles. Laioutr delivers a visual builder, ready-made components, themes, and EU hosting in the plan, so marketing and content teams become productive too, without building up a frontend engineering team.

Laioutr connects via the official Vendure Shop API (GraphQL). We support the standard operations for product search, cart, checkout, and account management, plus project-specific queries and mutations for custom logic.

Yes. Vendure channels are treated as standalone storefronts in Laioutr. Layouts, assortments, languages, and currencies can be configured separately per channel.

Yes. Vendure B2B features (customer groups, group-specific prices, plugin-based workflows) are exposed via the Shop API and rendered in Laioutr components. Specific B2B workflows can be extended with custom components.

Precisely because Vendure is headless-first, the frontend question stays open: Vendure delivers the GraphQL logic and starters, not the finished frontend that non-developers can operate. Laioutr builds on top of this clean API layer and makes the frontend something marketing, design, and dev can operate together, without you running the starter or a custom build yourself.

For a mid-sized setup with clear branding and no exotic custom logic: 8 to 14 weeks from kickoff to go-live. With multi-channel or complex B2B setups, correspondingly more.

We work with transparent SaaS plans based on traffic and required features. The total cost of ownership is typically below a custom build, because hosting, components, and editor are included in the license and no separate frontend engineering team is needed.

Yes. Laioutr is backend-agnostic. Moving from Vendure to Shopify, Shopware, commercetools, or another backend means reconfiguring an API connection, not rebuilding the frontend.

Yes. Server location EU/Germany, EU standard contractual clauses, German-language support, WCAG 3.0, and BFSG (the German Accessibility Reinforcement Act, binding since 2025) are covered as standard. Compliance is built in, not bolted on.

Backend plugins (inventory, pricing, promotions, shipping) stay unchanged. Frontend-oriented features (pop-ups, reviews, personalization) are typically replaced by Laioutr components or pre-integrated apps from our App Store. We review your plugin stack in the migration audit.