Hello there,
I have a product.template PPP.
This product has 2 variants : V1 and V2.
I want a different public price for V1 and V2.
But if I edit V1 and I save a public price, this price is applied to PPP, V1 and V2.... Ahhhhhhhhh!!!!!
Is it the same thing for you?
Real problem here
-------------------------------------------------------------------------------------------------------------------
See image. this is a variant product. I want to change the public price here. But if I change it there, it will replace the price of the main product an all the other variants of this main product. If this field public price exists, I think it should work no?
I have made a dream this night. And in my dream, I saw exactly the sentence of John Doe! Now, I understand that the base price (public price) for all the variants of a product will ALWAYS be the same. Thanks dear misters for all your comments.
Why do we have to use attribute extra prices for variants? I want to be able to just set a sales price for the variant, not calculate the difference with the base price. Its the wrong way round.
Has anyone found a better workaround for this? Setting attribute pricing is not ideal, both from the perspective of managing pricing in relation to vendor pricelists, but also because cost does not always grow in proportion to an attribute. Take the following items as an example:
Apple iPhone 7 32GB Black- Cost $640
Apple iPhone 7 64GB Black- Cost $700
Apple iPhone 7 32GB Gold- Cost $660
Apple iPhone 7 64GB Gold- Cost $760.
The cost difference between the 32GB and 64GB Black versions is $60, but the difference between the 32 and 64GB Gold versions is $100. How can you create uniform margins on pricing for these products? I suppose you could just create them all as separate products, not a single product with 4 variants, but forcing users on the front end to go to 4 different urls if they want to see which versions you have available creates a sub-par user experience. Just wondering if anyone has managed to solve this on their own.