Strike-thru price question

[Kent Multer]

HI folks,

I have a client that sells clothing products, and some of them have an added price for the larger sizes. We have set this up with inventory variants using the Specific Price method. When we view the product page, the displayed price updates as you select different sizes; that's all working OK. But right now I'm working with a product that is on sale, using a Product Discount price group; and the strike-thru normal price isn't doing what I expected. It remains at the value of the master product's price, even when you select one of the larger sizes.

For example, a shirt has a regular price of $54.99, but one of the larger sizes is $59.99. The discount is a flat $10 off. When you first view the page, is says the price is $44.99, with $54.99 shown in strike-thru; all correct. When you select the larger size, the current price changes from $44.99 to $49.99, as it should. But the strike-thru price stays at $54.99; I would expect it to auto-update to display $59.99.

I'm not sure if (a) this is actually the normal behavior, or (b) I don't have the settings right, or (c) some customization has broken it. Can someone please shed some light on this?

Thanks --

[lesliekirk]

I was going to say:

I think you need to use "Sum of Parts" or "Variant Price is set by the Inventory Product" - the method that creates the Inactive Product.

but I reread what you are trying to do and I'm wondering if that can be done...

[Bruce - PhosphorMedia]

Yes, i don't' believe the "MSRP" price has any scripting connected to it to allow for updating. Probably pretty easy to do, you just need to load the MSRP price into a js variable on page load, and trigger the switch along with the actual price.

[Kent Multer]

Right, not hugely difficult. But I've customized that page quite a bit; I want to make sure I haven't broken something that was supposed to be working.

Thanks --

[Kent Multer]

Can someone from Miva please confirm whether or not the strike-thru price is supposed to auto-update for variants? Thanks!

[lesliekirk]

Can someone from Miva please confirm whether or not the strike-thru price is supposed to auto-update for variants? Thanks!

Yes please - inquiring minds need to know.

[Brennan]

This should just work, but I believe it only updates when you are using "Sum Of Parts" Pricing.

[Kent Multer]

Does that mean it can't be done in this case. when the product has variants for attribute selections?

[Kent Multer]

Can I get some definite answers about this issue please? If there's some documentation that covers this, just give me the link. The Offocial Guide says very little about these settings. Thanks --

[lesliekirk]

Can I get some definite answers about this issue please? If there's some documentation that covers this, just give me the link. The Official Guide says very little about these settings. Thanks --

Yes please, what he said.

[Brennan]

It works "out of the box" when using inventory variants and Sum of Parts pricing (The second option when generating variants). If you wanted to get this functionality when not using variants or when using variants and Specific Price, you would need to build your own JS to give you the functionality.

Is there a reason you're using Specific Price, vs Sum of Parts?

[Kent Multer]

Hi Brennan -- In this case, we don't have any "collection" -type products. We have products with attributes for various size/color combinations. So there are "Parts," but no "Sum," i.e. every variant has just one Part. We do use individual prices for some variants, to make the larger sizes cost more; we don't use attribute or option prices for that.

Will Sum of Parts pricing work in that case?

Thanks --