Attributes require two things - An Option Name AND at least one Option Value (although you wouldn't need an attribute for just one option).
Let's say we have a 3 x 5 rug that we want to sell in colors of red, green, or blue.
The Option Name would be Color and the Option Values would be Select a Color, Red, Green, and Blue.
They would be assigned in the Attributes Controller thusly:
- Select a Color - sort order 0 - Attribute Flags Y N Y Y Y N
- Red - sort order 10 - Attribute Flags N N N Y Y N
- Green- sort order 20 - Attribute Flags N N N Y Y N
- Blue- sort order 30 - Attribute Flags N N N Y Y N
Here's the reasons for what I've shown are:
- You must have a "Descriptive Selection" that is not an actual selection that is set to display only and the default that the customer sees.
- The display only will force the customer to actually make a decision rather than accidentally selecting Red while actually wanting Blue.
- The Option Values are then added with sort orders. I use 10, 20, 30, etc. just in case another color comes along that needs to go between Red and Green.
Note that these instructions have nothing to do with an item that may have different weights, prices, discounts, etc. If this is the case, Price, Weight, and other Prices and Weights might come into play. In particular, a shirt might cost more for large and even more for extra-large. And, by the very nature of their different sizes, each would have more weight. Remember that the entry would be the amount ADDED to the basic cost/weight for that size.
That's a really quick explanation of a complicated portion of Zen Cart. There's lots more info in the forum if you search for Product Attributes.