The Order Product Unit Price field in Salesforce CPQ is read-only by design. Attempts to directly edit this field will appear to succeed but changes will not be saved. This behavior is intentional, as CPQ controls pricing through its calculation engine.
To allow price overrides on Order Products, CPQ supports a special currency field called UnitPriceForceOverride. When this field is created on the Order Product object with the exact API name required, CPQ recognises it and uses the entered value to override the Unit Price on that Order Product record.
This special field is available starting in CPQ version 216.10.1. It is not supported by Salesforce Billing. If your org uses Salesforce Billing, be aware that this override may introduce unintended changes to the Billable Unit Price (BUP) field. For more information on BUP behavior, refer to the Recurring Billing for Subscription Products documentation.
The following steps create the UnitPriceForceOverride special field on the Order Product object, enabling authorized users to override the Unit Price value on individual Order Product records.
1. Navigate to **Setup** in Salesforce.
2. Go to **Object Manager** and select **Order Product**.
3. Select **Fields & Relationships**, then click **New**.
4. Set the field properties as follows:
- Data Type: Currency
- Field Label: UnitPriceForceOverride
- API Name: UnitPriceForceOverride__c
- Length and Decimal Places: Set according to your business requirements for decimal precision.
5. Complete the remaining field creation steps and click **Save**.
6. Assign field-level security to grant edit access to the appropriate user profiles or permission sets.
Once the field is saved with the exact API name UnitPriceForceOverride__c, CPQ will recognize it as a special field. Users with edit access to the field can enter a value to override the Unit Price on any Order Product record. If the field is left blank, CPQ uses the standard calculated price.
000381813

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.