Imagine you are selling 1000 of a specific golf club, engraved 1/1000 through 1000/1000. The #1 club costs more than clubs #2-10, and the rest of the clubs #11-1000 have a lower price. Each club can have one of four different grips, each with an associated price:
#1 Base Price: $500 #2-10 Base Price: $100 #11-1000 Base Price: $50 Stock Grip: +$0 Cloth Grip: +$20 Leather Grip: +$40 Kevlar Grip: +$80 What would be the best way to implement this in Satchmo? Initially, I thought I would have to make 3 ConfigurableProducts (one for each "tier" of serial numbers), and then make an OptionGroup with the 4 grips. This configuration, however, leads to 12 Product entries for any given club offered. Is this the most efficient way to encapsulate the described functionality? Will this scale? If I have thousands of different types of clubs, then I will have 12*<number_of_clubs> total Products in my database - at what point does Satchmo choke? Thanks for any input on this thought exercise! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
