Salesforce Commerce Cloud: What UK Retailers Need to Know Before They Sign
Most ecommerce platforms charge a flat monthly fee. Salesforce Commerce Cloud takes a percentage of your revenue instead, a pricing structure that can cost a scaling retailer tens of thousands of pounds more than comparable enterprise alternatives before the first line of custom code is written.
Salesforce Commerce Cloud is an enterprise-grade, cloud-hosted ecommerce platform designed for high-volume retailers that need deep integrations, global scalability, and the ability to manage complex catalogues across multiple storefronts. If you are evaluating it, this guide covers what it actually does, what it costs in practice, where it falls short, and how to decide whether it belongs in your technology stack.
What Salesforce Commerce Cloud Is (and Where It Came From)
Salesforce Commerce Cloud began life as a separate product called Demandware, a SaaS platform that pioneered the idea of cloud-native ecommerce at scale. Salesforce acquired it in 2016 for roughly $2.8 billion and folded it into its broader Customer 360 ecosystem.
The core proposition has stayed consistent: a fully hosted, multi-tenant platform that handles infrastructure, security patching, and peak-traffic scaling on your behalf. You do not manage servers. You do not worry about Black Friday bringing the site down. The platform absorbs that operational burden in exchange for a significant ongoing licence cost.
What changed after the acquisition is the depth of native connectivity to the broader Salesforce suite, Sales Cloud, Service Cloud, Marketing Cloud, and the AI layer now branded as Einstein. For retailers already operating on Salesforce CRM, the Commerce Cloud integration story is genuinely compelling.
The Two Products: B2C and B2B Commerce
Salesforce Commerce Cloud is not a single product. It is an umbrella that covers two distinct platforms with different architectures, different buyer personas, and different implementation approaches.
B2C Commerce (the former Demandware platform) is built for direct-to-consumer retail. It handles product discovery, merchandising rules, promotions, cart and checkout, and storefront personalisation. The underlying architecture is based on a proprietary templating system, though Salesforce has been pushing its headless "Composable Storefront" (built on React and the SFRA framework) as the forward path for new builds.
B2B Commerce targets wholesale, distributor, and manufacturer selling, complex account hierarchies, contract pricing, order approval workflows, and large minimum-order quantities. It was rebuilt from scratch on the Salesforce platform (Apex, Lightning Web Components) rather than inheriting the Demandware codebase, which means the two products have entirely separate development ecosystems.
Many mid-market retailers evaluating "Salesforce Commerce Cloud" do not realise they are choosing between two different technical architectures. Getting that decision wrong early is an expensive mistake to unwind.
How the Pricing Model Actually Works
Salesforce Commerce Cloud does not publish its pricing publicly, which is itself a signal about the market it is targeting. Contracts are negotiated directly, and the base structure is a revenue-share model: the platform takes a percentage of the gross merchandise value (GMV) you process through it, combined with a base licence fee.
Industry estimates, and these are estimates, not figures we can verify independently, place the revenue share at somewhere between 1% and 3% of GMV, depending on tier and negotiating position. At £5 million annual revenue that is a platform cost of £50,000 to £150,000 before any implementation, customisation, or agency fees. At £20 million annual revenue the range becomes £200,000 to £600,000 per year, just for the licence.
Beyond the licence, the typical cost structure for a Commerce Cloud build includes:
- Implementation partner fees, Salesforce operates an accredited partner ecosystem. A mid-complexity B2C build typically runs between £150,000 and £500,000 in partner services, though larger enterprise builds can exceed seven figures.
- Ongoing development retainer, the platform is powerful but not simple. Most retailers retain a certified Salesforce developer or agency at day rates that reflect the specialist skill required.
- Add-on licences, Einstein AI personalisation, Order Management, and cross-cloud integrations often carry separate line items.
- Composable Storefront build costs, if you opt for the headless architecture (which Salesforce now recommends), the front-end is a separate React application that needs its own development and hosting.
The honest summary: Salesforce Commerce Cloud is a platform where total cost of ownership over three years frequently exceeds £1 million for a mid-market retailer. That is not a reason to avoid it, but it is a reason to be clear-eyed before entering commercial conversations.
What You Actually Get for the Investment
The case for spending at this level rests on capabilities that genuinely matter at scale.
Multi-site management is where the platform earns its keep. A retailer operating across five countries, three brands, and two languages can manage all storefronts from a single Business Manager instance, with shared catalogue logic and separate localisation layers. Replicating that in a mid-market platform requires significant custom development.
Peak traffic handling is automatic and contractually backed by SLAs. For retailers with seasonal spikes, a major sale event, a television appearance, a viral moment, the infrastructure simply scales. There is no capacity planning conversation with a hosting provider.
Merchandising tools in the native platform are mature. Searchandising rules, slot-based content targeting, A/B testing for product sorting, and Einstein-powered recommendations are available without third-party integrations. For a team of merchandisers making daily decisions, this translates into genuine operational efficiency.
Order management (available as a separate but integrated product) handles the complexity of omnichannel fulfilment: buy online/collect in store, ship from store, split shipments, and return routing. For retailers with physical estates, this is a meaningful differentiator.
Compliance and security are handled at the platform level. PCI DSS compliance, regular penetration testing, and infrastructure-level certifications reduce the burden on internal IT teams.
The Honest Limitations
No platform review is useful without a frank account of the drawbacks.
Complexity and speed-to-market are recurring criticisms. A typical B2C Commerce implementation takes six to twelve months from contract signature to live site. For a retailer moving off a Shopify or WooCommerce build, that timeline can feel punishing.
The Storefront Reference Architecture (SFRA), the legacy templating approach, is now a technical dead end. Salesforce is directing investment toward the Composable Storefront, which means retailers on SFRA builds face an eventual re-platform within a platform. Some older SFRA implementations are already carrying significant technical debt.
Partner dependency is structural. The platform requires certified expertise, and the pool of truly experienced Salesforce Commerce Cloud developers in the UK is not large. That scarcity keeps day rates high and can extend project timelines when specialist capacity is unavailable.
The Salesforce ecosystem lock-in is real. Once your merchandising team has built their workflows around Business Manager, once your data is normalised to Salesforce's object model, and once your integrations are built on the Salesforce connector framework, switching platforms is a major undertaking. That is a reasonable trade-off if the platform is delivering, but it limits your negotiating leverage at contract renewal.
Smaller catalogue and lower traffic businesses are simply not well served. The overhead of managing a Commerce Cloud implementation, in cost, in internal resource, in process change, is disproportionate for a retailer doing less than £5 million annually.
When Salesforce Commerce Cloud Makes Commercial Sense
The retailers for whom this platform genuinely delivers are those with:
- GMV of £10 million or above, ideally growing toward £50 million and beyond
- Multi-brand, multi-market, or multi-language complexity that simpler platforms handle clumsily
- An existing Salesforce CRM investment that creates genuine integration value
- A trading team large enough to use the merchandising and personalisation tooling actively
- Physical retail operations where omnichannel fulfilment capability matters
- Board-level appetite for a multi-year platform investment as a strategic infrastructure decision
Retailers who should look elsewhere before committing include those prioritising time-to-market, those whose primary need is a clean, well-converted storefront rather than operational complexity, and those without an internal technical resource to own the platform relationship.
The honest alternative landscape includes Shopify Plus for high-growth DTC brands, Adobe Commerce (Magento) for retailers with complex cataloguing needs and a preference for open-source flexibility, and BigCommerce for mid-market sellers seeking enterprise feature depth without Commerce Cloud's cost structure. Each is a legitimate choice depending on the specific profile of the business.
What a Commerce Cloud Implementation Actually Looks Like
Understanding the implementation journey prevents budget and timeline surprises.
The process typically begins with a discovery and solution design phase lasting four to eight weeks. This produces the technical specification, integration architecture, and project plan. Skimping on discovery is one of the most reliable ways to overspend on delivery.
The build phase covers front-end development (either SFRA templates or the Composable Storefront), back-end integrations (ERP, PIM, fulfilment systems, payment providers), data migration, and QA. This is where the majority of the budget is consumed and where scope creep is the primary risk to timeline and cost.
User acceptance testing and performance testing precede the launch phase. Load testing against projected peak traffic is not optional, it is the mechanism by which you verify the platform will behave as contracted under pressure.
Post-launch, most retailers retain a managed services or development retainer arrangement. The platform receives regular updates (Salesforce operates a release cycle with seasonal major releases), and keeping integrations current, exploiting new features, and managing technical debt requires ongoing developer access.
The retailers who extract the most value from the platform invest in internal platform ownership, typically a commerce manager or digital operations lead who understands both the business requirements and the platform capabilities. Outsourcing that ownership entirely to an agency tends to produce slow delivery and misaligned priorities over time.
Frequently Asked Questions
Is Salesforce Commerce Cloud suitable for small or medium-sized UK ecommerce businesses?
In most cases, no. The platform is engineered and priced for enterprise-scale retailers. The minimum viable investment, including licence, implementation, and ongoing development, typically exceeds the total marketing budget of a business with annual revenue below £5 million. Shopify Plus, BigCommerce, or a well-configured WooCommerce installation will deliver better commercial outcomes at that scale.
What is the difference between Salesforce Commerce Cloud and Shopify Plus?
Shopify Plus is a managed SaaS platform optimised for speed-to-market, ease of use, and a large app ecosystem. It charges a flat monthly fee (around £2,000 per month at standard tiers, with transaction fees variable by payment provider) and suits high-growth DTC brands with straightforward catalogue structures. Salesforce Commerce Cloud is better suited to retailers with multi-market complexity, omnichannel operations, or deep Salesforce CRM integration requirements, but it carries substantially higher implementation and licence costs. The two platforms serve overlapping but distinct market segments.
How long does a Salesforce Commerce Cloud implementation take?
A realistic timeline for a mid-complexity B2C Commerce build runs from six to twelve months between contract signature and launch. Simpler builds using an accelerator or pre-built Composable Storefront starter can compress toward the lower end of that range. Complex multi-site, multi-language builds with deep ERP integration frequently extend beyond twelve months. Any partner quoting three to four months for a full implementation without very clear scope constraints warrants careful scrutiny.
Disclosure: this post contains affiliate links. If you join through one of them we earn a commission, at no extra cost to you. It does not change what we recommend.
Building the money skills behind the store
The operational side of ecommerce, sourcing, pricing, fulfilment, is only half of it. The other half is the financial literacy to read your own numbers, understand cashflow, and make decisions about credit, tax and reinvestment without guessing. That is the part most sellers develop last, and it is the part that decides whether a growing store becomes a durable business.
We use Money.School for this. It is a membership built around practical money education, cashflow modelling, credit and borrowing, margins, tax and reinvestment — taught by people who have actually scaled businesses rather than only theorised about it. It suits sellers who want a structured, ongoing education rather than a one-off course.
- Standard Monthly, £15 + VAT a month
- Standard Yearly, £150 + VAT a year
- Standard Lifetime, £300 + VAT one-off
- GOLD Monthly, £38.33 + VAT a month
- GOLD Yearly, £380 + VAT a year
- GOLD Lifetime, £760 + VAT one-off
The monthly tiers are the low-commitment way in; the lifetime options suit anyone who wants permanent access. If you are weighing it up, start with a monthly plan and judge it against your own numbers.