Adding a B2B store to an existing Experience Cloud site
Key Takeaway
Adding a B2B store to an existing Experience Cloud site keeps the site's template, pages, components and navigation as they are. The store defaults (buyer group, entitlement policy, catalog, category and price book) aren't created, so you set them up yourself.
You can turn an Experience Cloud site you already run into a B2B storefront by adding a store to it. The store builds on what the site already has. After you create the store, you add the commerce parts yourself: the supporting records, the commerce pages you choose and category navigation.
What the store reuses and what you set up
The store reuses the site's domain, settings, branding and styling, so buyers get a consistent look and feel.
The site's template, pages, components and navigation stay the same, which means the site isn't rebuilt. You design the commerce experience afterward by adding commerce pages and components.
The store defaults for buyer group, catalog, category, price book and entitlement policy aren't created for you. Plan to set up these supporting records yourself.
Picture a manufacturer that already runs a partner site for warranty claims. The admin adds a B2B store to that site. Partners reach the store at the same domain, with the same logo and colors. The site's pages and navigation menu look the same as before. Adding the store didn't create a buyer group, entitlement policy, catalog, category or price book, so the admin sets those up next.