Limit number of event registrations for each registration type 
We desperately need the ability to limit registrations by the registration type. For example, we will have one event where there is an upper and a lower draw. There is room for 10 players in both draws.
Right now all we can do is say that the max number of players is 20. But that means we could get 15 players in upper and only 5 in lower. So we have to keep an eye on it and go in and manually close the type and hope we do it at the right time. We need this to be automatic.
Thanks in advance!
Released in 5.1
Published in version 5.1 on 31st of July.
See 5.1 release description http://help.wildapricot.com/display/DOC/Release+5.1 affected by 5.1 release.
LauraGAF - I'm merging your 2 posts into existing thread. The feature is in our roadmap and will be part of 5.1 release. See more on our plans and status of currently developed features here - http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8827717-roadmap-2015-plans-releases-expected-dates
Is it possible for the different event types to have limited registration? We have one event where there are ‘x’ number of 4 person tables, ‘y’ number of 6 person tables, etc. and some are upstairs and some are downstairs. Then there will also be single tickets sold as well, where people will not get a table. It is a karaoke event, so that I would like to get people to sign up to sing also. Do you have a suggestion on the best way to set this up?
I am trying to set up some event registrations, but have run into a big stumbling block. One event consists of a Dinner (which has a limited number of spots) and a Wine Tasting component (which has an unlimited number of spots). How do I handle that?
Another event has 'x' number of tables for 4 people and 'y' number of tables for 6 people and 'z' number of tables for 8 people, plus an unlimited number of people can buy a single ticket. How do I handle that?
Thanks for your help.
Richard Clayton commented
As I have been sent here following my request for this functionality, I think I had better post a reply - as apparently this was it drives items up the Wishlist - and as the queue for 5.1 is going to be a mile long when 5.0 does eventually get released, it will need all the help it can get!
In line with a response I posted to Dimitry's September newsletter, I do think that items like this which have already been specified ready for development really should be pushed to the front of the list, or at least listed for a one off vote as to what goes into 5.1 then 5.2 etc. Richard Clayton, UK
We cannot push it, sorry - it's already high in our priorities, has been designed and ready for development. Unfortunately, we're very busy with wrapping up our 5.0 release - see more at http://www.wildapricot.com/blogs/newsblog/2013/08/28/wild-apricot-software-news-august-2013
Another little push on being able to limit registrants by type. In my organization's case, we frequently have events that have a limited number of the 'main participant' slots, but an unlimited number of paid observers.
Someone is having to watch registrations multiple times a day to communicate appropriately with the overflow of 'main participants', without limiting the 'observers'. Creating two events, instead of two types, is a confusion many of our members do not understand - that's even harder to manage and hurts registrations. We'll end up back in the paper world!
My organization is new to Wild Apricot and the online event registration and payment were a principal reason we wanted to adopt an application like this. We saw we could limit registrations, but did not realize this was going to be an issue ...
I am concerned to see this discussion goes back to 2010 without this feature having been added. What would push up the urgency?
A HUGE YES for our organization as well. We have always limited some of our optional "break-out sessions" because they are held in smaller rooms with a capacity limit. We NEED this to make sure we don't over-book sessions and have to end up doing refunds!
Inge Zegel commented
Yes, this would be a helpful feature to have.
We too organize events where we need limits for different registrants types, such as those attending an event in person vs. online. There are many other situations in which limiting by registration types is necessary.
Can the "Registration code required" feature be used as a work-around to limit registrations by event type? The event organizer would clearly need to be involved. They would need to be contacted for the code by the registrant.
I'm currently evaluating Wild Apricot and have been thinking of using this feature to limit the number of non-members that can register for an event. Does this make sense?
We definitely need this feature as well. We have registrations that have multiple registration types and can only accommodate a specific number of registrations for each type, so we need to cap the registrations by registration type and not only by event.
We also need this feature.
However our requirement is that there is an option to create a registration type that is NOT limited by the overall event number.
Currently, we have several registration types that are limited by total event which we also need --- limitation is either bus seats or plane tickets for ski trips.
However we'd like to be able to add other types that do not add to the overall trip limit: we use these for Wait List; Late Cancels - so we can charge late fees within the event; and for those that are meeting the group at the destination so don't require a seat on the transportation.
Just wanted to make sure that when/if this feature is added, that the no limit option is part of it. It would be a HUGE help to us.
Hello, our organization also requires this feature. I am testing how this software can help us and so far that is the only feature that we need that is not supported.
We are a retreat center and run ~50 events per year. Participants can register for the event and choose from different types of accommodations. For example, I can host for event X a total of 15 participants and they can choose between private, semi private or shared room. We could accommodate all 15 in shared rooms but only a maximum of 4 on private rooms.
From the information above, you can see that limiting registrations for each registration type AND for the total number of registrations is exactly what we need for events management.
Is this feature in your product road map?
I desperately need this too!
We often have multiple types of registrations that I need to limit within my total registration pool. Here are some examples.
1) I have a room for 25, but time for only 10 people to get in depth classroom attention. The rest of the people can sign up for "observation only" tickets for a much reduced price. If I go over the 10 "in depth" ticket limit, I'm akwardly trying to rush through the workshop. If I limit the whole thing to 10, then I've lost over $500 in revenue for the day.
2) I'd love to open my networking events free to grad students. However, if I email a code to the university, then I get half the room showing up to drink free beer. If I could limit it to 5 free students, then I'm still including students but preventing a great deal of lost revenue.
Dmitry Buterin commented
Mike, we understand and agree with the priority of this, but it is quite a bit of work. Also, we are trying to figure out how this fits with a bunch of other event-related enhancements, i.e. combine them somehow or not. For now, we will not be able to do much until we complete our work on version 5.0 (best guess - end of the summer), so the timeline for this is end of this year at the earliest.
Mike Willis commented
Hi this is becoming a headache that this functionality is not currently available. We run a number of events that require people to seect what class of boat they wish to sail whether it is a hired boat and if so what type, or whether they will be sailing their own boats.
The reason why this is difficult is that lets say we have a ceiling of 20 people (this is currently set through the global maximum number which is good) out on the water we need to be able to know that we can supply the correct type of boats which we only have a fixed number for. So let us say have 12 boats which are type A and 4 boats each of boats B and C. Boat A is a single hander, Boat B can be sailed as a single hander or 2 handed and boat C is a 2 handed boat.
At the moment the system will allow us to Book 20 boats of Type A - but we only have 12 available. However we can more than handle boats the number of boat places across the fleet. However boats B and C require different skills and abilities to be able to sail them so it is important that participants are able to book onto the session, know that they have been allocated the right equipment and this will make the session more rewarding and less complicated for the participant, the people running the sessions and also the management of the club. It is also important that the participants go out on boats to their ability otherwise it becomes potentially dangerous.
This same scenario comes up with social events when we have adult and child places available it is important to be able to control the numbers of tickets sold for each type.
Conservatively I would say that we are affectted across approximately 25 events a year and I am sure that many others are in the same place.
This subject has been talked about alot since 2010 and there appears to be know answer to it - biut it is obviously a subject that is needed by a huge number of people and is a common feature on other onine booking systems. Please give an indication when this relatively basic funcitonality will be looked at properly and can you give some sort of indication of time when it may be actually impemented.
Thanks for comments - they are valuable and we going to use them in our design.
This would be a useful feature as long as the overall event limit still exists.
Also, it would be useful to have the option not to count a certain registration type in the event's limit.
Wanted to elaborate on this feature request---
In the event a future enhancement allows limiting event registrations by type, we need that to be more flexible than just limiting each type to a specific number. We need the ability to group registration types on a common limit number, and still have other types that are unlimited. That is a minimum requirement --- if any new enhancement requires us to set a limit by each type, that will be a big problem for us.
Here's our application: We sell seats on buses for ski trips. We have different types (such as members/nonmembers) that are priced differently but each take up a seat on the bus. We have no way of knowing how many of each type we would have, but we do know we have an overall limit as to number of bus seats available.
In addition, we would LOVE to be able to add additional registration types to the same event that don't impact the number of bus seats. Our examples are: lift ticket only (those that are meeting us at the resort and don't need a bus seat but want to buy a lift ticket from us), and Late Cancel (those that cancel within 7 days of a trip are charged for the bus --- we want to bill for bus only, but not take up a seat on the bus).
This is a part of scope of so called "events redesign" - see http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8826511-redesign-of-event-registrations