Wouldn't this just litter the db with unnecessary coupon codes? Wouldn't restrictions and limitations on coupon codes eliminate the need for personalize or validation. I understand wanting to track marketing efforts by employees or affiliates, which can easily be accomplished with the current setup. Sorry, I am just trying to understand why this would be viable.
The proposed precisely simplifies the creation of massive coupons.
In the present setup if you have to give away say 10 k coupons you have to create 10 k coupons
(impossible if you want to do it from the back end) with the corresponding load to the data base and server.
With the proposed setup, for that example, you just have to create one coupon
and one db record. At the same time it also gives you a way to keep track of the use and/or distribution of your coupons.
In the proposed method you just basically create one coupon for each discount campaign and its number for each user has one part or segment which is the same for all users (actually the discount coupon number); the second segment is another set of digits (which could be the customer-Id of the beneficiary) and the third segment is a strong validator to assure that the first 2 segments are valid and match with each other.