Limiting # of Add-on Discount via Pricing Rules by Production

Hello!

We have recently discovered the awesomeness of pricing rules and have utilized them for a few promotions (like our Cyber Monday sale).  They are so great!

But now, I am looking to implement pricing rules for our Subscriber discount, but may have hit a snag.

Our internal policy is that our subscribers are entitled to a 20% discount on up to ten (10) additional tickets per production (we have five mainstage productions a year).  I have figured out how to apply the discount with the ten ticket limitation per performance per order, but there is nothing stopping our subscribers from starting a new order to get the discount for more than 10 tickets (if that makes sense?) for the same performance.  For our in-house Audience Services team, this is ok as they know our policy, but we are hoping to implement this online through TNEW.  

Is there any way to limit the number of add-on tickets across a production rather than individual performance and/or order?

Thanks!
Kristine 



[edited by: Kristine Astop at 4:07 PM (GMT -6) on 16 Jan 2017]
Parents
  • We have a similar problem! We have a pricing rule that applies a steep discount to each performance, but only applies it to 1 ticket per order. However, there is nothing that restricts a constituent from starting a new order and receiving the steep discount again (either in TNEW or in the Application) Does anyone have a good solution for this? It is completely unsustainable to create an Exclusion List for every single performance we set up, and we've just started noticing a few patrons figure this loophole out and use it.
Reply
  • We have a similar problem! We have a pricing rule that applies a steep discount to each performance, but only applies it to 1 ticket per order. However, there is nothing that restricts a constituent from starting a new order and receiving the steep discount again (either in TNEW or in the Application) Does anyone have a good solution for this? It is completely unsustainable to create an Exclusion List for every single performance we set up, and we've just started noticing a few patrons figure this loophole out and use it.
Children
No Data