Implementing Salesforce Commerce Cloud is a multi-quarter project that combines platform setup, data migration, storefront development, and ongoing merchandising operations. The four core phases differ between B2C and B2B but follow a similar shape: provision the platform, migrate the product catalog and customer data, build and customize the storefront, and operationalize the merchant team. Each phase delivers customer-facing value and can be deployed iteratively. Mature Commerce Cloud implementations launch a minimum viable storefront first and add features (personalization, search tuning, payment options) over subsequent releases.
- Provision the platform and configure the realm or org
For B2C Commerce, Salesforce provisions a realm (the equivalent of an org) and gives the admin access through Business Manager. For B2B Commerce, the customer activates the feature in their existing Salesforce org or provisions a dedicated B2B Commerce org. In either case, configure the basic settings: site name, brand identity, supported currencies, supported countries, default language, time zone. Add the initial admin users and configure their roles. For B2C, set up the developer environment (SFRA repo or PWA Kit project) and connect it to the realm. Document the platform settings in the Commerce Cloud runbook for audit and future onboarding.
- Migrate the product catalog and customer data
Export the product catalog from the existing PIM or legacy commerce system. Transform the data to match the Commerce Cloud catalog schema (categories, products, variants, prices, inventory). Load through the Commerce Cloud bulk import API or the catalog feed (B2C) or through Data Loader (B2B). Validate counts after each load: product count matches, category structure matches, inventory levels match. Migrate customer data: account records, contact records, address books, saved carts. Test the migrated data by performing test customer journeys (browse, add to cart, checkout) against a sandbox realm. Iterate on the migration scripts until the test journeys all succeed cleanly.
- Build and customize the storefront
For B2C, pick the rendering model (SFRA for traditional, PWA Kit for headless). Develop the storefront using the platform developer tooling. Customize page templates, product detail pages, category pages, checkout flow, and account self-service pages per the brand design. For B2B, build the Experience Cloud site using Experience Builder; drag in the standard Commerce components for product browsing, cart, and checkout; add custom Lightning Web Components for any org-specific functionality. Configure search relevance through Coveo or Commerce Cloud Einstein Search. Test the storefront in a staging realm under realistic traffic load before going live.
- Operationalize the merchant team
After the storefront launches, the merchant team takes over for ongoing operations. Train merchandisers on managing the catalog through Business Manager (B2C) or the Lightning console (B2B). Train customer service on order management, returns, and customer impersonation. Configure dashboards for the operations team: orders today, conversion rate by category, abandoned carts, customer service ticket volume. Schedule a weekly business review with the merchant lead. Onboard the marketing team to manage promotions, personalization rules, and email campaigns through the integration with Marketing Cloud. Continuous improvement is the operating cadence; the storefront is never finished.
- B2C Commerce pricing uses GMV-based revenue sharing on top of seat licenses. Plan the budget conversation with finance leadership; the commercial model surprises customers used to predictable seat-based pricing.
- B2C and B2B Commerce run on different infrastructure with different data models. Customers operating both products integrate them through Salesforce-native integrations; they do not share runtime.
- Storefront performance at scale requires CDN, caching, and load testing. Launching without testing under realistic traffic load is the most common reason high-profile Commerce launches go badly.
- Catalog imports from PIM systems are the standard pattern; few Commerce customers manage catalogs entirely inside the platform. Build the integration first; the storefront depends on it.
- Search relevance does not work out of the box. Either tune Commerce Cloud Einstein Search with merchandising rules or integrate Coveo for B2C; either way, search tuning is an ongoing operational task, not a one-time setup.