If you quote multiyear contracts with an annual price escalator, Winter ‘27 changes how the pricing engine does the math. Salesforce added a compound uplift mode to Revenue Cloud ramp deals, so each segment builds on the previous segment’s net price instead of the original list price (Salesforce Help). It is one setting, and it decides whether a three year deal lands on the number your contract actually promises.

What standard ramp uplift gets wrong

Ramp deals split a subscription into annual segments, each with its own price. Until now the only option was standard uplift: a fixed percentage applied against the original list price for every segment (Salesforce Help). That reads fine for a flat escalator clause, but most escalators compound. When legal writes “10% annual increase”, they usually mean year three rises off year two, and standard uplift cannot express that.

For a $100 product with a 10% annual escalator, standard uplift prices year 1 at $100, year 2 at $110, and year 3 at $110 again, because it keeps applying 10% to the same $100 list price. To match the contract, deal desks were computing 10%, then 21%, in a spreadsheet and typing the escalating percentages back in by hand (The Cloud Update). That is manual work and an easy place to quote the wrong number.

What compound uplift changes

Compound uplift asks for the rate once. Enter 10%, and the engine applies it on top of each prior segment instead of resetting to list. Here is the same $100 example:

Year	Standard uplift (10%)	Compound uplift (10%)
1	$100	$100
2	$110	$110
3	$110	$121

The third year is the whole point. The compound ramp lands on $121, which is what the contract clause meant all along (The Cloud Update). The price waterfall now shows the applied unit price uplift percentage for each segment, so a reviewer can see how every number was reached (Salesforce Help).

How to turn it on

Compound uplift is not on by default. To configure the default ramp uplift type:

1. In Setup, use Quick Find to open Revenue Settings.
2. Turn on Advanced Detail Line Pricing.
3. Set the default ramp uplift type to standard or compound (Salesforce Help).

The uplift type is set at the ramp schedule group level and propagates to every line in that group, so you cannot set it per line on an initial sale (Salesforce Help). If you drive pricing through a price revision element rather than the org default, that element has an Enable Compound Uplift checkbox which appears once you attach a lookup table. It also exposes a Base Price Multiplier, an Uplift Method, and per-segment Effective From and Effective To dates (Salesforce Help).

You can also drive the method from decision table rules through the new UpliftCalculationMethod context tag, for example compound for software and flat for hardware, and it carries through amendments and renewals (The Cloud Update).

Limits and what to test first

A few behaviours are worth knowing before you flip the switch:

• The first segment has no prior segment to compound from, so it is priced at the baseline with an applied uplift equal to the line item’s unit price uplift.
• On renewal the compounding resets. Year 1 of the new term becomes the new baseline.
• For amendments, the previous segment’s uplift drives the applied percentage.
• Ramped records created before Winter ‘27 keep standard uplifts. Compound mode applies only when set on a new transaction.
• You can configure up to 10 ramp segments per transaction line, and ramped line items support the GMT time zone only (Salesforce Help).

One more thing before you enable it in production. Salesforce has documented a known Transaction Management issue affecting ramp deals that use compound uplift, where repricing or adding uplift percentages can produce incorrect prices (YuniQ). Treat compound uplift as something to switch on in a sandbox first, then reconcile quote totals against a deal you already know is correct.

What to do next

Three steps for CPQ and Revenue Cloud admins this month:

1. Confirm scope. Compound uplift lives in Revenue Cloud, now Agentforce Revenue Management, with the Revenue Cloud Growth or Revenue Cloud Advanced license. If you run only the legacy Salesforce CPQ managed package, this specific change does not apply to you (YuniQ).
2. Choose the mode per product family. Decide where the contract truly compounds, usually subscription software, and where a flat percentage is correct, often hardware. Drive the choice with a decision table rather than leaving it to the rep.
3. Reconcile a real deal. In your sandbox, reprice a signed multiyear ramp under compound uplift and check each segment price against the contract before you enable it org wide.