Salesforce Commerce Cloud
Salesforce Commerce Cloud (B2C Commerce, formerly Demandware) is the platform of choice for mid-to-large enterprise retailers who need multi-site architecture, robust out-of-the-box commerce capabilities, and deep integration with the Salesforce ecosystem - Service Cloud, Marketing Cloud, Einstein personalization, and CDP. The platform's managed cloud infrastructure, Einstein Einstein Commerce Intelligence, and LINK cartridge marketplace reduce the custom development burden for common enterprise needs.
Axevate's SFCC experience spans SFRA (Storefront Reference Architecture) implementations, LINK cartridge development and integration, multi-site and multi-locale configurations, Business Manager administration, and the full range of third-party integrations that enterprise retail requires. We've delivered payment integrations (Braintree, CyberSource, Klarna, Global-E), analytics platforms (Tealium, GTM), and operational tools (Ordergroove, Bazaarvoice) on top of SFCC for Fortune 500 clients.
1SFCC Architecture: SFRA and the Controller Model
SFRA (Storefront Reference Architecture) is the current development framework for SFCC storefronts. It replaced the older SiteGenesis architecture with a modular, component-based approach: controllers handle route logic, templates render views, and models encapsulate business logic. Customizations extend SFRA rather than modifying core files directly - a principle that's easy to understand but requires discipline to maintain, especially in large teams or after agency transitions.
The controller pattern uses a pipeline-style request/response flow. Custom controllers extend base controllers, hooking into the pipeline at defined extension points. The SFRA cartridge path determines which version of a controller or template is used for a given request - cartridges earlier in the path take precedence. Understanding cartridge path management is fundamental to SFCC development; incorrect configuration is one of the most common sources of unexpected behavior.
Business Manager is the administration interface for SFCC: site configuration, catalog management, promotion setup, A/B test configuration, job scheduling, and log access. Developers interact with Business Manager constantly during implementation - for environment configuration, data imports, and debugging. A working knowledge of Business Manager is required for effective SFCC development, not just client-side configuration.
2LINK Cartridge Integration
LINK is Salesforce's partner integration program. LINK cartridges are pre-built integrations for third-party services - payment processors, analytics platforms, email providers, loyalty programs - that follow a standard architecture and certification process. Hundreds of LINK cartridges exist, covering most of the integration needs a retailer has. Using a LINK cartridge rather than a custom integration typically saves 2-4 weeks of development time and provides a vendor-supported codebase.
However, LINK cartridges vary significantly in quality. Some are mature, well-maintained, and well-documented. Others are outdated, poorly tested, or missing support for edge cases that the certification process didn't cover. Before committing to a LINK cartridge, we audit the code quality, review community feedback, verify compatibility with your SFCC version, and assess whether the cartridge handles your specific requirements or will need significant modification.
3Salesforce Ecosystem Integration
SFCC's integration with the broader Salesforce platform is a primary value driver for retailers already on Salesforce. Commerce Cloud connects natively with Service Cloud for unified customer service (order history, returns, account information in the agent console), Marketing Cloud for transactional and marketing email triggered by commerce events, and Einstein for product recommendations, search ranking, and customer segmentation.
CDP (Customer Data Platform) integration creates a unified customer identity across all Salesforce products. Commerce events (purchases, browse activity, cart abandonment) feed CDP, which distributes segments and attributes to Service Cloud and Marketing Cloud. Implementing this data flow correctly requires careful planning of data schemas, consent management, and PII handling - the integration is powerful but the implementation has meaningful complexity.
How We Use It in Practice
Real architectural problems across industries — and how we approach them.
SFCC + LangGraph AI Support Agent: Live Order Data with Service Cloud Write-Back
A luxury European retailer needed an AI customer service agent with access to live order data from SFCC (via SCAPI), the ability to open return cases in Service Cloud, and escalation logic that respected business hours, customer tier, and sentiment. Fixed workflow automation couldn't handle the branching complexity — sometimes the agent needed two tool calls, sometimes seven, with human review required for high-value customers and frustrated shoppers.
Our approach
LangGraph stateful workflow with a triage node (Claude Haiku classifies intent and customer tier), specialized tool nodes (SCAPI for order and return eligibility lookup, Service Cloud REST API for case creation), and a HITL interrupt before any write operation on orders exceeding 500 EUR value. PostgresSaver checkpointer so conversations resume across browser sessions and channel switches. A parallel sentiment node scores frustration level; if the score exceeds threshold, the escalation path is taken regardless of other routing rules. Customer-facing response latency: under 3 seconds for standard queries; HITL approval path adds 4-8 business hours but applies to less than 6% of cases.
SFCC Migration from SiteGenesis to SFRA: Incremental Cartridge Strategy
A fashion retailer operating 8 SFCC sites across 4 regions had a legacy SiteGenesis implementation with 6 years of accumulated customizations: 14 custom cartridges, 3 LINK cartridges on outdated versions, and significant inline customizations that violated SFCC's extension pattern. A big-bang migration to SFRA had been scoped at 18 months; the business couldn't absorb an 18-month feature freeze.
Our approach
Incremental migration using SFCC's ability to run SFRA and SiteGenesis cartridges in the same path: a new SFRA site was built in parallel, migrating high-traffic pages first (homepage, category, PDP) while legacy pages remained on SiteGenesis. LINK cartridges were upgraded to current versions one at a time in a separate sandbox, with custom overlay cartridges isolated so upgrades became diffs rather than re-implementations. After 9 months, all primary pages were on SFRA; the remaining account and checkout flows were migrated in months 10-12. The 8th site (lowest traffic) was cut over last. Feature releases continued throughout on the SFRA sites while legacy pages remained frozen — effectively reducing the business impact of the migration timeline by 60%.
SFCC Composable Storefront (PWA Kit) + Cloudflare Workers: Sub-50ms TTFB Globally
A multi-national retailer's SFCC SFRA storefront was delivering 1.8-second TTFB to customers in APAC and LATAM — their largest growth markets — due to the platform's primary data center being US-East. The business case for a full headless migration existed, but the 12-18 month PWA Kit timeline meant customers in growth markets would continue experiencing poor performance for over a year.
Our approach
Two-phase approach: Phase 1 deployed Cloudflare Workers as an edge caching and routing layer in front of the existing SFRA storefront, implementing aggressive stale-while-revalidate caching for category and product pages (80% of traffic). TTFB in APAC dropped from 1,800ms to 220ms for cached responses within 6 weeks of Phase 1 deployment. Phase 2 built out the SFCC PWA Kit (Composable Storefront) as the permanent solution, deployed on Cloudflare Pages with SCAPI as the commerce backend. The Phase 1 edge layer remained in place during Phase 2 development, so APAC performance improvements were retained throughout the PWA Kit build. Full PWA Kit go-live: 14 months from project start; global p95 TTFB: 45ms.
FAQ
SFCC remains the right choice for enterprise retailers with complex operational needs, existing Salesforce ecosystem investment (Service Cloud, Marketing Cloud, CDP), or requirements for multi-site, multi-locale architecture at scale. For brands that don't need these capabilities, Shopify Plus has closed the gap significantly and offers lower total cost of ownership. Platform selection depends on your specific operational requirements, existing technology investments, and team capabilities.
A new SFCC implementation with standard features and 10-15 integrations typically takes 5-9 months: 1-2 months for architecture and setup, 3-5 months for development, 1-2 months for QA and launch preparation. Complex multi-site implementations or those with heavy Salesforce ecosystem integration take longer. Timeline is driven primarily by integration complexity and content migration scope.
SiteGenesis is the legacy SFCC development framework. SFRA is the current standard with a more modular architecture, better mobile support, and active Salesforce investment. For any new SFCC implementation, build on SFRA. If you have an existing SiteGenesis implementation, migration to SFRA is a significant undertaking but may be worth planning if you're doing a major redesign or feature build.
Yes. SFCC exposes a SCAPI (Salesforce Commerce API) that enables headless storefronts - React or Next.js frontends that consume SFCC as a commerce backend. Salesforce's Composable Storefront (formerly PWA Kit) is the reference implementation. Headless on SFCC makes sense for the same reasons it does elsewhere: performance requirements that exceed the native storefront, or multi-channel consistency needs. It adds frontend infrastructure complexity and removes some SFCC out-of-the-box capabilities.