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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Multiple brands on a single Spryker instance, with their own frontends, their own domains, a shared backend, and a shared B2B configuration.

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.

An existing Yves stack is to be replaced, without touching the Spryker backend. Migration in phases, without the existing performance suffering.

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.