SFCC (Salesforce Commerce Cloud) — The Complete Expert Guide

Written by Ozan Altinbas, Salesforce Commerce Cloud Technical Architect with 8+ years of SFCC experience, having led implementations for Karl Lagerfeld, Stella McCartney, Barbour, GameStop, and Ubisoft.

Salesforce Commerce Cloud (SFCC) is the enterprise eCommerce platform powering some of the world's most recognised retail brands. If you are evaluating SFCC, building on it, or hiring someone who knows it deeply — this is the most comprehensive, practitioner-written guide available.

---

What is SFCC?

Salesforce Commerce Cloud (SFCC) is a cloud-based enterprise eCommerce platform, originally built by Demandware and acquired by Salesforce in 2016. It powers online storefronts for hundreds of global brands across fashion, luxury, sporting goods, electronics, and more.

SFCC is not a one-size-fits-all platform. It is engineered for brands with complex requirements: multi-site operations, deep personalisation, high-volume traffic, international commerce, and sophisticated B2B workflows. The platform's strengths come at a cost — SFCC requires certified developers, has a steep learning curve, and carries a significant total cost of ownership.

Key facts:

• Originally called Demandware, acquired by Salesforce in 2016 for $2.8 billion
• Used by 500+ enterprise brands globally
• Revenue-share pricing model (typically 1–3% of GMV)
• Available as B2C Commerce Cloud and B2B Commerce Cloud
• Runs on Salesforce's global cloud infrastructure

---

SFCC Architecture Overview

Understanding SFCC architecture is essential for any developer or architect working on the platform.

The Cartridge System

The foundation of SFCC extensibility is the cartridge — a modular unit of code that extends or overrides platform functionality. Cartridges follow a path-based inheritance model defined in the cartridge path (configured per site in Business Manager).

When SFCC resolves a template or script, it searches cartridges from left to right along the cartridge path. The first match wins. This means custom cartridges override base cartridges without touching core platform code — enabling clean platform upgrades and reusable integrations.

Cartridge path example:
app_custom_mysite:plugin_wishlists:app_storefront_base

SFCC resolves app_custom_mysite first, then plugin_wishlists, then the base storefront. Any file present in app_custom_mysite overrides the equivalent in app_storefront_base.

Controllers and ISML

SFCC uses a controller-based MVC pattern:

• Controllers — JavaScript files that handle HTTP requests, orchestrate business logic, and render responses
• ISML templates — SFCC's server-side templating language (similar to JSP), used for HTML rendering
• Scripts — Reusable business logic modules, accessed via require()
• Models — Data access objects wrapping platform APIs

SFRA vs SiteGenesis

There are two front-end architectures in the SFCC ecosystem:

	SFRA	SiteGenesis
Status	Current (recommended)	Legacy (deprecated)
Architecture	Controller MVC	Pipeline-based
Mobile	Mobile-first, responsive	Desktop-first
Customisation	Cartridge override	Page-level override
New projects	Always use SFRA	Do not start new projects

All new SFCC implementations use SFRA (Storefront Reference Architecture). If you are maintaining a SiteGenesis site, migration to SFRA should be on your roadmap.

---

SFCC B2C vs B2B Commerce

Salesforce Commerce Cloud comes in two flavours:

B2C Commerce Cloud

The original and most widely deployed product. B2C Commerce powers consumer-facing storefronts — fashion, beauty, sporting goods, electronics, luxury. Key capabilities:

• Einstein AI product recommendations and predictive search
• Multi-site, multi-currency, multi-language management from a single instance
• SFRA storefront architecture
• Native promotions and coupon engine
• Order management integration
• A/B testing
• Page Designer (visual content management)

B2B Commerce Cloud

Built for manufacturer-to-distributor and wholesale commerce. B2B Commerce adds:

• Account hierarchies and buyer groups
• Contract-based and negotiated pricing
• Reorder lists and quick order entry
• Purchase approval workflows
• Complex order management (split shipments, partial fulfilment)
• ERP and procurement system integrations

For most of this guide, "SFCC" refers to B2C Commerce — the more widely deployed and more technically complex product.

---

SFCC APIs: OCAPI vs SCAPI

Two API systems govern how external applications interact with SFCC:

OCAPI — Open Commerce API

OCAPI is the legacy REST API for SFCC. It supports:

• Shop API (customer-facing: products, cart, checkout, orders)
• Data API (admin-facing: products, inventory, orders, promotions)
• Meta API (schema introspection)

OCAPI uses Basic Auth or OAuth 2.0 with client credentials. It remains widely used for back-office integrations, third-party tools, and legacy headless implementations.

SCAPI — Shopper Commerce API

SCAPI is the modern API introduced by Salesforce to replace OCAPI for shopper-facing operations. It improves on OCAPI in several critical ways:

• OAuth 2.0 PKCE — more secure token flow for public clients
• Shopper Login and API Access Service (SLAS) — unified identity layer
• Higher performance — purpose-built for storefront use cases
• Versioned endpoints — cleaner API lifecycle management

For new headless SFCC implementations, always use SCAPI. OCAPI remains the right choice for server-to-server Data API operations.

SCAPI base URL pattern:
https://{shortCode}.api.commercecloud.salesforce.com/checkout/shopper-baskets/v1/

---

SFCC Headless Commerce

Headless SFCC decouples the front-end from the back-end commerce engine. The storefront is a modern JavaScript application (React, Next.js, Vue) that communicates with SFCC exclusively through APIs.

Why Go Headless?

• Full control over front-end performance (Core Web Vitals, LCP, CLS)
• Modern developer experience (React ecosystem, npm, CI/CD)
• Composable architecture — swap components independently
• Better Lighthouse scores (headless implementations routinely hit 85+)
• Framework flexibility — host anywhere (Vercel, Netlify, custom CDN)

PWA Kit

Salesforce provides PWA Kit as the reference headless implementation for SFCC. It is a React-based storefront starter kit that:

• Uses SCAPI for all shopper operations
• Provides pre-built components for product pages, cart, checkout
• Integrates with Salesforce's CDN and managed runtime
• Supports server-side rendering for SEO

PWA Kit is the starting point for most new headless SFCC projects, though teams often replace or heavily customise its components.

Composable Commerce

Beyond headless, composable commerce takes the separation further — using best-of-breed services for each commerce capability (search, payments, promotions, content) and composing them via APIs. SFCC fits naturally into composable architectures as the commerce engine, with:

• Algolia or Salesforce Einstein Search for search
• Contentful or Amplience for content management
• Adyen or Stripe for payments
• Akeneo for product information management

---

SFCC Page Designer

Page Designer is SFCC's visual content management system. It allows merchandisers to build and publish page content through a drag-and-drop interface without developer involvement.

Developer responsibilities with Page Designer:

• Build page types — define the layout and available regions
• Build components — reusable content blocks (hero banners, product tiles, editorial grids)
• Define component attributes — the fields merchandisers configure in the editor
• Register components in the component library

Page Designer components are defined in JSON (component definition) and rendered via ISML. They are stored in the platform content layer and versioned independently of code deployments.

---

SFCC Performance Optimization

SFCC SFRA storefronts are not fast by default. A standard SFRA implementation will score 30–55 on Lighthouse without optimisation work. Achieving 70+ requires deliberate engineering.

Key SFCC Performance Techniques

Image optimisation

• Use WebP or AVIF formats. SFCC's Dynamic Imaging service can transform images at the CDN layer.
• Set explicit width and height attributes to prevent layout shift (CLS).
• Lazy-load below-fold images with loading="lazy".
• Use fetchpriority="high" on the LCP image.

CSS optimisation

• SFCC serves all CSS by default. Split stylesheets and load non-critical CSS asynchronously.
• Use <link rel="preload" as="style"> for critical CSS.
• Remove unused styles — SFRA's base CSS is large and includes many unused rules.

JavaScript deferral

• SFCC loads significant JavaScript synchronously. Defer all non-critical scripts.
• Use async or defer on third-party scripts.
• Implement service workers for static asset caching.

Caching strategy

• Use SFCC's page-level caching (full-page cache) for category and product pages.
• Use partial page caching for personalised regions.
• Set aggressive CDN cache headers for static assets.

Core Web Vitals targets:

• LCP < 2.5s — optimise hero image loading
• CLS < 0.1 — set image dimensions, reserve font space
• INP < 200ms — defer long tasks, reduce main thread work

---

SFCC Business Manager

Business Manager (BM) is the back-office administration console for Salesforce Commerce Cloud. Every SFCC developer and merchant uses it daily.

Developer tasks in Business Manager:

• Code deployment via Administration > Site Development > Code Deployment
• Cartridge path configuration per site
• Job execution and scheduling (custom and platform jobs)
• OCAPI permission configuration
• Log file access and custom log creation
• Custom object definition and data management
• A/B test configuration
• Site import/export (XML-based data migration)

Merchant tasks in Business Manager:

• Product and catalogue management
• Pricing and promotion configuration
• Content slot and campaign scheduling
• Order search and management
• SEO URL rules and redirects
• Search tuning with Einstein

Understanding Business Manager deeply is a prerequisite for any SFCC developer. The SFCC B2C Commerce Developer certification exam tests Business Manager knowledge extensively.

---

SFCC Jobs and Quota

SFCC's job framework allows developers to schedule and run custom server-side logic — product data imports, inventory synchronisation, order export, promotional data processing.

Job anatomy:

• Job definition — XML descriptor defining the job and its steps
• Job step — a JavaScript module implementing the execute() function
• Job schedule — cron-based trigger configured in Business Manager
• Job status — exit statuses: OK, WARN, ERROR, RUN

Quota limits are a critical SFCC-specific concept. The platform enforces hard limits on:

• Script execution time (default: 900 seconds per job step)
• Memory usage per execution context
• Number of objects iterable in a single search query
• API call rates

Exceeding quotas causes job failures and storefront errors. Experienced SFCC developers design jobs to process data in batches, checkpoint progress, and handle quota exhaustion gracefully.

---

SFCC Custom Objects

Custom Objects (also called Custom Data Objects) are SFCC's built-in key-value store for persisting custom data beyond the standard platform data model.

Use cases:

• Storing third-party integration state (webhook receipts, sync timestamps)
• User-generated content (wishlist items before native wishlists existed)
• Configuration data managed through Business Manager
• Caching external API responses

Custom Objects are defined via a type definition (attribute group, attributes, indexes) and accessed via the CustomObjectMgr API. They support up to 100 attributes per type and can be queried via OCAPI Data API.

---

SFCC Certifications

The primary certification path for Salesforce Commerce Cloud developers:

Salesforce B2C Commerce Developer

The foundational SFCC certification. Tests:

• Cartridge development and cartridge path mechanics
• SFRA architecture and controller development
• ISML templating
• Business Manager configuration
• OCAPI integration basics
• Platform debugging and log analysis
• Jobs and quota management
• Custom object usage

Prerequisites: Salesforce recommends 6+ months of hands-on SFCC development experience.

Format: 60 questions, 90 minutes, 65% passing score.

Preparation: Salesforce Trailhead SFCC trails, Salesforce partner training courses, and hands-on practice in a sandbox environment.

Salesforce B2C Commerce Architect

Advanced certification for solution architects. Covers:

• Solution design and technical architecture decisions
• Headless and composable commerce patterns
• Performance architecture
• Integration design patterns
• Multi-site and multi-region architecture

Salesforce B2B Commerce Administrator / Developer

Separate certification track for the B2B Commerce product.

---

SFCC vs Shopify Plus

The most common platform comparison for enterprise eCommerce:

Criterion	SFCC	Shopify Plus
Customisation depth	Deep (cartridge model)	Moderate (apps + Storefront API)
Out-of-box performance	30–55 Lighthouse	50–75 Lighthouse
Headless maturity	High (SCAPI + PWA Kit)	High (Storefront API)
Native AI	Einstein (deep integration)	Shopify Magic (limited)
B2B commerce	Purpose-built	Growing but limited
Multi-site	Native strength	Up to 9 stores per plan
Implementation cost	High (certified developers)	Moderate
Time to market	Slower	Faster
Ecosystem	SFCC partner network	8,000+ apps
Best for	Complex enterprise	Mid-market to enterprise

The choice between SFCC and Shopify Plus is not about which platform is "better" — it is about fit. SFCC wins when requirements are complex. Shopify Plus wins when speed and simplicity matter more than depth.

---

About the Author: Ozan Altinbas

Ozan Altinbas is a Salesforce Commerce Cloud Technical Architect and eCommerce Architect based in Izmir, Turkey. He has been building on SFCC since 2018, with 8+ years of hands-on platform experience and 14+ years in software engineering.

His SFCC portfolio includes implementations for:

• Karl Lagerfeld — global fashion brand (Alpenite, 2021–present)
• Stella McCartney — luxury sustainable fashion (Alpenite, 2021–present)
• Barbour — British heritage brand (Alpenite, 2021–present)
• Fred Paris — luxury jewellery (Alpenite, 2021–present)
• Shoeby — Dutch fashion retail (Emakina, 2020–2021)
• GameStop — gaming retail (OSF Global Services, 2018–2020)
• Ubisoft — gaming publisher (OSF Global Services, 2018–2020)
• Micromania — French gaming retail (OSF Global Services, 2018–2020)

He holds the Salesforce B2C Commerce Developer certification (issued 2019) and specialises in headless commerce via SCAPI/OCAPI, custom cartridge development, SFCC performance engineering, and payment gateway integrations (Adyen, PayPal, Klarna, Cybersource, Apple Pay).

View full portfolio · View career history · Contact Ozan

---