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.