Commerce engine moving to composable

Salesforce Commerce Cloud (SFCC)

What it is

An enterprise SaaS commerce platform (B2C/B2B), historically monolithic (SFRA), now offering a composable path via PWA Kit (React frontend), Managed Runtime hosting, and SCAPI headless APIs.

Where it sits in the stack

Commerce engine + optional composable storefront; pluggable CMS, search, and payments; deep ties to the broader Salesforce CRM/Marketing/Service ecosystem.

Why enterprises care

Managed hosting (no server management), an open-source React frontend with first-party hosting, and a phased, low-risk path to composability.

Business problem it solves

High-scale omnichannel commerce on a managed platform while modernising the storefront incrementally — without a full replatform.

Account-expansion opportunity

'Incremental composability' is a major expansion thesis: decouple the storefront first, then CMS, then search — each a fundable phase. A common Orium/Vercel play.

What Darren should say

"For an SFCC client, I'd frame modernisation as incremental composability — decouple the frontend first, keep the engine, and prove value phase by phase rather than betting on a big-bang replatform."

What NOT to overclaim

Don't claim SFCC is a MACH member (it isn't); composability comes via PWA Kit, not native MACH. Don't quote exact uptime figures as fact.

Likely client objection

"We're locked into SFCC" — incremental composability is precisely the de-risked exit ramp; you don't have to rip and replace.

Interview-ready phrasing

"Incremental composability lets an SFCC client modernise without betting the business on a big-bang replatform."