Imagine a small agency in Izmir that runs a five-day Cappadocia trip every other weekend in spring. The trip has one coach with 46 seats and a block of 20 rooms in a partner hotel. The agency adds a booking form to its website, the kind made for hotels: pick a date, pick a room, pay.
In the third week a group of four friends books two twin rooms, a couple books a double, and three solo travellers each book a room to themselves. By Thursday the form says "sold out", because the rooms are gone. The coach leaves with fourteen empty seats. Two weeks later the opposite happens: the rooms hold out, the coach does not, and the agency finds itself calling a family to say there is no seat for their teenager.
The form did nothing wrong. It was built to sell rooms, and a tour is a different product. The points below are what a tour booking form has to understand that a hotel form never needed to.
1. A departure has two limits, not one
A hotel sells nights in rooms. A group tour sells a place on a departure, and that place uses up two things at once: a seat on the vehicle and a bed in a room. Either can run out first.
The form needs to track both for every departure date and close sales when either limit is reached. It also helps to show what is left in the terms a traveller cares about: "6 places left" is more useful than a room count, and far more honest than a date that simply disappears from the calendar.
2. The price belongs to the person, and depends on the room
Tour prices are usually quoted per person in a shared double. Someone travelling alone pays a single supplement. A third person in the room often pays less, and a child sharing with parents less again.
A form that multiplies one price by the number of travellers will be wrong for a large share of bookings, and somebody will then correct it by phone. List the cases you actually sell, such as double, single, triple and child with two adults, give each its own per-person price, and let the form work out the rest.
3. Let the total change in front of the traveller
Once prices depend on hotel category, room share and the number of people, nobody can calculate the total in their head. If the form shows the amount only on the last screen, travellers go back and forth to compare options, and some give up halfway.
Show a running total that updates with each choice: change the hotel and the figure changes, add a third person and it changes again. People settle on an option faster when they can see what each choice costs.
4. Extras belong inside the booking
Tours come with extras: a visa service, a ski pass, an airport transfer, travel insurance, a seat at the gala dinner. If these are arranged later by message, each one becomes a separate conversation, a separate payment and a separate chance of being forgotten.
Put the extras in the form as options, priced per person or per booking as appropriate, and include them in the same total. Note which ones have their own deadline. A visa service, for example, cannot be added four days before departure.
5. Ask for little now and the rest later
To hold a place you need a lead name, a phone number, an email address and the room arrangement. To run the trip you need much more: full names as written in the passport, dates of birth, passport numbers, dietary needs, pick-up points.
Asking for all of this up front makes the form long and loses bookings from people who do not have their friends' passports to hand. Take the short version at booking, then send a link where the lead traveller completes everyone's details before a stated date. Show your team which bookings are still incomplete, so nobody discovers a missing passport number on the morning of departure.
6. The balance needs a date and a reminder
Most tours are sold with a deposit, with the balance due some weeks before departure. Forms often handle the first payment well and leave the second to a spreadsheet.
Each booking should carry its own schedule: what was paid, what is owed, and by when. A reminder a week before the due date and a clear list of overdue balances save the awkward round of calls in the final days. If you accept bank transfers, give each booking a reference code so that incoming payments can be matched to it.
7. If the tour needs a minimum number, say so
Many departures only run if enough people book. Travellers accept this when it is stated; they resent it when they hear about it afterwards.
State the minimum on the page, the date by which you will confirm the departure, and what happens if it does not run: a full refund or a move to another date. Inside the system, mark each departure as "open", "guaranteed" or "cancelled", so that the website and the confirmation emails always say the same thing.
8. Plans change, so write the rules into the system
In a group of four, one person drops out and a cousin takes the place. A couple wants to move to the next departure. Someone asks to upgrade to a single room.
Decide in advance which changes are free, which carry a fee and after which date nothing can be changed, then make these ordinary actions in the admin panel: replace a traveller, move a booking, change a room type, with the price difference calculated automatically. Changes handled only by phone tend to live in someone's memory until the day it matters.
9. The booking is finished when the lists are right
The purpose of all this information is the documents you hand over: a passenger list for the coach company, a rooming list for the hotel, a pick-up list for the guide, and a list of dietary needs for the restaurant.
If these still have to be typed out by hand from individual bookings, the form has only done half its job. Each list should come out of the system with one click, for one departure, in the layout your suppliers expect.
A quick test
Take your next departure and try three bookings yourself: a solo traveller, two adults with a child, and a group of four who want two rooms and one visa service. Check the total for each one against your price list. Then ask the system for the rooming list. Any step where you reach for a calculator or a spreadsheet is a gap in the form.
In short
- Track seats and rooms separately for every departure.
- Price per person, according to how the room is shared.
- Show a running total as the choices change.
- Sell extras inside the booking, with their own deadlines.
- Take a short form now and collect passenger details later.
- Give every booking a payment schedule with reminders.
- State minimum numbers and what happens if they are not met.
- Turn changes into ordinary admin actions with clear rules.
- Produce passenger, rooming and pick-up lists from the system.
A tour site we built for Bansko Skifest, a ski and festival trip from Istanbul, follows the same idea on a small scale: its booking form totals the price by hotel and room type as the visitor chooses, and offers the visa service as an option in the same form.
Our work on this: Web Development
Planning a project like this?
Plan it in 10 steps