Commerce Cloud is priced on gross merchandise value (GMV) rather than per user. The Admodum read on the GMV share, the B2C versus B2B variants, the Order Management module and the rate-card economics. Buyer-side. Independent.
Commerce Cloud is priced on gross merchandise value (GMV), not on the per-user metric that governs Sales Cloud and Service Cloud. GMV is the total dollar value of the orders processed through the Commerce Cloud storefront in a contract year. The GMV-share rate is the percentage of that gross value paid to Salesforce as the platform fee.
The model is transparent in the consumer-storefront retail context (a B2C merchant transacting orders directly with consumers) and less transparent in the B2B context (where the order-line economics are different). The wider Order Form anatomy spoke reads how the GMV-share rate is recorded on the Order Form artefact.
The GMV-share rate is band-tiered. The list rate sits in the one-to-two-percent range for the entry GMV band (the band that captures most mid-market merchants). Higher GMV bands negotiate to the sub-one-percent range. The rate breakpoint is the principal negotiation lever at renewal: a small reduction in the share rate compounds against the forecast GMV growth.
The buyer-side artefact is the GMV-by-band forecast: the merchant business plan, the seasonal-traffic profile, the growth-rate assumption, the band-by-band threshold mapping. The forecast is the evidence in the share-rate negotiation. The wider Salesforce renewal cycle spoke reads the timing on the band-tier renegotiation.
Commerce Cloud B2C is the consumer-storefront platform. The technical heritage is Demandware (the platform Salesforce acquired in 2016). The B2C variant is multi-tenant, cartridge-based and optimised for the high-traffic, seasonal-spike consumer-retail use case.
Commerce Cloud B2B is the business-to-business commerce platform. The technical heritage is Salesforce Platform (the B2B variant is built natively on the core platform, not on the Demandware codebase). The B2B variant handles account-hierarchy pricing, contract-pricing rules, requisition workflows and the B2B-specific commerce surface.
The B2B2C variant is the hybrid model that supports both a consumer storefront and a B2B reseller portal under one merchant. The two variants are commercially distinct: the B2C model is GMV-priced in the standard way; the B2B model often includes user-based components alongside the GMV share. The wider Sales Cloud editions spoke reads the B2B-Platform parallel.
Order Management is a separately licensed module. The product captures the order at storefront submit, applies fulfilment routing rules (which warehouse, which third-party logistics provider, which split-shipment policy), executes the payment capture against the configured payment provider, and handles the returns-and-exchange post-purchase workflow.
Order Management is the highest-services overlay-on in the Commerce Cloud portfolio and the most common over-buy at deployment. The over-buy pattern is the all-channel fulfilment licence (a flat fee for unlimited fulfilment locations) that exceeds the deployed fulfilment footprint. The buyer-side artefact is the active-fulfilment-location count and the order-line volume by location.
The wider Salesforce shelfware spoke reads the Order Management over-buy pattern.
Commerce Cloud has a separate API capacity surface that governs the inbound integration footprint. The OCAPI (Open Commerce API) and the SCAPI (Salesforce Commerce API) carry the storefront integration calls, the headless-storefront calls and the third-party integration calls (the inventory feed, the price feed, the order-management feed).
The API capacity is the silent gate on the headless-architecture decision. A merchant running a headless storefront on a third-party front-end is consuming the SCAPI capacity at a multiple of the templated-storefront baseline. The wider MuleSoft Pak model spoke reads the integration-layer commercial surface that often partners with the SCAPI consumption.
The rate-card economics depend on the merchant business model. A high-velocity, low-margin merchant (a discount-retail operation, a high-volume marketplace) pays the GMV share against a thin merchandising margin; the platform-fee-to-margin ratio can compound to a meaningful share of the operating margin.
A low-velocity, high-margin merchant (a luxury-retail operation, a high-AOV B2B distributor) pays the GMV share against a deep margin; the platform-fee-to-margin ratio is less consequential. The buyer-side counter is the margin-corrected total cost of ownership: the GMV share converted to a percentage of the operating margin, compared against the open-source or self-hosted commerce-platform alternative.
The wider Salesforce BATNA spoke reads the commerce-platform alternatives (Adobe Commerce, Shopify Plus, BigCommerce, self-hosted) that frame the GMV-share negotiation.
Credible alternatives across the Salesforce family.
The tiered commercial model on the adjacent customer-engagement cloud.
A senior Admodum Salesforce advisor will read your Commerce Cloud GMV band, your Order Management seat-count and your headless-architecture API consumption on a private call. Active renewal moments route to Renewal Programme.