It wont be using dropdowns Tiram, the idea is that u create one product per color variation and then use models for sizes under each product.
That way it makes sense for the productlist too, because the customer will see the same product in all its colors, then click the one he wants and when entering the product details page, he can choose the size (which can be set to show as either a radiolist or dropdown if I remember correctly).
The downside to that is, that he wont be able to see whether the product comes in the size he wants unless he click on it.
Another approach could be to create each combo of size and color as a separate product, then put them in categories by type and size:
Sweatshirt
When he click a size, he will see all the various designs for that size.
If u then use the cascade option for the treeview, he can also click the type and the prodlist will display all sizes in all colors for the chosen type.
With that solution, there wont be need for models or options on each product which will make it more simple for the customer.
The downside is, that if u at some point need to change anything that all the products have in common, like a basic description, u will have to go thru each and every one of them.
So if ur products tend to change a lot, I wouldn't recommend this, but if they don't, this could very well be a good solution, because each combo would have its own unique ref code and also stock, price etc.
The creation process shdnt be all that bad, because I seem to recall that u can actually clone a product in NBS? so just make one and clone away. :-D
If u go with the model presented by Geoff, u will gain the advantage of common updating, like the description aso in case that changes, but also u will make it more confusing to the customer, because if he clicks a category for a specific size, he would still have to choose the size when going to the product details page and in worst case, the customer might overlook this and by accident order the wrong size because to him, he chose the size when choosing the category.
Regards
Jake
That way it makes sense for the productlist too, because the customer will see the same product in all its colors, then click the one he wants and when entering the product details page, he can choose the size (which can be set to show as either a radiolist or dropdown if I remember correctly).
The downside to that is, that he wont be able to see whether the product comes in the size he wants unless he click on it.
Another approach could be to create each combo of size and color as a separate product, then put them in categories by type and size:
Sweatshirt
- S
- M
-
L
- S
- M
- L
-
XL
When he click a size, he will see all the various designs for that size.
If u then use the cascade option for the treeview, he can also click the type and the prodlist will display all sizes in all colors for the chosen type.
With that solution, there wont be need for models or options on each product which will make it more simple for the customer.
The downside is, that if u at some point need to change anything that all the products have in common, like a basic description, u will have to go thru each and every one of them.
So if ur products tend to change a lot, I wouldn't recommend this, but if they don't, this could very well be a good solution, because each combo would have its own unique ref code and also stock, price etc.
The creation process shdnt be all that bad, because I seem to recall that u can actually clone a product in NBS? so just make one and clone away. :-D
If u go with the model presented by Geoff, u will gain the advantage of common updating, like the description aso in case that changes, but also u will make it more confusing to the customer, because if he clicks a category for a specific size, he would still have to choose the size when going to the product details page and in worst case, the customer might overlook this and by accident order the wrong size because to him, he chose the size when choosing the category.
Regards
Jake