Skip to main content
Milind Amin (J4RVIS) 님이 #Salesforce CPQ & Billing에 질문했습니다

I have CPQ requirement to consider public holidays, business hours and weekends while selecting/calculating product price. so for example I have product "Personal Support" which required by customer every day between Mon and Sun 10am and 12pm from 01/01/2022 and 30/04/2022 (or no end date means whole year). The CPQ engine should automatically calculate how many public holiday are there between 01/01/2022 and 30/04/2022 including Weekends and apply rates accordingly.

 

Example rates (usages based cost):

 

Product name = Personal Support

Business hour rate = $55 (for 30 min $35)

After hour rate = $70 (for 30 min $50)

Saturday hour rate = $85 (for 30 min $70)

Sunday hour rate = $100 (for 30 min $85)

Public holiday hour rate = $150 (for 30 min $110)

 

How this can be achievable without lot of customisation? QCP is one of the option, I'm thinking of. Also, what is the best way to store above rates in terms of pricebook and product ( e.g. Products rules or Price rules)?

 

Any example or help would be appreciated!

 

Thanks. @CPQ CPQ

답변 3개
  1. 2022년 1월 14일 오전 12:43

    @Chris Gardner thanks for the detail response. Regarding "You could create formula fields to calculate the number of different day types (holiday, weekend, weekday) and summary variables to sum them up across a quote.", are you okay to give me some more insight with example if possible. How the the formula will be look like and scalable? 

     

    I'm will be to using Salesforce OOTB business hours/holiday configuration and Apex to parse hours and holiday.

     

    Also, I had a question on price book and product configuration. A one product can have multiple prices with unique UoM and a Product can be used by another business unit with different price so what is the best way to model it. See attached screenshot 1. 

     

    I'm thinking of having two price book e.g. Home Care and Co-Contribution and having two product Person Support associated individual price book so it will be scalable.  But now my question is that it is not just a single price. It is multiple price per UoM and per Product so what is the best practice to configure Product? Business can do the cross selling e.g. business unit A can sell product manage by business unit B. Should I create one standard price book for all business unit and drive price based on price rules OR unique price book per business unit?  At the moment, I'm planning to create custom object to store all price (see the screenshot 2) with Price rules on Product.

     

    (screenshot 1)

    thanks for the detail response.

     

    (screenshot 2)

    Screen Shot.png

0/9000