Skip to content
Neon Coast
Open menu

DirectoryHybrid storefronts

Use Storefront Next in a hybrid implementation

Salesforce Developers

Open the source (opens in a new tab)

Why this is useful

Use this when a cutover is partial. The routing matrix linked below is the worked set of split patterns.

Hybrid Auth keeps the SFRA or SiteGenesis dwsid and the SLAS JWT in sync so some routes can stay on the older storefront. You set hybrid.enabled and list legacyRoutes such as cart and checkout. eCDN sends the routes you choose to Managed Runtime or back to the B2C instance.

Before you start

The guide assumes a Storefront Next app already exists, plus Hybrid Auth setup: a SLAS client with the sfcc.session_bridge scope and Business Manager hybrid settings.

Access and version

Public hybrid guide. You still need the existing storefront and a Storefront Next app.

No charge to read the page.

The guide says B2C Commerce version 25.6 Hybrid Auth support includes Storefront Next, SLAS public and private clients, and SFRA and SiteGenesis templates.

Hybrid means Storefront Next and an existing SFRA or SiteGenesis storefront share a shopper session. It is not a guide to building SFRA itself. Passkeys in Storefront Next 1.2.0 release notes exclude hybrid storefronts.

Checked 8 Nov 2026, 12:45 UTC. developer.salesforce.com returned HTTP 403 to a direct client from this environment. A research reader retrieved the page on 8 Nov 2026.

Salesforce publishes this page. This directory stores an original short description and the link, not the document text.

Publisher
Salesforce Developers
Category
Docs
Access
Free to read
Level
Level unspecified
Topics
Hybrid storefronts, Migration, Configuration
Checked
8 Nov 2026, 12:45 UTC