You are here:
Qualification Rules for Pricing Adjustments (Contextual Adjustments)
To control the conditions in which a user can apply a manual pricing adjustment, you can use qualification context rules, starting in Summer '18. This feature is also known as contextual adjustments. You can also evaluate other data, such as the originating channel field on the order. Starting in the Fall '18 release, you can define maximum adjustment amounts or percentages, and also create pricing adjustment rules for specific products. Or you can disable pricing adjustments altogether.
For example, you can allow your platinum SLA accounts up to a 15% manual pricing adjustment, while your silver SLA accounts only are allowed up to a 10% manual pricing adjustment.
Unit Rate Adjustments
You can use a qualification context rule to allow unit rate adjustments. You use the AdjustmentData virtual object and context scope, and you use Source Expressions such as the following:
The AdjustmentMethod == Percent expression limits the
adjustments to percentages. The AdjustmentMethod == PD_HPH
expression specifies a product code for a unit rate to limit adjustments to
that product only.
Qualification rules for pricing adjustments evaluate data from the order, opportunity, quote, or account, as well as adjustment values and adjustment codes the user enters at run time. This approach ensures that pricing adjustments comply with your organization's business rules.
Pricing Adjustments and the AdjustmentData Virtual Object
Context rules for pricing adjustments must be mapped to the AdjustmentData virtual object. The AdjustmentData virtual object stores data the user enters at runtime in the Adjustment dialog box, such as adjustment values and adjustment codes. This data is not committed to Salesforce or persisted unless the rule passes and the user is allowed to apply the pricing adjustment. Instead, this data exists only in memory during the user's session.
The AdjustmentData virtual object must exist in the shared catalog before you can create rules for pricing adjustments. For more information about the AdjustmentData virtual object, see AdjustmentData Virtual Object.
Pricing Adjustments and the AdjustmentData Virtual Context Scope
Context rules for pricing adjustments must use a virtual context scope when creating mappings to the AdjustmentData virtual object. For more information, see Virtual Context Scopes . For more information on creating context mappings to the AdjustmentData virtual context scope, Using Source Expressions.
Additional Considerations
-
All or Nothing. Before you create context rules for pricing adjustments, users can make pricing adjustments at any time and for any amount. For more information about pricing adjustments, see Manually Adjust a Price in the Cart. However, as soon as you create a single rule and assign it to the AdjustmentData virtual object, pricing adjustment rules are enabled and govern the conditions in which users can make adjustments. For example, you may want to ensure that orders placed over the web are only allowed a pricing adjustment up to 5%. After you create and deploy that rule, the only orders that can be adjusted will be web orders, up to 5%. You will probably want to develop pricing adjustment rules for other channels and conditions as well, or create a catch-all Else rule condition.
-
Supported Mappings in Summer '18. In the Summer '18 release, pricing adjustment rules can evaluate data entered at runtime from the AdjustmentData virtual object as well as fields on Order, Quote, Opportunity, and Account sObjects. However, as with other context rules, you can't evaluate the following unless you use a custom function:
-
Products currently in the cart
-
User profile or role data from the currently logged-in user
-
Data stored in related sObjects such as Account.RecordType
-
-
Enhanced Mappings in Fall '18. Starting in the Fall '18 release, you can now create rules to evaluate product codes, so pricing adjustment rules can be applied to specified products. Also, you can also set maximum adjustment totals to ensure that multiple adjustments do not exceed defined thresholds.
-
Repricing Support. Context rules for pricing adjustments supports repricing. This functionality evaluates manual pricing adjustments as a part of the repricing process. Any manual pricing adjustments that are forbidden by current context rules are removed. This approach requires activation of the RepricingManualAdjEligibilityService implementation for the RepricingManAdjEligibilityInterface.
-
Multiple Pricing Adjustments. Users can apply multiple pricing adjustments as long as the adjustments meet context rule conditions.
Interface Implementations
Context rules for pricing adjustments require the following interface implementations to be active and default.
Interface |
Implementation |
Enables which context rules? |
|---|---|---|
PricingManAdjEligibilityInterface |
PricingManAdjEligibilityService |
For qualification context rules for pricing adjustments |
RepricingManAdjEligibilityInterface |
RepricingManualAdjEligibilityService |
For qualification context rules for pricing adjustments used in a repricing batch job |
Creating a Qualification Rule for Pricing Adjustments
You create qualification rules for pricing adjustments in Vlocity Product Console using the same context rule components as other context rules. For more information, see Create Qualification Rule Sets.
For details about disabling pricing adjustments, see Creating a Qualification Rule to Disable Pricing Adjustments
Assigning a Qualification Rule for Pricing Adjustments to the AdjustmentData Virtual Object
After creating a qualification rule for a pricing adjustment, you must assign it to the AdjustmentData virtual object. For more information, see Qualification Rules for Pricing Adjustments - Assigning or Deleting to the AdjustmentData Virtual Object.
