SAP CX licensing across five clouds. Where the volume fees grow faster than seats.

SAP CX is five clouds with five different metrics. Sales and Service are priced per user and easy to model, while the cost surprises come from Commerce, Customer Data and marketing, which bill on volume.

Which products does SAP CX licensing cover?

SAP Customer Experience is five separate clouds that SAP sells together and licenses one by one: Sales Cloud, Service Cloud, Commerce Cloud, Customer Data Cloud and the marketing tools. SAP presents the whole set on its customer relationship and CX page, but each cloud has its own metric and its own supplement in the contract.

Several of the products came to SAP through acquisitions, and their pricing logic came with them. The names have also moved more than once, so check which product sits behind each line of your order form.

• Sales Cloud and Service Cloud. The CRM applications, now sold as Version 2 alongside the older Cloud for Customer releases.
• Commerce Cloud. The online storefront platform SAP built on its hybris acquisition.
• Customer Data Cloud. The former Gigya platform, bought in 2017, covering customer identity and access management for B2C and B2B plus consent and preference management.
• Marketing. Emarsys, which SAP renamed SAP Engagement Cloud in February 2026 and now sells in a base edition and an enterprise edition.

How is each SAP CX cloud licensed?

Sales Cloud and Service Cloud are licensed per named user by tier, while Commerce, Customer Data and marketing are licensed on a volume that grows with your customers and revenue. The second group is where budgets break, because it costs what your business does. Each product supplement, cited in your order form by version, holds the detail.

How are Sales Cloud and Service Cloud licensed?

Both are licensed mostly per named user, by tier, so cost tracks headcount and is easy to model. SAP describes the products on its Sales Cloud and Service Cloud pages. Watch the tier definitions, because SAP gates features by tier and that pushes upgrades.

The Version 2 supplement defines a user as any individual authorized to access the service, whether or not they log in. It also sets usage limits worth checking before an integration project:

• Storage. 10 GB per user, capped at 10 TB or 250 million data records in total, whichever comes first.
• API and event calls. 150,000 per 24 hours, plus 1,500 per licensed user.
• Test tenants. No more than 50 users may access each test tenant.

How is Commerce Cloud priced?

Commerce Cloud frequently bills on a share of gross merchandise value, not on seats. That ties your software cost to revenue, so a good year raises the bill. SAP describes the product on its commerce platform page. Model the fee against your growth plan for the whole term, since last year's sales understate it.

The Commerce Cloud supplement sets out the metrics that decide the fee:

• GMV. Annual gross revenue from sales through the platform, excluding shipping, handling, taxes and returns.
• Orders. The alternative metric, counting sales and service orders per contract year. Returns and refunds do not reduce the count.
• Capacity units. Infrastructure sold in units of 64 GB of memory. If you exceed the memory limit for three or more consecutive months, SAP may require a scalability add on or a move to a higher GMV or orders tier.

How does Customer Data Cloud licensing work?

Customer Data Cloud counts customer records or active identities. The number grows each time you onboard a customer and rarely shrinks, because few companies delete accounts. Negotiate the tier and the overage rate carefully, since record growth is the metric most likely to outrun the contract.

How does marketing get counted?

The marketing tools, including the Emarsys platform, typically bill on contacts or message volume. Both scale with audience size and campaign activity. Audit your active contact base before signing, because many agreements count dormant records against the tier.

• Contacts: active and dormant records both count in most tiers.
• Sends: high frequency campaigns push message volume fast.
• Channels: adding SMS, mobile push or web channels can change the metric basis.

How much can volume growth add to an SAP CX bill?

Over a three year term, volume growth can add more to a CX bill than the entire seat budget. Say you run 300 Sales and Service users at $1,200 per user per year, and your online store takes $200 million in GMV at a fee of 0.4 percent. These rates are hypothetical and are not SAP quotes.

Now compare what each extra concession is worth over the three years:

• Another 10 percent off the seat price. Saves $113,400.
• Commerce rate cut from 0.4 to 0.35 percent. Saves $364,000.
• A cap of 10 percent a year on Commerce fee growth. Holds year 2 at $880,000 and year 3 at $968,000, saving $264,000.

Customer Data Cloud follows the same curve. If you start at 1.7 million identities against a 2 million tier and your customer base grows 25 percent a year, you pass the tier late in year 1.

By the end of year 3 you hold about 3.3 million identities, and 1.3 million of them sit above the tier at the overage rate unless the contract says otherwise.

Where do SAP CX costs run higher than expected?

Most overruns come from add ons and from volume meters that grow with the business. Map both before you commit.

How do sandbox and integration costs add up?

Non production sandboxes, additional environments and integration packs are usually priced separately. Teams budget the seats and forget the rest. Commerce Cloud sells non production environments in small, medium, large and extra large sizes. Connecting the clouds to S/4HANA often runs through Integration Suite on SAP BTP, which is billed separately again.

What overage terms matter most?

Overage is the most expensive line on the volume clouds once growth arrives. When records, contacts or merchandise value cross the contracted tier, the rate can be punitive. Agree these three terms before you sign, because after a breach you are negotiating with no alternative:

• Overage rate: cap the per unit cost above the tier.
• Grace band: secure tolerance before overage triggers.
• Step up: agree the next tier price in advance.

Why we would not spend the negotiation on seat discounts

The usual advice is to concentrate on seat discounts, because seats are the visible line on the quote. We disagree. In the CX deals we benchmarked, Commerce and Customer Data drove the cost growth, rising 20 to 40 percent faster than seat counts as the business succeeded.

A deep seat discount means little when the value based fee compounds every year. Take the standard discount on seats, then spend your negotiating capital on the overage rates, grace bands and tier step ups for the volume clouds, the metrics that scale with your success.

In SAP CX, the seat discount you fight for matters less than the overage rate you forget to negotiate.

What have we seen in recent SAP CX negotiations?

Across roughly 25 to 35 SAP CX deals we benchmarked in 2024 and 2025, the volume based clouds caused the cost surprises. The same three patterns came up again and again:

• Commerce fees outpaced seats. Value based Commerce Cloud fees rose 20 to 40 percent faster than seat counts. Across the volume clouds, fee growth typically ran about 30 percent ahead of seat growth.
• Record growth beat the tier. In most accounts, Customer Data Cloud record growth outran the contracted tier.
• Add ons landed late. Sandbox and integration add ons added 10 to 20 percent on top of the license, around 15 percent in a typical deal.

What will the SAP account team say, and how should you answer?

Expect the account team to steer the discussion toward the seat discount and a single bundle price. These are the lines we hear most on CX deals, with the reply we recommend:

• "GMV pricing means we only win when you win." Ask for a rate that declines as GMV passes set bands, and a cap on annual fee growth.
• "The tier gives you plenty of headroom." Ask for the headroom as a number, compare it with your three year forecast, and put the overage rate in the order form.
• "Standard sandboxes cover most customers." List the environments your project plan needs, by size, and have each one priced now.
• "Take all five clouds and we can improve the overall discount." Ask for the price of each cloud as its own line. A blended discount hides the volume rates you will pay for years.
• "This price is only valid until quarter end." SAP deadlines follow its own quarters, covered in our note on SAP fiscal quarter timing. Use the date if it suits your plan, and let it pass if it does not.

What SAP CX terms should you negotiate?

Split the negotiation by metric type. Win predictable discounts on the user clouds, then use your negotiating capital on the volume clouds where cost compounds. Read the cloud terms in the SAP agreements center before you sign, including the supplement version your order form cites.

• Volume protection: cap overage and lock tier step up rates in the order form itself.
• Bundle clarity: price each cloud line by line.
• Price hold: lock unit rates across the term.
• Sandbox terms: include the environments you actually need.

Contract wording to ask for

• Metric definitions fixed at signing. Confirm the order form names the supplement version in force at signature and that renewals keep it unless you agree a change, so a later revision cannot alter what is counted.
• A dormant record rule. Exclude contacts and identities with no activity for a set period, or confirm your right to purge them before each count.
• Overage priced relative to the base. State overage as the committed unit rate, or a fixed small premium on it, so growth costs what the base volume costs.
• Reallocation rights. Allow unused value in one cloud to move to another at renewal, so a slow Service rollout can fund Commerce growth.
• A renewal cap. Fix the maximum increase for the next term now, while SAP still wants the signature.

Our white paper The SAP contract. The buyer side fundamentals sets out nine contract fundamentals: discount baselines, indirect access caps, price protection, audit clauses and clean exit terms. For CX specifics beyond licensing, see our guide to SAP CX negotiation.

How do you check your own SAP CX usage before signing?

Pull your own numbers for each metric before SAP presents a quote, and reconcile them against the supplement definitions. Vendor sizing tends to start from the top of your growth range.

• Named users. List every user authorized in Sales and Service Cloud, including those who rarely log in, and remove leavers and duplicate accounts.
• GMV. Take online revenue from finance, then strip out shipping, taxes and returns as the definition allows. That net figure is what the fee should apply to.
• Identities. Count Customer Data Cloud accounts by site and flag those with no login in 12 or 24 months.
• Contacts. Split the marketing database into engaged, dormant and unsubscribed records before you agree a tier.

How SAP structures its cloud subscriptions more broadly, including tiers and renewal terms, is covered in SAP cloud licensing models.

What to do next

1. List the scope. Name every CX cloud in scope and its exact metric.
2. Forecast volume. Project records, contacts and merchandise value across each year of the term.
3. Split the cost. Separate user based cost from volume based cost in your model.
4. Audit the base. Check your active contact and record base before signing.
5. Negotiate the volume terms. Agree overage rates, grace bands and tier step ups.
6. Price the extras. Put sandboxes and integration packs into the deal.
7. Hold the price. Lock unit rates and a price hold across the full term.

Frequently asked questions