Complex Pricing and Discounts

[mvasquez]

Is anyone else working in a store with lots of discounts? We have an ERP system that allows us to provide 8 different "slots" of pricing. The are:

• Customer # + Item #
• Customer # + Product Category
• Customer Type + Item #
• Customer Type + Product Category
• Customer Specific (Customer # only)
• Item # Specific
• Customer Type Specific
• Product Category Specific.

All of the pricing has start and end dates, so a customer could have 2 records in the ERP today - one for a product 1/1/23 - 6/1/23 and then a new discount starting 6/2/23 - 12/31/23.

I've been talking to dev support and my own internal team to try and flesh out the best way to build this. There are at least 150 unique product categories, and at least 30 unique customer types. That alone would be over 15k permuations if I went and did them as price groups.

Does anyone else manage complex pricing logic in Miva, and if so - what tips can you provide?

I'd really like to stick with native Miva functions for this so we can use the API as much as possible and avoid issues with needing to make changes to a module. I'm thinking a few of these could be "grouped" almost based on shared customer type or customer #, but am stuck getting it much further than that.

Thanks!

[Kent Multer]

I have a module that can do all kinds of complex pricing. It uses page templates as scripts to handle the math, so it can compute prices using just about any scheme you can create. You can email me to discuss it.