Customer-Based Price Override Rule (APM)
A customer-based price override rule allows you to set up rules that override the price of a product for specific customers. For example, you can set up a rule that overrides the price of a product for a specific customer or group of customers.
When configured:
-
Price updates dynamically when a customer is selected
-
The quote items prices will change based on the customer selected for quote items
-
The ticket items prices will change based on the customer selected for ticket items.
-
-
Applies to both quotes and tickets
-
Quote item and ticket item prices reflect the selected customer
Setup Overview (APM)
1. Confirm Prerequisites
Licenses |
|
Installed Components |
|
User Permissions |
|
Admin Tool Permission Sets |
|
-
Ensure there is an active Advanced Pricing Module license.
-
You have correctly configured Price Books and items in Back Office.
-
Sync Profile configuration for Mobile enforcement:
-
Job and Price Book Dispatch enabled
-
Staged data permissions validated for Mobile users
-
-
FieldFX Managed Package and Mobile app installed and updated.
2. Navigate to the Conditional Pricing Admin tool
-
Open the Conditional Pricing Admin tool in the Admin Dashboard.
-
Click + Add.
-
Complete the following:
Field Description Header
Name
Enter "Price Override by Customer".
Override Type
Select "Price"
Active
Slide the toggle to on.
Applies to SObject
Add "Ticket Item" and "Quote Item".
-
Ticket - applies overrides to ticket items.
-
Quote - applies overrides to quote items.
The pricing logic needs to be consistent between quotes and tickets, so you need to select both.
Override Fields
Enter
FX5__Price__cThis entry maps the Price field on overrides to the Price field on quote items and ticket items.
The Override Field (Price) maps to the underlying API field (
FX5Pricec) configured in the Override Fields setting.Sort Clause
Select Price.
Specifies how matching override records are ordered. When multiple overrides match, the system applies the top result based on the sort order and limit.
Defines how matching override records are prioritized. When multiple records match, the system applies the highest-ranked record based on the selected field and direction.
Sort Direction
Select "Descending".
Limit
enter
1.Apply Null
Leave disabled.
-
-
Add a case to the rule configuration.
-
Click Save.
Add Case
-
Either select Always Case (This type of case is always considered and is AND’d with any other cases) or Or Case (This type of case is OR’d with any other cases) and add conditions.
The conditions you add here determine when the override is applied. For a customer-based price override, you want to trigger the override when the customer on a quote item or ticket item matches the customer specified in the override record.
This determines how conditions are evaluated:
-
Always Case — conditions are always evaluated and combined using AND logic
-
Or Case — one or more cases can apply using OR logic
-
-
Click Add
-
Click + Add Criterion.
-
Complete the following:
Override Field
Select "Price".
Operator
Select "Equals".
Type
Select "Ticket/Quote Item"
sObject Field
Select "Price".
-
Click Add.
3. Define Rule Conditions
For customer-based overrides, ensure conditions match:
-
Customer account
-
Catalog item (optional but recommended to avoid broad overrides)
4. Define Rule Actions
For customer-based overrides, ensure actions are defined to update the price field on quote items and ticket items when the criteria of the override are met
5. Activate the Rule
After setting up the override rule, activate the rule configuration to enforce the override on quotes and tickets.
6. Configure Sync Profiles
Necessary for mobile enforcement of overrides. See Sync Profile Manager for more information.
Modify Override Record
|
You can modify the override record to update the price or change the criteria that triggers the override using these steps. In Lightning Experience, the Overrides tab may not be visible by default. Use the App Launcher or update your navigation to access Override records.
|
-
At the Override Config list view, change the view to All.
-
Open the override configuration you created in the previous steps.
-
At the Filter Clause entry (on the Override Config record you just created), click the pencil icon.
The Filter Clause entry is where you define the criteria that triggers the override. For a customer-based price override, you want to trigger the override when the customer on a quote item or ticket item matches the customer specified in the override record.
-
Enter the following:
FX5__CustomerAccount__c==$FX5__CustomerAccount__c && FX5__Catalog_Item__c==$FX5__Catalog_Item__c
This entry ensures that overrides apply to quote items and ticket items with a matching customer.
-