Skip to main content
I have a very complex pricing scenario I’m trying to configure using price rules in CPQ and I have come across something that has scuppered my efforts and am seeking some guidance as to whether there is something I can do to get the desired outcome.

 

 

 

The scenario is as follows:

 

 

 

Our core product is a software licence and there can be 29 different combinations of licence that can be purchased, each one of these combinations can have an implementation product added that has a number of variables that can impact the effort (quantity). Using price rules and quote level fields I was able to perform a number of calculations based on these variables that inserts the correct quantity values into the implementation product. These products are all set in nested bundles to ensure the base quantities can be set and so that users are able to correctly choose the options available when selecting the licence. The issue I have found is that in many scenarios its possible (likely) that the same combination of licences could be selected (so that same product bundle selected many times) as we sell across multiple countries. When this happens the fields at the quote level that perform calculations using price rules become incorrect and therefore the quantities inserted are also incorrect as the calculation will double or more based on variables and then insert those inflated values into quantity fields.

 

 

 

My question is if the scenarios occurs in the quote configurator where the same parent product is selected more than once is there a way I can isolate those calculations so the output only impacts products that sit in the same bundle rather than others across the quote? I appreciate this might require a whole different approach but I’m not sure what to try next? I’ve had a look at the possibility of lookup object however some of the variables used in the calculation are configured in the quote (quantities from other products) and I’m not sure how to use these in the calculation of the base figures of the lookup object when used in a price rule.

 

 

 

Any suggestions welcome!

 

 

 

Thanks
5 answers
  1. Jul 22, 2025, 6:48 PM

    I'm going to try and awaken this thread, as I'm also in search of a good way to isolate the scope of my summary variable to a particular instance of a bundle. For example, my quote has bundle ABC with  one configuration, and it has the same bundle ABC entered again with a different configuration. I need to roll up the first instance separate from the second instance so that the totals aren't inflated. Any ideas out there? So far it seems that we need a distinct bundle SKU and summary variable to go with it.

0/9000