Here's my recommendation. If you don't need to search on the information,
if you don't need it in a very structured format, just put it into the item
description. If you do want it in a structured format, then you should use
attributes and variations.
Now, it's true that if you create one SKU and associate it with multiple
variations, you will get a selector on the item screen. And that means
you'll have something that can be bought multiple ways for the same price.
So, create multiple SKUs and for each one, select the appropriate variation.
Then you'll be able to set a different price for each.
Let me use an example to illustrate. Suppose I'm selling jeans. Model 501
comes in one color: blue. It comes in one fabric: denim. It comes in five
waist sizes: 28, 30, 32, 34, 36. It comes in three inseams: 28, 30, 32.
Here's how I'd lay it out:
SKU: 501-REG
Attribute/Variations:
Color: Blue
Fabric: Denim
Waist Size: 28, 30, 32, 34
Inseam: 28, 30, 32
Price: $30
SKU: 501-BIG
Attribute/Variations:
Color: Blue
Fabric: Denim
Waist Size: 36
Inseam: 30, 32
Price: $35
This configutation would create two lines on the item screen. The first
would have a selector for both waist and inseam. The second would only have
one for inseam. If you wanted to build a search page that looked at
variations, you could have people get every item made out of denim. (This
code doesn't exist).
The biggest problem is that it's a lot of work to go from a flat table into
this really flexible attribute/variation scheme. It may be worth it to
write some code to parse the original table and create the rows for the
FreeTrade schema.
Leon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Site: http://www.working-dogs.com/freetrade/
Problems?: [EMAIL PROTECTED]
