Booking Software for City Sightseeing, Hop-On Hop-Off and Trolley Tours

City sightseeing runs at a pace few other tours match. A trolley tour may leave every half hour from a busy square, a duck tour sells out on a sunny Saturday by lunchtime, and a bus operator may take bookings from its website, three marketplaces, a dozen hotel desks and a seller on the sidewalk, all for the same seats.

This guide covers what city tour operators need from booking software and where the line sits between tour booking platforms and specialist ticketing. It belongs to our series on booking software by tour type.

Departures or passes: decide first

City sightseeing products come in two shapes, and they need different software:

• Departure-based tours: a seat on the 10:30 trolley tour, the 2pm duck tour or the evening panoramic bus. Each sale removes a seat from one departure.
• Validity-window passes: a 24- or 48-hour hop-on hop-off ticket. Selling one removes nothing from a departure, and the guest boards wherever and whenever they like.

Tour booking platforms are built for the first. Pass operations with heavy street selling usually need specialist ticketing. Our guide to channel managers for sightseeing tours and hop-on hop-off buses explains why passes break seat-based software. The rest of this guide focuses on departure-based city tours, and on what to check if you sell both.

Frequent departures and walk-up sales

• Schedules at scale. Dozens of departures a day, varying by season and day of the week, should be set once as a pattern, not created one by one.
• Short cut-offs. City tours sell up to the last minutes, so online channels should stay open until shortly before departure.
• Instant confirmation. A guest buying on a phone at the stop needs a ticket on screen at once.
• Walk-up sales. Guests who buy in person must reduce the same availability as online buyers, or the bus is overbooked at the curb.
• Quick schedule changes. Traffic, parades and road closures mean departures are moved or merged at short notice, and every affected guest needs to know.

Picture a Saturday with a trolley leaving every thirty minutes from nine to five. That is seventeen departures, each selling through four or five channels, each needing a driver, a guide and a vehicle. The test of the software is whether the office spends that day selling and answering guests, or correcting calendars and counting seats by hand.

Capacity per vehicle and route

On departure-based tours, the vehicle is the limit. A trolley, an open-top bus and an amphibious duck vehicle each have their own seat count, and the departure's capacity should follow whichever vehicle is assigned.

• Swapping vehicles when demand is high should raise capacity on that departure, and a breakdown should show which guests need moving.
• Several routes, one fleet. Vehicles and drivers shared between routes must not be booked twice.
• Languages. Live-guided departures are often split by language, so passengers should be grouped by vehicle and language.
• Accessible seats are limited per vehicle, and guests who need them should be able to say so at booking.

For pass operations, capacity shows up as queues at stops rather than sold-out departures, and is managed with fleet size and frequency instead.

Ticket validation and on-board check-in

Every ticket should carry a code the driver or guide can scan at boarding. For a departure-based tour, one scan per guest does two jobs: it confirms the ticket is real and for this departure, and it builds the record of who boarded and who did not.

Pass operations scan at every boarding, all day, often where mobile signal is weak, so validation speed and offline use become the main requirement. Know which you need before you compare systems. The boarding routine for departure-based tours is set out in our article on manifests and check-in for tours.

Website, agents, kiosks and marketplaces in one inventory

City sightseeing has the widest sales mix of any tour type. Every seller should draw on one live inventory:

• Your website, through a booking widget that works on a phone at the stop.
• Marketplaces such as GetYourGuide, Viator and Google Things to Do, where many visitors search for city tours before and during a trip.
• Hotel desks and local agents, each with their own commission and, ideally, a way to book without phoning you.
• Kiosks and street sellers, who need a fast way to take payment and issue a ticket.

Where a seller cannot connect live, give them a fixed allocation per departure and release it before the bus leaves. Our guide to selling through agents and resellers covers commission and partner terms.

Combos, upsells and busy days

• Combination tickets. A bus tour with a river cruise, or a trolley tour with entry to a landmark, sells well. If the second part belongs to a partner, decide who holds the inventory and how the partner learns about each booking.
• Upsells at checkout. A night tour on the same day, a photo package or a priority boarding option raise the value of each booking without another vehicle.
• Language options. Live-guided departures in different languages are separate products in practice; recorded commentary is an option on the same seat.
• Predictable peaks. Cruise-ship days, festivals and long weekends bring surges you can see coming. Add departures or a larger vehicle early, and open them on every channel at once.
• Unpredictable dips. Rain empties open-top buses fast. Know how you will merge half-full departures and tell guests before they walk to the stop.

None of these needs exotic software, but each needs the schedule, vehicles and channels to change together. Test one combo product and one merged departure in any trial.

Checklist

1. Do I sell departures, passes, or both?
2. Can I set a season of frequent departures as one pattern?
3. Does capacity follow the vehicle assigned to each departure?
4. Can I group passengers by vehicle and language?
5. Does every ticket carry a code drivers can scan at boarding?
6. Do walk-up, agent, website and marketplace sales share one inventory?
7. Can hotel desks book themselves with their own commission?
8. How short can online cut-offs be?
9. For passes: is there fast validation that works without signal?

In a trial, sell the last seats on one departure from the website, a marketplace and an agent at the same time, then swap in a larger vehicle and see what changes.

Where Travelity fits

Travelity fits departure-based city tours: scheduled bus, trolley, duck and panoramic tours. Daily Operations fills vehicles according to your business rules, assigns vehicles, drivers and guides from one schedule, and groups passengers by vehicle and language. Every plan includes QR check-in, and check-ins and no-shows are recorded as guests board. The booking widget sells on your own site, live connections to GetYourGuide, Viator, Trip.com and Google Things to Do keep frequent departures accurate, B2B commission rules cover hotel desks and agents, and the Enterprise plan adds a partner portal where they book for themselves.

Travelity has no point-of-sale hardware, no pass product with a validity window and no offline scanning app. If unlimited hop-on hop-off passes sold on the street are most of your business, a specialist ticketing platform will serve you better. See plans and pricing.

Frequently asked questions

What is the best booking software for city tours?

It depends on what you sell. Scheduled city bus, trolley and duck tours with a seat on a departure suit tour booking platforms with strong vehicle scheduling and marketplace connections. Unlimited hop-on hop-off passes with heavy street selling usually need specialist ticketing software.

How do trolley and duck tours manage capacity?

Per vehicle and per departure. Each trolley or amphibious vehicle has a fixed number of seats, so the booking system must cap each departure at the vehicle assigned to it, and adjust when a larger or smaller vehicle is swapped in.

How are sightseeing tickets validated?

Usually with a QR code or barcode scanned on a phone or handheld at boarding. For departure-based tours, one scan per guest checks them in and shows who has not arrived. For hop-on hop-off passes, every boarding is scanned, which needs fast scanning that works without signal.

Can walk-up and kiosk sales share inventory with online bookings?

They should. If street sellers, hotel desks, your website and marketplaces all draw on one live inventory, the last seats on a departure cannot be sold twice. Where a seller is offline, give them a fixed allocation and release it before departure.

Should sightseeing tours be sold on marketplaces?

Usually yes. Visitors often book city tours on GetYourGuide, Viator and Google before or during their trip. Live two-way connections keep frequent departures accurate, and very short cut-offs let you sell seats until shortly before departure.

Bottom line

First decide whether you sell departures or passes. For departure-based city tours, look for capacity that follows the vehicle, fast boarding scans, short cut-offs and one inventory shared by every seller.

For unlimited passes sold on the street, look at specialist ticketing instead, and test validation speed where your buses actually run.

Related guides

• Tour booking software by tour type: what each kind of tour needs
• Channel manager for sightseeing tours and hop-on hop-off buses
• Digital manifests and check-in for tours