---
title: "Headless Frontend for OXID eShop, no custom build | Laioutr"
canonical_url: "https://www.laioutr.com/en/headless-frontend-for-oxid"
locale: en
meta:
  description: "Headless frontend for OXID eShop via the GraphQL API: visual page builder, 70+ components, B2B-ready. Faster to launch than a custom Next.js build."
  "og:description": "Headless frontend for OXID eShop via the GraphQL API: visual page builder, 70+ components, B2B-ready. Faster to launch than a custom Next.js build."
  "og:title": "Headless Frontend for OXID eShop, no custom build | Laioutr"
---

OXID × Laioutr

# Headless frontend for OXID, without custom-build engineering

The frontend management platform for OXID eShop: visual page builder, integrated headless CMS and 70+ e-commerce components, with EU hosting as an add-on. Faster to launch than a custom build with Next.js, for all OXID editions, with B2B requirements connected on a project basis.

5.0 stars on OMR Reviews. EU hosting available. BFSG-ready. Used with OXID partners in the DACH region.

[Request a demo](https://www.laioutr.com/en/contact)

![Headless frontend for OXID with Laioutr](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:2048/auto_image/cmk19p2eask1h07mlr6q5kx0k)

Partners from the Laioutr network implement e-commerce frontends based on Laioutr.

[![Fatchip](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:360/auto_image/cmix5spfkb8hx07lgcg3vk1r8)](https://www.bestit.de/ "Best it")

![Foun10](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:360/auto_image/cmnxbhihz3m4r06labx2pt1fm)

5/5

OMR Reviews

70+

E-commerce components

Lighthouse 100

Performance from day 1

Made in EU

GDPR-compliant by design, EU hosting available

## What does a headless frontend for OXID mean?

A headless frontend for OXID separates the storefront, everything customers see, from the OXID backend with products, customer groups, B2B logic and ordering processes. Instead of Flow or Wave, the frontend connects via the OXID GraphQL API and can be designed freely, without theme limits and with full control over performance.

Further reading: articles on [when a headless switch is worth it for OXID](https://www.laioutr.com/en/blog/oxid-headless-when-is-the-switch-worth-it), the [OXID 6 to 7 upgrade](https://www.laioutr.com/en/blog/oxid-6-to-7-upgrade-decouple-frontend-without-replatforming) and [what OXID 6 end of life means for the frontend](https://www.laioutr.com/en/blog/oxid-6-end-of-life-frontend-implications-2026).

[Book a strategy call](https://www.laioutr.com/en/contact)

### 1. The backend stays OXID

OXID continues to manage products, customer groups, customer-specific assortments, tax logic, orders and checkout. The OXID admin stays unchanged, including the B2B modules of the Enterprise Edition.

### 2. The frontend is chosen

Four options are established: the Flow theme (default), the Wave theme (a more modern variant, also not headless), a custom build with Next.js or Nuxt on the OXID GraphQL API, or a frontend management platform like Laioutr.

### 3. Data flows via GraphQL in real time

No second data store and no sync conflicts: Laioutr reads products, categories, search and the basket directly via the OXID GraphQL API. B2B features such as customer-specific assortments and approvals are connected in the project via Orchestr.

OPTIONS

## Which frontend options are there for OXID?

OXID has no official headless framework like PWA Studio for Magento. The choice is between classic themes, a custom build on the GraphQL API and a frontend management platform. Four options are established in the market. Here is when each one pays off.

[Book a strategy call](https://www.laioutr.com/en/contact)

### 1. Flow Theme (default storefront)

Smarty-based, shipped with OXID by default, not headless. A good fit for existing setups without a migration plan or for projects with minimal customization needs. The limits on performance and modernization are real.

### 2. Wave Theme

A more modern theme variant, also Smarty-based. A good fit for replacing Flow without going headless yet. A better interface than Flow, but the same architectural limits.

### 3. Custom build on the OXID GraphQL API (Next.js, Nuxt, Alokai)

Maximum control, highest effort. A six- to nine-month build phase plus ongoing maintenance with two to three engineers. A good fit for enterprise teams with their own frontend engineering and highly specific B2B requirements.

### 4. Laioutr

A frontend management platform with a visual builder, 70+ components, an integrated headless CMS and multi-backend support, with EU hosting as an add-on. A good fit for a fast go-live, marketing velocity without an engineering sprint per page, and B2B requirements connected on a project basis.

USE CASES

## What teams build with Laioutr for OXID

Laioutr is designed for OXID setups that want to leave the limits of classic themes behind without starting a months-long custom build with an in-house Next.js team: from customer-specific B2B portals to multi-brand storefronts.

[Book a strategy call](https://www.laioutr.com/en/contact)

### B2B portals with customer-specific assortments and approvals

The B2B workflows stay in OXID. Laioutr connects them in the project via Orchestr and renders customer-specific prices, assortments and permissions in dedicated components.

### 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 on the OXID GraphQL API

A custom build with Next.js on the OXID GraphQL API is running and the engineering team has shrunk. Move to a frontend management platform without touching the OXID backend.

### Greenfield storefronts on new OXID projects

A new OXID project, a fresh start. With Blueprints and the component library, the storefront is productive within weeks instead of months of custom development.

Laioutr vs. custom build with the OXID GraphQL API

## Laioutr and a custom build on OXID compared

A custom build is the most common route to headless with OXID: the OXID GraphQL API plus an in-house frontend in Next.js, Nuxt or Alokai. Laioutr is a complete frontend management platform with a visual builder, a component library, an integrated headless CMS and multi-backend support. Both work with OXID. A custom build offers maximum code control with an in-house frontend team; Laioutr offers marketing velocity and predictable total costs.

Pricing Plans Comparison

| Compare differences | Laioutr | Eigenbau (Next.js + OXID GraphQL API) |
| --- | --- | --- |
| Laioutr Eigenbau (Next.js + OXID GraphQL API) |
| Builder und Komponenten Was ab Werk enthalten ist, 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 B2B-Storefronts. | 70+ Komponenten B2B-Bausteine, B2B-Logik projektspezifisch angebunden | Selbst bauen B2B-UI als Custom-Build pro Workflow |
| Blueprints und Vorlagen Startpunkt für neue Storefronts ohne Greenfield-Aufwand. | Blueprints Sofort einsatzbereit, voll erweiterbar | Greenfield Storefront komplett selbst designen |
| Hosting Wo das Frontend ausgeliefert wird und wer es betreibt. | Als Add-on (Laioutr Cloud) Edge Hosting, nicht in der Lizenz enthalten | 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 API Standard-Anbindung über offizielles Modul | GraphQL API 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 welche Kosten über die Zeit entstehen. |
| 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 Blueprints 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) Komponenten inklusive, Hosting als Add-on](https://www.laioutr.com/pricing) [Preise ansehen](https://www.laioutr.com/pricing) | 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

An in-house Next.js or Nuxt team with OXID API experience (at least three engineers) is in place, six- to nine-month build phases are acceptable, pixel-level differentiation is strategically important, highly specific B2B workflows cannot be covered by standard components, and engineering maintenance is budgeted for years. Typical case: an industrial goods manufacturer with a complex configurator and its own frontend team.

LAIOUTR

### When Laioutr is the right choice

Go-live in weeks instead of months, marketing builds pages independently, standard B2B functions are connected on a project basis, there is no in-house frontend engineering team, total cost of ownership over five years matters, and BFSG compliance should be covered without a separate audit. Typical case: a mid-sized B2B brand in the DACH region on OXID that wants to modernize without building a frontend engineering team.

![Blueprint preview of a storefront in Laioutr](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:800/auto_image/cmkcncldp1l5b07mku0vzlxyc)

BLUEPRINTS

## Start with a Blueprint instead of from scratch

Blueprints are pre-composed frontends for each industry, ready to customize and combinable with OXID as the data source. A suitable starting point shortens the path to go-live.

[View Blueprints](https://www.laioutr.com/en/blueprints)

UI PREVIEW

## Page types for an OXID frontend with Laioutr

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

[View shop demos](https://www.laioutr.com/en/shop-demos)

![UI Demo](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:2048/auto_image/cml81bh8z7qjk07lczs1xft6f)

OXID implementation partners deliver frontend projects with Laioutr, from replacing the Flow theme to replacing a custom build.

[![Fatchip](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:360/auto_image/cmix5spfkb8hx07lgcg3vk1r8)](https://www.bestit.de/ "Best it")

![Foun10](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:360/auto_image/cmnxbhihz3m4r06labx2pt1fm)

FAQ

## FAQ on headless frontends for OXID

Does Laioutr work with OXID Community, Professional, and Enterprise Edition?

Yes. Laioutr uses the OXID GraphQL API, which is compatible with all three editions. B2B features such as account selection and permission sets are part of the Enterprise Edition and are connected in the project.

How does Laioutr differ from a custom build on the OXID GraphQL API?

A custom build with Next.js or Nuxt is code-first and needs an in-house frontend team plus a build phase of several months. Laioutr is a ready-made frontend platform with a visual builder, 70+ components and an integrated headless CMS, with hosting available as an add-on. That means a faster go-live, a gentler learning curve and a marketing team that works independently.

Can we use OXID B2B features like account selection and permission sets?

Yes, on a project basis. OXID EE B2B features such as account selection, permission sets, customer-specific assortments and price lists stay in the OXID backend; they are connected in the project via Orchestr and rendered in Laioutr components.

How does Laioutr relate to OXID modules from the OXID Marketplace?

OXID modules that provide backend functionality remain usable. Modules with frontend components (Smarty templates) are not carried over one-to-one with Laioutr; they need to be rebuilt as components in Studio or integrated via custom components.

Does Laioutr work with German ERPs like SAP, abas, Microsoft Dynamics?

Yes. ERP integration runs through OXID backend connectors, leaving the frontend untouched. Integration with third-party tools via the Laioutr App Store for marketing workflows (email, CRM, analytics) is standard.

Can we keep using our existing OXID analytics and tracking setups?

Yes. Analytics tags (Google Analytics, etracker, Matomo) are integrated via JavaScript, exactly as with any other frontend solution. GDPR-compliant setups via cookie management tools (Usercentrics, OneTrust) work as usual.

How long does a migration from Flow Theme or Wave Theme take?

A pilot is usually live within 14 days, and guided migrations to Laioutr take a median of under 14 days. Complex B2B workflows or setups across several editions take correspondingly longer. Founder-guided migration is standard, not an extra charge.

What does Laioutr cost compared to a custom build plus engineering?

A custom build on the OXID GraphQL API carries no license cost (the module is part of OXID), but the engineering investment is substantial: a six- to nine-month build phase plus ongoing maintenance with two to three engineers. Laioutr is SaaS with transparent plans; Studio and components are included, and hosting is available as an add-on. Total cost of ownership is typically 30 to 50 percent lower than a custom build.

Can we later move away from the OXID backend without rebuilding the frontend?

Yes. This is precisely one of the key advantages over a custom build. Laioutr is backend-agnostic: switching from OXID to Shopware, Adobe Commerce, or another backend means reconfiguring an API connection, not rebuilding the frontend.

Is the solution BFSG- and GDPR-compliant?

Yes. GDPR-compliant by design, EU hosting available (further regions on request), regional data residency possible, German-speaking support. WCAG 3.0 and the BFSG (German Accessibility Strengthening Act, mandatory since 2025) are built into the component standard. Exactly what mid-sized OXID buyers in the DACH region need.

Is Laioutr an OXID Solution Partner?

Yes, Laioutr is an official OXID partner.

Can OXID eShop run headless?

Yes. OXID eShop provides the necessary data via the GraphQL API, and Laioutr delivers the decoupled frontend on top. The backend stays OXID, while the frontend becomes headless and fast, without a custom build.

What does the move from OXID 6 to OXID 7 mean for the frontend?

The version jump increases the pressure to modernize the frontend. A decoupled Laioutr frontend separates this decision from the backend: the storefront is modernized independently and is ready for OXID 7, without a complete theme rebuild.

Does Laioutr use the OXID GraphQL Storefront API?

Yes. Laioutr talks to the OXID GraphQL Storefront API through the Orchestr layer and normalizes products, categories, prices and cart into one frontend data model, so the storefront components stay backend-agnostic.

Does a headless OXID frontend also work for B2B with tiered pricing and quotes?

Yes. The B2B logic with tiered prices, customer-specific prices and quote requests stays in the OXID backend. The standard connector includes tiered prices; account, approval and quick-order flows are connected in the project via Orchestr and rendered in Laioutr components.

## OXID insights

[All insights](https://www.laioutr.com/en/blogs/insights)

[![Hero owned b en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmradj7binsvg08mssb1pcx07)<h3>OXID eSales for B2B Wholesalers: A Modern Frontend, No Backend Swap</h3>B2B wholesalers running on OXID eSales can modernize their frontend layer, add tiered pricing, RFQ f…](https://www.laioutr.com/en/blog/oxid-b2b-wholesale-frontend-modernization-2026)

[![Hero current c en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmr928nrgwffk07mmf9bebpvx)<h3>The 2026 Headless Market: Four Enterprise Strategies, and Where the Frontend Layer Actually Decides</h3>CX Today published a rundown this week of "the four enterprise strategies reshaping CX software…](https://www.laioutr.com/en/blog/2026-headless-market-four-enterprise-strategies-frontend-layer)

[![Hero owned a en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmr4q2tb6th1407mjab9f1z6i)<h3>The 30-Minute Storefront Is the Easy Part. The 3-Year Storefront Is the Work</h3>This week was, once again, about speed. On July 2, Salesforce made Storefront Next generally availab…](https://www.laioutr.com/en/blog/frontend-management-vs-generation-lifecycle-fmp-2026)

[![Hero owned a en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmr0dujjmtypo07l62fgybls6)<h3>Composable Readiness Check: When Does Composable Actually Pay Off?</h3>The composable commerce conversation has shifted. Anyone who followed K5 2026 knows the tone: less e…](https://www.laioutr.com/en/blog/composable-readiness-check-dach-mid-market-2026)

[![Hero current c en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmquo2p6v0s2k06mnu5suveu7)<h3>Frontend Independence Becomes a Buying Criterion (Week 26 Wrap)</h3>This week, three moves in the commerce stack overlapped, and they all touch the same question: who a…](https://www.laioutr.com/en/blog/frontend-independence-buying-criterion-2026-wrap)

[![Hero owned b en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmquo22ig0sqp06l96ipbsupd)<h3>OXID 6 End-of-Life: What the Calendar Means for Your Frontend</h3>OXID 6 is no longer a current product, it's a winding-down version. In the official OXID eSales …](https://www.laioutr.com/en/blog/oxid-6-end-of-life-frontend-implications-2026)

[![Hero owned a en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmqrtmslgnvjg07ms8s7dg6l1)<h3>The Composable Stack in the DACH Mid-Market: What Actually Ships After K5</h3>K5 in Berlin is over, and the field agrees on one thing: composable commerce has arrived in the mid-…](https://www.laioutr.com/en/blog/composable-commerce-dach-mid-market-experience-layer-2026)

[![Hero current c en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmqp2oj9hzwkv06mg86pb5l1w)<h3>Spree BBQ 2026: What DACH Mid-Market Is Actually Discussing</h3>Tonight at 18:00, Dock 10 Berlin. The Spree BBQ 2026 kicks off, and Laioutr is there as co-sponsor. …](https://www.laioutr.com/en/blog/spree-bbq-2026-frontend-stack-dach-live)

[![Hero owned a en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmqp2oag803dv06mmrk55ogzi)<h3>How to Evaluate a Frontend Management Platform: 2026 Checklist</h3>The frontend management platform (FMP) market is consolidating fast. What was an open field with a h…](https://www.laioutr.com/en/blog/frontend-management-platform-evaluation-checklist-2026)

[![Hero tech en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmqknln8ymdod07mgl44dbrn6)<h3>MCP Commerce: How an Autonomous Agent Actually Acts on Your Storefront</h3>Next week in Berlin, the K5 Future Retail Conference brings together thousands of retail decision-ma…](https://www.laioutr.com/en/blog/mcp-endpoints-storefront-agent-actions-2026)

[![Hero business en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmqgd9e85i7yp06mn2pa5cfiq)<h3>Frontend Management Platform: a category of its own</h3>Why the autonomous stack makes the experience layer a category of its ownHere is my take: as backend…](https://www.laioutr.com/en/blog/frontend-management-platform-experience-layer-category-2026)

[![Hero en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmqdiyhgjcrea06mm83qaayhp)<h3>The Future of E-Commerce: Why Adaptation Falls Short and Evolution Starts in the Frontend</h3>At the eCommerce BBQ 2026, one line captured the mood of the whole evening: yesterday we did what wa…](https://www.laioutr.com/en/blog/future-of-ecommerce-evolution-frontend)

[![Hero business en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmqanc46xwzxi06mhvf3bdubn)<h3>Replatform the Backend or the Frontend First? A Sequencing Guide for Mid-Market 2026</h3>The one decision that shapes your entire replatforming projectYou know your commerce stack needs mod…](https://www.laioutr.com/en/blog/replatforming-sequencing-backend-or-frontend-first-2026)

[![Hero tech en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmqanc0i9xe2n07mnub4jcp27)<h3>Adobe Commerce Frontend 2026: Edge Delivery Services or Frontend Management Platform - Which Layer for What?</h3>Over the course of 2024 and 2025, Adobe has positioned two clearly distinct paths for Adobe Commerce…](https://www.laioutr.com/en/blog/adobe-commerce-edge-delivery-services-vs-fmp-2026)

[![Hero multichannel en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmq58p0nfqorz06mdcaoavmpj)<h3>Click & Collect and Store Availability: the Unified Commerce Frontend</h3>Click & Collect is no longer a differentiator. It is a baseline expectation. When a shopper open…](https://www.laioutr.com/en/blog/unified-commerce-click-collect-filialverfuegbarkeit)

READ MORE

## More on headless frontends with Laioutr

### Composable Headless Frontend

The concept behind decoupled storefronts: one frontend for any backend.

[More on composable headless frontends](https://www.laioutr.com/en/composable-headless-frontend)

### E-commerce systems

Which shop systems Laioutr connects as a frontend and how the connection works.

[More on e-commerce systems](https://www.laioutr.com/en/system/e-commerce)

### Composability & orchestration

How Orchestr connects backends and unifies data for the frontend.

[More on orchestration](https://www.laioutr.com/en/product/composability-orchestration)

### Headless frontend for Shopware

Laioutr as the frontend for Shopware 6, connected via the Storefront API and Admin API.

[More on Shopware](https://www.laioutr.com/en/headless-frontend-for-shopware)

### Headless frontend for JTL

Laioutr as the frontend for JTL-Wawi, connected via the JTL Platform API.

[More on JTL](https://www.laioutr.com/en/headless-frontend-for-jtl)

### Multi-brand & multi-market

Manage multiple brands, markets and languages on one platform.

[More on multi-brand & multi-market](https://www.laioutr.com/en/product/multi-brand-multi-market)

![CTA banner showcase hygraph bg desktop@2x](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:2048/auto_image/cmk2dpuehud7w07lbyidrc27g)

![Contact support image](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmqov61tdulqq07mph9phmvrk)

STILL UNSURE?

## Take an OXID frontend live in weeks instead of months?

30 minutes with the Laioutr team: Laioutr live on the actual OXID setup, with answers on migration, B2B features, the GraphQL connection and pricing.

[Request a demo](https://www.laioutr.com/en/contact)

## Structured Data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://www.laioutr.com/#identity",
      "name": "Laioutr",
      "legalName": "Laioutr GmbH",
      "url": "https://www.laioutr.com/",
      "logo": {
        "@type": "ImageObject",
        "url": "https://www.laioutr.com/laioutr-logo.png",
        "width": 400,
        "height": 400
      },
      "email": "info@laioutr.com",
      "telephone": "+49 30 75435715",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "Münchweilersteig 5",
        "postalCode": "12559",
        "addressLocality": "Berlin",
        "addressCountry": "DE"
      },
      "vatID": "DE450905846",
      "sameAs": [
        "https://www.linkedin.com/company/laioutr",
        "https://www.youtube.com/@Laioutr",
        "https://x.com/laioutr"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://www.laioutr.com/en/#website",
      "url": "https://www.laioutr.com/en/",
      "name": "Laioutr",
      "inLanguage": "en",
      "publisher": {
        "@id": "https://www.laioutr.com/#identity"
      }
    },
    {
      "@type": [
        "WebPage",
        "FAQPage"
      ],
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#webpage",
      "url": "https://www.laioutr.com/en/headless-frontend-for-oxid",
      "name": "Headless Frontend for OXID eShop, no custom build | Laioutr",
      "description": "Headless frontend for OXID eShop via the GraphQL API: visual page builder, 70+ components, B2B-ready. Faster to launch than a custom Next.js build.",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://www.laioutr.com/en/#website"
      },
      "breadcrumb": {
        "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#breadcrumb"
      },
      "primaryImageOfPage": {
        "@type": "ImageObject",
        "url": "https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmk19p2eask1h07mlr6q5kx0k"
      },
      "mainEntity": [
        {
          "@type": "Question",
          "name": "Does Laioutr work with OXID Community, Professional, and Enterprise Edition?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. Laioutr uses the OXID GraphQL API, which is compatible with all three editions. B2B features such as account selection and permission sets are part of the Enterprise Edition and are connected in the project."
          }
        },
        {
          "@type": "Question",
          "name": "How does Laioutr differ from a custom build on the OXID GraphQL API?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "A custom build with Next.js or Nuxt is code-first and needs an in-house frontend team plus a build phase of several months. Laioutr is a ready-made frontend platform with a visual builder, 70+ components and an integrated headless CMS, with hosting available as an add-on. That means a faster go-live, a gentler learning curve and a marketing team that works independently."
          }
        },
        {
          "@type": "Question",
          "name": "Can we use OXID B2B features like account selection and permission sets?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes, on a project basis. OXID EE B2B features such as account selection, permission sets, customer-specific assortments and price lists stay in the OXID backend; they are connected in the project via Orchestr and rendered in Laioutr components."
          }
        },
        {
          "@type": "Question",
          "name": "How does Laioutr relate to OXID modules from the OXID Marketplace?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "OXID modules that provide backend functionality remain usable. Modules with frontend components (Smarty templates) are not carried over one-to-one with Laioutr; they need to be rebuilt as components in Studio or integrated via custom components."
          }
        },
        {
          "@type": "Question",
          "name": "Does Laioutr work with German ERPs like SAP, abas, Microsoft Dynamics?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. ERP integration runs through OXID backend connectors, leaving the frontend untouched. Integration with third-party tools via the Laioutr App Store for marketing workflows (email, CRM, analytics) is standard."
          }
        },
        {
          "@type": "Question",
          "name": "Can we keep using our existing OXID analytics and tracking setups?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. Analytics tags (Google Analytics, etracker, Matomo) are integrated via JavaScript, exactly as with any other frontend solution. GDPR-compliant setups via cookie management tools (Usercentrics, OneTrust) work as usual."
          }
        },
        {
          "@type": "Question",
          "name": "How long does a migration from Flow Theme or Wave Theme take?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "A pilot is usually live within 14 days, and guided migrations to Laioutr take a median of under 14 days. Complex B2B workflows or setups across several editions take correspondingly longer. Founder-guided migration is standard, not an extra charge."
          }
        },
        {
          "@type": "Question",
          "name": "What does Laioutr cost compared to a custom build plus engineering?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "A custom build on the OXID GraphQL API carries no license cost (the module is part of OXID), but the engineering investment is substantial: a six- to nine-month build phase plus ongoing maintenance with two to three engineers. Laioutr is SaaS with transparent plans; Studio and components are included, and hosting is available as an add-on. Total cost of ownership is typically 30 to 50 percent lower than a custom build."
          }
        },
        {
          "@type": "Question",
          "name": "Can we later move away from the OXID backend without rebuilding the frontend?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. This is precisely one of the key advantages over a custom build. Laioutr is backend-agnostic: switching from OXID to Shopware, Adobe Commerce, or another backend means reconfiguring an API connection, not rebuilding the frontend."
          }
        },
        {
          "@type": "Question",
          "name": "Is the solution BFSG- and GDPR-compliant?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. GDPR-compliant by design, EU hosting available (further regions on request), regional data residency possible, German-speaking support. WCAG 3.0 and the BFSG (German Accessibility Strengthening Act, mandatory since 2025) are built into the component standard. Exactly what mid-sized OXID buyers in the DACH region need."
          }
        },
        {
          "@type": "Question",
          "name": "Is Laioutr an OXID Solution Partner?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes, Laioutr is an official OXID partner."
          }
        },
        {
          "@type": "Question",
          "name": "Can OXID eShop run headless?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. OXID eShop provides the necessary data via the GraphQL API, and Laioutr delivers the decoupled frontend on top. The backend stays OXID, while the frontend becomes headless and fast, without a custom build."
          }
        },
        {
          "@type": "Question",
          "name": "What does the move from OXID 6 to OXID 7 mean for the frontend?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "The version jump increases the pressure to modernize the frontend. A decoupled Laioutr frontend separates this decision from the backend: the storefront is modernized independently and is ready for OXID 7, without a complete theme rebuild."
          }
        },
        {
          "@type": "Question",
          "name": "Does Laioutr use the OXID GraphQL Storefront API?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. Laioutr talks to the OXID GraphQL Storefront API through the Orchestr layer and normalizes products, categories, prices and cart into one frontend data model, so the storefront components stay backend-agnostic."
          }
        },
        {
          "@type": "Question",
          "name": "Does a headless OXID frontend also work for B2B with tiered pricing and quotes?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. The B2B logic with tiered prices, customer-specific prices and quote requests stays in the OXID backend. The standard connector includes tiered prices; account, approval and quick-order flows are connected in the project via Orchestr and rendered in Laioutr components."
          }
        }
      ]
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Laioutr",
          "item": "https://www.laioutr.com/en/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Headless Frontend for OXID eShop, no custom build"
        }
      ]
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#webpage",
      "description": "Headless frontend for OXID eShop via the GraphQL API: visual page builder, 70+ components, B2B-ready. Faster to launch than a custom Next.js build.",
      "name": "Headless Frontend for OXID eShop, no custom build | Laioutr",
      "url": "https://www.laioutr.com/en/headless-frontend-for-oxid",
      "@type": [
        "WebPage",
        "FAQPage"
      ],
      "mainEntity": [
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/1"
        },
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/2"
        },
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/3"
        },
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/4"
        },
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/5"
        },
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/6"
        },
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/7"
        },
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/8"
        },
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/9"
        },
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/10"
        },
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/11"
        },
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/12"
        },
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/13"
        },
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/14"
        },
        {
          "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/15"
        }
      ]
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/1",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Does Laioutr work with OXID Community, Professional, and Enterprise Edition?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes. Laioutr uses the OXID GraphQL API, which is compatible with all three editions. B2B features such as account selection and permission sets are part of the Enterprise Edition and are connected in the project.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/2",
      "@type": "Question",
      "inLanguage": "en",
      "name": "How does Laioutr differ from a custom build on the OXID GraphQL API?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>A custom build with Next.js or Nuxt is code-first and needs an in-house frontend team plus a build phase of several months. Laioutr is a ready-made frontend platform with a visual builder, 70+ components and an integrated headless CMS, with hosting available as an add-on. That means a faster go-live, a gentler learning curve and a marketing team that works independently.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/3",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Can we use OXID B2B features like account selection and permission sets?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes, on a project basis. OXID EE B2B features such as account selection, permission sets, customer-specific assortments and price lists stay in the OXID backend; they are connected in the project via Orchestr and rendered in Laioutr components.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/4",
      "@type": "Question",
      "inLanguage": "en",
      "name": "How does Laioutr relate to OXID modules from the OXID Marketplace?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>OXID modules that provide backend functionality remain usable. Modules with frontend components (Smarty templates) are not carried over one-to-one with Laioutr; they need to be rebuilt as components in Studio or integrated via custom components.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/5",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Does Laioutr work with German ERPs like SAP, abas, Microsoft Dynamics?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes. ERP integration runs through OXID backend connectors, leaving the frontend untouched. Integration with third-party tools via the Laioutr App Store for marketing workflows (email, CRM, analytics) is standard.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/6",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Can we keep using our existing OXID analytics and tracking setups?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes. Analytics tags (Google Analytics, etracker, Matomo) are integrated via JavaScript, exactly as with any other frontend solution. GDPR-compliant setups via cookie management tools (Usercentrics, OneTrust) work as usual.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/7",
      "@type": "Question",
      "inLanguage": "en",
      "name": "How long does a migration from Flow Theme or Wave Theme take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>A pilot is usually live within 14 days, and guided migrations to Laioutr take a median of under 14 days. Complex B2B workflows or setups across several editions take correspondingly longer. Founder-guided migration is standard, not an extra charge.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/8",
      "@type": "Question",
      "inLanguage": "en",
      "name": "What does Laioutr cost compared to a custom build plus engineering?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>A custom build on the OXID GraphQL API carries no license cost (the module is part of OXID), but the engineering investment is substantial: a six- to nine-month build phase plus ongoing maintenance with two to three engineers. Laioutr is SaaS with transparent plans; Studio and components are included, and hosting is available as an add-on. Total cost of ownership is typically 30 to 50 percent lower than a custom build.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/9",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Can we later move away from the OXID backend without rebuilding the frontend?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes. This is precisely one of the key advantages over a custom build. Laioutr is backend-agnostic: switching from OXID to Shopware, Adobe Commerce, or another backend means reconfiguring an API connection, not rebuilding the frontend.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/10",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Is the solution BFSG- and GDPR-compliant?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes. GDPR-compliant by design, EU hosting available (further regions on request), regional data residency possible, German-speaking support. WCAG 3.0 and the BFSG (German Accessibility Strengthening Act, mandatory since 2025) are built into the component standard. Exactly what mid-sized OXID buyers in the DACH region need.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/11",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Is Laioutr an OXID Solution Partner?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes, Laioutr is an official OXID partner.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/12",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Can OXID eShop run headless?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes. OXID eShop provides the necessary data via the GraphQL API, and Laioutr delivers the decoupled frontend on top. The backend stays OXID, while the frontend becomes headless and fast, without a custom build.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/13",
      "@type": "Question",
      "inLanguage": "en",
      "name": "What does the move from OXID 6 to OXID 7 mean for the frontend?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>The version jump increases the pressure to modernize the frontend. A decoupled Laioutr frontend separates this decision from the backend: the storefront is modernized independently and is ready for OXID 7, without a complete theme rebuild.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/14",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Does Laioutr use the OXID GraphQL Storefront API?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes. Laioutr talks to the OXID GraphQL Storefront API through the Orchestr layer and normalizes products, categories, prices and cart into one frontend data model, so the storefront components stay backend-agnostic.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/headless-frontend-for-oxid#/schema/question/15",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Does a headless OXID frontend also work for B2B with tiered pricing and quotes?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes. The B2B logic with tiered prices, customer-specific prices and quote requests stays in the OXID backend. The standard connector includes tiered prices; account, approval and quick-order flows are connected in the project via Orchestr and rendered in Laioutr components.</p>"
      }
    }
  ]
}
```
