When sales reps create a contract, they can use quote line prices from their original
quote on future quotes within that contract’s account. This process, known as contracted pricing,
is useful when your sales reps have negotiated a price for a product and want to continue using
that price after making a contract. Salesforce CPQ uses the negotiated price on new quotes,
renewal quotes, and amendment quotes. (Salesforce CPQ Managed Package)
Required Editions
Available in: Salesforce CPQ Spring ’16 and later
Let’s say that a sales rep negotiates a price of $3000 for a laptop with an original price of
$4000. The $3000 price appears as the quote line’s net unit price after the rep has applied the
discounts. When they contract that quote’s order or opportunity, if contracted pricing is
enabled, future quotes for the account show the laptop’s price before discounts as $3000.
Salesforce CPQ applies contracted prices only after you add a product to a quote. Editing a
contracted price and then recalculating your quote doesn’t pull in the edited values.
During quote line price calculation, Salesforce CPQ checks whether your quote line has a
contracted price. If it does, Salesforce CPQ passes that price to your quote line’s special
price. It then updates the quote line’s Special Price Type field to Contracted Price.
Tip You can have only one contracted price record per currency per product. Assigning
another contracted price to a product and then contracting that product causes the contracting
process to fail. Therefore, we recommend that users who want to automatically generate contracted
prices choose Yes for the Generate Contracted Price field on only their
quote records. Setting that field to Yes on product records causes
Salesforce CPQ to calculate a new contracted price every time you contract that product, which
can cause an error.
Note If a contracted price record is associated with any line item in a quote, a DML operation is
performed during price calculation. The quote line gets inserted and then deleted (rolled
back).
Contracted Price Inheritance
Contracted prices inherit the prices of their parent accounts, unless a related account has
different contracted prices from its own parent. To prevent an account from applying parent
contracted prices to a subset of its related products, create a contracted price with an
additional discount set to 0. Contracted prices defined on an account
always override contracted prices that would be passed on from the account’s parents.
To prevent an account from applying parent contracted prices to all of its related products,
select the account’s Ignore Parent Contracted Prices field.
When conflicts exist among the inherited contracted prices, the contracted price for the
immediate parent overrides any other contracted price farther up in the family.
Automatically Create Contracted Prices Configure a quote so that when a sales rep contracts the quote’s opportunity or order, contracted prices for all the quote’s products are created. (Salesforce CPQ Managed Package)
Manually Define Contracted Prices Define a contracted price record and associate it with a product. This process is useful if you’re uploading records from an external system where you’ve already negotiated for a contracted price. This way, you don’t have contract a quote first to establish the contracted price for your account’s future quotes. You can also use filters to assign the contracted price to groups of items, or apply the contracted price only on certain dates. (Salesforce CPQ Managed Package)
Contracted Price Fields Contracted prices allow you to negotiate a price for a product and then use that price on future quotes within the same account. Your page layout and field-level security settings determine which fields are visible and editable on contracted price records. (Salesforce CPQ Managed Package)
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
Always Active
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
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
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.