# Capacity groups: share one capacity across multiple ticket types — MijnEvent [Home](https://mijnevent.app/en) / [Blog for event organizers](https://mijnevent.app/en/blog) / Capacity groups: share one capacity across multiple ticket types capacity-groups capacity ticket-types sold-out # Capacity groups: share one capacity across multiple ticket types Let multiple ticket types draw from one shared maximum — say, 500 places across adult, child and combo tickets. You'll never sell more than your venue holds, whatever the mix turns out to be. [Jasper Koers](https://mijnevent.app/en/author/jasper-koers) · 2 April 2026 · 4 min read ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/capacity-groups-shared-capacity.webp) Photo: [Yivan](https://unsplash.com/@yivan000?utm_source=MijnEvent&utm_medium=referral) / [Unsplash](https://unsplash.com/?utm_source=MijnEvent&utm_medium=referral) In short - A capacity group lets several ticket types share one maximum — for example 500 places across adult, child and combo tickets — so the total can never be oversold. - You can set a per-type sub-limit inside the group (say, at most 150 party-tent tickets within the 500); the stricter of the two limits always applies. - A per-group 'Show availability' toggle decides whether visitors see the remaining count and overrides the event-level setting, while the capacity is always enforced. - When a group is full every linked ticket type shows 'Sold out' at once and visitors can join the waiting list; a failed, expired or refunded order returns its reserved space automatically. # One venue, several ticket types, a single maximum Imagine you're running a parade weekend with room for **500 visitors**. You sell adult tickets, child tickets, an evening pass for the party tent and a discounted combo ticket. Four ticket types — but the grounds have just one limit. How sales will split across those types is anyone's guess. With a separate capacity per ticket type you're forced to guess: 300 adults, 150 children, 50 combos? Guess wrong and one type shows "sold out" while another still has room — or worse, together you sell more than the venue can hold. **Capacity groups** solve this. You create one group with one shared maximum and link multiple ticket types to it. Every sale — whichever type — counts down the same counter. Once the 500 places are gone, sales close for *all* types in the group at once. # Setting up a capacity group 1. In the management panel, open your event and go to the **Ticket types** tab. 2. Scroll to the **Capacity groups** section and click **Add capacity group**. 3. Give the group a recognisable name (for example "Regular tickets") and set the **shared capacity**. 4. Then open the ticket types that should draw from this pool and pick the new group under **Capacity group**. Done. From now on the group list shows live how many places are taken, how many remain and how many ticket types are linked. A ticket type *without* a group keeps working exactly as before: with its own capacity, or unlimited if you leave the field empty. You can freely mix groups and standalone types within one event — think of a separate "Grandstand" group next to the regular tickets. # A sub-limit within the group Sometimes you want to cap one type inside the shared pool. For example: the party-tent ticket may sell at most 150 times, *within* the 500 total places. Simply fill in an own capacity on that ticket type. The stricter of the two limits always applies. Leave the field empty and only the group limit counts — that's the default. # Show or hide "X places left" — per group Each capacity group has a **Show availability** toggle that controls whether visitors see the remaining count. This setting overrides the event-level preference: happily show "12 places left" on your regular tickets to create urgency, while keeping the number hidden for the grandstand. Good to know: the toggle only changes the **display**. The capacity itself is always enforced — even with the number hidden, the group can never be oversold. # What your visitors see On your sales page, visitors mostly notice the convenience: - Types in the same group show the same remaining count, because they draw from the same pool. - While selecting, the remaining space counts down **jointly**: pick 3 adult and 2 child tickets with 5 places left, and neither type lets you add more. - When the group is full, every linked type shows **Sold out** — and visitors can join the waiting list, even for types without an own capacity. # Never oversold, even at peak times At a busy on-sale, dozens of buyers check out simultaneously. MijnEvent guards the group capacity on the server with a locked counter per group: concurrent orders are processed one after another, and an order that would exceed the maximum is refused with a clear message. Also smart: an order mixing several types from one group is checked as a whole — the maximum can't be dodged by spreading tickets across types. If a payment fails or expires, or you issue a refund, the reserved space automatically returns to the group — and the waiting list gets its chance. # Deleting a group? No worries Delete a capacity group and its linked ticket types simply remain. They fall back to their own capacity — or unlimited, if none is set. Your sales keep running either way. # In short Capacity groups give multiple ticket types one shared maximum. You no longer have to predict the split, the counter guards the total, and visitors always see an accurate offer. Create a group, link your types, and the rest takes care of itself — including sold-out handling, the waiting list and oversell protection. Frequently asked questions ## Frequently asked questions ## What is a capacity group? It is one shared maximum linked to multiple ticket types, so every sale counts down the same counter whatever the type. Once the shared places are gone, sales close for all linked types at once. ## Can I still cap a single ticket type inside a capacity group? Yes. Fill in an own capacity on that ticket type and the stricter of the two limits applies — for example at most 150 party-tent tickets within a 500-place group. ## What happens if I delete a capacity group? The linked ticket types remain and fall back to their own capacity, or unlimited if none is set. Your sales keep running either way. [ Back to blog ](https://mijnevent.app/en/blog) MijnEvent ## Read more [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/betaalkosten-bij-ticketverkoop-de-tweede-rekening.webp) pricing MijnEvent · 3 August 2026 · 8 min read ## The second bill: what payment processing really adds to your ticket sales When comparing ticketing platforms, organisers look at the platform fee. But there is a second bill: the cost of the payment itself. What it is, how it adds up, and why it scales with orders rather than tickets. ](https://mijnevent.app/en/blog/payment-costs-ticket-sales-the-second-bill) [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/meertalige-ticketverkoop-bezoekers-kiezen-hun-taal.webp) dashboard Jasper Koers · 30 July 2026 · 4 min read ## Multilingual ticket sales: your visitors now pick their own language Tell your dashboard which languages your visitors speak and the entire sales side follows: ticket pages, e-mails, storefronts and FAQs. Visitors get the right language automatically and can switch with one click. ](https://mijnevent.app/en/blog/multilingual-ticket-sales-visitors-choose-their-language) [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/automatic-membership-renewal-dutch-law.webp) memberships Jasper Koers · 27 July 2026 · 6 min read ## Automatic membership renewal: collecting fees within Dutch renewal law Automatic renewal saves your club a pile of chasing work, but the law has rules about cancelling. Here is how renewal works in MijnEvent, and how to keep it clean. ](https://mijnevent.app/en/blog/automatic-membership-renewal-dutch-law) MijnEvent ## Ready to get started? Create a free account and sell your first tickets today. [Start free](https://mijnevent.app/registreer) [Pricing](https://mijnevent.app/en/pricing)