absolutly a required update. We spend a way too much time monitoring the number of people registering vs what we have available. Trying to use the registration types is just not fuctionable.

Evite has a feature “what to Bring” where you create a menu with a counter, and attendees choose an item and the counter is reduced by 1. Can wild apricot create this feature in the registration form section?

Not sure if this is precisely the same, seems like a solution might be related... we sell individual seats as well as blocks of seats (tables of 8, e.g.). So if I have a venue that holds 200 people, I can sell 200 individual seats or 25 tables of 8, or some combination. But in WA, they both count as just one registration so if I set a reg. limit of 200, I could theoretically end up with 1600 people registered (200 tables of 8).

Similarly, It would be very helpful to have an option for a reg. type to not count toward the limit, especially in light of COVID and the advent of virtual and hybrid events. I can see selling limited seats to experience an event in-person but unlimited to view it virtually.

Implementing a feature by which users can input a value to count toward a limit (8 for a table of eight, 0 for the virtual example), would be very helpful.

Events should have optional add-on fields with separate quotas. For example, parking pass. My event may have a limit of 500 people, but I only have 10 parking passes. Right now, this has to be done with separate registrations. I would prefer to have an event with 2 registration types: total people, parking passes. There should be a limit of 500 total people and a limit of 10 parking passes. Once all 10 parking passes are sold, that option is no longer available, but people can still register.

Please move this up on your development list. This is a basic registration need! I have to check registration everyday to remove sessions that are full and then refund anyone that got in before the last time I checked.

Any update on this? This is killing me. We need to limit things such as banquets purchased at an event.

This is absolutely essential. A deal-breaker. We have banquets, trips, and other functions within an event that are limited by space. It's ridiculous that I have to monitor the capacity of these functions manually and then remove custom field/option entirely. PLEASE FIX IMMEDIATELY.

THIS IS A NO-BRAINER FUNCTION THAT THE DEVELOPERS NEED TO WORK ON. ADDS IMMENSE FELX TO THE EVENTS

We are in need of this feature and use it with all of our larger events. We just started using Wild Apricot for event registrations, but may need to consider another source if this is not an option.

This is HUGE for us and causing us to seek out other event management options with some of the organizations we run. PLEASE FIX!!

Please implement this short-coming ASAP. I just discovered this snag and needs to be implemented.

10 years with no changes to this setup 'glitch'? This does present problems for organizations. Please consider adding this feature.

I have needed this for at least five years now. And I have a few clients who won't move to WA due to the fact that their breakout sessions (separate from the main event) can't have limits automatically setup.

It is very important to have limits on individual options within an event. Our organization has options for different classes each having a limit and we currently have to monitor during signups and post a notice on the event details screen that some are full (and hope people read the notice and no one signs up for the filled ones).

I would like the ability to place limits on custom fields, with or without a charge, in the registration form for events.

This feature is what may hold us back from moving over to Wild Apricot. I'm kind of shocked that it hasn't been implemented after almost 10 years of continuous interest!

This would be a valuable feature for us too. We're selling a limited number of raffle tickets for an event, and I can't keep checking registration to see how many have been sold.

We too need to be able to have an event with sub-events and limit the sign-up number per sub-event. We have an outing with different hikes available, but each hike needs a registration cap. Once the registration cap for the particular hike is met, the system should not allow people to sign up for that hike.

Plus, if you sign up for an all day hike, you should not be able to accidentally sign up for one of the 1/2 day hikes for the same day.

I have a client wanting to move to Wild Apricot, and not having this function is the only reason they haven't. Please implement this!

This would be great! Hope it comes to fruition.

Sorry Matthew, no updates.

Katya, Events development team