Product-specific discounts alter the per-unit price of the selected product, so a percentage setting would be redundant, as you can just figure what that percent of the price works out to, and set that as your discount amount -- e.g., 25% off an item priced at $20.00 would be $5.00 off each unit ordered, so you would set the discount amount at 5.00.

Yes, that is correct, and just the way it works; we don't have any way to calculate a strictly %-based discount on specific products independently of price.



BTW, you may be interested in our built-in affiliate system, which tracks referrals and commissions automatically without requiring buyers to remember to enter a discount code:

http://www.e-junkie.com/ej/help.affiliates.htm

Hello,



I would like to bring this thread back up.



I have products with multiple variants that have different price points, and I need to offer a percentage off each price point.



(Product A has 3 variants, each with different prices.)



If I try to set a discount for the parent product, it automatically sets the discount to Flat. That means the other variants with the different price points won't get the same level of discount, as they would with a percentage.



So, if Product A has Variant 1 for $20, Variant 2 for $30 and Variant 3 for $40, and I can only set a flat $10 off, instead of 50% off, I am only covering variant 1 for the intended discount, instead of all variants.



Is there any way to enable the % feature for single products, it is really crucial to my business model.



Thank you.

You may prefer to use our Variants configuration, which lets you define different prices for a product depending on which product option(s) the buyer selects:

http://www.e-junkie.com/ej/help.variants.htm#variants



That said, if you still prefer to do this with discounts, we do have an unofficial hack that lets you define a product-specific percentage discount; when you add/edit the discount, just enter the Discount amount as 0.00 followed by the percentage you want taken off -- e.g., enter 0.0025 for 25% off.

Thank you very much for the Percentage Hack. That works great for my particular issue. I really appreciate the quick answer and fix.

Hi,



I have the same issue as mentioned by BDT above. I tried the hack and it seems to work. It would be good to update the system so that people don't have to waste time in going through the forum to learn about the "hack". There's obviously a legitimate use case that's been missed.



Thanks.

I found a "bug" with the hack that renders it almost useless.



Product A has 2 variants:



V1 - $100

V2 - $60



I want to offer 40% discount on all variants. I created a coupon for Product A with discount as 0.0040 (as explained in the hack). If a customer adds V1 into the cart, it shows the discount as $40 (correct). If the customer adds V2 also into the cart, the discount becomes $80. It should be $64. If I remove V1 from the cart, the discount becomes $24 (correct). Basically it works when only 1 product is in the cart.



Please look into it and let me know if you can reproduce the issue. It's really important for me to have it work correctly.



Thanks in advance.

Thanks for reporting that bug; I've reproduced the problem behavior and will refer this to Development for a fix.



Our new Admin panel currently in Beta testing makes the hack transparent (along with other improvements to our discount settings interface), so you can simply specify the discount applies to the Item Unit Price, select the item, enter a percentage and select "% off". If you wish, you can access the new Admin beta right now, via the link provided in the yellow bar at the top of our site.

Thanks for your response.



I might be missing something but in the Beta panel discount settings, I can't see the Product drop-down list or field. The whole idea was to be able to apply % discount to a specific product.



Am I missing something?

Okay, I managed to figure it out. The Product drop down appears only when I select Discount Applies to -> Item Unit Price. You may want to make it more intuitive (just a feedback).



Also, I noticed that the bug is still there even if I use the Beta panel. So, I'll wait for an update from you when the bug is fixed.



Thanks.

The bug is actually in how the cart backend handles discounts, not in the Admin panel (old or new). Development has devised a bugfix, but that part of our codebase is incredibly complex, so they still need to sort out how to merge it into our production code and test that it actually works and doesn't introduce other bugs before the fix can go live for everyone.



The new Admin > Discount panel incorporates some interface changes, which admittedly may initially disorient users already familiar with the old panel, but it's actually intended to make more self-apparent how the various settings actually work and address common misconceptions we deal with in support constantly -- in particular, the fact that item-specific discounts adjust the original per-unit price of the item rather than taking a single flat amount off the order. Since the item selection is only relevant to discounts on the Item Unit Price, we hide the item selection menu when other discount types are selected.



A general principle of good interface design is not to confuse/distract the user with sub-settings that are useless in the user's current configuration, and to only display them when the master setting they depend on is enabled (you'll notice a lot of this particularly in the new Admin's product settings).

Is there any update on the bug fix? It's really causing problems for me and I'm looking forward to the fix.



About design, I agree that if certain options are not applicable at all, it's better to hide them completely rather than graying them out. But for dependent options that are applicable based on the selection of a primary option, graying out the dependent option when it's not applicable is a more intuitive and user-friendly alternative. Being a developer myself, I consider myself reasonably computer savvy and if I can get confused by your new UI then there's a high probability that many others would get confused too.



Anyway, it's your application and your call. I'm more interested in the bug fix.



Thanks.

Development reports that they have prepared and tested the fix for this bug and will most likely be rolling it into production today. Thanks for your patience and understanding, and we'll take your feedback about the new UI into consideration.

Development has confirmed, and I have tested to verify, that this bug is now fixed.