Right now, it is possible to limit a Coupon in time, plans it applies to and number of times it can be used. Nothing prevents a single profile to use the coupon repetitively, every period for example, until the Coupon is no longer valid.
We would like to restrict the use of a Coupon to "once per subscriber". Based on the code in Transaction.get_event it is possible that per-subscriber coupon use is stored in the Transaction table directly, as much as it is as text in Transaction.descr (see describe_buy_periods). It is not sure though the get_event idea works. Maybe will have to either use a regex on Transaction.descr or use an alternate implementation idea.
Right now, it is possible to limit a
Coupon
in time, plans it applies to and number of times it can be used. Nothing prevents a single profile to use the coupon repetitively, every period for example, until the Coupon is no longer valid.We would like to restrict the use of a Coupon to "once per subscriber". Based on the code in
Transaction.get_event
it is possible that per-subscriber coupon use is stored in theTransaction
table directly, as much as it is as text inTransaction.descr
(seedescribe_buy_periods
). It is not sure though theget_event
idea works. Maybe will have to either use a regex onTransaction.descr
or use an alternate implementation idea.