Sale only applies to base price of products

[gtgeorge]

ZC version 1.56B
list of plugins Sales report, encrypted master password, Mailchimp, google captcha
PHP version 7.2.19 (Zend: 3.2.0)
Mysql: MySQL 5.7.26

I tried to initiate a sale today on our site that products are all priced by attribute. For example the items are not sold individually but rather by quantities of 100, 250, 500 etc. The sale only apples to the base price of the items rather than all the different quantity attributes. Is this normal and my setup is at fault or is this a problem that has a fix?

Thanks for any help that can be offered.

[mc12345678]

Can you explain your setup/arrangement a little clearer?

Attributes, quantities, sale (or is it a special), base price, priced by attributes, etc...

If I were to try to test this product/scenario, please explain what to enter from product to problem.

As far as the issue, is it only seen when viewing the product information or is it occurring through checkout as well?

[gtgeorge]

Sorry for such a short description/explanation. I'll try to explain our setup better.

When setting up our products we add them as priced by attribute usually. These products are not sold individually so they have a $0.00 value in the net and gross setting there under products.

We then set up attributes for the product for quantity and size. Quantities are 100, 250, 500 and 1000 and are labeled "count" with radio buttons for each. 500 count is the default radio button selected and all attribute counts are set up to have sales applied by not checking "discount" boxes.

I am pretty sure the lack of discount followed the user through the shopping cart but did not try before I deleted the previous sale and entered a new one. When I entered the new sale all worked as expected as far as math but only shows the discount application in read for the starting page. The discount is applied on the different attributes. Is thee a way to show all the original pricing with the red crossout and new price? I am using a modified responsive template that comes in the installer.

[mc12345678]

So you did want the various counts to be on sale when the product was on sale, then?

As to the crossed out price, are any product showing the crossed out price with the sale/specials price adjacent or none? What do those product seem to have in common?

There are settings to address all product and then there is a setting for attributes to show the was and now price. Being specific and informative helps a lot.

[gtgeorge]

I now have the desired affect of all count attributes on sale. My only problem is the way they are displayed to the customer. Without the sale price being indicated as a sale price like the starting price is, a customer wouldn't know the other prices listed are on sale as well. Here is an image of how the items attributes are viewed on the customer view:



And here is how the product is setup in the attribute controller:



What I desire is all prices that are sale prices to show the original price crossed out and the sale price displayed in red just like the "starting at"

[numinix]

You may need to modify the attributes.php file in includes/modules/. I don't think there's currently an option to add the original price of an attribute beside the sale price.

[gtgeorge]

You may need to modify the attributes.php file in includes/modules/. I don't think there's currently an option to add the original price of an attribute beside the sale price.

Thanks, I was hoping there was a setting somewhere I missed or maybe an error in my installation. I would have though a discount would behave the same for all prices.

[mc12345678]

Thanks, I was hoping there was a setting somewhere I missed or maybe an error in my installation. I would have though a discount would behave the same for all prices.

The only built-in attribute price configuration that shows a "difference" between what it was and what it is where the attribute is free when the product is free and the product is marked as free. At that point the attribute will show a price was x.xx now is: 0.00 type statement. This is true even if the price was 0.00 and now is 0.00... anyways, it is something doable and as numinix suggested something involving the includes/modules/YOUR_TEMPLATE/attributes.php file. Even if it means using an observer to modify the desired line of text to add some css and the original price to the radio button/check box.

[gtgeorge]

The only built-in attribute price configuration that shows a "difference" between what it was and what it is where the attribute is free when the product is free and the product is marked as free. At that point the attribute will show a price was x.xx now is: 0.00 type statement. This is true even if the price was 0.00 and now is 0.00... anyways, it is something doable and as numinix suggested something involving the includes/modules/YOUR_TEMPLATE/attributes.php file. Even if it means using an observer to modify the desired line of text to add some css and the original price to the radio button/check box.

Well that went right over my head! But thanks for giving me a clue which will be researched and maybe I will learn something along the way.

I just thought it would have been a default way of displaying pricing in a shopping cart. It doesn't make sense to me to not be consistent with how pricing is displayed throughout the storefront. At least the ability to customize our copy is there.