Hi,

First, I love the purchased coupon module. I'm super happy to see it working so well. Still, I think there could be an improvement in how these codes are stored.

Current use: Every purchase creates an active, singleton code using an inactive single coupon as the base.
Proposed use: Every purchase increments a bulk code using an inactive bulk code as the base.

The reason is simple: management of possibly 1000's of coupons. If I'm doing it all with single coupons and I can't delete them out of the system, I could literally have 1000 coupons to now track in the system. But if they got wrapped into a bulk coupon interface, now they can be managed in a much neater little package.

Alternatively: if there was a way to expand active and inactive to active, inactive, active purchased, and inactive purchased; this could also help.

This is not a deal breaker and I'm planning on using the module anyway. I'm just worried about a storm of coupons. Also, I tried attaching a bulk coupon and the order made custom versions of each of the 10 bulk coupons. That wasn't what I was expecting, even though it exactly mirrors the behavior of the single coupons.

Thoughts?

Comments

rickmanelius’s picture

rickmanelius commented
Version: 6.x-1.6 » 6.x-1.5

Crap. I didn't realize I was using 6.x-1.5. Updating and testing again. Apologies if this is already fixed.

rickmanelius’s picture

rickmanelius commented
Version: 6.x-1.5 » 6.x-1.6

Nope. Still happens in 6.x-1.6.

Though, I can understand why you'd want to purchase a set of bulk codes... in case you were actually purchasing say 10 uses, you'd want 10 coupons sent. So I think the functionality is working as designed.

So I guess the feature request should more be in line with being able to group purchased coupons together for management purposes. Or have some better way of filtering/searching through them if that is not the case.

Anyway, feel free to close this as well. I just know I'm not looking forward to managing heaps of coupons!

wodenx’s picture

wodenx commented

I can see the utility of using a single bulk coupon for all purchased coupons - though it would change the way purchased coupons are managed (e.g. you couldn't deactivate or change the restrictions for a single purchase). There are some subtleties, though, that make this a bit of work to implement, so I don't think it will happen anytime soon unless someone wants to sponsor.

As to management - you might look into the Views support in the uc_coupon_tracking submodule. This links coupons to purchasers (all the "User" fields refer to the owner of the coupon) - so you could easily generate a view which shows only active coupons that haven't yet been purchased (just filter by "User Name" = "Anonymous". Hope this helps.

rickmanelius’s picture

rickmanelius commented

@wodenx. That might be my best best. And I agree, it would take a bit of reworking to do what I'm suggesting. Hopefully the module you linked to can get me to the 80% mark, in which case this is a moot ticket and efforts should be spent elsewhere.

I personally don't think I could get any sponsorship funding for this either (only in a perfect world!).

wodenx’s picture

wodenx commented

@markshah2 - what specifically are you interested in doing?

ravi007’s picture

ravi007 commented

Purchasing module works fine thanks for contribution.
I have an query : is it possible to restrict user to not have more than one coupon?
i.e. If user already has one coupon in his account then he can not purchase other.