CPQ approval rules
Approval rules protect margin and terms without stalling deals, when there are few of them, they're clear, and each is tied to a real risk: discounts beyond policy, margin below a floor, non-standard terms, or configurations that need engineering. Here's how to design them, how Salesforce implements them in classic CPQ and in Revenue Cloud, and a matrix you can adapt.
- What to approve
- Thresholds and chains
- Smart approvals
- Salesforce CPQ vs. Revenue Cloud
What to approve
- Discount beyond policy, by product family or deal size.
- Margin below a floor. This is better than discount alone when costs vary by configuration.
- Non-standard payment or contract terms: extended terms, uncapped liability, unusual warranty.
- Special configurations outside the standard rules that need engineering review.
- Large deals above a value threshold.
An approval matrix
Discount ≤ 10% → no approval
10% < discount ≤ 20% → sales manager
Discount > 20% OR margin < 28% → sales manager, then finance (sequential)
Payment terms > Net 45 → finance
Custom configuration flagged by rules → engineering (in parallel with commercial approvals)
Quote total > $250,000 → VP sales
Test it: a $180,000 quote at 18% discount, 31% margin, Net 30, standard configuration
→ sales manager only
Approve on margin when you can. A 15% discount on a high-margin product can be safer than 8% on a low-margin one.
Salesforce CPQ Advanced Approvals
Classic Salesforce CPQ uses the Advanced Approvals package, which is built from:
| Concept | What it does | Example |
|---|---|---|
| Approval rule | Defines an approval requirement and its approver | Discount approval for Product Family A |
| Approval condition | When the rule fires | Quote line discount > 15% |
| Approver | User, group or dynamic field (e.g. the rep's manager) | Regional sales manager |
| Approval chain | Routes approvals in sequence | Manager, then finance over 25% |
| Smart approvals | On resubmission, skips re-approval when the values a condition tests haven't changed | Rep edits the quote notes only → no re-approval |
What's different
Salesforce CPQ is end of sale for new customers. Existing customers can keep, renew and expand it, and Salesforce has announced no end-of-life date. New investment goes to Revenue Cloud Advanced (RCA). In Revenue Cloud, quote approvals are typically built with Salesforce's flow-based approval tools (approval processes or approval orchestrations in Flow Builder, with Advanced Approvals settings) rather than the CPQ managed package. If you're migrating, plan to rebuild approval logic rather than port it as-is.
Keep approvals fast
- Few rules. Every rule should map to a named risk. Delete rules nobody can explain.
- Show context. Approvers should see margin, discount, deal size, configuration and the reason for the exception on one screen.
- Parallel where independent. Engineering and finance can review at the same time.
- Service levels. Set a response time and an escalation path or backup approver.
- Report. Track approval volume, time to approve and rejection rate by rule. A rule that's always approved may be a policy that needs changing.
Where approval designs go wrong
- Thresholds on list-price discount when cost varies widely by configuration.
- Re-approving trivial edits because smart approvals aren't set up.
- Approvers seeing a number with no picture of what's being sold.
- Rules that block quoting entirely instead of routing for approval.
Approvers see the product
RenderDraw's visual CPQ shows the configured product in 2D or 3D, so approvers and engineers see what they're approving. Its workflows include human gates that route approvals, exceptions and engineering reviews, and they hand off to CPQ, pricing and Salesforce. Available surfaces and integrations depend on your implementation. Book a demo.
Questions estimators ask.
What should trigger a CPQ approval?
Discounts beyond policy, margin below a floor, non-standard terms, special configurations that need engineering, and deals above a value threshold.
What are Salesforce Advanced Approvals?
The approval package for classic Salesforce CPQ. Approval rules, conditions, approvers and chains route approvals, and smart approvals skip re-approval when the tested values haven't changed.
Is Salesforce CPQ being retired?
It's end of sale for new customers, not end of life. Existing customers can renew and add users, and Salesforce has announced no end-of-life date. Revenue Cloud Advanced is the successor.
How do approvals work in Revenue Cloud?
Typically through Salesforce's flow-based approval tools configured in Flow Builder, rather than the CPQ Advanced Approvals package.
How many approval rules should we have?
As few as cover your real risks. Track rules that are almost always approved and reconsider them.
Approvals with the configuration in view.
Book a demo to see RenderDraw's configuration and approval workflow in Salesforce.
- Pick one representative product, rule set or RFP.
- Walk it through configuration, pricing and review with RenderDraw.
- Decide on next steps with real output in front of you.
Where these numbers come from
We checked this guide against the standards, manufacturer documents and industry references below (last reviewed November 2026). Figures marked as rules of thumb are typical ranges, not requirements; your project documents, local code and your own cost history govern.