AI uses for records
When a one-off price spreads: a pricing exception sales dataset
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
A pricing exception sales dataset is only useful if every approved exception carries its boundary: the account, products, quantities, dates and condition it was granted for, why it was approved, and where the price appeared afterward. Software lets exceptions spread quietly. Salesforce CPQ renews at the same price when no renewal method is set, and an Odoo pricelist assigned to a customer becomes the default on that customer's new quotations.
Value drivers
Pricing exception sales
Key takeaways
- Freeze the exception's boundary at approval: account, products, quantity limits, start and end dates, the condition the customer met, the reason and the approver's role.
- In a field check of Odoo and Apache OFBiz, none of three default price records has a field for who approved a price or why, so the rationale has to be joined from the approval record.
- Five routes carry a one-off price into the standing price: renewal carry-forward, account-level price lists, open-ended coupon durations, linked-customer clauses and precedent.
- Label what happened to each exception after approval, from contained to carried by default, separately from whether the deal was won.
- Federal schedule contracts already ask contractors to explain the conditions behind price reductions given to the basis-of-award customer.
What separates a pricing exception from a new price?
A pricing exception is a price granted inside a stated boundary, for a reason, by someone allowed to grant it; a new price is a decision to move the boundary for everyone it covers. The dataset question is whether each exception stayed inside the boundary it was approved for, and answering it takes three things: the boundary itself, the reason, and every later transaction that used the price.
Most sales histories cannot answer that. They keep the discounted quote line and, at best, an approval stamp. How the approval decision should be recorded is covered in the site's pages on discount authority and on pricing exception approvals; this page starts after the yes, with where the price travels next.
The stakes for an AI team are concrete. A model trained on quotes where last year's exception reappears without comment learns that the exception is the price, and a pricing agent evaluated on that history is scored correct when it repeats the leak.
Five routes from a one-off price to the standing price
Exceptions travel through five routes, and four are built into software or contracts rather than memory. Each route needs its own field in the record, or the dataset cannot tell a deliberate renewal from a price that drifted forward.
Renewal carry-forward. Salesforce CPQ prices renewal quotes from a Renewal Pricing Method: Same carries the renewed subscription's price forward, Uplift adds a percentage to it, and List returns to the current price book. A Salesforce help article adds that when the picklist is left at --None--, renewal pricing defaults to Same, so a first-year concession renews unless someone chose otherwise.
Account-level price lists. In Odoo, the pricelist field on a customer record carries the help text 'Used for sales to the current partner', and draft quotations for that customer take it by default. A special pricelist created for one deal stays the customer's default until someone removes it or its rules lapse.
Open-ended discounts. Stripe coupons take a duration: once, the default, discounts the first invoice only; repeating runs for a set number of months; forever applies to every invoice. A forever coupon granted to close one deal is a permanent price unless the record says otherwise.
Linked-customer clauses. Some contracts tie one customer's price to another's. The price reductions clause in General Services Administration schedule contracts fixes a price or discount relationship to a basis-of-award customer, and a special discount to that customer that disturbs the relationship becomes a price reduction on purchases under the schedule contract, offered with the same effective date and for the same time period.
Precedent. The last approved price becomes the opening ask in the next negotiation and a training label when a model learns from approved quotes. No system field records this route, so the dataset has to infer it from later transactions. The map below pairs each route with the field that contains it:
| Route | Where it is set | Field that contains it | Outcome label when it fires |
|---|---|---|---|
| Renewal carry-forward | Renewal pricing method on the account | Renewal treatment chosen at approval: revert, carry or uplift | E3 carried by default, or E2 renewed by decision |
| Account default price list | Price list assigned to the customer | End date on each rule and a removal date for the assignment | E4 leaked in scope |
| Open-ended discount | Coupon or discount duration | Duration matched to the approved term | E3 carried by default |
| Linked-customer clause | Most-favored-customer or price reductions terms | Flag on accounts whose price moves other customers' prices | Passed on by contract; record beside E1 to E7 |
| Precedent | The next negotiation and model training | Precedent flag: one-off, or approved as a new standard | E5 copied or E6 standardized |
Which boundary fields do default price records hold?
Dates, yes; approvers and reasons, no, at least in the three records checked here. Each is a place where open-source business software stores a negotiated price; all three can hold start and end dates, and none has a field for who approved the price or why.
Odoo's pricelist rule holds a start date, an end date, a minimum quantity and what the rule applies to: one product variant, a product, a category or all products. It has no maximum quantity and no customer field; the customer link is the pricelist assigned to the customer record, and Odoo tracks changes to that assignment in the record's history. Apache OFBiz's price rule holds dates, a name and a description, and reaches customers or quantities through generic condition rows. OFBiz's agreement records come closest to a boundary: the agreement names the other party and runs between from and thru dates, its product line carries the price, and its terms can set minimum and maximum quantities. A separate status history can record who changed an agreement's status, with comments.
The practical consequence is a join. The rationale and approver live in an approval record, an email thread or a deal desk note, so the dataset needs an exception ID that links the price rule, the approval and every transaction priced under it. Free text such as a rule's name or description is not a substitute, and the check below does not count it as a reason field:
| Boundary | Odoo pricelist rule | OFBiz price rule | OFBiz agreement |
|---|---|---|---|
| Start and end dates | Yes | Yes | Yes |
| Quantity limits | Minimum only | Through condition rows | Minimum and maximum, on terms |
| Customer on the record | No; via the customer's assigned pricelist | Through condition rows | Yes, the other party |
| Who approved | No field | No field | No field; status history can show who changed status |
| Why it was approved | No field; name is free text | No field; description is free text | No field; description is free text |
The exception scope card: what to freeze at approval
Freeze the boundary in a structured record when the exception is approved, linked by ID to the price rule and the approval trail. Each field answers a question that a later reviewer, auditor or model will ask.
Leave out contact identities. The names, emails and phone numbers of the buyer's staff say nothing about whether a price stayed in bounds; keep roles, and convert prices to percent off list or price bands before the records leave the company. The minimum card:
| Field | Content | Why it matters later |
|---|---|---|
| exception_id | One ID shared by the price rule, the approval and every line priced under it | Lets each later transaction be traced to the grant |
| account_scope | Pseudonymous account ID, and whether affiliates are covered | Separates a sister company's quote from a new grant |
| product_scope | Products or categories, with minimum and maximum quantities | Shows use beyond what was approved |
| validity | Start date, end date and the renewal treatment chosen: revert, carry or uplift | Tells a renewal decision from carry-forward by default |
| condition_given | What the customer committed in return, such as term, volume or prepayment | Tests whether the price was earned or just repeated |
| reason_code and evidence | A coded reason plus the document behind it, such as a competing quote | Supports competition-law defenses and audit questions |
| approver_role | Role and approval level, not a name | Shows whether the grant was within authority |
| precedent_flag | One-off, or approved as a new standard with a policy change reference | Keeps deliberate standardization apart from drift |
| linked_price_exposure | Whether the account is a basis-of-award or most-favored-customer reference | Flags exceptions that move other customers' prices |
Seven outcomes for an approved exception
Give each approved exception one of seven outcome labels, assigned from later transactions rather than from the approver's recollection.
At a glance
Seven outcomes for an approved exception
E3 and E4 are the cases a model most needs and most histories hide, because the later quote looks just like a deliberate one. They surface only when each later priced line is joined back to its exception_id and compared, by date, product and quantity, with the scope card.
Measure leakage with an explicit denominator: of the same account's transactions in the twelve months after an exception's end date, the share priced at or below the exception level. SourceX has not published this measurement; it is a design for whoever holds the records. The seven labels:
- E1 Contained: used only inside its scope, and expired on schedule.
- E2 Renewed by decision: carried into a renewal with a recorded approval for the new term.
- E3 Carried by default: appeared on a renewal or later order with no new approval, for example through a blank renewal method.
- E4 Leaked in scope: applied to products, quantities or dates outside the boundary for the same account.
- E5 Copied: granted to another account with the earlier exception cited as the justification.
- E6 Standardized: adopted as list price or policy through a documented change.
- E7 Corrected: found to be a quoting or billing error and reversed, with documentation.
Contract, competition and accounting rules that already ask for the boundary
Three bodies of rules already ask for parts of the same boundary record, so some companies keep pieces of it for reasons that have nothing to do with AI. What follows is general information; counsel should read any specific contract.
Government schedule contracts. The GSAR price reductions clause asks a schedule contractor to report to the contracting officer every price reduction given to the basis-of-award customer, with an explanation of the conditions under which the reductions were made, and to notify the contracting officer no later than 15 calendar days after a reduction's effective date. Its exemptions are boundary conditions in their own right: no price reduction applies to sales to commercial customers under firm, fixed-price definite-quantity contracts with specified delivery above the contract's maximum order threshold, or to an error in quotation or billing when adequate documentation is furnished. The clause's Alternate I, used for schedules with Transactional Data Reporting, replaces that mechanism with voluntary reductions.
Competition law for goods. The FTC describes the Robinson-Patman Act as reaching sales of commodities, not services. A seller can defend a price difference by showing that it reflects cost differences or was given in good faith to meet a competitor's price, including a rival bid the seller reasonably believes is lower. An exception approved to match a competitor, with no competing offer on file, is weaker evidence.
Revenue accounting. Under IFRS 15, an option to buy additional goods or services 'gives rise to a performance obligation in the contract only if the option provides a material right to the customer that it would not receive without entering into that contract', and the standard's example is a discount beyond the range usually given to that class of customer. An exception promised for future purchases can therefore become an accounting question, and the scope card tells finance whether such a promise exists.
Did the exception win the deal, or did something else?
Keep the deal outcome and the exception outcome in separate columns, because either can be good while the other is bad. A won deal may have closed for reasons the exception never touched, such as a budget deadline or a competitor's outage, and a contained exception on a lost deal was still a well-bounded decision.
Evidence that the exception mattered is comparative: whether the customer's recorded objection was price, how close the competing offer on file was to the approved price, and how similar deals without an exception ended in the same period. Without that evidence, label the exception's effect on the deal as unknown instead of crediting the win to it.
Spread, the harm this page is about, can be measured whatever the deal outcome. An E3 on a renewal is a cost even if the original deal was worth winning, and an E5 copied into a second account repeats that cost without the original reason.
Illustrative: one exception, three later quotes
Illustrative example, invented for this page: a software vendor approves 18 percent off list on two products for one customer for a 12-month term, in exchange for a three-year commitment, with renewal treatment set to revert to list. The approval cites a competing quote, and the scope card records all of it.
Seven months in, a sister company of the customer is quoted 18 percent on the same products, and the approval note cites the earlier deal: label E5, copied. In month nine the original customer adds a third product at 18 percent off on an order nobody approved: label E4, leaked in scope. At renewal the quote again shows 18 percent: the scope card said revert, but nobody set the account's renewal method, so the CPQ default carried the price. Label E3, carried by default.
The original grant remains a well-documented decision. The dataset records three spreads from it, each traceable to one exception ID, and a model trained on those labels can learn to flag the renewal before the quote goes out.
Writing a request for pricing exception records
Request exceptions as linked sets, not as a list of discounted lines, and name the systems involved: CRM, CPQ and billing. State the years covered, whether renewals and later orders are included, and how prices will be transformed.
SourceX holds no stock of pricing histories; it looks for them at companies once a buyer describes what is needed, and its request form asks for scope, volume, format, timing and licensing terms. A company that supplies records signs off on the scope and terms before anything changes hands, and only a review of that company's own records can show whether its exceptions carry renewal and approval links.
Acceptance tests worth writing into the request:
- Every exception carries an exception_id that also appears on its approval record and on every quote or order line priced under it.
- Each exception has start and end dates, product scope and a renewal treatment, or an explicit blank with a reason.
- Later transactions for the same accounts cover at least twelve months after each exception's end date, so E1 to E7 can be assigned.
- Prices arrive as percent off list or bands, and customer and contact identities are replaced with stable pseudonyms or removed.
- Accounts subject to most-favored-customer or price reductions terms are flagged, without the contract text.
Methods note: the field check and what it leaves out
The field check ran on 2026-10-27 against odoo/odoo at commit f7780f3 (product and sale modules) and apache/ofbiz-framework at d6dc409 (data model entity definitions), both cloned shallow into a scratch folder. A script, price_scope_audit.py, read field declarations as text and executed nothing from either repository. The GSAR clause and its prescription were read in GSA's GSA-Acquisition-GSAM repository at commit 8a5cf9a.
Counting rule, as the script applies it: a boundary counts as present when the record, or for OFBiz one of its linked entities (condition and action rows for the price rule; product line and terms for the agreement), declares a field with one of the names listed for that boundary, such as date_end or thruDate for an end date. Free-text name and description fields are reported separately and not counted as a reason. OFBiz's agreement status history was reported but not counted, because it records status changes rather than an approval of a price.
Not checked: commercial CPQ objects beyond the renewal method, custom fields and approval apps, and how companies use these records in practice. Salesforce, Stripe, FTC and IFRS pages were verified through search excerpts on their own domains and should be opened by a reviewer.
Frequently asked questions
How is a pricing exception record different from a discount approval record?
An approval record shows the decision to grant a price: who asked, who approved and on what grounds. An exception record adds the boundary the price was granted within and tracks every later transaction against it. The second is what shows whether a one-off price quietly became the standard.
Does Salesforce CPQ keep a discounted price at renewal?
It depends on the Renewal Pricing Method. Same carries the renewed subscription's price forward, Uplift adds a percentage and List returns to the current price book. A Salesforce help article says a picklist left at --None-- defaults to Same, so a first-year concession renews unless someone chose otherwise.
Why store the reason for a pricing exception when the price is already recorded?
The price alone cannot show whether a later use was legitimate. A coded reason with its evidence, such as a competing quote, lets a reviewer tell a renewal decision from drift. It also supports the explanations that federal schedule contracts and competition law can require.
Can a promised future discount affect revenue accounting?
It can. Under IFRS 15, an option to buy more at a discount beyond what that class of customer usually receives may be a material right and a separate performance obligation. Finance should review any exception promised for future purchases.
Should a pricing exception dataset include exact prices?
Usually not. Percent off list or price bands keep the boundary and the spread measurable while protecting the price book and customer confidentiality. Exact figures add risk without helping a model learn when an exception is out of bounds.
Sources
- When Salesforce CPQ's Renewal Pricing Method picklist is set to --None--, renewal pricing defaults to Same behavior. Source
- Salesforce CPQ's renewal pricing methods are Same, which carries the subscription price forward, Uplift, which adds a percentage, and List, which uses the price book. Source
- Odoo's pricelist rule holds start and end dates, a minimum quantity and an applies-on scope of product variant, product, category or all products, with no maximum quantity, customer, approver or reason field. Source
- Odoo's customer pricelist field is described as used for sales to the current partner and is tracked in the record's history. Source
- Odoo sets a draft sales order's pricelist from the customer's assigned pricelist. Source
- Apache OFBiz's ProductPriceRule holds a name, description and from and thru dates, with conditions and actions in linked rows. Source
- Apache OFBiz agreements name the parties and from and thru dates, agreement terms can set minimum and maximum quantities, and a status history records who changed an agreement's status. Source
- Stripe coupon durations are once by default, repeating for a set number of months, or forever, which applies to every invoice. Source
- The GSAR price reductions clause ties the government's price to a basis-of-award customer, requires an explanation of the conditions behind reductions, sets exemptions and a 15-day notice, and has an Alternate I. Source
- GSAM 538.273 prescribes Alternate I of the price reductions clause for schedules with Transactional Data Reporting. Source
- IFRS 15 B40: a customer option creates a performance obligation only if it provides a material right the customer would not receive without the contract. Source
- The FTC says the Robinson-Patman Act reaches commodities, not services, and that a price difference can be defended as cost-justified or given in good faith to meet a competitor's price. Source
Tell us what data you need
Share scope, volume, format, timing and licensing needs. Datasets are sourced on request.