Salesforce Certified B2C Solution Architect – Complete Winter '26 Guide

Solution Design for B2C Retail

B2C Solution Architects design solutions spanning Commerce Cloud (storefront), Marketing Cloud (email/journey), Service Cloud (support), and Order Management (fulfillment). The architect balances business requirements (conversion, retention, support cost) against technical constraints (API limits, data residency, licensing). Salesforce Customer 360 provides a unified identity across clouds via Marketing Cloud Personalization and Data Cloud. The exam presents complex multi-cloud business scenarios and tests which combination of products, connectors, and configuration choices best meets the requirements — know the capabilities and limits of each cloud.

Multi-Cloud Integration Patterns

Key B2C connectors: Commerce to Marketing Cloud Connector (syncs shopper data and triggers journeys), Commerce to Service Cloud Connector (links shopper profiles to cases), Order Management Connector (syncs orders to Salesforce OMS). Data flows: purchase events → Marketing Cloud → re-engagement journeys; support cases → Service Cloud → order lookup. Marketing Cloud Connect links core Salesforce objects to Marketing Cloud data extensions. Salesforce CDP/Data Cloud unifies identity across all clouds. The architect must know which connector to use, its data latency, and what to do when a connector doesn't support a required use case (custom integration via API).

Data Architecture & Customer Identity

B2C data architecture centers on the shopper profile: anonymous browser → registered account → unified customer identity. Commerce Cloud Customer record (online profile) maps to Marketing Cloud subscriber and Service Cloud Contact. Duplicate management prevents fragmented profiles when the same customer shops across channels. External ID fields align records across systems. Data Cloud resolves identity using deterministic (email match) and probabilistic rules. GDPR and CCPA compliance requires consent management, preference centers, and Right to Be Forgotten across all connected clouds. The exam tests how identity flows across clouds and what an architect designs to ensure a single coherent customer view.

Order Management & Fulfillment Architecture

Salesforce Order Management (SOM) handles post-purchase orchestration: order capture, payment settlement, fulfillment routing, returns, and refunds. The Order Summary object is the central record in SOM. Fulfillment flows route orders to the correct warehouse or drop-shipper based on inventory availability and shipping cost. Change Orders handle post-purchase modifications. Distributed Order Management (DOM) optimizes fulfillment location selection. Integration with WMS (Warehouse Management Systems) and ERP happens via API or MuleSoft. The exam tests how an architect designs the order-to-fulfillment flow, handles partial fulfillment scenarios, and integrates SOM with external warehouse systems.

Non-Functional Requirements & Governance

B2C solutions must be designed for scale: peak traffic (Black Friday), global reach (multi-language, multi-currency, multi-region), and high availability (99.99% uptime SLA). Caching strategy across CDN, application, and browser layers reduces load time and infrastructure cost. Disaster recovery design defines RPO (Recovery Point Objective) and RTO (Recovery Time Objective). Release management for B2C spans multiple clouds — changes must be coordinated across Commerce Cloud code deployments, Marketing Cloud journey updates, and Salesforce metadata deployments. The exam tests how an architect balances speed to market against risk, and how to structure a release governance model for a multi-cloud B2C platform.

Multi-Cloud B2C Journeys

Know how to design customer journeys that span SFCC (shopping), Marketing Cloud (engagement), Service Cloud (support), and Data Cloud (unified profile). Understand the data flows and integration touchpoints between each cloud.

Identity & Profile Unification

Know how Customer 360 identity unification works across B2C channels: matching on email, mobile, cookie, and loyalty ID. Understand how Data Cloud resolves identity across SFCC, Marketing Cloud, and Service Cloud.

Commerce-to-Marketing Integration

Know the integration between SFCC and Marketing Cloud: abandoned cart triggers, post-purchase confirmation emails, and how SFCC transaction data flows to Marketing Cloud for segmentation and retargeting.

Order Management Integration

Know how SFCC orders integrate with Salesforce Order Management: the Order On Behalf Of (OBO) pattern, order status sync, return/refund flows, and how Service Cloud agents access order data.

Architecture Trade-off Decisions

Solution Architect questions test trade-off reasoning: when to use a shared Salesforce org vs. separate, when to use Data Cloud vs. Marketing Cloud audiences for segmentation, and how to balance performance vs. data freshness.