There is one decision in almost every commerce replatforming that gets postponed until it is too lat…
Custom build vs. Laioutr for OXID, which frontend for which team?
If you want to run OXID headless, two realistic paths are on the table: a custom build with Next.js, Nuxt, or Vue Storefront and the OXID GraphQL StoreFront module, or a Frontend Management Platform like Laioutr.
Both work with OXID. Both use the official GraphQL StoreFront module. Both are real headless. But they are built for different team setups, and that is why the decision is a strategic one, not a technical one.
This post looks at the two options along six dimensions.
What custom build means in the OXID context
Custom build with OXID GraphQL StoreFront means: the official headless module from OXID plus a dedicated frontend, built in Next.js, Nuxt, or Vue Storefront. Code-first, maximum flexibility, own hosting, own performance tuning.
Custom build is the tool for engineering teams that want maximum code control and bring a dedicated frontend team.
What Laioutr is
Laioutr is a Frontend Management Platform, a complete platform with visual page builder (Studio), 70+ pre-built e-commerce components including B2B building blocks, themes, app integrations, and EU hosting.
Laioutr is a tool for cross-functional teams in which marketing, design, and engineering work on the storefront together.
Six comparison dimensions
1. Who can work with it?
Custom build requires Next.js or Nuxt knowledge plus OXID API understanding. Marketing teams are out of the loop, every page change is a code commit. Laioutr targets marketing and design teams as well as engineering, with a visual builder for non-technical users.
2. B2B components
Custom build delivers no ready component library, B2B-specific UIs (permission sets, account selection flows, customer-specific catalogs) must be built yourself. Laioutr ships these as standard components.
3. OXID API connection
Both use the OXID GraphQL StoreFront module, here the architecture point is identical. The difference lies in how the API responses are rendered into the frontend.
4. Time to launch
Custom build needs 6 to 9 months build phase plus performance tuning. Laioutr is live in 6 to 12 weeks, with themes and components.
5. Performance and compliance
Custom build can reach Lighthouse 100, but only with dedicated performance engineering. BFSG and WCAG 3.0 are your responsibility. Laioutr components are out of the box compliant.
6. Total cost of ownership over 5 years
Custom build is free in software (the GraphQL StoreFront module is part of OXID), but the engineering investment is significant (six- to nine-month build phase plus permanent maintenance with two to three engineers). Laioutr is SaaS, hosting and components included. TCO calculation: typically 30 to 50 percent below custom build over 5 years. The full comparison is in the comparison table on the hub page.
Which team fits which solution?
Custom build is the right choice if …
- You have a dedicated Next.js or Nuxt team with OXID experience (at least three engineers)
- Maximum pixel-level differentiation is strategically important
- Highly specific B2B workflows can't be covered by standard components
- Budget for six- to nine-month build phase plus engineering maintenance over years is available
- Marketing teams primarily work via tickets, not directly in the frontend
Classic use case: an industrial goods manufacturer with a complex configurator and a dedicated frontend team.
Laioutr is the right choice if …
- You don't have or want to build a dedicated frontend engineering team
- Marketing should build pages independently, without engineering sprints
- You need B2B components without a sprint per workflow
- You need weeks instead of months to go live
- Total cost of ownership over 5 years is relevant
- 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.
When does a switch from custom build to Laioutr pay off?
We typically see the switch in two constellations:
First: when the frontend team that set up the custom build is thinned out or leaves the company. Maintenance gets expensive, updates stagnate, standstill threatens.
Second: when marketing should become strategically more independent. With custom build, every marketing page is an engineering sprint, with an FMP a configuration.
Conclusion: team setup is the strategy question
The custom-build vs. Laioutr question is a strategy question. Anyone with a mature frontend engineering team and pixel-level requirements should pick custom build. Anyone wanting marketing velocity, B2B components, and predictable TCO is better off with an FMP, more predictable and more affordable.
If you are unsure, we will run the comparison live on your OXID setup, including a 5-year TCO calculation.