hmm, the path I took was relatively simple, hence its implementation.
This is considerably more complex, and requires re-naming now-existing fields, so it will take a while to think it through.
Well, I thought about it, and it is messing my head up with so many different ways of doing it
Right now, my thoughts are as follows
- set up a new db table where x% discount for group X, y% for Group Y, etc (cached)
- the advantage lies in future product pricing updates
- the admin interface allows selection of multiple groups for each product
- the user interface picks up the Group X name and displays that in the order button
- multiple crossed out prices is not workable with multiple pricing
Thoughts anyone?
Separate from this, but arising from it, is the issue of product management which I have initiated as a separate Bugger and topic.