The following is a note to the (future) designers of a proper Product Variant function: There is a gap in understanding here. I have recently had this same conversation with a person who is creating something like
ShapeJS.
When a jeweler offers a ring for $100, they (commonly) mean "pick your size - all for the same price". They can do this because the net volume of material between various ring sizes is small enough that they can average the price across all sizes and not significantly affect their markup.
However, we Model Train Aficionados deal with significant differences in price between the variants. To go from N scale at 1:160 to HO scale at 1:87 requires SIX TIMES the volume of material (for the identical geometry). There's no getting around the fact that different Train Scales will require different price points.
It would make sense to have
both options as choices for the shopowner.
My own frustration comes from the fact that I'd like to have completely separate shops between HO, N, Z - even to the point of possibly having separate accounts here at Shapeways. For my customers, the scale of the model matters first. I effected some of this in my
shop description, but it's rather klutzy, and "average" shop owners might not be able to pull off creating that bit of html code.
<end of note to the future>
Click to expand...