Demandware implementation cost: B2C Commerce pricing, work packages and quotes

Ask a Salesforce account executive for the price of Demandware and within a sentence you will be talking about B2C Commerce. The rebrand record says it plainly: "In 2016, the company acquired Demandware, which later became B2C Commerce Cloud." Business Manager, the cartridges your developers maintain, the storefronts your customers buy from: all of it is B2C Commerce now. What has not changed is that B2C Commerce is priced and built differently from almost everything else Salesforce sells, and that shapes how you should budget for an implementation.

#B2C Commerce is quote-only

B2C Commerce does not run on the core Salesforce platform. It has its own infrastructure, its own instances, its own APIs and its own commercial model. Salesforce does not publish a list price for any edition. On the B2C Commerce pricing page, read on 11 October 2026, each of the three editions shows "Contact for pricing" in every currency the page offers, Australian dollars included.

The editions are still worth reading closely, because they show which levers move the price.

Salesforce describes the Plus edition in one line: "Scale with more sites and price books, and create AI-powered consumer experiences with templates and composable storefronts." That is the clearest statement Salesforce makes about what separates the tiers. A brand with one storefront in one currency sits comfortably within Growth. A retailer running separate sites per country, brand or channel, each with price books for currencies, customer groups and sale events, is a Plus or Premium customer whether it planned to be or not.

#What sets the licence price

Because the page publishes no figure, everything you know about the licence will come from your contract or your account executive. Unlike Sales Cloud, B2C Commerce is not presented as a per-seat product, so the questions are different. Before you negotiate, get written answers to these.

What the subscription is measured on. Ask whether your quote is based on gross merchandise value, on order volume or on a fixed fee. If it is tied to sales, ask how the measure is defined (for example, whether tax, shipping and returns are excluded) and what happens when a strong year takes you over the contracted band. A licence that grows with trading is not a bad thing, but it must be in the forecast.

Sites and price books. Count them honestly. Include sites you plan to launch during the contract term, not only those live today, and every price book you maintain for currencies, wholesale groups or promotions.

Order Management. Premium includes full Order Management. Salesforce Order Management also appears as a separate product on the wider Commerce pricing page, so on Growth or Plus ask whether you need it and what it adds.

Data 360. Premium lists personalisation with Data 360 segments. Segmentation in Data 360 consumes credits, so ask what is included and how overage is charged.

Support. The Commerce pricing page lists Premier and Signature Success Plans. Premier is priced as a share of net licence fees, so it scales with whatever the licence turns out to be.

#What a B2C Commerce implementation is made of

A storefront build is a different kind of project from a CRM rollout. The work packages below appear in almost every serious quote. What varies is their size.

Discovery. Sites, locales, currencies, catalogues, price books, inventory lists, promotions, customer groups, integrations and expected peak traffic. Discovery should also record the trading calendar, because no retailer wants to cut over in the weeks before its biggest sale.

Storefront architecture. This is the largest single decision. Older Demandware storefronts were built on the SiteGenesis reference application; most current builds use the Storefront Reference Architecture (SFRA), which is cartridge-based and rendered on the platform. The alternative is a headless, composable storefront built with PWA Kit and hosted on Managed Runtime, calling the Salesforce Commerce API. SFRA usually means less custom front-end engineering; a composable storefront gives more front-end freedom and asks more of your developers. A quote that does not name the architecture is not a quote yet.

Catalogue and price book design. Master catalogue versus storefront catalogues, category structure, product variation attributes, bundles and sets, inventory lists and price books. Product data usually arrives through XML imports or a product information management system, and getting that feed right takes longer than buyers expect.

Cartridges and integrations. Payment (Salesforce Payments or a payment provider's cartridge), tax calculation, address validation, fraud screening, search, ratings and reviews, loyalty, and the link to your ERP or warehouse for stock and order export. Integration patterns include the Open Commerce API and the Commerce API, scheduled jobs in Business Manager, and MuleSoft where an integration layer already exists.

Customer and order data. Customer accounts, order history and saved addresses. Plan for password resets: credentials from another platform may not carry over in a usable form.

Content and SEO. Page Designer content, content assets, and a full redirect map from old URLs to new ones. Losing search rankings at launch is a cost even if it never appears on an invoice.

Testing and performance. Functional testing, payment testing and a load test sized to peak trading. B2C Commerce has its own environments: development, staging and production instances, plus on-demand sandboxes for developers. A core Salesforce sandbox copies none of this, so the quote should name which B2C Commerce environments it uses and who runs the load test.

Launch and hypercare. A staged launch by site or locale, with support through the first trading peak.

#Upgrade, replatform or new build

Demandware customers fall into three groups, and the cost differs sharply between them.

Some still run storefronts built on SiteGenesis. Their project is a rebuild onto SFRA or a composable storefront. The catalogue, price books and orders stay on the same platform, but almost all front-end and cartridge code is rewritten.

Some are already on SFRA and want to add sites, adopt Order Management or move to a composable front end. That is an extension project, and the licence questions about sites and price books matter more than the build.

Others are leaving another commerce platform for B2C Commerce. That is a full replatform: every work package above, plus a longer data migration and a period where both platforms are paid for.

Ask each bidder which group they think you are in. If they disagree, settle that before comparing prices.

#Connecting the shop to the rest of Salesforce

Because B2C Commerce sits outside the core platform, every link to Sales Cloud, Service Cloud or Marketing Cloud is an integration with its own scope, not a setting you switch on. This is where Demandware projects most often grow after the contract is signed, so it is worth thinking through before the first quote arrives.

The usual pattern is that customer profiles and orders flow from the storefront into Service Cloud, so that a contact centre agent can see what a caller bought and when it shipped. That needs a decision about which system owns the customer record, how duplicates are matched, and how often orders synchronise. Salesforce and its partners offer connectors for this, and MuleSoft is common where the business already uses it, but each option still needs mapping, error handling and testing against real order volumes.

Marketing is the second link. Abandoned basket emails, order confirmations and back-in-stock alerts all depend on events leaving the storefront and reaching Marketing Cloud Engagement or another sending platform quickly and reliably. Transactional email in particular cannot wait for an overnight batch.

The third link is Data 360. If the plan is to unify commerce, service and marketing profiles for segmentation, Data 360 connectors ingest the commerce data, and the work becomes a data modelling exercise as much as an integration one. Premium edition customers will hear about this early, because the edition lists Data 360 segments among its inclusions.

None of these links is required to launch a storefront. Plenty of retailers go live with the shop, payments, tax and an ERP feed, and add the Salesforce connections in a second phase. That is often the sensible way to keep the first quote honest: price the storefront, then price each connection as its own work package once the shop is trading and the data is real.

#A budget frame without invented numbers

A sensible budget for a B2C Commerce project has four lines, and only the first comes from Salesforce. The licence, quote-only, set by edition, sites, price books and whatever the subscription is measured on. Third-party subscriptions for cartridges, payment processing and any product information system. The implementation services quote, built from the work packages above. And the run cost after launch: site operations, merchandising, release regression testing and support. Buyers who budget only the first and third lines are the ones who come back for a second approval six months later.

#Hidden costs and what quotes leave out

These are the items most often missing from a B2C Commerce proposal.

• Subscriptions for third-party cartridges such as search, reviews, tax and fraud screening, each with its own vendor contract.
• Payment processing fees, which sit outside the Salesforce licence.
• A product information management system, if the catalogue cannot be maintained in Business Manager alone.
• Order Management on editions that do not include it, and Data 360 credits if segments drive personalisation.
• Integration with Service Cloud, so agents can see orders, and with Marketing Cloud Engagement for triggered email. Each is its own scope.
• Regression testing after platform releases. Custom cartridges need checking when Salesforce updates the platform.
• Merchandising and site operations staff after launch. A storefront is never finished.
• Overlap with the old platform during a replatform, often timed around trading peaks.

#How to get quotes you can compare

Send every bidder the same brief: sites and locales, currencies, product and SKU counts, price books, active promotions, order volume and peak traffic, the integration list, and your preferred storefront architecture if you have one. Ask each bidder to state the architecture it has priced, which cartridges it reuses and which it rebuilds, the data migration volume, the load test it will run, and the launch window relative to your trading calendar. Ask too for the assumptions about who supplies product data and content. Two quotes that differ on those assumptions are describing different projects.

It also helps to ask every bidder the same three questions in the room. Which of our current cartridges would you keep, and why? What did the last load test you ran for a retailer of our size find? And what would you cut first if the launch date could not move? The answers tell you more about how a firm will behave in month four than any rate card. A partner who has shipped storefronts through a peak season will answer the third question quickly, and usually with something specific, such as deferring a second locale or a loyalty integration rather than trimming testing.

Finally, read the payment terms. Commerce projects are often milestone-billed, and the milestones should line up with things you can see working: a storefront on staging with real catalogue data, a successful payment test, a passed load test. A milestone called "build complete" with no test attached protects the supplier, not you.

#Where to go next

Licence and renewal questions are on the Demandware licence cost page. The acquisition story is on what happened to Demandware, and the platform itself is covered on the B2C Commerce page. For choosing a firm, read who to hire for Demandware. For connectors to Service Cloud and Marketing Cloud, see integrating Demandware with Salesforce, and if you are weighing a move away from the platform, should I migrate from Demandware sets out that decision. For an independent view of your proposal, our Salesforce consultancy team reviews commerce quotes.