Salesforce Commerce Cloud Development — B2B & B2C E-Commerce Guide
E-commerce is no longer a channel — it is the primary way customers interact with most brands. Whether you are selling directly to consumers or managing complex B2B transactions with negotiated pricing and multi-level approval workflows, the e-commerce platform you choose determines your ability to scale, personalize, and adapt to changing market conditions. The wrong platform creates technical constraints that your business will fight against for years.
Salesforce Commerce Cloud provides two distinct products for two distinct commerce models. B2C Commerce (formerly Demandware) powers direct-to-consumer retail with high-volume transaction processing, sophisticated merchandising, and AI-driven product recommendations. B2B Commerce is built natively on the Salesforce platform and handles the complexity of business purchasing — account hierarchies, contract pricing, bulk ordering, and integration with CPQ and ERP systems. Both products benefit from deep integration with the broader Salesforce ecosystem, creating a connected commerce experience that spans marketing, sales, service, and fulfillment.
At ESS ENN Associates, our commerce practice has built storefronts for retail, manufacturing, and distribution companies. This guide covers the architecture, development approaches, and implementation decisions that determine whether your Commerce Cloud investment delivers a competitive advantage or just another online store.
B2C Commerce Cloud Architecture
B2C Commerce Cloud runs on its own infrastructure, separate from the core Salesforce platform. This architectural independence is by design — e-commerce workloads have fundamentally different performance requirements than CRM workloads. A product listing page must render in under 2 seconds during a Black Friday traffic spike. A checkout flow must handle thousands of concurrent transactions without degradation. These performance demands require dedicated infrastructure optimized for commerce.
The commerce pipeline. B2C Commerce processes requests through a pipeline architecture. When a customer requests a page — a product listing, a product detail page, a cart — the request flows through a controller that orchestrates data retrieval, business logic, and template rendering. Controllers are written in server-side JavaScript (not to be confused with Marketing Cloud's SSJS — they are different runtimes). Templates use ISML (Internet Store Markup Language), a tag-based templating language that mixes HTML with Commerce Cloud-specific tags for data binding, content slots, and component rendering.
SFRA (Storefront Reference Architecture). SFRA is Salesforce's modern storefront framework that replaced the older SiteGenesis reference implementation. SFRA provides a production-ready storefront with responsive design, modular JavaScript controllers, client-side JavaScript using jQuery and Bootstrap, server-side ISML templates with a component-based structure, and built-in support for product search, filtering, sorting, cart management, checkout, and account management. SFRA follows a cartridge-based architecture where customizations are layered on top of the base SFRA cartridge. This layering enables upgrades — when Salesforce releases a new SFRA version, your customization cartridge overlays continue to work without rebuilding the entire storefront.
Cartridge architecture. Commerce Cloud organizes code into cartridges — modular packages that contain controllers, templates, static assets, and configuration. The cartridge path determines which cartridge serves each request, enabling an override pattern where a custom cartridge can replace specific controllers or templates from SFRA without modifying the base code. Third-party integrations (payment gateways, tax engines, address verification) are typically packaged as cartridges that plug into the cartridge path. This modularity enables a clean separation between base platform functionality, customizations, and third-party extensions.
Headless Commerce and PWA Kit
Headless commerce decouples the storefront presentation layer from the commerce backend. The Commerce Cloud backend provides APIs for product search, cart management, checkout, and order management, while the frontend is built as an independent application using modern JavaScript frameworks. This architecture provides several advantages over the traditional SFRA approach.
Why headless. Headless architecture enables frontend teams to use modern development tools and frameworks (React, Vue, Next.js) rather than Commerce Cloud's proprietary ISML templates. It provides better performance through static site generation, edge rendering, and aggressive caching that is difficult to achieve with server-side rendered SFRA pages. Headless enables omnichannel commerce — the same backend APIs can power a website, a mobile app, an in-store kiosk, and a voice commerce application. It also enables independent deployment cycles — the frontend team can deploy UI changes without a Commerce Cloud deployment, and the backend team can update business logic without affecting the frontend.
PWA Kit. Salesforce's PWA Kit is the recommended headless storefront framework for Commerce Cloud. It provides a React-based progressive web application with server-side rendering for SEO and performance, pre-built retail React components for product listings, product detail pages, cart, checkout, and account management, integration with Commerce Cloud's Shopper APIs (SCAPI) for product data, search, pricing, promotions, and order management, hosting on Salesforce's Managed Runtime platform with CDN-based edge delivery, and built-in support for offline capabilities, push notifications, and home screen installation that PWA technology enables.
Composable Storefront. Salesforce's Composable Storefront vision extends beyond PWA Kit to a fully modular architecture where every storefront capability — search, cart, checkout, recommendations — is a composable service that can be replaced or customized independently. This composability enables best-of-breed strategies where you might use Algolia for search, Stripe for payments, and Commerce Cloud for catalog and order management, all composed into a seamless storefront experience.
B2B Commerce Cloud
B2B Commerce is fundamentally different from B2C. Business buyers do not browse and impulse-purchase. They have purchase orders, negotiated contracts, approval hierarchies, and procurement systems. B2B Commerce Cloud is built on the core Salesforce platform, which gives it native access to accounts, contacts, opportunities, CPQ, and the full Salesforce data model — a significant advantage for B2B scenarios where the buying process involves multiple stakeholders and CRM context matters.
Account-based experiences. B2B Commerce displays different catalogs, pricing, and promotions to different accounts. A distributor might see wholesale pricing and bulk packaging while a direct enterprise customer sees volume-discounted list pricing and standard packaging. Account hierarchies support parent-child relationships where a corporate headquarters places orders on behalf of regional offices, with visibility and approval controls at each level. Buyer groups define which users within an account can browse, which can add to cart, and which can place orders.
Contract and negotiated pricing. B2B Commerce integrates with Salesforce CPQ to honor negotiated contract prices. When a buyer logs in, they see prices that reflect their specific contract terms rather than list prices. Price books can be assigned at the account, buyer group, or individual user level. Volume discounts, tiered pricing, and promotional pricing layer on top of contracted base prices. This pricing complexity is a core B2B requirement that B2C platforms cannot handle natively.
Reorder and quick order. B2B buyers frequently reorder the same products. B2B Commerce provides reorder functionality that lets buyers view their order history and reorder with a single click. Quick Order enables buyers to enter product SKUs and quantities directly without browsing the catalog — essential for procurement professionals who know exactly what they need. CSV upload allows buyers to upload a spreadsheet of SKUs and quantities, creating a cart from a purchase order document.
Checkout and approval workflows. B2B checkout is more complex than B2C. It may require purchase order numbers, cost center allocations, shipping to multiple addresses in a single order, and approval from a procurement manager before the order is submitted. B2B Commerce supports configurable checkout flows that match the buyer's procurement process. Orders that exceed a threshold can be automatically routed for internal approval before being sent to the seller for fulfillment.
Order Management System
Salesforce Order Management (SOM) handles everything that happens after a customer clicks "Place Order." It orchestrates the fulfillment lifecycle — routing orders to the optimal fulfillment location, managing payment capture, coordinating shipping, and processing returns and exchanges.
Order routing. SOM's order routing engine determines which fulfillment location handles each item in an order. For retailers with multiple warehouses and stores, routing considers inventory availability at each location, proximity to the shipping address (minimizing shipping cost and transit time), fulfillment capacity and workload at each location, and fulfillment cost (shipping from a store versus a distribution center). Orders can be split across multiple locations when no single location has all items in stock.
Fulfillment flows. SOM uses visual flow-based configuration for fulfillment processes. Standard flows handle the common sequence: allocate inventory, capture payment, create shipment, generate shipping label, confirm shipment, and send shipping notification. Custom flows handle exceptions: partial fulfillment when some items are backordered, hold orders for fraud review, split payment across multiple methods, and manage pre-orders that ship on a future date.
Returns and exchanges. Returns processing in SOM supports return merchandise authorization (RMA) generation, multiple return reasons with configurable business logic for each, refund processing (original payment method, store credit, or exchange), restocking logic that returns inventory to available stock, and appeasement workflows for customer satisfaction gestures like partial refunds or discount codes. Service Cloud agents can initiate returns and exchanges directly from the Service Console, providing a unified customer support experience.
Einstein for Commerce
Einstein AI capabilities in Commerce Cloud provide product recommendations, predictive sorting, and commerce insights that drive higher conversion rates and average order values.
Product recommendations. Einstein Product Recommendations analyze purchase history, browsing behavior, and product attributes to generate personalized product suggestions. Recommendation types include "customers who bought this also bought," "recently viewed," "trending products," "new arrivals for you," and "complete the look." Recommendations appear on product detail pages, cart pages, home pages, and post-purchase confirmation emails. Einstein requires historical transaction data to train its models — typically 3-6 months of order data for accurate recommendations.
Predictive sort. Einstein Predictive Sort personalizes the order of products on category and search result pages for each individual shopper. Instead of showing products in a fixed merchandising order, Einstein reranks products based on each shopper's likelihood to purchase, considering their browsing history, demographic signals, and the purchase patterns of similar shoppers. Predictive sort typically improves conversion rates by 5-15% on category pages without any manual merchandising effort.
Commerce insights. Einstein Commerce Insights provides dashboards that reveal shopping behavior patterns: which products are frequently bought together (informing bundling strategies), which products have high browse-to-cart rates but low cart-to-purchase rates (indicating pricing or checkout friction), and which search terms return no results (identifying catalog gaps or search configuration issues).
"The biggest mistake in commerce platform selection is choosing based on features. Every major platform has product catalogs, carts, and checkout. What matters is how well the platform integrates with your existing systems, how easily your team can customize and maintain it, and whether the architecture supports your growth trajectory for the next five years."
— Karan Checker, Founder, ESS ENN Associates
Commerce Cloud Integration Patterns
A Commerce Cloud storefront does not operate in isolation. It integrates with payment processors, tax calculation engines, shipping carriers, ERP systems, PIM (Product Information Management) systems, and marketing platforms. The integration architecture determines both the customer experience and the operational efficiency of your commerce operation.
Payment integration. Commerce Cloud supports payment processing through Link Cartridges — pre-built integration packages for major payment providers including Stripe, Adyen, PayPal, CyberSource, and Worldpay. Link Cartridges handle payment authorization during checkout, settlement and capture during fulfillment, refund processing for returns, and tokenization for stored payment methods. For B2B Commerce, payment integration extends to purchase order processing, credit term management, and invoice-based payment.
ERP integration. Commerce-ERP integration typically synchronizes product catalog and inventory data from the ERP to Commerce Cloud, pushes orders from Commerce Cloud to the ERP for fulfillment, retrieves order status and tracking information from the ERP, and synchronizes customer account data bidirectionally. For detailed ERP integration patterns, refer to our Salesforce integration services guide.
Search and merchandising. While Commerce Cloud includes native search powered by Einstein, many retailers implement third-party search solutions like Algolia, Bloomreach, or Coveo for advanced search capabilities. These solutions provide AI-powered search relevancy, visual search, natural language processing, and sophisticated merchandising rules that go beyond Commerce Cloud's native capabilities. Integration typically replaces the search index and query processing while maintaining Commerce Cloud as the system of record for product data.
Performance and SEO
E-commerce performance directly impacts revenue. Research consistently shows that each additional second of page load time reduces conversion rates by 7-10%. Commerce Cloud performance optimization spans both frontend and backend considerations.
Frontend performance. Minimize JavaScript bundle sizes, optimize image delivery using responsive images and modern formats (WebP, AVIF), implement lazy loading for below-the-fold content, and leverage browser caching aggressively. For SFRA, use the built-in page caching mechanisms. For headless PWA Kit storefronts, the Managed Runtime provides CDN-based edge caching that serves pages from locations closest to the customer.
SEO for commerce. Commerce Cloud provides SEO-friendly URL structures, customizable meta tags, canonical URL management, XML sitemap generation, and structured data markup (JSON-LD) for products, reviews, and breadcrumbs. For headless storefronts, server-side rendering via PWA Kit ensures that search engine crawlers see fully rendered pages. Implement product schema markup for rich search results, manage faceted navigation to prevent duplicate content, and configure robots.txt and noindex directives for filter pages and session-dependent URLs.
Frequently Asked Questions
What is the difference between Salesforce B2C Commerce and B2B Commerce?
B2C Commerce (formerly Demandware) is designed for direct-to-consumer retail with high-volume transaction processing, product catalogs, promotions, and Einstein product recommendations. It runs on its own infrastructure. B2B Commerce is built on the core Salesforce platform and handles business purchasing with account-specific pricing, contract pricing, bulk ordering, approval workflows, and CPQ integration. B2C handles high-volume consumer transactions. B2B handles lower-volume, high-value transactions with complex buying processes.
What is SFRA and how does it differ from headless commerce?
SFRA (Storefront Reference Architecture) is a server-side rendered storefront framework using JavaScript controllers and ISML templates rendered on Commerce Cloud servers. Headless commerce decouples the frontend — the Commerce Cloud backend provides APIs while the frontend is built with React, Vue, or Next.js and hosted independently. PWA Kit is Salesforce's recommended headless framework. SFRA offers faster time to market. Headless offers more frontend flexibility, better performance through edge rendering, and the ability to use modern JavaScript frameworks.
How does Salesforce Order Management work with Commerce Cloud?
Salesforce Order Management handles the post-purchase lifecycle. When a customer places an order on Commerce Cloud, it flows to SOM where routing logic determines the optimal fulfillment location, payment is captured, and shipping is initiated. SOM supports split shipments, partial cancellations, returns, exchanges, and appeasements. Built on the core Salesforce platform, it integrates natively with Service Cloud so agents can manage orders directly within their support console.
What is the PWA Kit for Salesforce Commerce Cloud?
PWA Kit is Salesforce's headless commerce framework providing a React-based progressive web app. It includes pre-built retail components, server-side rendering via Managed Runtime hosting, integration with Commerce Cloud Shopper APIs, and support for SEO, performance optimization, and mobile responsiveness. Managed Runtime provides CDN-based edge rendering for fast global performance. The composable architecture enables customization while maintaining upgrade compatibility.
How much does Salesforce Commerce Cloud cost?
B2C Commerce is typically priced as 1-3% of GMV with a minimum annual commitment. B2B Commerce starts around $48,000 per year for the Growth edition. Order Management has separate licensing based on order volume. Implementation costs range from $100,000-300,000 for standard B2C, $50,000-150,000 for B2B, and $200,000-500,000+ for complex multi-brand deployments. Ongoing costs include hosting, third-party integrations, and managed services.
For organizations building a commerce strategy alongside CRM, our Salesforce implementation guide covers the broader platform methodology. If your commerce platform needs complex pricing, our CPQ implementation guide covers pricing automation for B2B scenarios.
At ESS ENN Associates, our Salesforce consulting services team has built commerce solutions for retail, manufacturing, and distribution companies. If you need an e-commerce platform that integrates with your CRM, ERP, and marketing systems, contact us for a free technical consultation.
Ready to Build Your Commerce Platform?
From B2C storefronts and headless PWA Kit to B2B Commerce and Order Management — our certified Salesforce consultants build commerce experiences that convert. 30+ years of IT services. ISO 9001 and CMMI Level 3 certified.
