Salesforce Commerce Cloud B2C
Salesforce Commerce Cloud B2C is the e-commerce platform Salesforce offers for retail brands and direct-to-consumer companies selling to end consumers.
Definition
Salesforce Commerce Cloud B2C is the e-commerce platform Salesforce offers for retail brands and direct-to-consumer companies selling to end consumers. Originally Demandware (acquired by Salesforce in 2016), the product runs as a Salesforce-managed SaaS platform that hosts the storefront, the catalog, the cart, the checkout, the order management, and the merchant administration tools in a single integrated environment. It targets brands that sell through online channels to individual consumers at scale, with the operational features they need: high concurrent traffic capacity, CDN-cached storefront, multi-site multi-locale management, and the merchant tooling for daily merchandising operations.
The product sits inside the broader Salesforce Commerce Cloud portfolio alongside B2B Commerce (on Lightning), but the two have very different architectures. B2C runs on the Salesforce-managed Demandware platform with its own developer tooling (Storefront Reference Architecture or PWA Kit) and its own data model. B2B runs on the standard Salesforce Lightning platform alongside Sales Cloud. Picking the right product depends on whether the use case is genuinely consumer-facing retail (B2C) or business-to-business selling (B2B); the answer drives the entire architecture.
Salesforce Commerce Cloud B2C: platform, multi-site, merchandising, and the holiday-load reality
Architecture: the Demandware runtime and Salesforce hosting
B2C Commerce runs on what was the Demandware platform: a Salesforce-managed multi-tenant runtime with built-in CDN, autoscaling compute, and globally-distributed data storage. Each customer gets a realm (the equivalent of a Salesforce org) with one or more sites (the consumer-facing storefronts) inside it. The realm hosts the catalog data, the order data, the merchant administration tools, and the deployment pipeline. Storefronts render through either the Storefront Reference Architecture (SFRA, the server-rendered template), the PWA Kit and Managed Runtime (the React-based headless template), or a custom-built headless integration that pulls data through the B2C Commerce REST APIs (the SCAPI). The platform handles infrastructure scaling automatically up to defined per-realm limits.
Storefronts, sites, and the multi-site model
A single B2C Commerce realm can host multiple sites: a US storefront, a UK storefront, a Japan storefront, a separate brand storefront under the same parent company. Each site has its own catalog (with optional sharing across sites), its own pricing, its own merchandising rules, its own checkout configuration, and its own branding. The multi-site model is the primary reason large retail conglomerates choose B2C Commerce; managing five brand storefronts in one realm is far simpler than managing five separate Magento or Shopify instances. Sites can share inventory, customer accounts, and product catalog where appropriate, with overrides per site. Mature B2C Commerce implementations exploit this multi-site model heavily for regional and brand variants.
Catalog, merchandising, and the Page Designer feature
B2C Commerce ships catalog management tools tuned for retail operations: product variants by size and color, hierarchical category trees with multiple paths, time-bound sale price overrides, promotion rules (buy one get one, percentage off, free shipping above a threshold), and search relevance configuration. Merchandisers manage all of this through Business Manager, the merchant administration UI. Page Designer is the non-developer-facing tool that lets marketers build category landing pages, campaign pages, and homepage sections without writing code; it sits on top of the developer-built page templates with drag-and-drop content management. Mature retail operations use Page Designer heavily for seasonal campaign launches and time-limited promotional pages.
Einstein for B2C Commerce: AI-driven personalization
B2C Commerce includes a suite of Einstein-powered features that target conversion and engagement. Einstein Product Recommendations surfaces You may also like and Customers also bought blocks on product pages, ranked per visitor by a personalization model. Einstein Predictive Sort reorders category listings per visitor based on their browsing and purchase behavior. Einstein Search Recommendations surfaces tailored suggestions in the search bar. Einstein Commerce Insights provides merchandising analytics on what is selling, what is abandoning, and where conversion drops. These features are included in the B2C Commerce subscription and require relatively little configuration to activate; the models train on the customer browsing data and improve over time. For consumer retail at scale, these features typically deliver double-digit revenue lift.
Performance, peak load, and the holiday season
B2C Commerce is engineered for peak retail load: Black Friday, Cyber Monday, holiday season, flash sales. The platform autoscales compute up to the realm allocated capacity, the CDN absorbs front-end traffic, and the order pipeline handles thousands of orders per minute. The cost is that customers operating at very high peak load need to coordinate with Salesforce in advance: capacity planning, load testing, code review of any custom Apex or custom controllers, and Salesforce-side support staffing for the peak window. Brands that skip the coordination and try to absorb Black Friday with a default configuration often see degraded performance or outright outages. Mature retail brands run formal pre-holiday readiness reviews every August through October.
Pricing model: GMV-based revenue sharing
B2C Commerce uses a GMV-based revenue sharing pricing model in addition to platform license fees. A percentage of the customer gross merchandise value (GMV) is paid to Salesforce, typically in the mid-to-high single digits, with the percentage decreasing as GMV scales. This model rewards Salesforce for the customer success but surprises finance teams used to predictable per-seat SaaS pricing. The total cost of ownership scales with revenue, which can be either a feature (cost grows with the business) or a bug (Salesforce captures a percentage of every sale). Negotiate the rate carefully at contract signing and revisit it at renewal as GMV grows; multi-year contracts often lock in a lower rate that becomes more favorable as the business scales.
Implementing a B2C Commerce storefront from realm to operations
Implementing B2C Commerce is a multi-quarter project. The four-phase routine covers: provision the realm and configure the basic site, build out the catalog and merchandising data, develop the storefront with SFRA or PWA Kit, and operationalize the merchant team for ongoing operations. Each phase has its own stakeholders (admins, merchandisers, developers, operations) and its own milestones. Mature B2C Commerce launches stage these phases over six to twelve months; squeezing them into less typically produces a launch that misses the holiday window or loses to performance issues at peak load.
- Provision the realm and configure the basic site
Salesforce provisions a B2C Commerce realm after contract signing. The customer receives access to Business Manager (the admin UI) and the Studio (the developer tool). Configure the basic site: site name, supported currencies, supported countries, default language, time zone. Set up the initial admin users with appropriate roles (Merchant, Developer, Operations). Configure the connection to your payment processor (Salesforce Payments, Stripe, Cybersource, or other) and to your inventory management system. Document the realm configuration in the Commerce runbook; future admins inherit the configuration and need to understand the rationale.
- Build out the catalog and merchandising data
Import the product catalog from your existing PIM (product information management) system. Configure category trees, product variants, prices, inventory. Set up search synonyms and merchandising rules. Build Page Designer pages for the homepage and key category landing pages. Configure promotion rules for any launch-time campaigns. Test the catalog by browsing the storefront as a guest user and confirming products display correctly with the right prices and availability. Iterate until the catalog matches your business model. Document the catalog data flow from PIM to B2C Commerce so future maintenance does not require reverse-engineering.
- Develop the storefront with SFRA or PWA Kit
Pick the rendering model based on your development team skills and your UX goals. SFRA is server-rendered, easier to onboard, and supported by a large Demandware partner ecosystem. PWA Kit is React-based, more flexible and modern, requires stronger frontend skills. Either way, customize the storefront templates to match your brand: layout, typography, color palette, product detail page design, checkout flow. Implement any custom business logic through SFRA controllers (Apex-like server-side scripts) or PWA Kit components. Run usability testing before launch with real consumers; storefronts that work for the brand team often fail for actual shoppers.
- Operationalize the merchant team
After launch, the merchant team takes over daily operations. Train merchandisers on Business Manager: managing the catalog, configuring promotions, updating prices, scheduling sale events, reviewing search analytics, troubleshooting customer issues. Set up dashboards in Commerce Cloud Reports or in CRM Analytics for the operations team: orders today, conversion rate, abandoned cart rate, top-selling products, customer service ticket volume. Schedule a weekly merchant business review. Plan capacity reviews ahead of peak load (Black Friday, Cyber Monday, major brand promotions). Mature retail operations turn the launch into a continuous-improvement engine; the storefront is never finished.
- B2C Commerce pricing uses GMV-based revenue sharing on top of platform license fees. Plan the budget conversation with finance leadership; this surprises customers used to per-seat SaaS pricing.
- Peak load handling requires Salesforce-side coordination. Black Friday, Cyber Monday, and major brand promotions need pre-holiday readiness reviews; skipping them risks degraded performance or outages.
- Storefront customization through SFRA controllers or PWA Kit components requires Demandware-specific skills. The talent pool is smaller than for general web development; budget time and money for the right hires.
- Page Designer requires developer-built page templates as the foundation. Without templates, merchandisers cannot build new pages without engineering help; invest in the template library early.
- Catalog imports from PIM systems are the standard pattern. Few B2C Commerce customers manage catalogs entirely inside Business Manager; build the PIM integration first.
Trust & references
Straight from the source - Salesforce's reference material on Salesforce Commerce Cloud B2C.
- B2C Commerce OverviewSalesforce Help
- B2C Commerce Einstein FeaturesSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Commerce Cloud B2C?
Q2. What was it formerly?
Q3. How does it differ from B2B Commerce architecturally?
Discussion
Loading discussion…