How do CPQ renewals work?
Renewal Quotes, Uplifts, Co-Terming, and Amendments Explained
CPQ Renewals: How Renewal Quoting Works in Salesforce
By Kuldip Hillyer, Founder & CEO, Kugamon · Published September 15, 2026
A CPQ renewal is a quote generated from what the customer already owns — the active subscriptions and renewable products on their contract — repriced and re-termed for the next period. It isn't a copy of the original quote. The original quote is history. The contract is the present, and the renewal quote is built from the present.
That distinction is where most renewal problems start. Build the renewal from the original deal and it misses every mid-term change: the seats added in month seven, the module dropped in month nine, the price cap negotiated at signing. Build it from the current contract and it reflects all of them by construction.
This guide covers the renewal models your CPQ can run, what a renewal quote is made of, how uplift and price protection apply, how mid-term amendments reshape it, how renewal quoting differs across Salesforce CPQ, Revenue Cloud Advanced, external quoting tools, and a Salesforce-native platform like Kugamon Subscription Management, and which metrics show whether it's working. The automation side — notices, scheduled jobs, auto-generated renewal orders — has its own guide: how to automate subscription renewals.
What Counts as a CPQ Renewal
Any quote whose lines originate from an existing contract rather than a blank opportunity is a renewal quote. It has three things a new-business quote doesn't: a source contract, a fixed start date (the day after the current term ends), and a pricing rule that references the customer's current price instead of list. Everything else — approvals, discounts, documents, e-signature — is ordinary CPQ. Renewals are a data problem before they're a quoting problem. The quote is easy. Knowing exactly what the customer owns on the day you build it is the hard part.
Renewal Models: Which One Does Your CPQ Use?
A renewal model is the rule that decides whether a customer's term continues, on what terms, and what has to happen for it to take effect. Most B2B contracts run one of four.
| Renewal model | How the term continues | What it means for quoting |
| Term-based quote renewal | Term ends on a fixed date; the customer signs a new quote or order for the next period | A full renewal quote every term, built from current subscriptions and signed before the end date |
| Auto-renew (evergreen) with opt-out | Term rolls over automatically unless the customer cancels by a notice deadline | Quote is optional, but the CPQ still generates the renewal order, applies any uplift, and records the notice date |
| Contracted renewal with negotiated uplift | The contract fixes the renewal price or caps the increase (for example, "no more than 5% per year") | The renewal quote reads the cap from the contract; an uplift above it is a breach, not a negotiation |
| Uncontracted / at-list renewal | No renewal terms; each renewal reprices at the current list price | The quote pulls current price-book prices; expect negotiation, so start earliest |
Most companies run more than one. Enterprise contracts negotiate caps, self-serve plans auto-renew, and legacy customers on old price lists are effectively uncontracted. Your CPQ needs to know which model applies to each contract, because the pricing rule depends on it.
Anatomy of a Renewal Quote
A renewal quote is six decisions, made in order. Get the source right and the rest is arithmetic.
1. Source lines from active subscriptions and renewable products
The lines come from the contract, not the original quote: every subscription that's active on the renewal date and flagged to renew, plus any product flagged renewable that isn't tracked as a subscription (a support plan, a license bundle). Cancelled subscriptions are excluded. Mid-term expansions are included. If your CPQ can't answer "what does this customer own today" from one record, the renewal quote will be wrong in proportion to how much changed during the term.
2. Renewal term and dates
The start date is the day after the current contract ends; the end date is start plus the renewal term. The term usually matches the original, but multi-year deals often renew to one year, and one-year deals sometimes renew to multi-year for a discount. Two settings matter: whether the renewal extends the existing contract or creates a new one, and whether the term is fixed or editable on the quote.
3. Renewal pricing method: same price, list price, or uplift percent
Three options, and the contract decides. Same price: the line carries the customer's current effective price. List price: the line reprices from the current price book, and the customer loses whatever discount they negotiated. Uplift percent: the current price times one plus the uplift, set per account or per product. Uplift is applied when the renewal quote is generated, before the rep touches it. That gives the rep a defensible starting number and makes any discount below it a visible, approvable decision.
4. Price protection and caps
Price protection is a contract term limiting how much the price can rise at renewal — a fixed price for a set number of years, or a cap on the annual increase. The cap needs to live on the contract or account record where the CPQ can read it, not in a PDF. If the uplift rule says 7% and the contract says 3%, the quote should come out at 3% without anyone remembering.
5. Substitutions when a product is retired
A renewal quote can't renew a product that's no longer sold, so the catalog needs a renewal-product mapping: when Product A renews, quote Product B instead. Without it, someone edits every affected renewal by hand, and the ones they miss renew a SKU that doesn't exist.
6. Add-ons and removals at renewal
Renewal is a negotiation. The customer often wants to add a module or drop seats, and the renewal quote should support both as ordinary line edits, with the subscription changes flowing through on release. What it shouldn't do is treat the add-on as a separate opportunity with its own term. That creates the multi-renewal problem co-terming exists to prevent.
How Mid-Term Amendments Change the Renewal
An amendment changes the renewal because the renewal is built from the contract, and the amendment changed the contract.
Take the standard case. A customer on a twelve-month term adds ten seats in month seven. In a well-designed CPQ, the expansion co-terms to the contract end date — the new seats end when the original ones end — and prorates the charge for the remaining part of the term. On release, the contract's subscription count and ARR roll up to include the new seats, and the renewal opportunity is updated so the renewal quote reflects the expanded footprint. The customer gets one renewal for 110 seats, not a renewal for 100 and a second one five months later for 10. Cancellations work in reverse: cancelling a subscription mid-term decrements it from the renewal, so the quote never offers the customer something they've already dropped.
The failure mode is a CPQ that treats the renewal opportunity as a snapshot taken at the original close. Every amendment then has to be re-keyed onto the renewal by hand. If your platform can rebuild the renewal lines from the contract, run it before every renewal quote goes out. The proration math and co-terming rules behind amendments are in how subscription amendments work.
Renewal Quoting in Salesforce CPQ vs. Its Successors
The platforms differ less in what the renewal quote looks like and more in where its source data lives. Salesforce CPQ has been end-of-sale since March 2025 — existing customers can renew, and Salesforce has published no retirement date — so most teams evaluating renewal quoting are also choosing a successor.
| Platform | Where the contract and subscriptions live | How the renewal quote is built | Uplift and co-terming | Published pricing |
| Salesforce CPQ (legacy) | Native Salesforce records | Contract renewal settings generate a renewal opportunity and quote from the contract | Per the contract renewal settings | End-of-sale; existing customers can renew |
| Revenue Cloud Advanced (Salesforce) | Native Salesforce records on the new Revenue Cloud data model | First-party successor; existing CPQ configuration doesn't carry over directly — confirm the renewal flow in a demo | Confirm in a demo against your renewal model | $200/user/month, billed annually |
| Kugamon Subscription Management | Native Salesforce Contract, Subscription, and Asset records | Renewal opportunity auto-created on order release; renewal notice 120–90 days before end date; renewal order auto-generated 60–30 days out; "Refresh Products" rebuilds the renewal lines from contributing orders | Uplift percent per account or per product; expansions co-term and prorate to the contract end date | $95/user/month (AppExchange listing) |
| External quoting tools synced to Salesforce (DealHub and others) | Vendor platform; synced copy in the CRM | Renewal quote built in the vendor platform, synced to the CRM | Per vendor; confirm in a demo | Not published — contact vendor |
The test question for any of them: where's the record that says what the customer owns today, and does the renewal quote read from it directly or from a copy? A synced copy means the renewal is as current as the last sync. The cost model for the first-party path is in How Much Does Revenue Cloud Advanced Cost?, and the wider field is in Salesforce CPQ alternatives.
Renewal Metrics That Tell You It's Working
Five numbers, all computable from the contract and renewal records if they're kept current.
| Metric | Formula | How to read it |
| Renewal rate (logo) | Contracts renewed ÷ contracts up for renewal in the period | Counts customers, not dollars; a high logo rate can hide shrinking accounts |
| Gross revenue retention (GRR) | (Starting ARR − churn − contraction) ÷ starting ARR | Capped at 100%; measures what you kept before any expansion |
| Net revenue retention (NRR) | (Starting ARR − churn − contraction + expansion + uplift) ÷ starting ARR | SaaS Capital's 2025 benchmark: median around 102% for $25–50K ACV; 110% or higher correlates with faster growth |
| Uplift capture rate | Uplift dollars realized ÷ uplift dollars quoted | Tells you whether the uplift rule survives negotiation |
| Days-to-renew before end date | Contract end date − renewal signature date, averaged | Negative means late renewals; rising means your notice cadence is working |
The last two are the ones most teams don't track, and they're the ones that measure the renewal quote itself rather than the customer. The full metric set is in how to measure subscription metrics.
Common Mistakes in Renewal Quoting
- Building the renewal quote from the original quote. Clone it and you renew the customer's day-one footprint, not the one they have now.
- Forgetting amendments. If expansions and cancellations don't flow to the renewal automatically, someone has to remember them. Someone won't.
- Applying uplift after negotiation instead of before. Uplift added at the end looks like a surcharge and gets waived. Uplift built into the generated quote is the starting price, and every discount from it is visible.
- Quoting the renewal 30 days out. Procurement cycles run longer than that. A late renewal quote lapses, goes month-to-month, or renews at last year's price because there was no time to argue.
- Keeping price protection in the PDF. A cap the CPQ can't read is a cap the CPQ will break.
Frequently Asked Questions
Q: What is a CPQ renewal?
A CPQ renewal is a quote generated from the subscriptions and renewable products a customer currently owns on their contract, repriced under the renewal pricing rule and re-termed for the next period. It's built from the current contract, not the original quote, so it reflects every mid-term amendment.
Q: What is a renewal model in CPQ?
A renewal model is the rule that determines how a customer's term continues: a term-based renewal that needs a new signed quote, an auto-renew or evergreen term with an opt-out deadline, a contracted renewal with a negotiated uplift or cap, or an uncontracted renewal that reprices at list. The model decides which pricing rule the renewal quote applies and whether a signature is required.
Q: How do Salesforce CPQ and DealHub compare for renewal quoting?
The difference is architectural. Salesforce CPQ stores the contract and subscription records as native Salesforce objects and generates the renewal opportunity and quote from them, so the renewal's source data is in the CRM. DealHub builds the renewal quote in its own platform and syncs it to Salesforce, so the CRM holds a synced copy rather than the source. Which is better depends on whether your reporting, forecasting, and finance processes need the source record in Salesforce. Salesforce CPQ is end-of-sale, so a like-for-like evaluation should also include its successors.
Q: What is a renewal uplift, and when should it apply?
A renewal uplift is a percentage increase applied to the customer's current price when the renewal quote is generated. It should apply before the quote reaches the rep, so the uplifted price is the starting point and any discount below it is a visible, approvable decision. Uplift can be set per account, per product, or both, and it must respect any price-protection cap in the contract.
Q: How do mid-term amendments affect the renewal quote?
Because the renewal quote is built from the contract, any change to the contract changes the renewal. An expansion that co-terms to the contract end date adds its lines and value to the renewal opportunity; a cancelled subscription is removed from it. If your CPQ doesn't update the renewal automatically, rebuild the renewal lines from the contract before quoting.
Q: How do you manage renewal products in Salesforce?
Flag each product as renewable or not, decide whether it creates a subscription or an asset record, set whether its price is subject to uplift, and map a replacement renewal product for anything you plan to retire. Those four settings, held at the product level, let the CPQ assemble a renewal quote from the contract without manual line editing.
Q: What is price protection in a renewal?
Price protection is a contract term that limits how much the price can increase at renewal, either by fixing the price for a set number of years or by capping the annual increase. For the renewal quote to honor it, the cap needs to be stored on the contract or account record where the CPQ can read it, not only in the signed document.
Q: How far ahead should a renewal quote go out?
Far enough that the customer's budget cycle and procurement review finish before the end date. A common cadence is a renewal notice 120 to 90 days before the contract ends and a renewal order 60 to 30 days out. Quoting 30 days out leaves no time to negotiate, and a late renewal is often a lapsed one.
Next Steps
Pick one contract that had a mid-term expansion and build its renewal quote in your current CPQ. If the expanded seats aren't on it without manual editing, the source data is the problem, not the quote. To see renewals built natively from Salesforce contract and subscription records, explore Kugamon Subscription Management, read how subscription management works in Salesforce, or schedule a demo and bring a contract that changed mid-term. No pitch — just the renewal quote, built from what the customer actually owns.