How do multi-venue groups handle different venues and promoters?
Multi-venue groups handle different venues and promoters by sharing technology where useful while keeping operational permissions, event inventory, branding and commercial responsibilities explicit. A group can have central oversight without requiring every venue or third-party organiser to work under identical booking, admission or settlement rules.
The central challenge is governance: who is allowed to create, sell, modify, view and report on each event—and who receives the money when a ticket is sold?
Which controls should be shared and which should remain local?
Shared services can standardise identity, reporting and core transaction processing, while venue-level settings preserve legitimate differences. A group might run one technology platform but have separate box-office teams, payment arrangements and programmes at its theatre, comedy club and festival site.
A theatre needs assigned seating and subscription holds. A club may primarily use general admission and door sales. An attraction may need timeslot limits. The platform should not impose a single inventory model simply because the venues belong to one organisation.
Group governance can define common standards for finance exports, accessibility information, audit trails and incident handling. Local employees still need the authority to manage a schedule, release an operational hold or admit an attendee when their job requires it.
How should access work for promoters and venue teams?
The system should separate permission to perform an action from permission to access a particular record. A promoter might be able to edit its own event, view its inventory and retrieve sales reports without seeing another promoter’s customer data or changing the venue’s global payment configuration.
The access model should answer several independent questions: Can the user view the event? Can they change its prices? Can they issue complimentary tickets? Can they release a seating hold? Can they refund orders? Can they export purchaser records?
Role-based permissions can govern actions, while record-level visibility can limit the venues, events or promoters to which those actions apply. OWASP’s multi-tenant security guidance explains why a shared platform also needs enforceable tenant boundaries, not merely hidden interface elements.
Temporary staff and contractors should not retain indefinite access after an event. Review how accounts are created, approved, monitored and disabled.
How do promoters receive their allocations and sales information?
A promoter’s sales allocation is a controlled right to sell from a defined pool of inventory. That right may differ from the right to change total event capacity, alter prices or issue refunds.
For a co-promoted show, one partner may receive 150 exclusive seats and another permission to sell from shared availability. Those arrangements have different reconciliation and stock-release implications. A report should identify which channel sold the ticket, whose allocation it used and which event and settlement rules apply.
If external channels participate, the primary system needs an authoritative view of availability or clearly defined stock boundaries. Sending an availability spreadsheet once a day is not sufficient for rapidly changing shared stock.
Can different venues keep their own branding and customer journeys?
A shared platform can present different brands while using common services underneath, if its configuration and access model support it. A venue may need its own ticket-shop domain, email identity, languages, payment methods or checkout components.
Brand independence and business independence should not be confused. A custom domain does not establish which entity is merchant of record, who may contact the customer or how records can be used across the group.
A group may prefer a single customer account across venues; another may preserve separate identities. Either approach can work, but authentication, account matching and consent handling need to reflect the intended experience.
How should payments and promoter settlements be handled?
Payment responsibility, settlement and commercial reporting are contractual questions supported by technology, not determined by branding alone. For each event, identify who sells to the customer, who contracts with the payment provider, who owes refunds and which charges belong to the venue or promoter.
Some payment systems support more than one connected business or transfer recipient. Stripe Connect illustrates that multiple-party payout patterns exist, but available arrangements depend on provider, geography and the agreement. A shared checkout does not automatically allow unrestricted funds splitting.
The operational reports should preserve the original gross amount, taxes, fees, refunded amounts and the resulting amounts owed to each party. Staff should be able to trace a settlement figure back to orders rather than rely on an unexplained monthly total.
What should a group test before rolling out shared technology?
Test one event run by the venue and one by an outside promoter. Have each team create or edit a permitted event, sell tickets through different channels, handle a customer service exception and review the final reports. Then attempt an action the promoter should not be allowed to perform.
A sensible implementation can keep a central operations team, a local venue administrator and external promoters on a common platform without treating them as one unrestricted business. The quality of that separation determines whether shared technology is practical at scale.