Give your Vue and Saleor team a visual editor, 70+ e-commerce components, and EU hosting, and go live in weeks instead of months.
OMR Reviews
E-commerce components
Performance from day 1
GDPR-compliant, servers in Germany
Saleor is headless and API-first from the ground up: the Python/Django backend with products, channels, orders, and checkout is already decoupled from the frontend and is addressed exclusively through the Saleor GraphQL API. Headless here 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.
Saleor continues to manage products, channels, warehouses, price lists, orders, taxes, and checkout. You use the Saleor dashboard and the familiar business tools unchanged, with all your established workflows, apps, and webhooks.
You've got four options: adopt the Saleor storefront example, use a community storefront with a Saleor connection, go custom (Next.js or Nuxt), or use a Frontend Management Platform like Laioutr. Each option comes with its own pros and cons.
No duplicated data, no sync conflicts. Laioutr talks directly to the Saleor GraphQL API, including native multichannel, customer group, and B2B support.
Saleor is GraphQL-first and delivers the building blocks with a Next.js storefront example and an end-to-end GraphQL API, but no finished frontend product that non-developers can operate. That puts the frontend question on the table for every Saleor project. Four options are established in the market.
Saleor's official open-source storefront example, built with Next.js App Router, React, TypeScript, and Tailwind. 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 further yourself. A sensible choice for small shops or as an interim solution.
Open-source frontend frameworks with a community-maintained Saleor connection. An active community, but no official production storefront product and no direct enterprise support net. A sensible choice if you have a suitable frontend team and open source is strategically important.
Maximum control, maximum effort. A six- to twelve-month build phase and ongoing maintenance by an in-house Python and React or Vue team that orchestrates the Saleor GraphQL API itself. A sensible choice if frontend engineering is your strategic core competency.
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.
Laioutr is built for Saleor setups that need to change fast and scale globally. From a native multichannel storefront for brand portfolios to a B2B configurator frontend with large catalogs.
Saleor's multichannel is first-class in the core: multiple channels (brands, markets, sales channels) with their own pricing, currency, and assortment logic, each with a standalone frontend, its own domain, its own brand identity. One component pool, multiple brand experiences.
Saleor delivers customer groups, channel-specific prices, and permission structures. Laioutr calls the GraphQL API directly and renders customer-group-specific prices, assortments, and workflows.
Industrial goods, customization workflows, B2B specifications. Complex state management logic is handled at the Laioutr component level, while GraphQL calls stay cleanly separated.
One Saleor instance, many channels. Languages, currencies, layouts, and assortments can be controlled per channel, compatible with Saleor's native channel concept.
An existing Saleor frontend needs a refresh, without touching the backend configuration. Phased migration, with a clear rollback plan.
A new Saleor project, a fresh start. With Laioutr themes and the UI library, you go live in weeks rather than investing months in a custom build.
Saleor is a GraphQL-first headless framework and delivers an API, dashboard, and a storefront example, but no finished frontend product for non-developers. The most common frontend decision is therefore: a 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 Saleor B2C and B2B.
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 Saleor, commercetools, Shopware, Shopify | Backend-spezifisch Code an Saleor GraphQL 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 Python/Django plus Saleor 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 information is based on publicly available sources, insights from sales conversations with DACH e-commerce brands, and our own platform testing. As of June 2026. Saleor features may have evolved since.
You have a dedicated React or Vue team with Python and Saleor experience, at least three engineers. You're building exactly one Saleor 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.
You want weeks instead of months to go-live, you want marketing to build pages on its own, you serve multiple Saleor channels or brands, you want to keep your backend options open, and BFSG as well as WCAG 3.0 need to be solved without a separate audit. Classic use case: a mid-market or enterprise Saleor shop that wants to scale without a double-digit engineering investment.