Event ticket limits online

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. 

Parents
  • We've asked this question a couple of times (always hoping that someone has figured it out!) we have a young patrons program that is limited to 2 tickets per production, but enforcing that has been a matter of messaging followed by reporting and clean-up. The only suggestion we've ever really gotten was to build a pricing rule that would only fire for customers within a dynamic list - the problem there being twofold: how often that list would need to be generated in order to be effective, and how to manage new-to-file customers. I believe we were told we'd also have to schedule a report that would regenerate the list regularly because they don't refresh simply by merit of being associated with a pricing rule.

    Sans programming tricks, I think if it's a special event where you can feature strong messaging (including something to the effect of "if you go over this limit, you will be refunded, etc."), and you have the staffing resources to handle clean-up then you can report on anyone who's over that limit and do that necessary clean up (refunds, etc.) 

    I'm excited to see if anyone has any new suggestions!

Reply
  • We've asked this question a couple of times (always hoping that someone has figured it out!) we have a young patrons program that is limited to 2 tickets per production, but enforcing that has been a matter of messaging followed by reporting and clean-up. The only suggestion we've ever really gotten was to build a pricing rule that would only fire for customers within a dynamic list - the problem there being twofold: how often that list would need to be generated in order to be effective, and how to manage new-to-file customers. I believe we were told we'd also have to schedule a report that would regenerate the list regularly because they don't refresh simply by merit of being associated with a pricing rule.

    Sans programming tricks, I think if it's a special event where you can feature strong messaging (including something to the effect of "if you go over this limit, you will be refunded, etc."), and you have the staffing resources to handle clean-up then you can report on anyone who's over that limit and do that necessary clean up (refunds, etc.) 

    I'm excited to see if anyone has any new suggestions!

Children
No Data