Currently, the price list increase adjustment functionality can either be set on individual quotes by the sales rep or by an admin person in the model config section of iQuote. When year end approaches and CAT releases next years price increases we need a better way to load these into iQuote. Currently, if you set up this price list increase adj field in the model config page then it applied this additional percentage to ALL quotes for that model (new, used, rental fleet, current year deals, etc). This is not correct for the annual price increase.
We would like to be able to load this in through model config so reps don't forget to add it to their individual quotes (they often forget which means we lose money!). I think there is an easy solution to this: make the Price List Increase Adj field in model config ONLY apply to NEW machines that ALSO have an Estimated delivery date in the next year.
For example, if I am quoting a NEW machine with an Est Delivery Date of Jan 31st 2020 then the price list increase adj value would apply to my quote. However, if my Est Delivery Date is instead December 30th 2019 then it would NOT apply. The Price list increase adj percentage would also NOT apply to used or rental fleet machines.
Tony Lucini
Hello. We have utilized this function in iQuote for the first increase that is coming in April. When I ran test quotes, it actually only adds the increase percentage to new machines being built off the price lists. Anything feeding off of inventory (new, used, on order, DBS Configuration does not get affected by the price increase adjustment since those numbers feed off of DBS instead. For inventory and on order, we had created a line item with the price increase amount, so it can automatically factor into the quotes and reps do not forget. Except, this is still very confusing because the top header will show an increase amount with a green check regardless but won't increase the cost. It be nice for this function to allow the increase option to work for Price List, Cat Configurator, DBS Configuration and On Order.
I agree with Tony's comments. We currently don't utilize the field due how it functions but we would definitely use it if the logic was set up right. Price protection think would also have to come into play here, some units are price protected at the end of the year (mostly HEX).
We are also working on an enhancement w/ Accenture w/ the ability for DBS to store and look at 2 price tapes based on the RTS... I can see some connection here, if DBS stores 2 tapes, then Uptake would have to be able to handle that too.
Correct, if we can get it to just apply to New machines only that would be a huge win. Right now, it applies the increase to ALL quotes no matter what! also, the increase is not viewable to the sales rep (only for admin users). So two things, ideally it would only apply to ORDERS, and Price List Orders, Base Machines, DCAs, and DBS Configs. If we could apply it to the estimated delivery date this would be good but it is not required. Just having it apply to the quote types above would be HUGE and also showing the percentage to the sales rep and allowing them to edit it is important (especially if not tying it to the estimated delivery date).
I am not sure if other dealers use this price list increase adj functionality for other purposes outside of annual price increases but if they do this would maybe need to be a new field on the Model Config page because again the key is this should not apply to current inventory, used equipment, rental fleet equip, etc as the annual price increases only impacts ordered equipments past Jan 1 RTS dates.
Thank you!
Hey Tony, Kelly & Dylan... question on this one. Do you want this to be for ALL new machines and build logic around the delivery date? What if the machine is in inventory (new status)... I'm assume you don't want this marked up? Should this only be applied to builds from Price List, Cat Configurator, DBS Configuration and On Order?...
Also... thinking through associating this with delivery date may be tricky, since as we know... delivery date is often wrong, and the user will just keep the default or maybe won't know delivery date. Let's think through that part more...
I totally agree and understand what you're going for as far as only applying the increase to a certain type of quote (however we describe new).
I think there's more discovery that needs to be discussed here.
Your thoughts, all?