Multiple ticketing platforms in one event

Under Ticket sources in the manager app, add a separate source for each place you sell tickets. The name should make it obvious in reports and at import time (for example the platform’s brand name).

Examples (names are yours to choose):

• Source Resident Advisor for sales through that channel.
• Source Eventix for another channel.
• Source Direct / Box office for in-house sales, if you track them separately.

Imports always ask which source a file belongs to. Getting this layer right first avoids mixing batches from two systems under one label.

Each ticket type belongs to exactly one source. Create the tiers you sell on platform A under source A, and the tiers for platform B under source B. Display names can match across platforms (for example “General admission”) as long as each type record is tied to the correct source in your account.

When validators scan, the system knows which pool a ticket came from. That also lines up with CSV exports: the “type” column in each file maps to types that share that source when you import.

Create a single event and, on the Types step, include all ticket types that should be valid at the door, across every platform. You are not duplicating the event per platform; you are listing every tier the show offers so imports can attach tickets to the right type regardless of where they were sold.

Complete dates, location, validators, and validation rules as usual. See How to set up an event for the full flow.

From the event, open Tickets and run Import tickets once per export file. Each run uses the CSV from one platform and the source that matches that platform. Column and type mapping works the same as a single-channel import; you repeat the wizard for the next file when the first import succeeds.

Typical order:

1. Upload platform A’s CSV, choose source A, map columns and type values, confirm.
2. Upload platform B’s CSV, choose source B, map again, confirm.
3. Continue until every batch is in.

Details on CSV shape and mapping are in How to prepare tickets for import.

• Traceability: You can see which channel a ticket came from in reporting and support.
• Cleaner imports: Each file maps to one origin, so you are not forcing two exporters into one ambiguous source.
• Future rules: Validation or analytics can be scoped per source when your workflow needs it.

• Wrong tickets after import: confirm the source selected for that run matches the platform you exported from.
• Type mapping errors: ensure ticket types exist under the same source as the CSV’s platform, and names align with the export.
• Missing tier at the event: edit the event and add the ticket type on the Types step, then import again or adjust the file.