Does anybody have any custom work online to assess and enforce (in real time) an event ticket limit across a constituent's previous and current orders?
Eg - if an event has a strict limit of 10, we can limit it at order level but there's nothing to prevent a second or third order.
I suspect this is a no but worth asking the question. If anyone is doing anything special with ticket limits I'd love to hear what you're doing.
I'm following along to see what you all learn! We are in a similar situation as Lauren, where we could potentially use a dynamic exclusion list tied to a pricing rule but if a patron does two orders back-to-back, it wouldn't have generated quickly enough. Our most common use of ticket limits is for student and senior discounts (2 ticket limit) and we count on our will-call staff to notice if a patron has more than two tickets under their name, and flag that envelope to see the qualifying number of ID's upon pickup. It's not ideal and people definitely get through the system.
Another thing I noticed is that our student and senior offers (which are tied to a MOS and pricetype flip) will impact ALL tickets in the cart if the promo code is added after the tickets are in the cart, rather than obeying the 2 ticket max (which works if the promo is unlocked before seats are added). This has resulted in parents inadvertently buying student price for everyone in their party, not just for the kids.