I sell jump rings and have a very specific price for each size.
I originally was going to have a product for each wire gauge, with all the ring sizes as attributes. I know how to set the pricing for each ring size if I do it this way.
But I would RATHER have just 1 product, with 2 options, wire gauge, and ring size. But I am not sure how to set up pricing this way, as the price changes for which gauge they select.
Just a short example of my pricing:
14g 4.00mm $32.76
14g 4.25mm $32.62
14g 4.50mm $32.49
14g 4.75mm $32.37
16g 4.00mm $33.81
16g 4.25mm $33.61
16g 4.50mm $33.43
16g 4.75mm $33.27
18g 4.00mm $35.36
18g 4.25mm $35.08
18g 4.50mm $34.82
18g 4.75mm $34.59
Am I forced to handle this the first way -- making a product for each gauge, with ring size as the only attribute?
Or is it possible to set different prices depending on the first attribute they select? They would select the gauge, and then the ring size prices would differ depending on the gauge.
The real kicker to this is I have these rings in 3 different metals as well, so this is a difference between having only 3 products (1 for each metal, with many attributes for gauge and size) or 24 products (1 product for each wire gauge = 8, times 3 different metals = 24) and I'd like to keep the db as quick as possible.
Thanks so much!
amy



