5.0 stars on OMR Reviews. EU server location. BFSG-ready. In use with DACH Spryker partners.
Spryker × Laioutr
Headless for Spryker, without a composable storefront build
The Frontend Management Platform for Spryker composable commerce. Visual page builder, 70+ e-commerce components including B2B and marketplace building blocks, EU hosting. Faster to launch than the Spryker Composable Storefront, compatible with the Glue API and GraphQL, plus company hierarchies, quote management, and approval workflows.
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 Spryker?
Headless for Spryker separates the frontend, everything your buyers see, from the Spryker backend with its products, company hierarchies, quotes, multi-cart, and marketplace sellers. Instead of Yves, the frontend is connected through the Spryker Glue API (REST) or the newer GraphQL API and can be designed freely, without Twig theme limits and with full performance control.
1. The backend stays Spryker
Spryker continues to manage products, company hierarchies, permission sets, quote management, approval workflows, marketplace sellers, multi-cart, and punchout integration. You use the Spryker Backoffice unchanged, with all its B2B and marketplace modules.
2. The frontend is chosen
You have four established options: Yves (classic Twig), Spryker Composable Storefront (the official Next.js headless), Custom Build (Next.js, Nuxt, Remix), or a Frontend Management Platform like Laioutr.
3. Data flows via API in real time
No data duplication, no sync conflicts. Laioutr talks directly to the Spryker Glue API and the newer GraphQL connection, including all B2B and marketplace endpoints for company hierarchies, quotes, and multi-seller features.
Benefits
What frontend options do you have for Spryker?
Spryker has a clearly split frontend story: the older Yves and the newer Composable Storefront. Plus custom build and FMP. Four options are established in the market. Here's where each one pays off for Spryker buyers.
1. Yves (classic)
A Twig-based web frontend, still in production in many existing implementations. Useful for brands that don't want to migrate, but strategically a clear phase-out model. The deepest backend integration, but perceived as engineering-intensive and slow in the build cycle.
2. Spryker Composable Storefront
Spryker's official Next.js-based headless frontend, open source and performance-first. Useful if you have a dedicated Next.js team with Spryker experience and accept six- to nine-month build phases. Native Spryker API depth is the biggest advantage.
3. Custom Build (Next.js, Nuxt, Remix)
Maximum control, highest effort. A six- to twelve-month build phase plus ongoing maintenance. Useful for enterprise teams with dedicated frontend engineering and highly specific B2B or marketplace requirements.
4. Laioutr FMP
A Frontend Management Platform with a visual builder, 70+ components including B2B and marketplace building blocks, EU hosting, and multi-backend support. Useful if you want to go live fast, need standard B2B features and marketplace UIs out of the box, and prioritize marketing velocity.
USE CASES
What you build with Laioutr for Spryker
Laioutr is built for Spryker setups that want to carry through their composable vision consistently, without investing in a six- to nine-month composable storefront build. From a company-hierarchy portal to a marketplace operator frontend.
B2B portals with company hierarchies, quote management, and approval workflows
Spryker B2B delivers the complete workflows. Laioutr calls the Glue API directly and renders customer-group-specific frontends with approval flows, quote negotiation, permission UIs, and multi-cart.
Marketplace operator frontends with seller profiles and multi-seller PDPs
You operate Spryker as a marketplace with multiple sellers. Laioutr connects to the Spryker Marketplace API and renders seller profiles, multi-seller PDPs, filter-by-seller, and operator tools as standard components.
Multi-brand storefronts on a single Spryker instance
Multiple brands on a single Spryker instance, with their own frontends, their own domains, a shared backend, and a shared B2B configuration.
International multi-country setups with localized B2B workflows
Spryker multi-store with localized price lists, tax IDs, quote templates, and approval hierarchies. The frontend is configured in Studio, without setting up a composable storefront build per market.
Replatforming from Yves to Laioutr
An existing Yves stack is to be replaced, without touching the Spryker backend. Migration in phases, without the existing performance suffering.
Greenfield storefronts on new Spryker projects
New Spryker project, clean slate. With Laioutr themes and the UI library, you go live in weeks instead of investing six months in a custom composable storefront build.
Laioutr vs. Spryker Composable Storefront
The honest composable comparison
Spryker Composable Storefront is Spryker's official headless frontend, Next.js-based, open source, with native Glue API and GraphQL integration and a performance-first architecture. Laioutr is a complete Frontend Management Platform with a visual builder, component library, and multi-backend support. Both work with Spryker. If you want a mature engineering team and deep API-native integration, the Composable Storefront is the most native option. If you want marketing velocity, B2B and marketplace components, and predictable TCO, you'll be more productive with Laioutr.
Compare differences | Laioutr FMP | Spryker Composable Storefront |
|---|---|---|
Builder und Komponenten Was Sie aus der Box bekommen, mit Fokus auf B2B und Marketplace. | ||
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 Company Hierarchies, Quote Management und Approval Workflows. | 70+ Komponenten B2B-Bausteine inkl. Quote- und Approval-UIs | Basis-Demo B2B-UI selbst aufbauen |
Marketplace-Komponenten Vorgefertigte UI-Bausteine für Seller-Profile und Multi-Seller-PDPs. | Enthalten Marketplace-Bausteine inkl. Operator-Tools | Selbst bauen Marketplace-UI als Custom-Build |
Themes und Vorlagen Startpunkt für neue Storefronts ohne Greenfield-Aufwand. | Vorgefertigte Themes Sofort einsatzbereit, voll erweiterbar | Starter-Templates Demo-Storefront als Starthilfe |
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 Spryker-Integration Wie eng die Integration in den Spryker-Composable-Stack ist. | ||
Backend-Flexibilität Welche E-Commerce-Backends sich anbinden lassen. | Multi-Backend Spryker, Shopware, commercetools, weitere | Nur Spryker Lock-in zum Spryker-Stack |
Spryker-API-Anbindung Glue API (REST) und neuere GraphQL-Anbindung. | Glue plus GraphQL Beide APIs voll unterstützt | Native Anbindung Glue plus GraphQL als Standard |
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 | Out of the box Performance-First-Architektur |
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, Spryker-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 Spryker-Erfahrung |
Total Cost of Ownership Software plus Engineering plus Wartung über 3 bis 5 Jahre. | SaaS (planbar) Hosting und Komponenten inklusive Preise ansehen | Open Source plus Engineering 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. Spryker features may have evolved since.
Spryker
When the Composable Storefront is the right choice
You have a dedicated Next.js team with Spryker experience (at least three engineers), you actively leverage the Spryker roadmap synergies, you accept six- to nine-month build phases, marketing teams work primarily through tickets, and maximum code control matters more than time-to-launch. Classic use case: an enterprise B2B operator with dedicated frontend engineering expertise and a deeply API-integrated architecture.
LAIOUTR
When Laioutr is the right choice
You want weeks instead of months to go-live, marketing should build pages on its own, you need B2B and marketplace components without a React sprint per workflow, you haven't built 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: an enterprise B2B brand on Spryker that wants to carry through its composable vision consistently, without building a frontend engineering team.
You don't have to do this alone. Our certified Spryker implementation partners have delivered Spryker frontend projects with Laioutr, from Yves migrations to Composable Storefront replatformings.
FAQ