Chris. Thanks for the reply. Interesting take on how to handle variations.
Question on your recommendation: wouldn't creating separate products for both men and women's tees make it difficult to display both options on a single page, as the men's tee and the women's would lack links back to each other? I created 3 Option Groups (Gender, Size, Color) and attached variations to a single master product. Still not sure how to access the variations from the template system, though I'm finding hints in satchmo's views. Is the product/variations model hardened in your eyes? If I were to submit an overhaul of the system, would the team be open to looking at it? Don't want to spend time redoing work folks are happy with. Thanks again for the response. On Nov 9, 8:16 pm, "Chris Moffitt" <[EMAIL PROTECTED]> wrote: > On Sun, Nov 9, 2008 at 6:58 PM, Jack Shedd <[EMAIL PROTECTED]> wrote: > > > Nevermind on question A, sorted that bit out. > > > Can anyone explain the thinking behind the ProductVariants system? It > > seems almost unnecessarily complicated and fantastically inconvenient > > in terms of management. > > The basic thinking behind it is that I wanted an easy way to create a type > of product like a T-shirt that has multiple sizes and colors, etc. The basic > shirt really only has 1 description but the customer may choose the size and > color at the time of ordering. They key is that each of these combinations > is a physical product so you would want an underlying inventoriable item > tied to each combo. So for a shirt with 3 sizes and 3 colors you would have > 9 different products. It felt repetitive to have to enter all 9 products, > why not create the Master product, associate the different options (size & > color) then automatically create the Variations you need? The variation > manager, then provides a nice way to manage those variations if you need to. > > Looking at your screen shot, I'd create 1 Men's Product and 1 Women's > Product for the shirt and have options for size and color. You wouldn't > apply color to the women's tee. With this setup, when a person orders a > product, you'll be able to control the inventory down to the exact shirt. > > If for some reason, the product variation concept is too much, the Custom > Product may be more of what you're looking for. A custom product is > essentially indistinguishable from an end user's perspective but from a > store owner's perspective, you loose the ability to track inventory of each > combo. The user can select options but the expectation is that when you get > the order, you know how to assemble the product as described by the > customer. > > Anyway, I hope this helps. If you still have questions or suggestions, > please let me know. I agree it's a tricky concept and I don't think we have > it nailed down yet. I'm just not exactly sure what the solution is. > > -Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
