When you create or edit an event, you can set an overall capacity for the entire event, per-ticket limits for each ticket type, per-order minimum and maximum limits, or any combination of these. This guide explains how each setting works and when to use them.
Eventually uses three separate controls for managing attendance:
Total Event Capacity — The maximum number of attendees across all ticket types combined. Leave this blank for unlimited capacity.
Ticket Limit — The maximum number of tickets available for a specific ticket type. Each ticket type can have its own limit, or none at all.
Per-order minimum and maximum — The number of tickets a single buyer can purchase in one order for a specific ticket type. Use these to require a minimum group size or to prevent a single buyer from sweeping a capped tier.
All three settings work independently. You can use one, two, or all of them together.
Total event capacity controls how many people can attend your event overall, regardless of ticket type. This is useful when you have a venue with a fixed occupancy.
Open your event for editing.
Expand the Tickets & capacity section.
Enter a number in the Total Event Capacity field.
Save your event.
When total event capacity is set, all ticket sales stop once the combined total reaches that number. Leave the field blank for unlimited capacity—if you don't enter a number, there's no overall cap. When you focus the Total Event Capacity field, its current value is selected so you can type a replacement directly.
Each ticket type can have its own separate limit, which is useful when different ticket types have different constraints—such as VIP availability or early-bird pricing tiers.
Open your event for editing.
Expand the Tickets & capacity section.
For each ticket type, enter a number in the Ticket Limit field, or leave it blank for unlimited.
Save your event.
When a ticket type reaches its limit, it shows as Sold out on your calendar widget and during checkout. Other ticket types remain available if they haven't reached their own limits.
Per-order limits control how many tickets a single buyer can purchase in one order for a specific ticket type. They are enforced server-side on every public registration path, not only by the widget UI steppers.
Min per order — The smallest number of tickets a buyer can purchase in a single order for this tier. Set this to 2 or higher when your event requires pairs or groups (for example, couples classes). The default is 1.
Max per order — The largest number of tickets a buyer can purchase in a single order for this tier. Leave this blank for no limit. Use this to prevent scalping or to preserve availability for other buyers.
To set per-order limits:
Open your event for editing.
Expand the Tickets & capacity section.
Open the ticket tier you want to edit and find the Min per order and Max per order fields.
Enter the values you want, then save the tier.
When a buyer tries to register with too few or too many tickets for a tier, the system blocks the request before creating a registration or checkout. The buyer sees a message that includes the ticket name and the exact limit:
Under the minimum: the message says the ticket requires a minimum of N per order, where N is the minimum you set.
Over the maximum: the message says the ticket is limited to N per order, where N is the maximum you set.
These checks run before the capacity check, so an attempt with a very high quantity gets the limit error rather than revealing how many tickets are left.
Because a buyer can still edit their cart quantity on the Squarespace product page or in their cart after checkout intent is created, a paid order may occasionally complete with a quantity that violates your per-order limit. The system flags that order for review instead of blocking it at the registration stage. Review the guest list and contact the buyer if you need to adjust the order.
You can combine total event capacity, per-ticket limits, and per-order limits. Here's how they interact:
If total event capacity is 100 and you have three ticket types with limits of 50 each, the event sells out at 100 total attendees—even though each ticket type could theoretically sell 50 tickets, they share the same 100-person cap.
If total event capacity is 100 and one ticket type has a limit of 20, that ticket type sells out once 20 are sold, while the other ticket types continue selling until the combined total reaches 100.
Per-order minimum and maximum limits do not affect total event capacity or per-ticket availability. They only control how many tickets one buyer can purchase in a single order.
When your site is connected, Eventually pushes remaining stock to each Squarespace ticket variant for the whole event. For Standard seat tiers, that stock is the lower of the tier’s own remaining limit and the seats left under Total Event Capacity.
A tier with a blank Ticket Limit is unlimited inside Eventually only until the shared room fills. If total event capacity is set, Squarespace still receives a finite remaining count so the cart cannot sell past the room cap. Virtual and Add-on tiers ignore the shared room and follow only their own limits.
Only active registrations reduce the stock pushed to Squarespace. Incomplete checkout holds still count on Eventually surfaces, but they do not lower Squarespace cart stock. Read more in How Squarespace sync works.
You're hosting a workshop in a room that holds 50 people. You offer General Admission and VIP tickets.
Total Event Capacity: 50
General Admission Ticket Limit: Blank (unlimited)
VIP Ticket Limit: 10
Result: VIP tickets sell out after 10 sales. General Admission keeps selling until the combined total reaches 50. The event then shows as sold out.
You're running an ongoing event series with no venue limit, but you want to limit your early-bird pricing to the first 25 tickets.
Total Event Capacity: Blank (unlimited)
Early-bird Ticket Limit: 25
Standard Ticket Limit: Blank (unlimited)
Result: Early-bird tickets sell out after 25 sales. Standard tickets continue selling with no cap. Because there's no total event capacity, the event never sells out—early-bird just becomes unavailable.
