SAP Commerce Cloud OCC API + Laioutr: How the Frontend Connects

If you run SAP Commerce Cloud and want a modern frontend without rebuilding the backend, the integration question is simple: how does the frontend layer talk to SAP? This article walks through how Laioutr connects to the OCC REST API and what stays where.

What the OCC API provides

OCC (Omni Commerce Connect) is the official set of REST endpoints SAP Commerce Cloud exposes for storefront use. It covers product search and catalog, cart operations, checkout flows and customer account management. Because OCC is technology-agnostic, any frontend can consume it. The Composable Storefront uses OCC; a custom React app would use OCC; Laioutr uses OCC.

Laioutr is the consumer, SAP is the source of truth

Laioutr connects to the existing OCC endpoints as a configured layer, not a custom integration project. SAP Commerce Cloud remains the single source of truth: catalog, pricing, promotions, inventory and order management all stay in the backend. There is no data duplication and no sync layer to keep consistent. The frontend requests data when it renders and submits cart and checkout actions back through OCC.

What this means in practice

• Product and category pages render from live OCC catalog and search responses
• Cart and checkout actions are OCC calls, so order logic and tax stay in SAP
• Customer accounts, addresses and order history come from the OCC account endpoints
• B2B specifics such as cost centers and customer-specific pricing are served through OCC and rendered in Laioutr components

Why a configured layer beats a custom integration

A custom frontend has to handle every OCC edge case itself: cart states, B2B price lists, checkout step logic, error handling. Laioutr ships these as configured component behaviors, so the connect step is configuration, not a greenfield build. Marketing teams then compose pages and campaigns on top without touching the integration.

Performance and hosting

Laioutr serves the frontend from an EU CDN with a Lighthouse 100 performance target and server-side rendering for SEO. Caching at the frontend layer reduces load on the SAP backend for read-heavy catalog traffic.

FAQ

Do we need custom OCC extensions?

Standard OCC endpoints cover most storefronts. Project-specific logic can be exposed through custom OCC endpoints and consumed by Laioutr components.

Does Laioutr store our product data?

No. Data stays in SAP Commerce Cloud. Laioutr requests it at render time through OCC; there is no duplicate datastore to maintain.

Is the backend touched during setup?

No backend re-architecture is required. You expose the OCC API (already standard) and configure the Laioutr connect layer. Talk to our team to scope your specific OCC setup.

Related: Headless frontend for SAP Commerce Cloud.

More on Laioutr: Personalization.

Related reading: Vendure Shop API + Laioutr: How the Frontend Connects and SCAYLE Storefront API + Laioutr: How the Frontend Connects.