Salesforce Commerce Cloud
B2B Commerce and CloudCraze

Commerce Cloud is a family of products. Salesforce groups them on its Commerce page as follows:

Salesforce's pricing page lists Commerce Cloud B2B Growth Edition and the other commerce products as "contact for pricing", and says commerce capabilities are built into the CRM at no cost for Sales and Service Enterprise Edition or higher, through Foundations. For quoting, see our Revenue Cloud page.

Salesforce completed its acquisition of CloudCraze, a B2B commerce platform built natively on Salesforce, on 6 April 2018. In June 2018 Salesforce announced the launch of B2B Commerce and said Commerce Cloud now offered solutions for both B2C and B2B commerce, crediting the CloudCraze acquisition.

Today Salesforce sells the product as B2B Commerce, part of Commerce Cloud. Its B2B Commerce page lists account and buyer entitlements, negotiated pricing, split shipments, more than 200 promotion types, headless Commerce APIs for cart, checkout and catalog, more than 30 built-in reports and dashboards, and Agentforce skills for merchandising and for business buyers.

If your store still runs on the original CloudCraze build, we review what it does today and plan the move to the current B2B Commerce, store by store. Book a discovery call to talk it through.

The original build. CloudCraze is a managed package. Salesforce's CloudCraze patch notes describe a storefront made of Visualforce pages in the ccrz namespace, with permission sets and JavaScript libraries that the package installs. In most builds, the customizations sit in extensions and overrides of that package.

What the current B2B Commerce changes. Salesforce Help says that starting with Summer '23, all new B2B stores are built on the Lightning Web Runtime (LWR). Stores are built from templates in Experience Builder, by dragging Commerce components onto store pages and setting their properties, and checkout, payment and store settings use standard Lightning functionality. Salesforce supports B2B Commerce on Developer, Unlimited and Enterprise editions.

Because the two products are built so differently, we treat the move as a new store build on LWR rather than a package upgrade. In an architect-led migration, the steps are:

1. Inventory the CloudCraze store. List every Visualforce page, package override, custom field and integration, and record what each one does for buyers today.
2. Map data and rules. Map products, price lists, buyer accounts, entitlements and order history to the current B2B Commerce data, and decide what history to bring across.
3. Create the LWR store. Start from the B2B Commerce template in Experience Builder and rebuild the storefront with standard Commerce components, keeping custom Lightning web components for what the standard set does not cover.
4. Rebuild checkout and integrations. Set up checkout and payment with standard Lightning functionality, then reconnect ERP, pricing and inventory systems.
5. Test, then move the configuration. Test with real buyer accounts in a sandbox. Salesforce Help describes exporting a store configuration and moving it between orgs with a change set, which carries the store's metadata such as descriptions, localization, pricing and search settings.
6. Cut over by buyer group. Move buyers in waves, run both storefronts briefly if needed, then retire the Visualforce pages and the managed package.

For the ERP side of the move, see Salesforce integration services.

1. Buyers and accounts. Decide which accounts buy online, who can order for whom, and what each buyer sees.
2. Catalog and pricing. Load products, build personalized catalogs and set negotiated prices and promotions.
3. Checkout and orders. Set payment options, shipping and split shipments, and route orders to fulfilment.
4. Integration. Connect ERP, inventory, tax and pricing systems, through APIs or MuleSoft.
5. Test and launch. Test with real buyers, train sales and service teams, and open the store by region or account group.

Integration is often the largest part of the work. See MuleSoft services and the implementation cost guide.