For example, we have registrants select their workshop choices within their form but sometimes a topic will sell out. It would be great to be able to set a capacity per field answer option so that the option automatically becomes unavailable for selection when it reaches capacity.

Our annual meeting (=Event) typically includes optional meals and field trips. It would REALLY help if we could set a limit on how many can sign up for a particular field trip. We do NOT want to have the field trips be separate "events" (which do allow limits) because it would be too confusing and wouldn't be linked to registration for the annual meeting.

I need to be able to set different registration limits for items added as custom fields. Lunches, tours, etc. It seems it would be a simple add to set that limit and then just pop up "Limit Reached" to registrants who get there after it is full. Without this, the work around is a mess. The lack of features like this is what makes otherwise dedicated WA users start to look elsewhere.

I don't understand what you are trying to do. You can set ticket types within an event registration to address this issue.

Could there be an option to set a capacity on a field within a form. Ex. a smaller session within the event has a different capacity than the overall event. Would be great to cap that field so no other registrants are accepted for the smaller session add on while the main event stays open.

I'd like to see enhancement to Event Ticket Types, by introducing Resource Type, where each Resource Type can have its distinct inventory constraint.
Context:
When we hold events, we sell tickets for more than one type of scarce resource:
- Tickets (constraint is maximum number of people that can attend, this is supported by default)
- Tables (or seats, as standing only can be an option)
- Early entry ...

There is not a way to control this in the system from my research and support engagement.

Rationale, we want to have new members (through a registration code) get free tickets to certain events, if they become members within x months before an event. To facilitate this, I have set up different Ticket Types, Members Only (with Guest Price), Complimentary New Member ticket (coupon), and Regular Tickets. This works for capacity control when I turn on registration limit for the event

From what I understand, if I add ticket types for Table or Early Entry, these would be double counted as registrations. Setting a limit by regular ticket type isn't practical.

Ideally, we can have multiple ticket types, then add-ons with resource types.

This is especially helpful for events where a certain group of food/drink is needed. A registrant can select a particular item and the need is filled. Then it should show on the drop-down list but cannot be selected. Similar to a "wedding registry". Tech support said this was not possible at this time.

YES. For example, our attendees register for an annual meeting and some bring spouses. Then they can add on optional tours. Currently, this has to be set up as a field on the form, but the tours have max. limits and sell out when we hit those numbers...we have to watch this like a hawk AND once we sell out, there is no way to turn off or hide this option on the form, so attendees can keep booking it. This results in a lot of manual refunds, people being upset ("it said I was confirmed and I paid!") and hits to our bottom line on merchant processing fees.

Take a look at RegFox - they have a much better registration form with this kind of flexibility built in. We have been using their form for these types of events, but then we don't have a record of anything in WA - financial, attendance or otherwise - and we really shouldn't have to be using 2 systems to do this.

Can I upvote this like 1000 times?? Because the struggle is real....

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.

Event registration fields sometimes have a limit on the quantity of items that can be selected for a field. This if fine, for each individual registration for that event. But it also needs to have an aggregate limit assigned to prevent multiple members registering for the event option exceeding a "grand" total for that option; with a wait list similar to the "registration type" capability that only applies to the event as whole. This will prevent having to delete the option and put something in like a "gee, could I get one if it becomes available?" option in its place.

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!!