In Salesforce CPQ, Contracted Prices can be generated. This behavior is governed by the 'Generate Contracted Price' field across different levels. This article explains the evaluation order and how to prevent Contracted Prices from being generated unintentionally.
Contracted Prices may be generated when:
The Opportunity has Create Contracted Prices enabled.
The decision to generate Contracted Prices depends on the value of the 'Generate Contracted Price' field, evaluated across multiple levels.
The system checks the 'Generate Contracted Price' field in the following order:
Quote Line
Product
Quote
The system uses the first non-null value it finds in this hierarchy. Once a non-null value is encountered at any level, the evaluation stops, and that value is used to determine whether to generate a Contracted Price.
Example:
If Quote Line.Generate Contracted Price = 'Do Not Generate' → This value is used. The system doesn't check Product or Quote.
If Quote Line.Generate Contracted Price is null and Product.Generate Contracted Price = 'Do not Generate' → The system uses the Product value.
If both Quote Line and Product Generate Contracted Price values are null, then Quote.Generate Contracted Price is used.
To ensure Contracted Prices aren't generated, follow these best practices:
Explicitly set 'Generate Contracted Price' to 'Do Not Generate' at the appropriate level.
The safest and most controlled approach is to set it directly at the Quote Line level, ensuring no fallback occurs.
Avoid leaving the field blank at all levels unless you intend to use the fallback logic.
Note: If you leave the field as null on the Quote Line, the system will proceed to check the Product, and if that is also null, the Quote which may lead to unintended Contracted Price generation.
https://help.salesforce.com/s/articleView?id=sales.cpq_contracted_prices_parent.htm&type=5
https://help.salesforce.com/s/articleView?id=sales.cpq_auto_gen_contracted_price.htm&type=5
005104782

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.