| googleposter78@yahoo.com 2005-04-27, 3:23 am |
| I know this has probably been discussed a thousand times over
throughout the last 50 years, However I am finding it difficult to find
answers.
What is the best way to implement a pricing and promotion structure in
a relational database? what rules should one follow?
Does anyone have any good resources/books for this type of architectual
information?
I have a design that has a different price as a lookup for different
pricing groups and shipping methods. that is the PricingGroupID and the
ShippingMethodID determine what price to return from a look up.
promotions are done in a similar way. that means there are a thousand
different prices for each product and wich price you return is based on
all the inputs (PricingGroupID, ShippingMethodID, PromotionID).
I strongly beleive that there should be one base price for the
item/product and the price that gets return to the user should be
calculated based on that base price and an additive or multiplicative
influence that a particular option for that item, promotion or shipping
method may have. this would shrink the amount of data needed to store
pricing and allow a model with the most granularity to add or remove
items, options and change shipping and be able to quickly determine
price or change the amount to charge if an item in an order was not
able to be produced for the customer (shipped,printed,cre
ated)
some additional information: this is a catalog for multiple clients
each clients catalog differs(subsets of one master catalog)
anyone have any thoughts/opinions? I challenge you to give me a good
response or at least a location or resource to find the answers I am
looking for.
|