CommerceBolt — a Perigeon company
Talk to an expert

Platform

Salesforce Commerce Cloud Development

Commerce Cloud fits retailers and B2B sellers whose wider business already runs on Salesforce, where keeping commerce, service and marketing data in one model is worth more than storefront flexibility alone.

Where it fits

Where Commerce Cloud fits

The argument is rarely the storefront in isolation. It is the integration layer you no longer have to build.

  1. You already run on Salesforce

    Service Cloud, Marketing Cloud or Data Cloud already in place, so commerce joins the same customer model instead of syncing to it.

  2. Service needs order context

    Agents see order history and status in the console they already use, without a middleware sync between systems.

  3. High-volume consumer retail

    B2C Commerce is built for large catalogues, frequent promotions and traffic peaks across many sites and locales.

  4. Account-based B2B buying

    B2B Commerce covers contract pricing, buyer hierarchies and reorder flows on the same CRM data your sales team uses.

Salesforce Commerce Cloud at a glance

Best for
Retailers and B2B sellers whose business already runs on Salesforce
Hosting
Fully hosted SaaS, run by Salesforce
B2B
Separate B2B Commerce product, on the same CRM data
Headless
Commerce API with the PWA Kit composable storefront
Pricing model
Typically a share of gross merchandise value

Our view

One data model instead of a sync

The argument for Commerce Cloud is rarely the storefront in isolation. It is the removal of an integration layer: customer, order and service data sit in the same platform as your support and marketing operations, so a service agent sees order history without a middleware sync, and segmentation reaches commerce data directly.

If your business does not already run on Salesforce, that advantage largely disappears and the comparison becomes much closer.

How we scope it

Commerce Cloud licensing is usually tied to gross merchandise value, so the business case is sensitive to revenue projections in a way flat-fee platforms are not. We model that against Shopify Plus and Adobe Commerce during discovery rather than after.

See platform migration for how a move is structured, and unified commerce for the store and marketplace side.

Capabilities

What we do on Commerce Cloud

Implementation and migration on B2C and B2B Commerce, and the Salesforce estate around them.

  • SFRA storefronts

    Storefront Reference Architecture builds and redesigns — the fastest route to a production Commerce Cloud site.

  • Composable storefronts on PWA Kit

    Headless builds on the Commerce API and PWA Kit, where one frontend has to serve several channels.

  • B2B Commerce

    Account-based buying, contract pricing and reorder flows implemented on B2B Commerce.

  • Migration into Commerce Cloud

    Moves from legacy platforms, with catalogue, customer and order data mapped to the Commerce Cloud model.

  • Salesforce and back-office integration

    Service Cloud and Marketing Cloud connections, plus ERP and OMS integrations outside the Salesforce estate.

  • Release management and support

    Ongoing development, a predictable release cadence and performance work once the site is live.

The case for Commerce Cloud is the integration you do not build

When customer, order and service data already sit in Salesforce, Commerce Cloud removes an entire middleware layer. Without that existing estate the advantage largely disappears, and the comparison with Shopify Plus and Adobe Commerce gets much closer. We model both sides before you commit.

Book a platform review

Services

What we deliver on Salesforce Commerce Cloud

The same services run across our platforms. These are the ones Salesforce Commerce Cloud projects most often need.

Compare

How the platforms compare

The right platform depends on where your complexity sits, not on a feature list. This is the short version of the conversation we have in discovery.

Shopify Plus Adobe Commerce Salesforce Commerce CloudThis page
Best for Brands that want speed to launch and a store their own team can runComplex catalogues, contract pricing and deep ERP couplingRetailers and B2B sellers whose business already runs on Salesforce
Hosting Fully hosted SaaS; Shopify runs infrastructure, security and upgradesAdobe-managed cloud or self-hosted, with more of the stack in your controlFully hosted SaaS, run by Salesforce
B2B Built-in B2B features on Plus: company accounts, catalogues, price lists, payment termsNative B2B module: company accounts, shared catalogues, quotes and approvalsSeparate B2B Commerce product, on the same CRM data
Headless Hydrogen framework and Oxygen hosting, over the Storefront APIGraphQL and REST APIs for a decoupled frontendCommerce API with the PWA Kit composable storefront
Pricing model Monthly subscription, with a variable fee that scales with revenueAnnual licence, typically tiered by revenueTypically a share of gross merchandise value

Vendor pricing and plan features change. Confirm current commercial terms with the vendor before you decide.

How it runs

How a Salesforce Commerce Cloud project runs

  1. Discovery

    Your Salesforce estate, integrations and revenue projections mapped. Licensing tied to GMV makes the business case sensitive to those projections.

  2. Architecture

    SFRA or composable storefront chosen, and the data model and integration pattern agreed with the trade-offs written down.

  3. Build and integrate

    Storefront, cartridges and Salesforce connections built against a sandbox, tested with real catalogue and customer data.

  4. Launch and support

    Data migration, redirects and a monitored cutover, then release management and support on an agreed cadence.

Frequently asked questions

When does Salesforce Commerce Cloud make sense?

Almost always when the rest of the business already runs on Salesforce. Native access to Service Cloud, Marketing Cloud and Data Cloud removes an entire integration layer, and that single-vendor data model is usually the deciding factor rather than storefront features in isolation.

What is the difference between B2C Commerce and B2B Commerce?

B2C Commerce (formerly Demandware) is built for high-volume consumer retail. B2B Commerce targets account-based buying — contract pricing, buyer hierarchies, reorder flows. They are separate products with different data models, and brands selling both ways often run both.

Is SFCC headless?

It supports headless through the Salesforce Commerce API and the PWA Kit reference architecture. Many implementations still run the traditional SFRA storefront, which is faster to deliver. Headless is worth it when you need a shared frontend across several channels.

How does SFCC pricing work?

Commerce Cloud is typically licensed on a share of gross merchandise value rather than a flat fee, so cost scales with revenue. Model it against your actual projections — it changes the comparison with Adobe Commerce and Shopify Plus significantly at different revenue levels. Confirm current commercial terms with Salesforce.

Planning a Salesforce Commerce Cloud build or migration?

Tell us where it hurts. We will tell you honestly whether we are the right people for it.

Talk to an expert Book 30 minutes