Capacity on General Admission (GA)

We have a handful of non-traditional Performances that currently have setup as GA.  We are searching for a way to force the capacity to trigger based on the Price Types we're selling, not the overall capacity.  

We have two Price Types that we sell for these events

  • Child Ticket
  • Adult Ticket

The Child Ticket has a capacity of 40 that we internally associate with it.  Once a performance reaches 40 Child Tickets sold, it's at capacity regardless of how many Adult Tickets have been sold.  

At present we're using the method of setting the capacity really high, then blacking out the seats so that we've created a capacity, but again, that only works for the overall capacity so we're presently having to watch each of these Performances and try to catch them before they oversell, but that does no good if you're close to capacity and someone is able to go on the web and purchase 19 Child Tickets to a Performance, thereby overselling you.

Additionally, due to the nature of the shows and unique setup of the theatre, we cannot really sell these Performances as Seated.  

If anyone has any ideas for this, we would appreciate it - thanks!

 

Parents
  • Hi, Jolene –

     

    I have a very similar situation once upon a yesteryear. The way I got around it was not to have separate price types, but rather separate price zones, one called “Child” and one called “Adult”. The capacity of the child zone would be 40, and the ticket price can be “Full price” or “Standard”, whatever you’d like. The price of the Full Price ticket in the two zones can also vary, of course, which is handy. It works well with most web solutions, is relatively easy to set up and respects capacities nicely.

     

    This obviously means that you wouldn’t oversell any child tickets. The things to think about are:

    1) Ticket design. You may need to rethink the design to make the zone name more prominent.
    2) People buying Adult tickets for children when the Child zone is full. I used to run occasional spot checks to see when the child zone was full and then manually retire the performance.

     

    …I think that’s about it. It worked well for me, at least!

     

    C.//

    X.

     

Reply
  • Hi, Jolene –

     

    I have a very similar situation once upon a yesteryear. The way I got around it was not to have separate price types, but rather separate price zones, one called “Child” and one called “Adult”. The capacity of the child zone would be 40, and the ticket price can be “Full price” or “Standard”, whatever you’d like. The price of the Full Price ticket in the two zones can also vary, of course, which is handy. It works well with most web solutions, is relatively easy to set up and respects capacities nicely.

     

    This obviously means that you wouldn’t oversell any child tickets. The things to think about are:

    1) Ticket design. You may need to rethink the design to make the zone name more prominent.
    2) People buying Adult tickets for children when the Child zone is full. I used to run occasional spot checks to see when the child zone was full and then manually retire the performance.

     

    …I think that’s about it. It worked well for me, at least!

     

    C.//

    X.

     

Children