Unlock limitless creativity and commerce performance with Laioutr
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 OroCommerce?
Headless for OroCommerce separates the frontend, everything your customers see, from the OroCommerce backend with catalogs, price lists, corporate accounts, RFQs, orders, and checkout. The frontend connects via the OroCommerce Storefront REST API (JSON:API) and can be designed freely, without the limits of the Twig storefront and with full performance control.
1. The backend stays OroCommerce
OroCommerce continues to manage catalogs, price lists, corporate accounts, RFQs, orders, taxes, and checkout, including the built-in OroCRM. You use the back-office interface and the familiar business tools unchanged, with all your established B2B workflows and extensions.
2. The frontend is chosen
You've got four options: keep the Twig/Symfony storefront, use a community/partner headless frontend with an Oro connection, go custom (Next.js or Nuxt), or use a Frontend Management Platform like Laioutr. Each option comes with its own pros and cons.
3. Data flows in real time via the Storefront API
No duplicated data, no sync conflicts. Laioutr talks directly to the OroCommerce Storefront REST API (JSON:API), including corporate account, price list, and RFQ support.
Benefits
What frontend options do you have for OroCommerce?
OroCommerce is traditionally a server-side-rendered Symfony storefront and ships a strong headless layer with a JSON:API-compliant Storefront REST API, but no ready-made headless frontend product that non-developers can operate. That puts the frontend question on the table for every headless Oro project. Four options are established in the market.
1. Twig/Symfony storefront (default)
The server-side storefront that ships with OroCommerce, built on Symfony and Twig. Solid and deeply integrated with the B2B features, but the performance ceiling and theme limitations become noticeable past a certain scale. A sensible choice for classic B2B setups or as a transitional solution.
2. Community/partner headless frontend with Oro integration
Headless frontends built by the community or partners that decouple via the Storefront API. Flexible, but not an official headless product from Oro, with uneven levels of support. Sensible if you have an implementation partner with the right expertise.
3. Custom Build (Next.js or Nuxt)
Maximum control, highest effort. A six- to twelve-month build phase, ongoing maintenance by an in-house PHP and React or Vue team that orchestrates the Oro Storefront API itself. Sensible if 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 OroCommerce
Laioutr is built for OroCommerce setups that need to change fast and scale globally. From a B2B self-service portal with corporate accounts and RFQs to a configurator-driven manufacturer frontend.
B2B self-service portals with corporate accounts and RFQs
OroCommerce is B2B-first: corporate accounts, company hierarchies, RFQ workflows, customer-group-specific price lists. Laioutr calls the Storefront API directly and renders these B2B features into high-performance, on-brand components.
Multi-website storefronts on a single OroCommerce backend
Multiple websites (brands, markets, sales channels) on a single Oro instance, each with its own frontend, its own domain, its own brand identity. One component pool, many brand experiences.
Configurator-driven PDPs for manufacturers and distributors
Industrial goods, customization workflows, B2B specifications. Complex state-management logic is solved at the Laioutr component level, while Storefront API calls stay cleanly separated.
International storefronts with a dedicated website per market
One OroCommerce instance, many websites. Languages, currencies, layouts, and assortments can be controlled per website, compatible with Oro's multi-website concept.
Replatforming from the Twig storefront to headless without touching the backend
An existing OroCommerce stack that needs a frontend refresh without touching the backend configuration or the B2B logic. Migration in phases, with a clear rollback plan.
Greenfield storefronts on new OroCommerce projects
A new OroCommerce 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 OroCommerce
The honest comparison
OroCommerce is traditionally a server-side-rendered Symfony storefront and ships a strong headless layer with a JSON:API-compliant Storefront REST API, but no ready-made frontend product for non-developers. So the most common frontend decision for a modern, decoupled storefront is: custom build in Next.js or Nuxt, or a Frontend Management Platform like Laioutr. A custom build gives you maximum control but costs a six- to twelve-month build phase plus ongoing maintenance. Laioutr delivers Studio, 70+ components, and hosting in the plan, with full code extensibility for edge cases. Both work with OroCommerce B2B and B2C.
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 OroCommerce, commercetools, Shopware, Shopify | Backend-spezifisch Code an OroCommerce Storefront API 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 PHP/Symfony plus OroCommerce Storefront 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, insights from sales conversations with DACH e-commerce brands, and our own platform testing. As of: June 2026. OroCommerce features may have evolved since.
OroCommerce
When a custom build is the right choice
You have a dedicated React or Vue team with PHP and OroCommerce experience, at least three engineers. You're building exactly one OroCommerce storefront with extremely specialized requirements. Frontend engineering is your strategic core competency. Classic use case: a manufacturer with its own engineering team and a pixel-level-control ambition.
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 run several OroCommerce websites or brands, you want to keep backend optionality open, and BFSG as well as WCAG 3.0 need to be handled without a separate audit. Classic use case: a mid-market or enterprise B2B manufacturer on OroCommerce that wants to scale without a double-digit engineering investment.
You don't have to do this alone. Our certified composable partners have delivered OroCommerce frontend projects with Laioutr, from greenfield setups to Twig migrations.
FAQ