Touring Production Ticketing: Platforms, Venue Allocations and Settlement
Choose a ticketing setup for a multi-city tour: compare venue-controlled inventory, centralized sales, allocation reporting, refunds and per-show settlement.
A touring production needs more than a reusable event page. It needs an agreed owner for every seat, a reliable sales report for each stop, and a clear process for paying venues, promoters and artists. Start with venue contracts: a platform you prefer cannot necessarily replace a venue's contracted box office.
Choose the operating model before the software
| Model | When to evaluate it | Main risk to resolve |
| --- | --- | --- |
| Centralized ticketing | The producer is permitted to operate sales at every stop | Venue layouts, local payments, staffing and access-control requirements differ |
| Venue-led ticketing | Each venue controls its own inventory and checkout | Inconsistent reporting, attribution and customer-data permissions |
| Shared allocations | A promoter sells an agreed allocation alongside the house box office | Double sales if inventory is not synchronized or allocations are not held exclusively |
A tour landing page can link to multiple authorized sellers without pretending to provide one checkout. Publish the correct city, venue, date, currency and seller for each performance. Never redirect a sold-out performance to a different date without explaining the change.
A sourced starting shortlist—not a tour ranking
vivenu's product overview describes white-label shops, reservations, seat maps, POS, real-time dashboards and ERP integrations. Those capabilities make it relevant to investigate for branded venue operations. The public overview does not establish every tour settlement, cross-venue permission or promoter-split workflow; require a demonstration.
TryBooking's UK product page describes multiple sessions, configurable seating plans, event cloning, role-based access, custom reports and a developer API. Evaluate it for independently operated dates where these tools fit. Cloning an event is not evidence of automated consolidated tour accounting.
TicketSource describes seating plans, online and recorded offline bookings, scanning and sales reports. It is a candidate for local or community productions needing straightforward venue sales. Confirm market availability, reporting permissions and whether every venue can use the proposed setup.
These are vendor-described product capabilities, not hands-on testing or guarantees of contract inclusion. Do not infer payout schedules, offline scanning, currency coverage or automated artist settlement from general product descriptions.
Run a three-stop rehearsal
Use hypothetical venues: a seated theatre, a general-admission club, and a venue whose existing box office cannot be replaced.
1. Create inventory. Configure the theatre's seat map, the club's capacity, and the third venue's reserved promoter allocation. Identify the authoritative inventory record at each stop.
2. Set permissions. Give each house manager access only to the appropriate show. Check whether the producer can obtain a consolidated view without exposing unrelated venue data.
3. Place sample orders. Include a paid seat, concession, accessible/companion booking, complimentary ticket and VIP add-on.
4. Change a date. Show what happens to tickets, messages, refunds and settlement when just one show is postponed.
5. Reconcile entry. Test duplicate scans and a device losing connectivity; document the actual behavior rather than assuming offline support.
6. Export and settle. Reconcile each stop to processor deposits and the negotiated promoter/venue agreement.
Per-show settlement worksheet
Request the following fields before signing. This is a procurement checklist, not a claim that every shortlisted vendor exports them natively.
| Field | Why the producer needs it |
| --- | --- |
| Show identifier, date, venue and currency | Prevent mixing different performances or currencies |
| Ticket type, face value and quantity | Separate seats, concessions, comps and add-ons |
| Booking and processing fees, with fee payer | Distinguish buyer charges from organizer deductions |
| Refunds, disputes, taxes and reserves | Explain the difference between sales and available proceeds |
| Payments received, settlement date and reference | Reconcile the report to actual deposits |
| Venue/promoter allocation and contractual split | Apply the signed agreement; do not assume an automatic split |
Keep separate columns for gross sales, deductions and funds received. A dashboard's sales total is not the same as cash available for the next production deposit.
Questions for the contract
- Who is the merchant of record at each venue, and who responds to disputes?
- Who approves allocation increases and unsold seat releases?
- Are cross-venue reporting and API access included or charged separately?
- Which customer fields may be exported and used for future marketing?
- Who handles an individual canceled show, and are booking fees refundable?
- What support is available during the actual on-sale and door-opening hours?
Frequently asked questions
Can one ticketing platform cover an entire tour?
Possibly, when venue contracts, markets and operational requirements permit it. Otherwise a venue-led or shared-allocation model may be more practical. Verify the conditions before changing sellers.
Is a tour the same as a theatre season subscription?
No. A tour moves a production between stops; a subscription typically bundles performances or booking credits for one organization. Some operations need both. Read the season-pass and subscription guide.
How should I compare touring ticketing costs?
Request a quote for the same hypothetical basket and sales channels at each stop. Include processing, implementation, access-control equipment, reporting, refunds and any reserves. Use the pricing guide and refund and cancellation checklist.