Special Terms
Special Terms in Salesforce CPQ are non-standard pricing, contractual clauses, or commercial exceptions attached to a quote, order, or contract that go beyond the standard agreement language.
Definition
Special Terms in Salesforce CPQ are non-standard pricing, contractual clauses, or commercial exceptions attached to a quote, order, or contract that go beyond the standard agreement language. They cover everything from negotiated discount tiers, payment schedules, volume commitments, and renewal protections on the pricing side, to non-standard liability caps, indemnification language, and SLA commitments on the legal side. Special Terms exist because real B2B deals rarely fit a one-size-fits-all template, and they need to be tracked separately so finance, legal, and operations can honor them through the lifecycle of the customer relationship.
The mechanism for storing Special Terms varies by org. Some use a Long Text field on the Quote or Opportunity. Some use a related Special Terms object with structured fields per clause. Sophisticated orgs use Salesforce CPQ Contract Terms with Clause Library integration, which gives finance a structured catalog of pre-approved clauses that sales can select from rather than free-text. The choice depends on how much governance the legal team wants and how often Special Terms are negotiated.
How Special Terms work in Salesforce CPQ across pricing, legal, approvals, and renewal
Why Special Terms exist and what problem they solve
Standard quote templates and contract templates are designed for the most common deal shape. Once a customer asks for something unusual (a 10 percent volume discount above 1,000 seats, a payment schedule of net 90 instead of net 30, a most-favored-nation clause, a service level commitment higher than the standard SLA), the standard template stops fitting. Special Terms are the structured place to record those negotiated exceptions so they survive the deal lifecycle. Without them, exceptions get scattered: a Slack message between sales and legal, an email thread, a one-off clause typed into the quote PDF that legal never sees. Each unstructured exception is a future support escalation when the customer asks finance to honor a commitment that nobody can find. Special Terms make the commitment explicit and discoverable.
Pricing Special Terms versus Legal Special Terms
Most orgs treat Special Terms as two distinct categories. Pricing Special Terms cover non-standard discount tiers, payment schedules, volume commitments, renewal protections (cap on the annual price increase), and any negotiated unit prices. They drive billing automation and renewal quoting, so they need structured fields that the billing system can read. Legal Special Terms cover non-standard contract language: liability caps, indemnification, data ownership, audit rights, SLAs above the default. They drive contract-redline workflow and need legal sign-off but do not necessarily drive automated downstream behavior. Mature CPQ implementations store these in separate objects (Quote Pricing Term and Quote Legal Term) or in separate field groups on the Quote so that finance and legal can each work the parts they own without stepping on each other.
Clause Library, pre-approved Special Terms, and the negotiation funnel
Salesforce CPQ supports a Clause Library where legal pre-approves clause variants that sales can select from. Each clause is a record with the variant name, the actual contract language, the discount percentage or commercial impact, and the approval level required to use it. Sales picks from the library on the Quote, the platform calculates the financial impact, and the chosen clauses flow into the generated contract document. The library replaces free-text Special Terms with a structured selection process, which is much faster to legal-review and much safer to honor downstream. If a customer asks for a clause not in the library, the rep submits a new clause for legal approval; once approved, the clause becomes available to every future deal. Over time, the library captures the negotiation patterns of the customer base.
Approval workflows for Special Terms
Special Terms are the most common driver of approval workflow in CPQ. Each clause has an approval level based on its financial impact or its deviation from standard language. A 5 percent discount may be auto-approved up to manager level. A 15 percent discount may require VP approval. A net-90 payment schedule may require CFO sign-off. A non-standard liability cap may require legal counsel review. Salesforce CPQ supports per-clause approval rules through Advanced Approvals (or the older Approval Process feature), routing each Quote that contains the clause to the right approver before the Quote can be presented to the customer. Mature CPQ orgs document the approval matrix as part of the Clause Library so sales sees the approval requirements upfront and can negotiate within them.
How Special Terms flow into the order, contract, and billing
After a Quote with Special Terms is accepted by the customer, the terms have to flow into the downstream artifacts. The Quote-to-Order step copies the Special Terms onto the Order record so fulfillment honors them. The Order-to-Contract step renders the terms into the contract document (typically a Word or PDF generated by a CPQ contract template). The Contract-to-Billing step makes the negotiated payment schedule and discount tier visible to the billing system so invoices reflect the agreement. Each handoff is a place where Special Terms can get lost. Mature implementations validate each handoff with a Reconciliation Report that confirms Special Terms on the Order match the Quote, on the Contract match the Order, and on the Invoice match the Contract. This is essential for orgs where billing leak is a real cost.
Tracking, renewal, and the value of structured Special Terms
Renewals are where structured Special Terms pay off the most. When a customer renews a year later, the Renewal Quote should automatically inherit the Special Terms from the prior Order (negotiated discount, payment schedule, SLA, renewal cap). With structured Special Terms, this inheritance is automated through CPQ Renewal Quoting. With free-text Special Terms, the rep has to manually copy the language from the old contract, which is error-prone and time-consuming. Reporting also depends on structure: questions like How many customers have non-standard payment terms?, How much margin do volume discounts cost us by region?, and Which Special Terms are most commonly negotiated? are easy with structured data and impossible with free text. Treat structured Special Terms as a long-term investment in commercial intelligence, not just a CPQ feature.
Standing up Special Terms in Salesforce CPQ
Standing up Special Terms in Salesforce CPQ is a coordinated effort across sales, legal, finance, and operations. The technical setup is a four-piece configuration: define the data model (where Special Terms live and how they connect to the Quote, Order, Contract, and Invoice), build the Clause Library with legal-approved variants, configure approval rules per clause, and wire the downstream flow so terms make it to billing. This guide covers the recommended sequence; skipping any step leaves a gap that surfaces as a customer dispute or a billing leak later.
- Design the data model and choose your storage approach
Decide whether Special Terms live as fields on the Quote object, as a related Special Terms custom object, or through Salesforce CPQ native Quote Term and Contract Term objects. The Quote Term approach is the most flexible and integrates with the Clause Library. Define the fields each Special Term needs: Name, Type (Pricing or Legal), Variant Name (which clause), Financial Impact, Approval Level Required, Approver, Status. Plan how each Special Term connects to the parent Quote and to the downstream Order, Contract, and Invoice records. Document the data model in the CPQ design document so future admins inherit a clear picture.
- Build the Clause Library
Work with legal counsel to identify the clauses you are willing to pre-approve. Common starting points: discount tiers (5, 10, 15, 20 percent), payment schedules (Net 30, Net 60, Net 90), volume commitments (per-seat thresholds), renewal protections (annual increase cap), liability cap variants (1x ACV, 2x ACV), and SLA variants (99.5, 99.9, 99.99 percent uptime). For each, capture the actual contract language, the approval level required, and the financial or operational impact. Store the clauses as records in a Clause object. Tag each clause with which Quote types it can apply to (new business, renewal, expansion). The library is a living artifact; expect to add clauses over time as new patterns emerge.
- Configure approval rules per clause
In Salesforce CPQ Advanced Approvals (or the older Approval Process if you do not have Advanced Approvals), define an approval rule for each clause. Set the entry criteria (Quote has this clause), the approver chain (Sales Manager, then VP, then CFO depending on the clause), the rejection behavior (Quote returns to sales with a note), and any auto-approval thresholds (under 5 percent discount auto-approves at manager level). Test each rule by submitting a Quote with the clause and confirming the right approver is notified. Document the approval matrix in the CPQ runbook so sales reps know what to expect before they negotiate.
- Wire the downstream flow and add reconciliation
Configure the Quote-to-Order, Order-to-Contract, and Order-to-Invoice flows in Salesforce CPQ to copy Special Terms onto the downstream records. Use Trigger Flows or Apex to validate that no terms are lost in the handoff. Build a Reconciliation Report that checks each Special Term on the Quote against the matching Term on the Order, Contract, and Invoice. Schedule the report to run weekly and surface any drift. For renewals, configure CPQ Renewal Quoting to inherit Special Terms from the prior Order by default; reps can override on a per-clause basis. Document the renewal inheritance rules in the sales playbook so reps know what carries over.
- Free-text Special Terms in a Long Text field do not flow to billing automatically. Anything that does not have a structured field for the financial impact has to be honored manually by finance, which is error-prone and slow.
- Approval rules execute at Quote submission time. A clause added after approval requires re-approval; without re-trigger logic, reps may bypass the approval chain accidentally by adding clauses post-submission.
- Clause Library variants do not version automatically. If legal updates the language on a clause, existing Quotes still reference the old language. Plan a re-quoting cadence for material clause updates.
- Special Terms do not auto-inherit on renewal unless you configure Renewal Quoting to do so. Without explicit configuration, the renewal starts from the standard template and reps have to manually re-add the terms.
- Reconciliation Reports are only as good as the data model. If a Special Term lives in two different places (Quote Term object and a Long Text field on the Quote), the reconciliation has to check both. Pick one storage approach and stick to it.
Trust & references
Straight from the source - Salesforce's reference material on Special Terms.
- Quote Terms in Salesforce CPQSalesforce Help
- Advanced Approvals OverviewSalesforce Help
- Clause Library in Salesforce CPQSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What are Special Terms?
Q2. Why do they need approval?
Q3. How can CPQ help?
Discussion
Loading discussion…