Hi there,
I'm trying to figure out whether Tessitura promo codes can be restricted to one time use online. Right now, it seems like they can't be, but wanted to be sure that there really was no way to prevent folks from going online and putting through multiple purchases with the same discount code.
Assuming that's correct and promo codes can not be limited to one time use, any suggestions for a way around it? We had the thought to try to set up the pricing rule/promo code with a dynamic list that removed the group of ticket buyers who have already used the code and run it every day, but since pricing rules don't register dynamic lists, we'd have to manually update the list in the pricing rule every day, and that doesn't seem ideal.
Any guidance is very much appreciated!
-Nicole
Hi Nicole,
The issue of a way to limit a promo code to being used once by a particular constituent is a thorny one. There are a couple of routes to follow. You could experiment with the procedure LWP_VALIDATE_CART although the pricing rule option is possibly easier - depending on what SQL resources you have in your organisation.
What you could do is schedule the Generate a List report/utility to run on a periodic (hourly?) basis to get over the face that Pricing Rules don't regenerate a dynamic list. Beware though that this report doesn't gobble up valuable database resources during busy periods.
Martin
Could you create a non-ticket buyer Attribute or Constituency that automates frequently and then set the Constituent Criteria to equal that Attribute/Constituency? Not sure on your database size, but you could add the Attribute/Constituency automatically using the proper utility and then automate the removal of the attribute once someone purchases tickets using the promo code.