Ability to designate sale prices...
...and display both the sale price and the regular and/or MSRP on category and product pages.
I'm surprised I haven't seen this one yet. I realize there are already ways to do this, but they are somewhat convoluted and sometimes lacking in flexibility.
Suggestion:
Add a "sale price" field below the price and cost fields in the Product tab. If left blank, this field is ignored. If a sale price is specified it supersedes the regular price field and is used by the cart as the price. Both prices are displayed (or better yet, you have the option to display both prices if you like) with a strike through on the higher price (or the option to do so).
I can even see the need for MSRP Price, Our Price and Sale Price fields, but I don't want to get too greedy...
Why this is needed:
Without the Product Template Manager module there seems to be no way to label prices as, for example, "Our Price:" for non-sale items and "Sale Price:" for sale items using the method from the Miva Tips N’ Tricks page (essentially putting the sale price in the standard price field, creating a custom product field for the higher price and entering the higher price there, and then using SMT to display both prices in a template). With only one product template, whatever price is to be used by the cart, whether a sale price or regular price, would have to share a common label which most merchants would probably decide has to be "Our Price:"
And even with the Product Template Manager, which would allow you to create a template just to display a "Sale Price:" label, you’d have to undergo the extra step of assigning sale products to a "sale" product template. All this in addition to having to add the higher price as a custom product field no matter what method you use. That’s a fair amount of work just to display both the MSRP price and a sale price and would obviously be problematic if you had lots of stuff on sale.
Most everyone who uses Miva has sales from time to time. This would make things much easier, especially since sales prices could then theoretically be importable.
...and display both the sale price and the regular and/or MSRP on category and product pages.
I'm surprised I haven't seen this one yet. I realize there are already ways to do this, but they are somewhat convoluted and sometimes lacking in flexibility.
Suggestion:
Add a "sale price" field below the price and cost fields in the Product tab. If left blank, this field is ignored. If a sale price is specified it supersedes the regular price field and is used by the cart as the price. Both prices are displayed (or better yet, you have the option to display both prices if you like) with a strike through on the higher price (or the option to do so).
I can even see the need for MSRP Price, Our Price and Sale Price fields, but I don't want to get too greedy...
Why this is needed:
Without the Product Template Manager module there seems to be no way to label prices as, for example, "Our Price:" for non-sale items and "Sale Price:" for sale items using the method from the Miva Tips N’ Tricks page (essentially putting the sale price in the standard price field, creating a custom product field for the higher price and entering the higher price there, and then using SMT to display both prices in a template). With only one product template, whatever price is to be used by the cart, whether a sale price or regular price, would have to share a common label which most merchants would probably decide has to be "Our Price:"
And even with the Product Template Manager, which would allow you to create a template just to display a "Sale Price:" label, you’d have to undergo the extra step of assigning sale products to a "sale" product template. All this in addition to having to add the higher price as a custom product field no matter what method you use. That’s a fair amount of work just to display both the MSRP price and a sale price and would obviously be problematic if you had lots of stuff on sale.
Most everyone who uses Miva has sales from time to time. This would make things much easier, especially since sales prices could then theoretically be importable.
Comment