Headless for SAP Commerce Cloud separates the frontend, everything your customers see, from the SAP Commerce backend with its products, catalogs, orders, and checkout. The frontend connects through the OCC API (Omni Commerce Connect, REST) and can be designed freely, without the constraints of the Accelerator storefront and with full performance control.

SAP Commerce Cloud continues to manage products, catalogs, customer hierarchies, orders, taxes, and checkout. You keep using Backoffice, ImpEx, and the familiar business tools unchanged, with all your established workflows and extensions.

You have four options: keep the Accelerator storefront, go with the Composable Storefront (Spartacus), custom-build (Next.js or Nuxt), or use a Frontend Management Platform like Laioutr. Each option has its pros and cons.

No duplicated data, no sync conflicts. Laioutr talks directly to the OCC REST API, including support for multi-site, customer groups, and B2B commerce.

Unlike backends without an official frontend, SAP ships its own headless product with the Composable Storefront (Spartacus). That turns the frontend question into a strategic decision for every SAP Commerce project: keep the Accelerator running, go with Spartacus, build your own, or use a Frontend Management Platform. Four options are established in the market.

The classic, server-side storefront from the SAP Commerce Accelerator, built on JSP and Spring MVC. Solid for established setups, but the performance ceiling and frontend limitations are becoming increasingly noticeable, and SAP positions the Composable Storefront as its successor. A sensible transitional solution, not a path to the future.

SAP's official, Angular-based headless frontend that communicates exclusively via the OCC API. Backed by SAP support since version 5.0 rather than being pure open source. Solid and vendor-backed, but Angular expertise, modular library maintenance, and ongoing upgrade cycles sit with your team. A good fit if you have an Angular team and an appetite for running it yourself.

Maximum control, highest effort. A six- to twelve-month build phase and permanent maintenance by an in-house Java and React or Vue team. A good fit when 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 SAP Commerce setups that need to change fast and scale globally. From a multi-site storefront for brand portfolios to a B2B configurator frontend with complex catalogs.

Multiple base sites (brands, markets, sales channels) on a single instance with standalone frontends, their own domains, and their own brand identity. One pool of components, many brand experiences.

SAP Commerce delivers B2B commerce with organizations, customer hierarchies, and approval workflows. Laioutr calls the OCC API directly and renders customer-group-specific prices, assortments, and approval processes.

Industrial goods, customization workflows, B2B specifications, and CPQ scenarios. Complex state-management logic is solved at the Laioutr component level, while OCC API calls stay cleanly separated.

One SAP Commerce instance, many base sites. Languages, currencies, layouts, and assortments can be controlled per site, compatible with the SAP Commerce multi-site concept.

An existing SAP Commerce stack needs a frontend overhaul without touching the backend configuration. Migration in phases, with a clear rollback plan.

A new SAP Commerce project, a fresh start. With Laioutr themes and the UI library, you go live in weeks instead of investing months in a custom build.