Product A is a Product Option in a bundle and has a Price Book price of $100. When Product A is selected and its quantity is greater than 10, its price falls to $50. The Admin decides to use a Price Rule targeting the Configurator to implement this price change. Which minimum set of Price Conditions and Price Actions should the Admin create for this Price Rule?
A. One Price Condition verifying that the SBQQ__ProductName__c field on the Product Option object is equal to “Product A”. One Price Condition using a Summary Variable summing up the quantity of Product A to verify that this Summary Variable is greater than 10. One Price Action to inject the value 50 into Unit Price field.
B. One Price Condition using a Summary Variable counting Product A to verify that Product A is selected. One Price Action to inject the value 10 into the Quantity field. One Price Action to inject the value 50 into the Unit Price field.
C. One Price Condition using a Summary Variable summing up the quantity of Product A to verify that this Summary Variable is greater than 10 One Price Action to inject the value 10 into the Quantity field. One Price Action to inject the value 50 into the Unit Price field.
D. One Price Condition using a Summary Variable counting Product A to verify that Product A is selected One Price Condition using a Summary Variable summing up the quantity of Product A to verify that this Summary Variable is greater than 10 One Price Action to inject the value 50 into the Unit Price field.
D. One Price Condition using a Summary Variable counting Product A to verify that Product A is selected One Price Condition using a Summary Variable summing up the quantity of Product A to verify that this Summary Variable is greater than 10 One Price Action to inject the value 50 into the Unit Price field.
Explanation:
This scenario is about changing Unit Price in the configurator (not on the quote line directly) when Product A is selected and its quantity is over 10.
Let’s break it down:
🎯 Requirements
Product A must be selected → We must confirm that the user has picked it in the configurator.
Quantity > 10 → Only then does the unit price drop to $50.
Price changes in the configurator → So we’re using a Price Rule targeting the configurator (not quote lines yet).
✔️ Why D is Correct
→ Condition 1 (Product selected):
To ensure Product A is selected, we use a Summary Variable counting Product A.
A count ensures the product exists in the configuration.
If count > 0, Product A is selected.
→ Condition 2 (Quantity):
To check if the quantity exceeds 10, we use a Summary Variable summing Product A’s quantity and compare it to >10.
Both conditions together ensure:
Product A is selected
Quantity > 10
→ Action (Update Unit Price):
One Price Action changes the Unit Price to $50.
No need to update Quantity because the requirement is to lower the price when the quantity exceeds 10—not to set quantity to a different value.