5.0 stars on OMR Reviews. EU server location. BFSG-ready. In use with DACH OXID partners.
OXID × Laioutr
Headless for OXID, without custom-build engineering
The Frontend Management Platform for OXID eShop. Visual page builder, 70+ e-commerce components including B2B building blocks, EU hosting. Faster to launch than a custom build with Next.js, multi-edition-ready, compatible with account selection, permission sets, and customer-specific assortments.
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
100% Match
What does headless mean for OXID?
Headless for OXID separates the frontend, everything your customers see, from the OXID backend with its products, account selection, permission sets, and ordering processes. Instead of the Flow Theme or Wave, the frontend is connected through the OXID GraphQL StoreFront module and can be designed freely, without Smarty theme limits and with full performance control.
For deeper reading, see our guides on when a headless switch is worth it for OXID, the OXID 6 to 7 upgrade, and what OXID 6 end of life means for your frontend.
1. The backend stays OXID
OXID continues to manage products, account selection, permission sets, customer-specific assortments, VAT workflows, orders, and checkout. You use the OXID admin unchanged, with all the B2B modules of the Enterprise Edition.
2. The frontend is chosen
You have four established options: Flow Theme (default Smarty), Wave Theme (a more modern variant, also not headless), Custom Build (Next.js or Nuxt with OXID GraphQL StoreFront), or a Frontend Management Platform like Laioutr.
3. Data flows via GraphQL in real time
No data duplication, no sync conflicts. Laioutr talks directly to the OXID GraphQL StoreFront API, including all B2B endpoints for account selection, permission sets, and customer-specific assortments.
Benefits
What frontend options do you have for OXID?
OXID has no official headless framework like FastStore or PWA Studio. Instead, you choose between classic themes and a custom build with GraphQL StoreFront. Four options are established in the market. Here's where each one pays off for OXID buyers.
1. Flow Theme (default storefront)
Smarty-based, shipped with OXID by default, not headless. Useful for existing setups that don't want to migrate, or for greenfield projects with minimal customization needs. The performance and modernization limits are real.
2. Wave Theme
A more modern theme variant, also Smarty-based. Useful if you want to replace Flow but aren't ready to go headless yet. Better UI than Flow, but the same architectural limits.
3. Custom Build with OXID GraphQL StoreFront (Next.js, Nuxt, Vue Storefront)
Maximum control, highest effort. A six- to nine-month build phase plus ongoing maintenance with two to three engineers. Useful for enterprise teams with dedicated frontend engineering and highly specific B2B requirements.
4. Laioutr FMP
A Frontend Management Platform with a visual builder, 70+ components including B2B building blocks, EU hosting, and multi-backend support. Useful if you want to go live fast, need standard B2B features out of the box, and need marketing velocity without an engineering sprint per page.
USE CASES
What you build with Laioutr for OXID
Laioutr is built for OXID setups that want to leave their Smarty theme limits behind, without starting a six- to nine-month custom build with their own Next.js team. From an account-specific B2B portal to a multi-brand storefront.
B2B portals with account selection, permission sets, and customer-specific assortments
OXID B2B delivers the complete workflows. Laioutr calls the GraphQL StoreFront API directly and renders account-specific frontends with permission logic, customer-specific price lists, and individual assortments.
Modernizing Flow Theme or Wave Theme
An existing Smarty theme stack is to be replaced, without touching the OXID backend. Migration in phases, without the existing performance suffering.
Multi-brand storefronts on a single OXID instance
Multiple brands on a single OXID EE instance, with their own frontends, their own domains, a shared backend, and a shared B2B configuration.
Internationalization setups with localized B2B workflows
OXID multi-country with localized price lists, VAT workflows, and language variants. The frontend is configured in Studio, without setting up a custom build per market.
Replacing a custom build with OXID GraphQL StoreFront
You have a custom build with Next.js and OXID GraphQL StoreFront running, and the engineering team has been thinned out. Migration to an FMP, without touching the OXID backend.
Greenfield storefronts on new OXID projects
New OXID project, clean slate. With Laioutr themes and the UI library, you go live in weeks instead of investing six months in a custom build with OXID GraphQL StoreFront.
Laioutr vs. Custom Build (Next.js with OXID GraphQL StoreFront)
The honest composable comparison
A custom build is the most common path to headless OXID: the official GraphQL StoreFront module plus your own frontend in Next.js, Nuxt, or Vue Storefront. Laioutr is a complete Frontend Management Platform with a visual builder, component library, and multi-backend support. Both work with OXID. If you want maximum code control and a dedicated frontend team, a custom build is the most flexible option. If you want marketing velocity, B2B components, and predictable TCO, you'll be more productive with Laioutr.
Compare differences | Laioutr FMP | Custom Build (Next.js + OXID GraphQL StoreFront) |
|---|---|---|
Builder und Komponenten Was Sie aus der Box bekommen, mit Fokus auf B2B und DACH-Mittelstand. | ||
Visueller Page Builder Drag-and-Drop-Editor für Marketing- und Content-Teams. | Inklusive (Studio) Live-Preview, komponentenbasiert | Nicht enthalten Reine Code-Entwicklung in Next.js |
B2B-Komponenten Vorgefertigte UI-Bausteine für Account-Selection, Permission-Sets, kundenspezifische Sortimente. | 70+ Komponenten B2B-Bausteine inkl. Permission-UI | Selbst bauen B2B-UI als Custom-Build pro Workflow |
Themes und Vorlagen Startpunkt für neue Storefronts ohne Greenfield-Aufwand. | Vorgefertigte Themes Sofort einsatzbereit, voll erweiterbar | Greenfield Storefront komplett selbst designen |
Hosting Wo das Frontend ausgeliefert wird und wer es betreibt. | Inklusive (EU-CDN) Laioutr Cloud, kein separater Deploy | Selbst hosten Vercel, AWS, Hetzner, eigene Infrastruktur |
Architektur und OXID-Integration Wie das Frontend das OXID-Backend nutzt und wie viel Eigenleistung nötig ist. | ||
Backend-Flexibilität Welche E-Commerce-Backends sich anbinden lassen. | Multi-Backend OXID, Shopware, commercetools, weitere | OXID-spezifisch Code ist auf OXID-Schema zugeschnitten |
OXID-API-Anbindung Wie das Frontend mit dem OXID-Backend kommuniziert. | GraphQL StoreFront Standard-Anbindung über offizielles Modul | GraphQL StoreFront Standard-Anbindung über offizielles Modul |
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 |
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 Next.js, GraphQL, OXID-Schema |
Time-to-Launch Realistische Zeitspanne bis zum Live-Gang einer neuen Storefront. | Wochen Mit Themes und Komponenten | Monate 6 bis 9 Monate Build-Phase |
Ideales Team-Setup Wer mit der Plattform arbeiten kann und wer arbeiten muss. | Cross-funktional Marketing, Design und Dev gemeinsam | Engineering-only Next.js-Team mit OXID-Erfahrung |
Total Cost of Ownership Software plus Engineering plus Wartung über 3 bis 5 Jahre. | SaaS (planbar) Hosting und Komponenten inklusive Preise ansehen | Engineering-lastig Hohe Build- und Wartungs-Kosten |
All data is based on publicly available information, insights from sales conversations with DACH e-commerce brands, and our own platform testing. As of: April 2026. OXID features may have evolved since.
OXID
When a custom build is the right choice
You have a dedicated Next.js or Nuxt team with OXID API experience (at least three engineers), you accept six- to nine-month build phases, maximum pixel-level differentiation is strategically important, highly specific B2B workflows can't be mapped with standard components, and years of engineering maintenance are budgeted for. Classic use case: an industrial goods manufacturer with a complex configurator and a dedicated frontend team.
LAIOUTR
When Laioutr is the right choice
You want weeks instead of months to go-live, marketing should build pages on its own, standard B2B features should be available out of the box, you don't have a dedicated frontend engineering team, total cost of ownership over 5 years is relevant, and BFSG compliance must be solved without a separate audit. Classic use case: a DACH mid-market B2B brand on OXID that wants to modernize without building a frontend engineering team.
You don't have to do this alone. Our OXID implementation partners have delivered OXID frontend projects with Laioutr, from Flow Theme migrations to custom-build replacements.
FAQ