What ticketing capabilities do multi-day festivals need?
Multi-day festivals need ticketing that can manage overlapping admission rights across dates, areas, campsites and additional experiences. A festival may sell full-event passes, day tickets, camping, vehicle permits, VIP access, upgrades and guest credentials, each with different validity and capacity rules.
The complexity comes from the relationship between these products. A three-day admission ticket is not necessarily three unrelated single-day tickets, and a camping pass does not automatically grant entry to the festival site.
How should day tickets and full-event passes be represented?
A ticket should express exactly which event days or sessions its holder may attend. A weekend pass can cover Friday, Saturday and Sunday, while a day ticket covers only one of them. Some sites permit re-entry; others limit it. The platform must preserve those rights when a ticket is transferred, upgraded or cancelled.
For a festival with a daily attendance limit, a weekend pass normally consumes the relevant capacity on every day it covers. Selling 5,000 weekend passes and 5,000 Saturday-only tickets is not a 10,000-ticket total if the question is Saturday attendance; it is potentially 10,000 Saturday admission rights before considering other ticket classes.
That is different from the number of people scanned into the site at any one moment. Reporting needs to distinguish tickets sold, entitlements valid for each day, and actual arrivals.
How do camping, parking and other add-ons work?
Festival add-ons often draw from independent stock pools. A camping field has a campsite or pitch limit, parking has a vehicle limit, and a VIP lounge may have a restricted entitlement count. They should not all inherit the general admission capacity.
Consider a buyer purchasing two weekend passes and one vehicle permit. The basket must validate both pass inventory and the permit stock. If the permit is unavailable, the system should clearly explain whether the buyer can proceed without it rather than silently selling an invalid combination.
Some products have prerequisites: camping may require a full-event admission ticket, while a VIP upgrade might be purchasable only by someone holding an eligible base ticket. Those relationships need rules and validation, not only descriptive text on a sales page.
What makes festival entry and credentials different?
Festival admission may require multiple related access rights across time and zones. The main gate, campsite, backstage area, staff entrance and hospitality space can have different entry policies.
A credential can be a printed ticket, mobile barcode or RFID wristband. RFID does not itself define admission rights; the system behind it decides which zones and dates a credential may access. Intellitix describes a model connecting festival credentials, access control, cashless commerce and reporting, illustrating why these functions may need to exchange information.
Teams should test how credentials are issued, replaced, transferred and revoked. Losing a wristband should not automatically give someone two independently valid admissions. Where scanners operate offline, organisers need a clear policy for handling changes that have not reached every device.
How do festival onsales and distribution work?
Festivals commonly sell in phases with different prices, eligibility rules and allocations. Examples include early-access memberships, deposit plans, general releases, local partners and invited guest lists. A sales channel may have an exclusive allocation or sell from shared stock.
The system must prevent overselling across phases and external sellers. A promotional code that gives access to a presale is not the same as reserving a particular ticket for that customer. If a basket expires, its reserved stock should return to the appropriate available pool under the configured rules.
A waiting room can limit the rate at which people enter the checkout, but it cannot replace inventory consistency. For a major announcement, test the complete path from queue admission through ticket reservation, payment and order confirmation.
What should organisers be able to change after purchase?
Post-purchase support needs to respect individual product rights. A customer may change the name on a pass, add camping, transfer one ticket or request an eligible refund. Cancelling a pass may require associated campsite or parking products to be reviewed; the correct result depends on the organiser’s terms.
If a day is cancelled but the festival continues, the effect on three-day passes may differ from the effect on Saturday-only tickets. Organisers need an auditable way to identify affected customers and update validity without guessing from the original email confirmation.
Which reports matter during and after the event?
Festival teams need both commercial and operational reporting. Useful views include tickets valid by event day, access scans by gate and zone, camping occupancy or permits issued, premium-product sales, promoter allocations and settlements, and refunds or chargebacks.
Cashless point-of-sale data may be integrated with ticketing, but it is a different transaction stream and may be controlled by a different supplier. Do not present merchandise or bar turnover as ticket revenue unless the accounting definition intentionally includes it.
Before buying a platform, run a multi-day scenario: one weekend pass, one Saturday pass, a camping add-on, a transferred credential and a revoked lost wristband. The provider should show which rights survive at each step and how operations can audit the result.