Use Composable Storefront in a Hybrid Implementation

A hybrid storefront allows the combination of traditional storefronts built on Salesforce Commerce Cloud with decoupled, headless Composable Storefront sites. B2C Commerce supports hybrid storefront implementations so that you can execute on your headless strategy with reduced cost and faster time to market.

Only existing customers can access some of the links on this page. Visit Salesforce Commerce Cloud GitHub Repositories and Access for information about how to get access to the Commerce Cloud repositories.

Starting with B2C Commerce version 25.3, Hybrid authentication replaces Plugin SLAS. Hybrid auth is a standalone solution for implementations that need both SFRA/SiteGenesis authorization and Shopper Login and API Access Service (SLAS) authorization. This means you need both a dwsid (SFRA/SiteGenesis) and a JSON Web Token (SLAS), and these tokens must be kept in sync. Hybrid auth is an improvement over the Plugin SLAS approach, offering enhanced performance and stability of hybrid storefronts by moving the feature directly into the B2C Commerce platform.

Hybrid storefronts that use Plugin SLAS will continue to work, but we highly encourage adopting hybrid auth.

For implementation details, see Configure a Hybrid Storefront with Hybrid Auth.

Launch faster with out-of-the-box authentication, ensuring automatic data synchronization between SFRA and Composable Storefront pages. You no longer need Plugin_SLAS!

Shoppers can navigate across your hybrid site with no disruption or loss of data. Synchronization is expanded to include Shopper Context session attributes and support for consistent analytics.

Whether you are using SiteGenesis or SFRA, we have you covered with a fully supported and productized solution to ease your path to Composable Storefront success.

The initial release of hybrid auth in B2C Commerce version 25.3 supports:

  • SLAS Private Clients
  • SFRA and SiteGenesis templates
  • PWA Kit 3.10.0 or later
    • More specifically, @salesforce/commerce-sdk-react: v3.3.0, which comes packaged with PWA Kit 3.10.0
  • Third-party IDP login with SLAS. SFRA third-party IDP logins are not supported.
    • Third party IDP interaction should only be done with SLAS - no SFRA 3rd party IDP logins
  • SLAS Public Clients
  • PWA Kit v2.x support for hybrid auth
  • SFRA “Remember Me” functionality. This is not currently supported. Do not turn on hybrid auth if currently using this.

Decide on the goals, scope, and timeline for your hybrid (phased headless) rollout. Keep in mind that the longer your site is in hybrid mode, the more time you have to spend on the operating complexity involved. Set a due date for transitioning to a 100% Composable site.

A principal benefit of a single page application (SPA) like PWA Kit is that the app bundle is sent to the client and subsequent page requests can often be served without server requests. For this reason, we highly recommend having more than 1 page on PWA Kit to gain performance and shopper UX efficiencies, for example: instead of just your homepage - migrate your homepage and next 1-2 most common journey steps (homepage & search; homepage & our brand). Use the analytics tools at your disposal to chart these common customer journey paths through your site.