Great module. Thanks for the same. I have been switching back and forth between Discount coupons and this one and leaning towards this one because of handling of multiple discounts and code less discounts.

For the discount combining logic, does it make sense to have instead of, boolean can or cannot be combined an additional choice of can only be combined if other discount can be combined. So basically 3 choices: 1: yes, 2: No and 3: Iff other discounts can be combined. The problem this will solve is: consider you have 2 mutually exclusive discounts one for sale above 150 and another for sale above 250. The module works fine. But if you add a 3rd discount on a certain sky only whic can individually be combined either with 150 discount or with 250 discount, there is currently no way to specify that.

The other choice to solve the above would be to provide a drop down with all of the discounts and selecting the discounts with which it can be combined.

My 2nd feature request is to provide a way to send email of a one time discount on user registration.

Thanks,

Comments

ryangroe’s picture

ryangroe commented

If I am reading that correctly I think you want to be able to say "discount A can be combined with discount B but not with discount C". I see the reason for this. This goes back to earlier requests for an "upper bounds" on qualification. So you could set your first discount to trigger at 150 items but have an upper bound of 249 items. Then the second discount of 250+ kicks in. I think that would give you the functionality you desire. For the life of me I can't remember off the top of my head if this was committed to CVS. I know it was implemented in a patch by a user.

In a perfect world this module would allow you to select a specific list of other discounts any particular discount could be combined with, but I worry about the performance and ease of use that type of system exhibit. Perhaps the best implementation is somewhere in the middle.

As for the second request, as long as the discount is codeless or uses the same code for each user, you could alter your registration email to tell the new user about the discount. You could probably also use conditional actions to send an email about the discount. Just remember to set the "max uses per user" to 1.

If you want a unique code per user that would be a little more tricky, however I still think conditional actions is probably the way to go, but with the need for a trigger inside uc_discounts_alt for creating the unique codes. I would suggest using the same for all users as I believe that will work with the current implementation of this module.

novice’s picture

novice commented

>> In a perfect world this module would allow you to select a specific list of other discounts any particular discount could be combined with, but I worry about the performance and ease of use that type of system exhibit. Perhaps the best implementation is somewhere in the middle.

I agree with both the ideal scenario and somewhere in between scenario. And hence, I had suggested a third option of Can only be combined if other discount is combinable. This would solve most of the cases (or at least the ones I am interested in :).

I was looking for a unique code per user on registration. I actually took the module Discount Coupon at registration and changed it to work with this Discounts module. Basically upon user registration the module inserts a new code for existing discount and sends it to user. If you like I can attach it here and you can combine this with discount module if you like.

Thanks