Stores created using the Unified Commerce Template are internally classified as B2B. This behavior is expected and by design.
The WebStore type is determined by the underlying template architecture. Since the Unified template is built as an extension of the B2B framework, all stores created using this template inherit the B2B classification, regardless of UI capabilities.
Starting from Release 258, the D2C template is no longer available in the default storefront creation flow for new customers.
While the template is not deprecated for existing use, it is no longer actively offered as part of standard provisioning.
A Product Management-controlled permission, B2CTemplateCreationEnabled, can be enabled to allow the creation of D2C/B2C stores using the legacy template. This permission is granted on a case-by-case basis and is not enabled by default.
The Unified Commerce Template does not support configuration as a D2C store. There is currently no supported mechanism to convert or explicitly configure a Unified (Commerce Store) template as D2C.
The product direction remains B2B-first, with UI enhancements bridging certain experience gaps rather than changing the underlying business model.
Customers requiring full D2C capabilities must rely on access to the legacy D2C template through the appropriate Product Management approval process.
Implementing D2C use cases on a WebStore configured as B2B is not the intended or supported approach.
While certain scenarios may appear to function due to UI flexibility, this setup can lead to:
Customers are advised to align their implementation with the intended B2B architecture to avoid such issues.
As part of the Unified Commerce Template initiative, enhancements have been limited to the user interface and user experience layer.
There are no changes to:
All order-related functionality continues to follow standard B2B Commerce platform conventions.
005319550

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.