Newbie Needs Help With Attributes

[dcwd]

I'm having issues with Attributes, too.

My client has products that are offered in various sizes and varieties -

Example:

PRODUCT

OPTION A - .75 (small size) $1.80 (XL size)
OPTION B - .65 (small size) $1.00 (XL size)
OPTION C - .75 (small size) $1.50 (XL size)

How can I use the attributes area to accommodate this?

Thank you!

[Ryk]

I take it that by OPTION A you actually mean Product A

Option name: Size
Option Values: Small XL

A price=0.75

Add the Size option (both values) but for the XL put 1.05 in the price field in the Attributes Controller.

B price=0.60; XL attribute price:0.40

You may have to change these amounts depending on whether or not you're displaying prices with taxes.

Experiment - you're not going to do any (permanent) damage, and you'll learn a lot!

[dcwd]

I'm not sure I explained by situation very well, so I'm going to try again:

I'm working with different types of plants.
So, so far I have added the categories for the various plants, and the names
of each plant (product)

Now, each plant has various varieties.

So, example:
AZALEAS - product name
variety (option name)
cora bell (option value)
formosa pink (option value)
pride of mobile (option value)

Now, there are 3 different SIZES that those plants are available in:
option name - SIZE
option value - 1 gallon, 3 gallon, 5 gallon

and the price varies according to variety and container size

Is there a way to set the attributes to allow the cart to work this way?

I attempted this with one product, and, while it worked fine, adding $1 to one variety for 1 GAL, it added too much to the 5 GAL price, because the price for that variety in the 5 GAL is the same as the base price for 5 GAL (no extra should've been added to the larger size.)

Does that make any sense?

[Ryk]

I'm not sure I follow what you're getting at, but if the size prices are different for each variety then it becomes a far more complex process in that you will need different size options for each variety, so instead of 3 size values, you are going to need 9 as you can't have dependent attributes.

If that's the case, you are better off having each variety as a product, applying just the size option to each

[dcwd]

Yeah, that's pretty much what I was thinking, after typing all that in, but I was holding out for a possibility!

Thanks so much for replying so quickly to my posts!

I'm not sure I follow what you're getting at, but if the size prices are different for each variety then it becomes a far more complex process in that you will need different size options for each variety, so instead of 3 size values, you are going to need 9 as you can't have dependent attributes.

If that's the case, you are better off having each variety as a product, applying just the size option to each