Salesforce Commerce Cloud is licensed on a percentage of gross merchandise value — typically 1–2% of the revenue transacted through the storefront — rather than per user. B2C and B2B Commerce price differently, and order-volume tiers can apply, so cost scales directly with sales.
Salesforce Commerce Cloud is licensed on a percentage of gross merchandise value (GMV) — typically 1–2% of the revenue transacted through the storefront — rather than per user. Because cost scales directly with sales, Commerce Cloud is the one major Salesforce cloud where growth automatically grows the bill, and the negotiation is about the GMV rate, the step-downs as volume rises, and the overage mechanics. B2C Commerce and B2B Commerce use related but distinct models, so the first question is always which one you are buying. This article sits under our Salesforce pricing pillar; see also the Salesforce practice page.
The GMV model cuts both ways. It aligns vendor and buyer in a downturn — if sales fall, so does the fee — but it punishes success: a high-growth merchant can see Commerce Cloud cost rise faster than the margin it funds. That is why the GMV percentage and its step-downs are the heart of the deal.
We model your GMV curve against the rate tiers so the percentage steps down as you scale, not just at the thresholds Salesforce proposes.
The two Commerce products serve different buyers and price differently. The table summarises the distinction.
| Dimension | B2C Commerce | B2B Commerce |
|---|---|---|
| Primary model | % of GMV | % of GMV or per-order, sometimes blended with per-seat for buyers/admins |
| Typical GMV rate | ~1–2% | Often lower % but with order-volume floors |
| Order profile | High volume, low value | Lower volume, high value |
| Watch-outs | Overage rate above committed GMV; peak-season spikes | Order-count tiers; mixed seat + GMV double counting |
Commerce Cloud contracts commit you to a GMV band and apply an overage rate above it. The indicative planning bands below show how the effective percentage should fall as committed GMV rises — if your proposal does not step down, that is the first thing to negotiate.
| Committed annual GMV | Indicative effective rate | Negotiation focus |
|---|---|---|
| Under $10M | ~1.5–2.0% | Cap the overage rate; avoid long lock-in |
| $10M–$50M | ~1.0–1.5% | Secure step-downs at defined GMV milestones |
| $50M+ | Often below 1.0% | True-down rights; peak-season overage protection |
GMV step-down models and the overage clauses that protect high-growth merchants.
Four levers move a Commerce Cloud deal: (1) GMV step-downs written as automatic rate reductions at defined milestones, not discretionary reviews; (2) a capped overage rate so a strong quarter does not trigger punitive billing; (3) peak-season protection so seasonal spikes are measured against an annual commitment rather than a monthly one; and (4) clarity on whether seats and GMV are both charged in B2B, to avoid double counting. Sequence the negotiation so the GMV rate is settled before any add-on modules enter the conversation — our contract negotiation team runs Commerce deals in exactly that order. Buyers comparing commerce and HR platform economics in the same procurement should also see Workday vs SuccessFactors for how consumption versus per-seat models trade off.
Because the fee is a percentage of GMV, the definition of GMV is worth more than any rate negotiation. The order form specifies what counts, and the defaults usually favour Salesforce: gross order value before deductions. The lines to scrutinise are returns and cancellations (do they reduce billable GMV, and over what window?), taxes and shipping (are they excluded from the GMV base, as they should be?), and discounts and promotions (is GMV measured on the discounted price the customer actually pays, not the list value?). A merchant with a 20% return rate that is billed on gross-before-returns GMV is paying for revenue it never recognised. We have re-opened Commerce Cloud agreements purely on the GMV definition and recovered double-digit percentages without touching the headline rate. Get the measurement window and the exclusions written explicitly into the order form — "GMV" left undefined defaults to the vendor's broadest interpretation.
Commerce Cloud rarely ships as a single line. The adjacent modules that commonly get added — and that should be priced in the initial deal, not bolted on later — include:
Model the all-in effective percentage — GMV fee plus every attached module divided by GMV — rather than the headline rate alone, or the deal will look cheaper than it is. For the full edition and cloud reference, return to the Salesforce pricing pillar.
The GMV model is not unique to Salesforce, and a credible alternative on the table is itself a discount lever. Shopify Plus blends a platform fee with a revenue-share that can step down at scale; Adobe Commerce (formerly Magento) is licensed largely on a tiered model tied to GMV and order volume; BigCommerce leans more on a flat platform fee with order or sales thresholds. The practical implication for a Commerce Cloud negotiation is that you should know your effective all-in percentage and be able to compare it like-for-like against at least one alternative. Salesforce Commerce Cloud tends to justify its premium where the merchant is already invested in the wider Salesforce estate — Service Cloud for customer care, Marketing Cloud for engagement, Data Cloud for unification — because the integration value is real. Where that estate does not exist, the GMV percentage has to stand on its own, and the comparison gets harder for Salesforce to win.
Run the comparison on three-year total cost at your projected GMV, not on year-one headline, since the GMV model compounds with growth in a way flat-fee platforms do not.
The licence fee is only part of the total cost of ownership. Commerce Cloud implementations are non-trivial: storefront build, catalogue and pricing setup, payment and tax integration, OMS configuration and the inevitable systems-integrator engagement. For a mid-sized B2C launch, implementation frequently lands in the mid-six figures, and ongoing run cost — agency or in-house development, optimisation, peak-season readiness — is a recurring line that often rivals the licence over a multi-year horizon. Budget for it explicitly so the GMV rate is evaluated against the full picture, not in isolation. The same discipline of modelling total cost rather than headline price runs through every engagement our contract negotiation team takes on.
A defensible Commerce Cloud business case has four moving parts: the committed GMV fee at each year's projected revenue, the attached-module fees, the overage exposure under realistic peak-season scenarios, and the implementation-plus-run cost amortised across the term. Build the model before you negotiate, stress it against an upside-growth case where the GMV fee balloons, and use that scenario to justify the step-downs and overage caps you ask for. The merchants who arrive at the table with a TCO model — rather than reacting to Salesforce's proposal — consistently secure better step-down schedules, because they can show exactly where the deal becomes uneconomic. Bring that model to the first vendor meeting, not the last: the GMV rate, the overage cap and the step-down schedule are all easier to move before Salesforce has anchored you on its own proposal, and a buyer who has done the maths is far harder to rush toward signature. For the full edition and cloud reference, see the Salesforce pricing pillar.
We model GMV curves and step-downs so the rate falls as you scale. We represent buyers exclusively.
Weekly compliance intelligence for IT leaders.