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