Demandware licence cost after the acquisition

A storefront licence is a strange thing to price because the buyer usually knows the shop better than the vendor does and still ends up negotiating blind. Demandware, the commerce platform Salesforce acquired in 2016, is sold today as Salesforce B2C Commerce. The rebrand record puts it simply: "In 2016, the company acquired Demandware, which later became B2C Commerce Cloud." What it does not say is what the shop costs, and Salesforce's own pricing page does not say either.

That is the honest starting point. B2C Commerce is quote-only. What you can do is read what Salesforce does publish, which is the shape of each edition, and use it to understand what drives the quote and which questions to put in front of a sales representative.

#What Salesforce publishes and what it holds back

The B2C Commerce pricing page lists three editions and prints "Contact for pricing" against each of them, in every currency. We read it on 13 October 2026. The entitlements are published; the price is not.

The page describes the middle tier in one sentence worth reading closely: "Scale with more sites and price books, and create AI-powered consumer experiences with templates and composable storefronts." The step from Growth to Plus is therefore a step in scale, from a handful of sites to a hundred and from ten price books to thousands. The step from Plus to Premium leaves the site and price book counts alone and adds the order management and data entitlements.

#Why there is no list price

Salesforce does not say on the page what B2C Commerce is priced against, and that is the most important thing to find out. A storefront can be priced on the number of sites, on the volume of orders or the value of goods sold through it, on traffic, on a flat platform fee, or on a blend. The page tells you the edition and its limits, not the meter.

So the first request to make of your account executive is for the pricing metric in writing, with the edition, the term and the renewal mechanics beside it. If the metric is tied to sales volume, ask how it is measured, whether returns and cancellations are netted off, and what period it is measured over. If it is tied to something else, ask how growth during the term is handled. A quote that arrives without a stated metric is not comparable with any other, including last year's.

#Sites and price books are the limits that bite

The two numbers that most often decide the edition are sites and price books, and they are worth understanding in your own terms.

A site is a storefront: a brand, a region or a language-and-currency combination that has its own catalogue view, content and checkout. A retailer with one brand in one market needs one site. The same retailer selling under two banners in Australia and New Zealand may need four. Growth's limit of five sites suits a business with a compact footprint. A business that expects to launch markets or brands during the term should ask what adding a site beyond the limit costs, and whether crossing from Growth to Plus mid-term is credited.

A price book holds the prices for a currency or a customer group. Ten price books sounds generous until you count currencies, wholesale and retail tiers, loyalty prices and promotional lists. Plus and Premium lift the ceiling to 3,500, which is a different order of scale. If you know your count today, you can match the edition to it. If you do not, ask your merchandising team before you ask Salesforce.

#Sandbox credits are an operating cost in disguise

On-demand sandbox credits are the line that looks like a technical detail and turns out to be a delivery budget. The page lists 1.2 million on Growth and 2 million on Plus and Premium. The credits are consumed as your developers spin up on-demand sandboxes to build and test. A team that runs several feature branches, a performance test environment and a staging copy will use them faster than a team shipping one change at a time.

Ask how credits are consumed and how many a typical sandbox uses, and ask what happens when you run out: is there a top-up price, and does it differ from the cost of a higher edition? A programme with a busy release cadence should model its consumption before signing, because a licence that runs dry mid-year can stall a peak-season build.

#What Premium bundles

Premium is the only edition on the page with full order management, a 500K credit allocation for the data product the page still calls Data Cloud, personalisation built on Data 360 segments with intelligence dashboards, and seven CRM Analytics users. The data product has since been renamed Data 360, so expect your contract and Salesforce's newer documents to use that name.

The question is whether you would otherwise buy those pieces separately. If you already run an order management system you are happy with, the bundle may be shelfware, and a Plus quote that leaves it out could be the better fit. If you are rebuilding fulfilment at the same time, Premium may be cheaper than assembling the parts. Ask for an itemised comparison rather than a single edition price.

#Do not confuse it with commerce built into the CRM

Salesforce also promotes commerce capabilities built into Sales and Service Cloud at no cost for Enterprise Edition or higher; the commerce pricing overview describes the offer as a way to try commerce before buying. That is a different thing from B2C Commerce. It is not Demandware, it does not give you the storefront platform, and it should not be netted off a B2C Commerce quote or used as a reason to expect one is included. Likewise a Sales Cloud licence does not cover the storefront. They are separate contracts, and your renewal pack should show them on separate lines.

#Contract and renewal mechanics to settle

Because there is no list, the contract carries the commercial weight. These are the points to agree and write down.

The term and billing frequency, and whether the price is fixed for the term or reviewed. Many enterprise software contracts allow an uplift on renewal, so ask whether a cap applies and what it is.

The measurement and true-up. If the metric is volume-based, find out how overage is handled: whether you pay in arrears, whether there is a banded step, and whether a seasonal peak is smoothed across the year or billed as it falls.

The treatment of sandboxes, additional sites and additional price books beyond the edition limits.

The support plan. The pricing page shows three success plans: Standard included in all licences, Premier priced as a share of net licence fees, and Signature through your account executive. Since the Premier share scales with the licence, a licence negotiated down brings the support cost down with it, and a licence negotiated up pushes it up.

The exit position. If you intend to replatform, ask what notice and data export arrangements apply, because a storefront that cannot be switched off cleanly makes the next contract harder to negotiate.

#Right-sizing before you sign or renew

Right-sizing a storefront licence starts with an inventory. List your live sites and which of them earn revenue, your active price books by currency and audience, the sandboxes you actually use each month, and your order volume by month for the last year. Sites that were launched for a campaign and never retired, and price books for products you no longer sell, are the quickest wins.

Then test the edition boundary. If you run three sites and expect five, Growth fits and the jump to Plus is a decision for a future year. If you run forty, Plus is the only listed edition that covers you. If the order management is the reason for Premium, check whether it is doing real work or only sitting there.

Finally, ask what has changed in the product since your last contract. A renewal is a chance to retire a line that no longer applies and to remove entitlements you added for a project that has ended.

#Timing, currency and peak trading

Two commercial details sit outside the entitlement table and are easy to overlook. The first is when your term ends. A storefront renewal that falls in the weeks before your biggest trading period hands the vendor the stronger hand, because you cannot realistically replatform or even delay a launch. Ask for the term to end well clear of peak, or for a short co-term that realigns the date, and start the conversation six months out rather than six weeks.

The second is currency. The pricing page shows the same "contact for pricing" in six currencies, which tells you Salesforce quotes in several. If you earn in Australian dollars and the contract is in US dollars, a swing in the exchange rate lands on your margin. Ask for the quote in the currency you trade in, and ask whether the price is fixed in that currency for the term.

#Questions to put to your account executive

Gathering the above into a list helps, because a sales conversation about a quote-only product rewards the buyer who arrives with the questions already written. Ask what the pricing metric is and how it is measured. Ask which edition the quote assumes and what the next edition up would add. Ask what happens at the site and price book limits. Ask how sandbox credits are consumed and what a top-up costs. Ask whether order management and the data credits are in the quote or priced as extras. Ask what the renewal uplift is capped at. And ask for each answer in the order form, since a verbal assurance does not survive a change of account executive.

#Comparing two licence offers

When you hold two offers, reduce each to the same terms. Write down the edition, the pricing metric, the term, the billing frequency, the site and price book limits, the sandbox credits, the bundled extras and the renewal uplift. An offer that leaves a cell blank has not answered the question, and a blank is not a zero.

Compare like with like on a scenario. Ask each side to price the same two years: your expected volume in year one, a launch of one new site in year two, and a peak season that runs a fifth above forecast. The offer that looks cheapest on year one can be dearer once the second site and the peak arrive. Ask each seller to show the working.

#Where the other questions sit

The licence is the fee you pay Salesforce. The work to build or move a storefront is a separate cost, and the Demandware implementation cost guide covers it. The acquisition itself is on what happened to Demandware. How the shop exchanges orders and customers with the core org is on integrating Demandware with Salesforce, whether to move is on should I migrate from Demandware, and the delivery side is on the Demandware implementation page.