CoverCount Events use event capacity, not reservation table capacity. When a guest registers, CoverCount counts tickets sold against the event date. It does not consume reservation availability, block tables, or apply reservation pacing.
This is the right model for ticketed dinners, release parties, classes, pickup events, and other programs where staff need a headcount and attendee list.
Start With Real Capacity
Capacity should reflect what the team can actually host.
Consider:
- Room size
- Fire or permit limits
- Seating limits
- Service staffing
- Bar or tasting counter throughput
- Food quantity
- Parking or arrival flow
- Check-in capacity
Examples:
| Event | Capacity basis |
|---|---|
| Winemaker dinner | Seats available for dinner service |
| Pickup party | Guest flow the team can manage during the window |
| Cocktail class | Instructor capacity and workstations |
| Barrel tasting | Tour guide capacity and cellar space |
| Release tasting weekend | Number of guests the team can serve per event date |
For seated events, capacity may equal the number of seats you plan to use. It still does not assign specific tables inside CoverCount Events.
Set Ticket Quantity
Ticket quantity is the number of tickets available for an event date. For recurring events, each generated date has its own capacity and tickets-sold count.
If the same event repeats on Friday, Saturday, and Sunday, each date can sell against its own capacity.
Capacity is shared across ticket prices. If the event offers a discounted member price alongside the public price, member and public registrations sell from the same capacity — there is no separate member allocation. See Offer member pricing and members-only Events.
Use a conservative first capacity when the team is testing a new event type. It is usually easier to add capacity later than to unwind oversold tickets.
Set Max Tickets Per Registration
The max tickets per registration controls how many tickets one guest can reserve at once.
Common starting points:
- Small dinner: 2, 4, or 6
- Class: 2 or 4
- Release party: 4 or 6
- Club pickup party: 2, 4, or the number your club rules allow
- Free RSVP event: a limit that prevents one guest from taking the whole capacity
This limit applies even to free events. Free events still need protection against one registration taking more tickets than intended.
Free Events Still Need Limits
A free event can be useful when you need RSVP headcount but do not want to collect payment.
Examples:
- Member pickup RSVP
- Complimentary tasting for club members
- Open house with limited arrival capacity
- Education session included with membership
Set capacity and max tickets per registration for free events just as carefully as paid events. The guest does not pay, but the attendee list and capacity are still real.
Paid Events Need Payment Readiness
Paid events use the venue's connected Stripe account. Before publishing a paid event, confirm payment setup is ready in CoverCount and that the guest checkout shows the expected total.
If payment setup is not ready, keep the event hidden or use a free event only if that matches the real business policy.
For payment settings, see Set event pricing, tax, service charges, and gratuity.
Understand Sold-Out Behavior
An event date should stop selling when remaining capacity is lower than the requested ticket quantity.
For example:
- Capacity is 40.
- 37 tickets are sold.
- Max tickets per registration is 4.
- A guest asking for 4 tickets should not be able to register because only 3 remain.
Check sold-out and low-inventory behavior before launching high-demand events.
Capacity Is Not Table Inventory
Do not use Events when the main constraint is table availability, reservation duration, party-size rules, or the host stand workflow. Use an Experience for that.
Use Events when the main constraint is event headcount and staff need an attendee list.
For the decision guide, see Events vs Experiences vs Private Events.