variation price set

Let me explain how I would do it, and we can see if you are doing it the same.

• Let’s say bed size 140?cm costs $200, 160?cm cost $250, and 180?cm costs $300.
• I would create the global attribute of Size. 140?cm would have no markup, 160?cm would have a $50 markup, and 180?cm would have a $100 markup.
• Let’s also say modification A is standard, but B is $10 more, C is $20 more, and so on.
• Create another global attribute for A, B, C, D, and E. Since A is standard, there is no markup. B has a $10 markup, C has a $20 markup, and so on.

Then I would create the product and use the Create variations from all attributes function to make all 15 variations.

Now, since there is no markup for 140 cm, and no markup for A, 140-A is the lowest priced bed at $200. This is the base price. When I use the Set regular price function, $200 is the price I would use.

Is that how you did it?

• This reply was modified 4 years, 11 months ago by Mark Tomlinson.

Thanks for the quick response!
Yes, I’m doing just that, but there is one thing but

140 has its price
160 has its price
180 has its price

and 160 is not worth 140 + X

I guess I’m confused. Are 140, 160, and 180 three separate products? Or did you set the prices in the attribute?

Here is what I did to test what I think you are saying.

• I created three Size attributes and set them to +100, +200, and +300.
• I created 5 Color attributes and set them to +1, +2, +3, +4, and +5.
• I went to the product, added the attributes, and used Create variations from all attributes, which gave me 15 variations.
• Finally, I used Set regular prices, and set the price to 0.

What I ended up with is that 140-A was $101, 160-A was $201, 180-A was $301, and so on. The lowest price was 140-A, and the highest was 180-E at $305.

The above should also work if you use something other than 0 with the Set regular prices function. For instance, you made decide that you will charge 123, plus add a little for each size. But, if you were to do that, I’d recommend doing what I outlined in the first response and setting the base price at the least expensive option and adding a markup from there.

The trick here is to recognize that the prices for each variation are all a “mark-up” from whatever price you use with the Set regular prices function.

Does that help any? Or am I still misunderstanding?

• This reply was modified 4 years, 11 months ago by Mark Tomlinson.

Your option is suitable but not for me.

I have different beds (about 10pcs)
each has 3 sizes (140, 160, 180)
The cost of these sizes in each bed is different.

each bed also has options (in your version it is color)
extra charge for each color is the same in all beds

A-100, B-200, S-300

and now all this needs to be connected using your plugin
Thanks!

Your option is suitable but not for me.

I have different beds (about 10pcs)
each has 3 sizes (140, 160, 180)
The cost of these sizes in each bed is different.

It seems this is where I am misunderstanding you. The plugin is written is to assume that size is an attribute, and that one of those sizes will be the least expensive. The other two sizes are some amount more than the least expensive one. So, if 140 is the least expensive and 180 is the most expensive, then 180 simply cost ‘x’ amount more than 140, and that is the markup.

However, you may be telling me that each bed type costs a different amount. So, just assuming that 180 beds cost some flat amount more than 140 beds is not suitable. If this is the case, then can I suggest a percentage markup? If 180 beds always cost about 50% than 140 beds, regardless of the bed type, then the markup would be 50%. That way, if b1-140-a is $100, then b1-180-a would be $150. If b2-140-a is $150, then b2-180-a would be $225.

That may not work for you either, depending on how you calculate your prices. But I thought I’d toss it out there and see if it is any help.

it doesn’t quite work for me
But in any case – thanks for the desire to help !!!

I have another product and maybe use a plugin for them.