Thanks for the quick reply Chris! What you describe is what I'm leaning towards; having 3 ConfigurableProducts for the tiers. In this example, there would be 12 (3*4) Products. However, this was just a simplified example, so there could possible be other options chosen (I don't know....I just picked golf clubs since it was the first thing that came to mind :P) like club length, color, etc, etc. Each of this additional options would multiply the number of Products in the database (i.e. there would quickly be a large number of Products for even one club: 3*4*3*5*6*... let alone multiple clubs). This would lead to extremely convoluted Products in the database like: long_flight_3000_leather_red_36inch_etc_etc
I'm just trying to make sure I'm not missing something in that there is so much redundancy of database objects stored, all for basically the same physical golf club. On Oct 24, 1:41 pm, "Chris Moffitt" <[EMAIL PROTECTED]> wrote: > One question - do you need to stock each of these as inventory or are you > going to "build" each of these to order based on the customer's selection? > If you are going to build to order a custom product might be a simpler > alternative. > > You could have custom Product #1, then #2-10 and one for #11-1000 and offer > the 4 grip choices for each. > > I think that should work just fine in your situation and will save you the > issue of having to deal with 1000's of different options. > > -Chris > > On Fri, Oct 24, 2008 at 3:19 PM, subgiambi <[EMAIL PROTECTED]> wrote: > > > 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 -~----------~----~----~----~------~----~------~--~---
