Salesforce Commerce Cloud is an enterprise e-commerce platform covering two distinct markets: B2C Commerce for consumer-facing retail storefronts and B2B Commerce for business buyer self-service portals. Originally acquired from Demandware in 2016 for $2.8 billion, Commerce Cloud has become one of Salesforce’s fastest-growing cloud products — powering storefronts for global retail brands including Adidas, L’Oréal, Puma, and PGA Tour, while its B2B variant serves manufacturers and distributors building digital buying experiences for business customers. This guide covers the core features, architecture options, AI capabilities, and integration points that define Commerce Cloud in 2026.
The best guide is the one that makes the commerce layer feel clear.
A useful explanation should help the reader understand where Commerce Cloud fits in the customer journey.
That means the guide should focus on practical use cases rather than broad platform labels.
For many teams, the value is in connecting storefront activity to broader customer management.
It should also show why the product matters for businesses with more complex online selling needs.
A good guide should explain what the platform is meant to do and how it supports commerce-led workflows.
That makes it different from a standard CRM-only conversation.
What is Salesforce Commerce Cloud is a useful question because the product sits at the intersection of commerce, customer experience, and digital selling. It is designed for businesses that want to manage the buying journey in a more connected way.
B2C Commerce vs B2B Commerce: Two Products, One Brand
Salesforce Commerce Cloud is marketed as a single platform but consists of two functionally distinct products with different architectures, pricing models, and use cases:
B2C Commerce (formerly Demandware)
B2C Commerce is the consumer-facing e-commerce platform — the technology behind the digital storefront when a shopper visits a brand’s website, browses products, adds to cart, and checks out. B2C Commerce handles:
- Product catalogue management: hierarchical category structure, product variants, bundles, digital products
- Global site management: multiple storefronts for different countries, languages, and currencies from a single admin console
- Pricing and promotions engine: complex promotional logic — tiered pricing, buy-X-get-Y, coupon codes, flash sales with time-based rules, customer group pricing
- Search and merchandising: on-site product search with searchable attributes, sorting rules, synonym management, and AI-powered Einstein Search
- Order management: order capture, payment processing integration, fulfilment routing, returns and refunds
- Checkout: multi-step or single-page checkout, guest and registered checkout flows, address validation, tax calculation integration
B2C Commerce pricing: Revenue share model — B2C Commerce licensing is calculated as a percentage of gross merchandise value (GMV) processed through the platform, plus a platform base fee. This means licensing costs scale with commercial success — high-GMV retailers pay substantially more than smaller brands. The revenue share percentage varies by contract volume; Salesforce negotiates rates individually.
B2B Commerce
B2B Commerce is built on Salesforce’s core platform (Lightning Experience), not on the Demandware technology stack. It is designed for manufacturers, distributors, and wholesalers creating digital buying portals for their business customers — replacing the phone-and-email ordering process with a self-service web experience that respects negotiated contract pricing, account-specific product catalogues, and business approval workflows.
B2B Commerce features specific to business buying:
- Account-based pricing: each buyer account sees their negotiated contract prices, not list prices — configurable per account and per product
- Buyer groups: customers segmented into pricing tiers with different catalogue visibility and price levels
- Order templates: reorder lists for customers who frequently purchase the same products — one-click reorder from saved templates
- Purchase approval workflows: orders above a threshold require manager approval before submission — enforcing business procurement policies
- Punchout catalogue: integration with procurement systems (SAP Ariba, Coupa, Jaggaer) for large enterprise buyers who purchase through ERP-connected procurement tools
- Split shipping: one order shipped to multiple addresses — a common requirement for distributors shipping to multiple warehouse locations
B2B Commerce pricing: Per-org licensing, similar to other Salesforce clouds, rather than the GMV-based model of B2C Commerce.
Storefront Architecture: SFRA vs Composable Storefront
B2C Commerce storefronts are built on one of two reference architectures:
Storefront Reference Architecture (SFRA)
SFRA is Salesforce’s server-side rendered storefront framework — the traditional B2C Commerce implementation approach. SFRA provides a complete reference implementation (product pages, category pages, cart, checkout, account management) that development teams customise. SFRA storefronts render HTML server-side on each page request, delivering content directly from the Commerce Cloud servers.
SFRA is appropriate for: organisations with existing SFRA implementations, teams with deep B2C Commerce developer expertise, and deployments where the full Commerce Cloud platform (built-in search, promotions engine, site management) is the primary differentiator. Most large Salesforce B2C Commerce implementations from 2016–2022 are SFRA-based.
Composable Storefront (PWA Kit)
The Composable Storefront is Salesforce’s React-based, API-first storefront framework — designed for headless commerce architectures. PWA Kit builds a Progressive Web App (PWA) frontend that communicates with Commerce Cloud’s backend via the Shopper API. The frontend is hosted on Salesforce’s Managed Runtime (a Node.js hosting environment) or on any CDN.
Composable Storefront advantages:
- Performance: React-based single-page app with server-side rendering for first-load performance — typically achieves higher Core Web Vitals scores than SFRA, which matters for SEO and mobile conversion
- Developer ecosystem: React development skills are significantly more widely available than SFRA-specific expertise
- Composability: the API-first architecture allows mixing Commerce Cloud’s backend services with other headless services — a CMS from Contentful, search from Algolia, reviews from Yotpo — while using Commerce Cloud for the core transaction and catalogue management
- Salesforce’s strategic direction: Composable Storefront is where Salesforce is investing — new features appear on the Shopper API first
New B2C Commerce implementations in 2024–2026 should default to Composable Storefront unless there is a specific reason to choose SFRA (existing SFRA investment, specific capability not yet available in the Shopper API).
Einstein AI for Commerce
Commerce Cloud includes Einstein AI features across the shopping experience — most significant for personalisation and search:
Einstein Product Recommendations
Machine learning-powered product recommendation widgets embedded in the storefront — “Customers also bought,” “Recently viewed,” “You might also like.” Einstein Recommendations analyses purchase history, browsing behaviour, and product affinity data to generate personalised recommendations per shopper. Recommendations are rendered via API call to Einstein’s recommendation engine — site teams configure the recommendation strategy (collaborative filtering, content-based, trending) and the placement (homepage, product detail page, cart page, email).
Einstein Predictive Sort
Personalises the order of products in category listings and search results — showing each shopper the products most likely to appeal to them based on their behaviour and purchase history, rather than a single global sort order for all visitors. According to Salesforce’s customer data, sites implementing Predictive Sort see an average 5–9% increase in conversion rate on category pages.
Einstein Search Dictionaries
Automatically identifies synonyms and relationships between search terms used on the site — mapping shopper vocabulary (“kicks” → “sneakers”) to catalogue terms without manual synonym list maintenance. Einstein Search Dictionaries analyse actual search queries and purchase outcomes to build the synonym map dynamically.
Einstein Commerce Insights
A reporting dashboard showing AI-generated insights about the shopper funnel — identifying which products are high-impressions-but-low-conversion (possibly quality or pricing issue), which search terms return zero results (catalogue gap), and which promotional offers are driving the highest incremental revenue.
Order Management System
Salesforce Order Management (OM) is a separate but closely integrated product — the operational system for managing orders after they are placed. Commerce Cloud captures the order; Order Management handles the subsequent lifecycle:
- Order routing and allocation: determining which warehouse or store location fulfils each order based on inventory availability, proximity, and carrier cost optimisation
- Fulfilment workflows: ship from warehouse, ship from store, buy online pick up in store (BOPIS), endless aisle (order in-store for home delivery)
- Returns and exchanges: return merchandise authorisation (RMA), refund processing, exchange order creation
- Customer service integration: order management data is visible in Salesforce Service Cloud — customer service agents see order status, tracking, and fulfilment details on the customer record, enabling case resolution without switching systems
Integration with the Salesforce Platform
Commerce Cloud’s primary competitive advantage over standalone e-commerce platforms (Shopify Plus, Magento Commerce, BigCommerce Enterprise) is its integration depth with the broader Salesforce ecosystem:
- Data Cloud: unified customer identity across Commerce Cloud purchase history, CRM contact and account data, and Service Cloud case history — enabling a single customer profile that Marketing Cloud and personalisation tools can use across all touchpoints
- Marketing Cloud: triggered emails and journeys based on Commerce Cloud events — abandoned cart emails sent within minutes of cart abandonment, post-purchase loyalty emails, win-back campaigns to lapsed purchasers — all driven by real-time Commerce Cloud event data flowing into Marketing Cloud’s Journey Builder
- Service Cloud: customer service agents access order status, return status, and purchase history directly on the Salesforce Contact and Case records — reducing AHT and improving first-contact resolution for order enquiries
- Loyalty Management: Salesforce Loyalty Management integrates with Commerce Cloud to apply points redemption at checkout, issue points on purchase, and display loyalty tier status in the storefront account section
When Commerce Cloud Is the Right Choice
Salesforce Commerce Cloud is enterprise-grade infrastructure — implementation costs, platform fees, and the specialist developer ecosystem make it appropriate for a specific profile of organisation:
- Mid-to-large retail brands: annual e-commerce GMV typically above $50M for B2C Commerce (below that threshold, the platform cost vs. Shopify Plus is hard to justify)
- Multi-site, multi-region operations: managing 10+ storefronts across different countries from a single platform is a genuine Commerce Cloud differentiator — the Site Genesis / multi-site management capabilities outperform mid-market platforms
- Organisations already on Salesforce: the data unification and Marketing Cloud integration value compounds significantly when the rest of the customer data is already in Salesforce CRM and Service Cloud
- B2B manufacturers and distributors: organisations replacing phone/email ordering with a digital buyer portal where account-specific pricing, approval workflows, and ERP integration are requirements — B2B Commerce is purpose-built for this use case
Conclusion
Salesforce Commerce Cloud is the enterprise e-commerce platform of choice for global retail brands and B2B manufacturers building sophisticated digital buying experiences integrated with their broader Salesforce investment. B2C Commerce’s AI-powered personalisation, multi-site management, and Marketing Cloud integration make it competitive against other enterprise platforms (SAP Commerce, Oracle Commerce). B2B Commerce’s account-based pricing, approval workflows, and native Salesforce CRM integration address the specific requirements of manufacturer and distributor digital transformation that generic e-commerce platforms don’t serve well. The platform’s cost structure — GMV-based for B2C, per-org for B2B — and implementation complexity mean it is not the right choice for organisations below a certain scale, but for enterprises where these features are requirements, Commerce Cloud’s tight integration with the Salesforce Customer 360 is a durable competitive moat.
Sources
Salesforce, Commerce Cloud Product Documentation (2026)
Salesforce, Composable Storefront PWA Kit Developer Guide (2026)
Salesforce, Einstein Commerce AI Features Documentation (2026)
Gartner, Magic Quadrant for Digital Commerce (2025)
Forrester Wave: B2C Commerce Solutions (2025)
Problem: Configuration Completed Without Documenting the Setup
Salesforce configurations built without documentation create fragility — when the admin who set it up leaves or is unavailable, nobody understands why things are configured the way they are. Undocumented customizations, workflows, and field choices become institutional knowledge that walks out the door. Fix this by maintaining a living configuration document that records every non-default setting: custom fields and their purpose, automation rules and their trigger logic, permission sets and who holds them. Store it in a shared location and update it whenever the configuration changes.
Problem: Team Adoption Stalls Because Training Was One-Time Only
Organizations that run a single training session at launch and then leave users to figure things out on their own see adoption rates decline within 60 days as habits revert to spreadsheets and email threads. New hires get no structured Salesforce training at all. Fix this by building a recurring training cadence: a 30-minute monthly “tips and tricks” session for the whole team, a structured onboarding checklist for new users (covering the 10 most common tasks), and recorded walkthrough videos for each role stored in a shared knowledge base. The best-adopted Salesforce implementations treat training as a continuous program, not a one-time event.
Problem: Reports Built for Management Don’t Help the Frontline Team
Most Salesforce dashboards are designed to give managers visibility into team metrics — pipeline totals, activity counts, conversion rates. Reps who only see management-facing reports get no personal value from the CRM, which reduces their motivation to keep data clean and current. Fix this by building personal dashboards for each user role: a rep sees their own pipeline, their overdue activities, and their win rate this quarter versus last quarter. When individual contributors see Salesforce as a tool that helps them close more deals rather than just a reporting layer for management, data quality improves significantly.
The best commerce setup is the one that keeps the buying journey connected. If the experience is fragmented, the platform is harder to use well.
Frequently Asked Questions
How long does it take to see ROI from Salesforce?
Most organizations see measurable ROI from Salesforce within 6–12 months of go-live, assuming the implementation was done correctly and adoption is active. Early wins typically come from pipeline visibility (fewer deals falling through the cracks) and time savings from automation (fewer manual follow-up reminders). Larger ROI gains — from better forecasting accuracy, improved win rates, and shorter sales cycles — typically take 9–18 months as the system accumulates enough data to reveal patterns. Companies that invest in change management alongside the technical implementation consistently reach ROI faster than those that treat it as a pure software deployment.
What’s the biggest mistake companies make with Salesforce?
The most common mistake is configuring Salesforce to match a generic best-practice template rather than the company’s actual sales process. When the CRM doesn’t reflect how the team works, reps build workarounds and CRM usage becomes performative — they update it because they have to, not because it helps them. The second most common mistake is under-investing in data quality from the start. Importing dirty, duplicate, or incomplete data as a “we’ll clean it up later” plan almost never results in cleanup — the bad data compounds and eventually undermines trust in the system.
How many users does Salesforce work well for?
Salesforce scales from individual users to enterprise organizations with thousands of seats, though the right tier and configuration differs significantly by team size. Small teams (under 10 users) benefit most from simplicity — stick to standard features, avoid over-customization, and prioritize adoption over sophistication. Mid-market teams (10–100 users) need more process definition, automation, and reporting structure. Enterprise implementations require dedicated admin resources, governance policies, and often external implementation support. Match the complexity of your Salesforce setup to the maturity and size of your team.
Can Salesforce integrate with our existing tools?
Most modern CRM platforms including Salesforce offer native integrations with common business tools — email clients (Gmail, Outlook), calendar apps, marketing platforms, support desks, and accounting software. For tools without native connectors, middleware platforms like Zapier, Make, or dedicated integration tools fill the gap. Before assuming an integration is available, verify whether it’s native (built and maintained by the CRM vendor), partner-built (listed on their marketplace but maintained by a third party), or middleware-dependent (requires Zapier or similar). Native integrations are generally more reliable and require less maintenance than middleware-based connections.