Salesforce Commerce Cloud Setup Playbook: Build, Launch, and Scale Your Store

A Salesforce Commerce Cloud implementation is more than creating product pages and enabling checkout. A production commerce platform has to coordinate catalogs, pricing, inventory, payments, fulfillment, customer data, content, integrations, security, and storefront performance.

Salesforce currently refers to Commerce Cloud as Agentforce Commerce, although Salesforce applications and documentation still contain Commerce Cloud terminology. For search intent and familiarity, this playbook uses Salesforce Commerce Cloud throughout.

The first architectural decision is understanding which Salesforce commerce product you are implementing.

Salesforce B2C Commerce Cloud supports enterprise direct-to-consumer commerce experiences across storefronts, products, promotions, and checkout. It runs in Salesforce B2C Commerce realms with separate development, staging, and production infrastructure and is administered largely through Business Manager.

B2B Commerce, by contrast, runs directly on the Salesforce Platform and is managed through the Commerce application in a Salesforce org.  

A typical implementation can include storefront architecture, product catalogs, pricing, inventory, promotions, checkout, payments, integrations, search, personalization, security, testing, launch planning, and post-launch optimization.

This playbook takes those decisions from initial requirements through launch and scale.

Implementation note: Sections referring to Business Manager, realms, B2C instances, SFRA, Composable Storefront, PWA Kit, and Storefront Next apply specifically to B2C Commerce. B2B Commerce follows a Salesforce-org-based setup model.

Define Your Commerce Requirements Before Setting Up Salesforce Commerce Cloud

Commerce architecture should start with the business model and customer journey—not configuration screens.

Define Your Business Model

Identify the selling model before deciding how stores, catalogs, pricing, and integrations should be structured.

B2C: High-volume consumer storefronts with individualized shopping experiences, promotions, merchandising, and checkout.

B2B: Authenticated business buyers, often with buyer accounts, negotiated or tiered pricing, larger order quantities, purchasing permissions, and repeat-order requirements. Salesforce describes B2B Commerce supports authenticated business buyers, buyer-specific product visibility through entitlements, negotiated pricing, purchasing permissions, and repeat-order requirements.

B2B2C: Organizations serving both business buyers and consumers may require separate experiences while sharing products, inventory, fulfillment, or customer data.

Multi-brand: Decide whether brands share catalogs, customer identities, infrastructure, and integrations or operate independently.

Multi-region: Plan localization, currencies, tax, payment providers, fulfillment, languages, and regional regulations early.

Marketplace considerations: Determine whether you sell only owned inventory or need third-party sellers, commissions, seller onboarding, or marketplace order orchestration.

The output should be a clear commerce operating model before storefront configuration begins.

Identify Core Commerce Requirements

Document what the commerce solution must support across the complete transaction lifecycle:

• Product catalog and taxonomy  
• Pricing and price books  
• Promotions and coupons  
• Inventory and availability  
• Customer accounts
• Cart and checkout  
• Payment methods
• Shipping  
• Tax  
• Order management  
• Returns and cancellations  

Classify each requirement as standard, configurable, integrated, or custom.

For example, a standard percentage discount should not require custom development, while a complex contract-pricing model or external inventory promise may require additional architecture.

Define Your Customer Experience Requirements

Translate the business model into shopper expectations.

Consider:

• Personalized product experiences  
• Search and navigation  
• Product recommendations  
• Loyalty  
• Omnichannel journeys  
• Mobile commerce  
• Guest versus authenticated checkout  
• Account management  
• Accessibility  
• Localization  

Prioritize the moments that directly affect discovery, conversion, and repeat purchasing.

Establish KPIs

Define success before implementation so post-launch optimization has a baseline.

Typical commerce KPIs include:

Tie each KPI to a measurable baseline and post-launch target rather than treating launch itself as success.

Plan Your Salesforce Commerce Cloud Architecture

Architecture determines how easily the storefront can evolve when products, brands, countries, channels, or integrations increase.

Choose Your Commerce Cloud Architecture

For B2C Commerce, storefront architecture is a major early decision.

Storefront Reference Architecture (SFRA) provides a Salesforce reference storefront and MVC-based development model. Salesforce still supports SFRA, while newer storefront approaches provide more composable options.  

Composable Storefront separates the storefront experience from the commerce backend. It uses PWA Kit, React, Salesforce Commerce APIs, and Managed Runtime. This approach provides greater flexibility to combine Salesforce with other search, CMS, or commerce technologies. For organizations evaluating headless Salesforce Commerce Cloud, Composable Storefront provides a decoupled storefront using PWA Kit, React, Managed Runtime, and Salesforce Commerce APIs.

Storefront Next is Salesforce's newer B2C storefront architecture and became generally available in June 2026. It uses modern technologies including React 19 and React Router 7 with server-side rendering and integrates with Managed Runtime.  

Architecture selection should consider:

• Required customization  
• Existing storefront investment  
• Development skills  
• Performance goals  
• Upgrade strategy  
• Content-management requirements  
• Third-party technologies  
• Long-term maintainability  

Avoid choosing headless or composable architecture simply because it is newer. Use it where decoupling and frontend flexibility solve a real requirement.

Design the Commerce Ecosystem

The storefront rarely operates alone.

Map how Commerce Cloud exchanges data with:

• CRM: accounts, contacts, customer context, sales or service activity ‍
• ERP: products, costs, inventory, financial data ‍
• OMS: order routing, fulfillment, cancellation, returns ‍
• PIM: product attributes and enriched product content ‍
• Payment gateways: authorization, capture, refund ‍
• Tax platforms: tax calculation and jurisdiction rules ‍
• Shipping providers: rates, delivery options, tracking ‍
• Marketing automation: campaign and engagement data ‍
• Customer service: order and shopper context ‍
• Analytics: commerce and behavioral data

For every connection, define:

System of record → Data direction → Frequency → Volume → Failure handling → Reconciliation

This prevents architecture from becoming a collection of unrelated point-to-point integrations.

Plan Data Architecture

Identify ownership for the main commerce domains:

Define identifiers and synchronization rules before integrations are built.

Set Up Your Salesforce Commerce Cloud Environment

Set Up Your Commerce Cloud Account

Provision the appropriate Salesforce Commerce product, organizations, users, stores/sites, and required environments.

For B2C Commerce, users commonly work across Account Manager, Control Center, Business Manager, and storefront development tooling, depending on their responsibilities.

For B2B Commerce, setup occurs within a Salesforce org using the Commerce application and associated permissions.

Configure Development, Staging, and Production Environments

B2C Commerce has distinct instance types.

Salesforce documents four major types: Sandbox, Staging, Development, and Production. Staging is commonly used for merchandising work, Development for final testing of code and content interaction, Production for live transactions, and sandboxes for development work.  

Keep environments separated so unfinished code, test data, or configuration changes do not affect the live storefront.  

Development typically starts in sandboxes. In the Primary Instance Group, approved code and commerce data are prepared in Staging, replicated to Development for final validation where appropriate, and then replicated to Production.

Composable and Storefront Next implementations also use Managed Runtime environments for storefront deployments.

Configure Roles and Permissions

Define access according to responsibilities:

• Administrators  
• Merchandisers  
• Developers  
• Content managers  
• Business users  

B2C Commerce supports role-based access control in Business Manager. Salesforce recommends granting users access only to the modules required for their job and following least-privilege principles.  

For example, a merchandiser may need catalog, pricing, promotion, and search access but should not automatically receive development or organization-administration permissions.

Configure Business Manager

For B2C Commerce, Business Manager is the central administration environment for commerce operations.

Depending on permissions, teams can use it to manage:

• Catalogs  
• Products  
• Pricing  
• Promotions  
• Content  
• Orders  
• Customers  
• Sites  
• Search  
• Inventory  
• Configuration  

Salesforce describes Business Manager as the command center for B2C Commerce merchandising, administration, and site-development capabilities.  

Keep module access role-specific rather than giving every commerce user administrator permissions.

Configure Site and Locale Settings

For regional storefronts, define:

• Countries  
• Languages  
• Currencies  
• Time zones  
• Regional storefronts  
• Locale fallback  
• Regional formatting  

B2C Commerce supports organization-level and site-level locales. Only activated locales are available to storefronts, and individual sites can define allowed and default locales.  

Do not treat localization as translation alone. Pricing, currency, tax, fulfillment, product availability, content, legal notices, and payment options may all differ by market.

Configure Your Product Catalog and Commerce Data

Build Your Product Catalog

Create a catalog structure that makes sense to both shoppers and merchandisers.

Configure:

• Categories  
• Products  
• Product variations  
• Product attributes  
• Bundles  
• Sets  
• Product relationships  

Keep the distinction between merchandising categories and underlying product data clear.

Avoid deeply nested category structures simply because the source ERP or PIM has the same hierarchy. Storefront navigation should reflect how customers shop.

Configure Pricing

Plan:

• Price books  
• Customer-group or personalized pricing where applicable  
• Regional pricing  
• Currency  
• Sale pricing  
• Effective dates  

In B2C Commerce, price books define product prices and can be assigned to one or more storefronts. Price books are organization-level entities, and Salesforce supports relationships between price books so a sale price book can inherit missing prices from a base book.  

B2B implementations may require buyer-specific or negotiated pricing and should model those requirements separately.

Configure Inventory

Determine how Commerce Cloud receives and presents product availability.

Configure:

• Inventory lists  
• Availability rules  
• Multiple locations where applicable  
• Safety stock  
• Inventory synchronization  
• Out-of-stock behavior  

Define whether inventory must be real-time, near-real-time, or periodically synchronized.

A storefront showing inventory that is technically accurate but several hours old may still create overselling during high-volume periods.

Configure Promotions

Common promotion models include:

• Percentage discounts  
• Fixed discounts  
• Buy-one-get-one  
• Free shipping  
• Coupon codes  
• Customer-segment promotions  

Before building custom promotion logic, verify whether native promotion capabilities already support the requirement.

Also define promotion precedence, exclusions, stacking rules, eligibility, and start/end dates so overlapping campaigns do not produce unexpected discounts.

Build and Customize the Salesforce Commerce Cloud Storefront

A strong Salesforce Commerce Cloud development approach combines native commerce capabilities with custom development only where the storefront experience or business requirements demand it.

Choose Your Storefront Approach

Choose between the supported architecture options based on the decisions made earlier.

For B2C implementations, current options can include:

• SFRA  
• Composable Storefront with PWA Kit  
• Storefront Next  
• Hybrid migration approaches  

Storefront Next is now a current production option rather than a future architecture. Salesforce made version 1.0 generally available in June 2026.  

For a new implementation, evaluate the requirements and Salesforce roadmap instead of automatically reproducing the architecture of an older storefront.

Design the Customer Journey

Map the critical shopper flow:

Landing → Search/Browse → Product Detail → Cart → Checkout → Confirmation → Post-Purchase

Also design secondary journeys such as:

• Login and registration  
• Wishlist  
• Password recovery  
• Returns  
• Reordering  
• Order tracking  
• Customer service  
• Store pickup  

Prioritize friction reduction at high-intent stages such as PDP, cart, and checkout.

Customize Storefront Components

Create reusable components rather than hard-coding each campaign page.

For B2C Commerce, Page Designer lets developers create reusable page and component types that merchants can later arrange, schedule, and publish through Business Manager.  

Storefront Next also integrates Page Designer with React-based components, allowing merchants to manage storefront content without requiring a developer for every content change.  

Separate reusable commerce behavior from campaign-specific content wherever possible.

Optimize for Mobile

Treat mobile as a core storefront, not a reduced desktop experience.

Focus on:

• Responsive navigation  
• Touch-friendly controls  
• Simplified forms  
• Fast image delivery  
• Clear product information  
• Minimal checkout friction  
• Wallet-friendly payment flows  
• Core Web Vitals  

Performance and usability should be tested on actual mobile devices and realistic networks, not only desktop browsers.

Configure Commerce Cloud Integrations

A well-designed Salesforce Commerce Cloud integration strategy defines the system of record, synchronization direction, latency, error handling, and reconciliation for every connected platform.

ERP Integration

ERP integration commonly exchanges:

• Products  
• Pricing  
• Inventory  
• Customers  
• Orders  
• Financial status  

Define which platform owns each field and how failures are retried and reconciled.

CRM Integration

Connect Commerce Cloud to CRM when sales, service, or customer-success users need commerce context.

Examples include:

• Customer profile synchronization  
• Order visibility  
• Cases linked to orders  
• Account context  
• B2B buyer information  

Avoid copying every commerce event into CRM simply because the integration exists.

OMS Integration

Order Management becomes critical after checkout.

Define responsibilities for:

• Order routing  
• Fulfillment  
• Inventory allocation  
• Cancellations  
• Returns  
• Refunds  
• Order status  

Commerce Cloud should know which system owns the order after placement.

Payment Integration

Payment architecture should define:

• Payment service provider  
• Authorization  
• Capture  
• Refund  
• Tokenization  
• Failure handling  
• Fraud controls  
• Supported payment methods  

Sensitive payment data should remain within supported secure payment architectures rather than being stored unnecessarily in custom commerce data.

Shipping and Tax Integrations

Determine whether shipping and tax calculations are native, externally provided, or a combination.

Test:

• Shipping methods  
• Multiple destinations  
• Rate failures  
• Regional restrictions  
• Tax-exempt scenarios  
• Discounts affecting tax  
• Cross-border orders  

Marketing and Analytics Integrations

Connect commerce events with marketing and analytics only after defining the business questions those platforms must answer.

Useful events can include:

• Product views  
• Search  
• Add-to-cart  
• Checkout progression  
• Purchase  
• Abandonment  

Salesforce provides Data 360 connectors for B2C Commerce data and storefront engagement events, enabling commerce behavior to be incorporated into broader Salesforce data use cases.  

Configure Search, Personalization, and Merchandising

Configure Site Search

Search affects product discovery directly.

Configure:

• Searchable attributes  
• Synonyms  
• Stop words  
• Search suggestions  
• Sorting  
• Redirects  
• Zero-result handling  

B2C Commerce also provides Einstein-powered search recommendations that can offer AI-driven type-ahead suggestions, autocorrection, and term completion.  

Monitor actual shopper queries after launch rather than assuming the initial dictionary is complete.

Configure Merchandising

Give merchandising teams controlled tools to influence:

• Product ranking  
• Category placement  
• Campaign content  
• Promotions  
• Recommendations  
• Seasonal products  
• New arrivals  
• Inventory-sensitive presentation  

Business users should be able to operate routine merchandising without requiring a development deployment.

Implement Personalization

Personalization can use context such as shopper behavior, purchase history, product affinity, or audience membership.

B2C Commerce Einstein Product Recommendations supports recommenders and strategies that predict relevant products for shoppers and can be placed across storefront surfaces such as PDPs, carts, category pages, and checkout.  

Start with a measurable personalization use case rather than personalizing every component.

Connect Commerce With Salesforce Data and AI

Connect commerce data with the broader Salesforce ecosystem where it improves decisions or customer experiences.

Potential use cases include:

• Data 360 customer profiles  
• Commerce engagement events  
• Salesforce CRM context  
• Product recommendations  
• Service experiences  
• Agentforce-assisted commerce  

Keep customer identity, consent, data freshness, and system-of-record rules clear as more platforms share customer information.

Implement Security, Performance, and Scalability

Salesforce Commerce Cloud Security

Apply least privilege to business users, developers, service accounts, and integrations.

For B2C Commerce:

• Assign role-specific Business Manager permissions.  
• Protect non-production storefronts.  
• Secure API clients and secrets.  
• Restrict administrative access.  
• Review third-party integrations.
• Use supported authentication mechanisms.  

Salesforce's B2C authorization model is deny-by-default for newly created Business Manager users: users receive no operational permissions until roles are explicitly assigned.  

Performance Optimization

Performance should be measured throughout development.

Review:

• Page rendering  
• Images and assets  
• API latency  
• Third-party scripts  
• Cache behavior  
• Search response  
• Checkout dependencies  
• Mobile performance  

For composable storefronts, Managed Runtime provides CDN and caching capabilities, while Salesforce's server-side rendering architecture is designed to improve initial page performance.

Design for Scalability

Design for expected peak traffic rather than average traffic.

Consider:

• Seasonal peaks  
• Flash sales  
• Product launches  
• Promotion spikes  
• API throughput  
• Payment-provider capacity  
• ERP/OMS capacity  
• Inventory synchronization  
• Third-party rate limits  

Salesforce provides dedicated sale-event preparation guidance covering traffic estimation, platform configuration, external-service readiness, and real-time monitoring.  

The storefront is only as scalable as its weakest dependency.

Test Your Salesforce Commerce Cloud Store Before Launch

Functional Testing

Validate complete business flows:

• Search  
• Product selection  
• Promotions  
• Cart  
• Checkout  
• Payment  
• Account management  
• Orders  
• Returns  

Test negative and boundary scenarios not only happy paths.

Integration Testing

Test every integration across success and failure conditions.

Verify:

• Authentication  
• Retry behavior  
• Duplicate prevention  
• Data mapping  
• Error logging  
• Reconciliation  

Performance Testing

Test expected and peak traffic levels with realistic workloads.

Include third-party services because payment, tax, search, shipping, and external APIs can become bottlenecks even when Commerce Cloud itself performs well.

Security Testing

Review:

• Authentication  
• Authorization  
• Administrative permissions  
• API security  
• Input handling  
• Session behavior  
• Secrets  
• Payment flows  
• Third-party scripts  

Cross-Browser and Device Testing

Cover supported browsers, major mobile devices, breakpoints, and representative network conditions.

PWA Kit documentation, for example, defines supported browser versions across Android, iOS, macOS, and Windows.  

User Acceptance Testing

UAT should involve actual commerce stakeholders:

• Merchandisers  
• Customer service  
• Operations  
• Marketing  
• Fulfillment  
• Finance  
• Business owners  

Test both shopper experiences and back-office commerce operations.

Prepare for Salesforce Commerce Cloud Launch

Create a Go-Live Checklist

Include:

• Domain and DNS  
• SSL  
• Production configuration  
• Catalog  
• Price books  
• Inventory  
• Promotions  
• Payments  
• Tax  
• Shipping  
• Integrations  
• Analytics  
• Monitoring  
• Support ownership  

For the first B2C Commerce site in a realm, Salesforce currently requires a Go-Live Support case at least five business days before launch and requires completion of its Go-Live checklist.  

Data Migration Validation

Reconcile:

• Products  
• Categories  
• Prices  
• Inventory  
• Customers where applicable  
• Content  
• Redirects  
• Historical data  

Validate totals and relationships, not just whether import jobs completed.

Final Integration Validation

Perform end-to-end production-readiness tests covering ERP, OMS, payments, tax, shipping, CRM, analytics, and marketing systems.

Confirm production credentials and URLs rather than relying on staging configuration.

Backup and Rollback Planning

Document what happens if launch must be reversed.

Define:

• Previous storefront/code version  
• Data recovery approach  
• Integration rollback  
• DNS or routing reversal  
• Feature-disable options  
• Decision authority  

Composable storefront deployments use immutable bundles, making prior versions identifiable for troubleshooting and deployment management.  

Launch-Day Monitoring

Create a launch command center covering:

• Traffic  
• Errors  
• Page performance  
• Search  
• Cart  
• Checkout  
• Payment failures  
• Inventory  
• Order flow  
• Integration failures  

Agree on escalation paths before the first shopper arrives.

Launch Your Store and Monitor Performance

After launch, monitor both technical stability and commercial outcomes.

Track:

Technical

• Availability  
• Page response  
• API failures  
• Payment errors  
• Integration jobs  
• Search performance  

Commerce

• Conversion  
• Cart abandonment  
• Average order value  
• Orders  
• Revenue  
• Search conversion  
• Payment success  

Customer experience

• Support requests  
• Checkout issues  
• Search failures  
• Mobile usability  
• Returns  

Avoid making large optimization changes immediately unless production data clearly identifies a problem.

Establish the baseline first.

Optimize and Scale Your Salesforce Commerce Cloud Store

Improve Conversion Rates

Analyze where shoppers leave the journey.

Test changes to:

• Product information  
• CTAs  
• Promotions  
• Trust signals  
• Recommendations
• Cart  
• Checkout  

Optimize one measurable problem at a time.

Optimize Search and Product Discovery

Review:

• Zero-result searches  
• Low-converting searches  
• Misspellings  
• Synonyms  
• Filters  
• Sorting  
• Recommendations  

Search behavior is valuable merchandising data, not simply a technical function.

Improve Checkout

Reduce unnecessary steps and fields.

Monitor:

• Checkout abandonment  
• Payment failures  
• Address validation  
• Shipping selection  
• Authentication friction  

Storefront Next, for example, now includes capabilities aimed at simplifying repeat checkout through saved shipping/payment details and verification-based login.  

Expand to New Markets

Before adding a country or region, evaluate:

• Locale  
• Currency  
• Catalog  
• Pricing  
• Tax  
• Shipping  
• Payments  
• Inventory  
• Legal requirements  
• Content  
• Customer support  

Do not assume a translated storefront is a market-ready storefront.

Add New Commerce Capabilities

Future roadmap items may include:

• Loyalty  
• Subscriptions  
• Additional payment methods  
• New fulfillment models  
• Marketplace capabilities  
• Store inventory  
• AI-assisted shopping  
• New customer-service experiences  

Add capabilities through the same architecture and governance process used during initial implementation.

Establish Continuous Optimization

Create a recurring commerce roadmap.

A useful cycle is: Measure → Identify friction → Prioritize → Test → Release → Measure again

Balance:

• Revenue improvements  
• Customer experience  
• Technical debt  
• Platform upgrades  
• Security  
• Performance  
• Merchant productivity  

Commerce implementation never truly ends at go-live.

Common Salesforce Commerce Cloud Implementation Challenges

Common problems include:

1. Choosing architecture too early: Selecting headless or composable architecture before requirements are understood can add unnecessary complexity. ‍
2. Poor product data: Incomplete attributes and inconsistent taxonomy weaken navigation, search, personalization, and merchandising. ‍
3. Underestimating integration: ERP, inventory, tax, payments, and OMS frequently consume more implementation effort than storefront pages. ‍
4. Over-customizing native capabilities: Custom pricing, promotion, or checkout code increases maintenance when Salesforce functionality already meets the requirement. ‍
5. Weak environment discipline: Making configuration directly in production introduces avoidable risk. ‍
6. Ignoring peak traffic: Average performance is not enough for holiday traffic, flash sales, or major product launches. ‍
7. Treating launch as completion: Conversion, search, performance, merchandising, and customer behavior require continuous optimization.

Salesforce Commerce Cloud Implementation Best Practices

Use these principles throughout the implementation:

1. Define the commerce operating model first. Know whether you are solving B2C, B2B, multi-brand, multi-region, or a combination.  ‍
2. Separate B2C and B2B architecture decisions. They are Salesforce Commerce products, but they do not run on identical underlying architectures.  ‍
3. Choose storefront architecture deliberately. Evaluate SFRA, Composable Storefront, Storefront Next, and hybrid approaches according to business requirements.  ‍
4. Define systems of record. Product, price, customer, inventory, and order ownership should never be ambiguous.  ‍
5. Use native commerce functionality before custom code. Customize where differentiation or requirements justify it.  ‍
6. Make merchandising self-service. Routine catalog, promotion, and content changes should not require developer releases.  ‍
7. Build integration failure handling from day one. Logging, retries, idempotency, and reconciliation are production requirements.  ‍
8. Design security around least privilege. Separate administrators, developers, merchandisers, and operational users.  ‍
9. Test with realistic volume. Include downstream platforms and third-party services in performance planning.  ‍
10. Optimize continuously after launch. Use actual customer and commercial data to guide improvements.  

‍