Single event vs multi-city tour — which do I create?

Quick answer

You are selling…	Create…	How many events in dashboard
One show — one city, one date (or one weekend)	A single event	1 event
Same headline artist in many cities — shared tour branding, separate dates	A multi-city tour	1 event per city/date, linked by tour slug
Same show repeated weekly (e.g. Sunday service)	A recurring series	1 parent + auto-generated occurrences
Conference with workshops	Multi-session event	1 event with multiple sessions inside

---

Single event (most common)

When to use

• Church night, conference day, single concert, fundraiser dinner, one-off webinar
• One venue, one start time, one checkout page

Steps

1. Events → Create event
2. Fill title, date/time, venue, cover image, ticket types
3. Optional: seating map, add-ons, promo codes
4. Connect Stripe payout account (paid events)
5. Publish → public URL: https://www.ticketingbook.com/e/{your-slug}

Discovery

Appears on Find events as a single show (not inside a tour carousel).

One event, multiple ticket types

GA, VIP, early bird, child — all on the same event. You do not need separate events per ticket type.

---

Multi-city tour (same headline artist, many cities)

When to use

• A headline artist or act playing multiple cities — gospel tour, comedy run, arena run, festival circuit
• Same artist name and tour brand everywhere; each city is its own show with its own venue, capacity, and checkout
• Fans pick their city from a tour page

Important

A tour is not one event with multiple dates. It is multiple separate events sharing tour metadata.

Steps

1. Create the first city date as a normal event (e.g. "Chandler Moore — Omemma Tour — London")
2. Open Multi-city tour panel (same event settings area as Listing type)
3. Set:
   • Tour URL slug — e.g. kingdom-world-tour (lowercase, hyphens)
   • Tour name — e.g. Omemma Tour (fan-facing — usually the headline artist + tour title)
4. Click Save tour on this date
5. Duplicate or create additional events for each city:
   • Manchester, Birmingham, Glasgow, etc.
   • Each has its own venue, date, ticket types, capacity
6. On every stop, set the same tour slug and tour name (or use bulk apply on the tour panel)
7. Publish every stop — missing one city means fans cannot buy that date

Fan experience

• Find events → Tours or the Featured carousel → tour card → All dates
• Public tour page: /events/tours/kingdom-world-tour lists every stop
• Fan clicks a city → checkout on that stop's /e/{slug} page

Bulk tools

From the tour panel on any stop:

• See all dates on the tour
• Select stops → bulk apply cover image, hosted-by name, discovery flags

Seating on tours

Each city event has its own seating map (venues differ). Build seating per stop in Event → Seating.

---

Comparison table

	Single event	Multi-city tour
Dashboard records	1	1 per city/date
Public URLs	1 × /e/slug	1 × /e/slug per stop + 1 tour page
Ticket inventory	Shared on one event	Separate per city
Stripe Connect	One payout account per event (can reuse)	Same — configure per stop if needed
Discovery	Single-show grid	Featured tour rail + tour page
Best for	One-off show	Same headline artist, many cities

---

Common mistakes

1. Creating one event and manually editing the date for each city — breaks inventory and reporting. Create separate events instead.
2. Forgetting tour slug on a stop — that date won't appear on the tour page.
3. Only publishing some stops — fans see a tour with missing cities.
4. Using a tour for ticket tiers — VIP vs GA belongs on one event as ticket types, not separate tour stops.

---

Related models (not the same as a tour)

• Recurring series — same content repeating (weekly service); see Recurring events guide
• Multi-session — one day, multiple workshops/tracks; see Multi-session guide
• Transport listing — coach to a show; separate transport event linked to main slug — see Coach & transport guide