Keep the Shopware checkout, decouple the frontend: our connector is open source

We shipped our Shopware connector, open source on GitHub, under the MIT license. It answers the one question that comes up first in every frontend decoupling conversation with a Shopware shop: "and what happens to my checkout?"

The answer is now simple. Your checkout stays where it is. You keep Shopware's native payment methods exactly as they are configured. Laioutr takes over the frontend and the content experience, and the connector hands your shoppers from the Laioutr storefront straight into the Shopware checkout, with the session carried over. No rebuilding payment, no PCI discussion, no break in the buying flow.

Why this matters for Shopware shops

If you are on Shopware 6, your backend question is solved. The frontend question often is not. Twig themes scale poorly across multi-brand and multi-country setups, and building your own Vue storefront is a separate project with its own team and months of lead time. This is where Laioutr fits: as a Frontend Management Platform (FMP) sitting on top of your Store API, with a Studio editor for marketing, WCAG 3.0 ready out of the box and EU hosting.

The catch with nearly every decoupling approach so far was the checkout. Payment methods, tax logic, customer groups, mandatory legal pages: all of that lives deep in the Shopware core, and nobody wants to rebuild it in the frontend layer. There is no need to. The best checkout for your Shopware shop is the one Shopware already has.

The connector makes the clean division of labor possible: Laioutr delivers discovery, content, category and product experience, and at the moment of the purchase decision it hands off to the native Shopware checkout. Your payment providers, your configuration, your compliance setup stay untouched.

What the connector actually does

The connector is a standalone Shopware 6 plugin. It builds a session bridge between the Laioutr storefront and your Shopware instance so that cart and login context survive the handover. To the shopper it feels like one continuous flow; technically the checkout stays entirely in Shopware.

Two things mattered to us here.

First, security by default. The connector works with an allowlist of permitted callback domains, including wildcard support for preview environments. An empty configuration rejects every callback. You decide explicitly which domains are allowed to receive a handover.

Second, a lean plugin. It ships no JavaScript, Twig or SCSS baggage of its own and needs no asset build. It does one thing cleanly: connect your decoupled frontend to the Shopware checkout.

For developers: the plugin installs with `composer require laioutr/shopware-connector` and is available on Packagist. It supports PHP 8.2 through 8.5 and Shopware 6.6 through 6.7. Session coupling runs over two endpoints: `GET /laioutr/connect-session` starts the connection and redirects to a local Shopware route, and `GET /laioutr/cookie-bridge` establishes the Shopware session in the embedded flow. Because embedding Shopware is part of the integration, the plugin removes `X-Frame-Options` globally. Deployments should restrict embedding with an appropriate Content Security Policy using `frame-ancestors` at the application or reverse-proxy layer. Cross-site sessions require HTTPS, `cookie_samesite: none` and `cookie_secure: true`. The code is MIT licensed on GitHub, and releases are versioned and signed.

The real lever: decoupling without switching backends

The connector is more than an integration detail. It makes the frontend-first migration path real for Shopware shops.

If you are on Shopware 6: put Laioutr on your Store API and modernize the frontend without touching the backend. Multi-brand and multi-country on one codebase instead of theme forks, landing pages in hours instead of sprints, Core Web Vitals and accessibility compliance as a platform property.

If you are still on Shopware 5 and facing the 5-to-6 migration: decouple the frontend first. The frontend runs on Laioutr before the migration, you migrate the backend in isolation, and at cutover you only switch the connector. No theme rewrite, no parallel double effort during the migration.

In both cases the checkout stays what it is: native to Shopware, with your payment methods. The frontend becomes replaceable, the backend stays your decision.

Why open source

We are releasing the connector openly and under the MIT license on purpose. To us, decoupling means keeping architecture decisions reversible and integrations transparent. You can read the code, fork it, adapt it to your deployment reality and see for yourself how the session bridge works before you rely on it. Transparency at the interface to the checkout is exactly where it counts.

Next step

The connector is available on GitHub now: github.com/laioutr/shopware-laioutr-connector.

If you want to see what Laioutr looks like on your Shopware setup, with your checkout and your payment methods, Sebastian and I will walk you through it in a 30-minute demo. Backend stays Shopware, frontend becomes replaceable, checkout stays native.

Related: Composable Headless Frontend.

Related: headless frontend for Shopware.

Related: Agentic Frontend Management Platform.