If you run OroCommerce and want a modern frontend without building one from scratch, the integration question is simple: how does the frontend layer talk to OroCommerce? This article walks through how Laioutr connects to the REST API (API-first) and what stays where.

What the REST API (API-first) provides

OroCommerce is API-first on Symfony and built for complex B2B, though custom implementations often run 6 to 12 months. The API serves product and catalog data, cart operations, customer accounts and checkout. Because the API is the contract, any frontend can consume it, including Laioutr.

Laioutr is the consumer, OroCommerce is the source of truth

Laioutr connects to the existing REST API (API-first) as a configured layer, not a custom integration project. OroCommerce remains the single source of truth: catalog, pricing, promotions, inventory and orders stay in the backend. There is no data duplication and no sync layer to keep consistent. The frontend requests data when it renders and sends cart and checkout actions back through the API.

What this means in practice

• Product and category pages render from live REST API (API-first) responses
• Cart and checkout actions go through the API, so order logic stays in OroCommerce
• Customer accounts and order history come from the API
• B2B specifics are served through the API and rendered in Laioutr components

A configured layer, not a greenfield build

A custom frontend has to handle every API edge case itself. Laioutr ships the commerce components and their API behaviors prebuilt, so the connect step is configuration against your schema. 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 target and server-side rendering for SEO. Frontend-layer caching reduces load on the OroCommerce backend for read-heavy catalog traffic.

FAQ

Does Laioutr store our product data?

No. Data stays in OroCommerce. Laioutr requests it at render time through the REST API (API-first); there is no duplicate datastore.

Is the backend touched during setup?

No backend re-architecture is required. You use the REST API (API-first) and configure the Laioutr connect layer. See the OroCommerce pillar page or talk to our team.

More on Laioutr: Personalization.

Related reading: BigCommerce GraphQL Storefront API + Laioutr: How the Frontend Connects and Pimcore GraphQL API (Datahub) and REST + Laioutr: How the Frontend Connects.