Handling Booking Changes, Rebookings and Amendments Without Chaos
A new booking touches your calendar once. A change touches it twice — and sometimes nobody tells you it happened.
Operators build careful systems for taking bookings and handling cancellations, then run changes from memory. It is understandable — a change feels like a small favour to a guest, not a transaction. It is also where a surprising share of double-bookings, wrong manifests and missed pickups come from.
This covers the changes you will actually see, the policy that keeps them fair, what happens when a marketplace booking changes, and the one rule that stops a moved booking landing on a full departure.
The changes you will see
Five kinds cover almost everything, and each touches something different.
- Date or time. Releases a place on one departure and needs one on another. The riskiest change, and the most common.
- Headcount up. A new sale in disguise, subject to availability like any other.
- Headcount down. A partial cancellation, which is how your cancellation terms should treat it.
- Pickup or meeting point. No capacity effect, but it changes a driver's route and is the change most often lost before the morning.
- Upgrade or product switch. Private instead of shared, a longer version. Treat it as a new booking on the new product plus a cancellation of the old one.
Policy: free, fee or no
The principle is that change terms have to agree with cancellation terms. If cancelling two days before costs a guest the full price but moving to next month is free, you have a free cancellation with an extra step — and the seat you are holding for them next month may never be used.
- Well ahead: free. A guest who can move keeps their booking rather than cancelling it.
- Close to departure: a fee, or not at all, because the seat they release can no longer be resold.
- After a fixed cut-off: no changes. That cut-off should match the time you freeze tomorrow's manifest, so the guide's list is final when you say it is.
Publish all three with your cancellation terms, and apply them consistently. The hardest guest to say no to is the one who was allowed an exception last year.
When a marketplace booking changes
Direct bookings change where you can see them. Marketplace bookings change on someone else's platform, under someone else's process, and the details matter.
Viator is a useful example because it documents this plainly. Its booking amendment interface sends a traveller's change straight to the operator's reservation system — and according to its supplier documentation, operators only receive an amendment email when that automated attempt fails. A change that works arrives silently.
That is good automation and a trap at the same time. If your system receives the amendment, the new date is right there. If you are relying on email to notice changes, you will not notice this one, and the guide will work from the old list. Viator also notes that when an operator proposes a change on a booking sold through one of its distribution partners, that partner may need to approve it.
Other platforms handle changes differently; some route them through their own support rather than letting either side edit. Check each channel's process rather than assuming, and check the reverse too — whether a change you make on your side travels back to the platform, or leaves the guest's marketplace booking showing the old details.
Capacity and waitlists
A date change is two capacity events, not one. Take the new place first, then release the old one — never the other way round. If you release first and the new departure filled an hour ago through a marketplace, you have a guest with no booking at all and a place you just gave away.
Both steps have to happen in the one availability every channel reads, at the moment you agree the change. Managing capacity across several marketplaces covers why; a change recorded in a spreadsheet that evening is exactly the gap double-bookings come through.
When the date a guest wants is full, a simple waitlist beats a refusal: note who is waiting and in what order, and when a place opens, offer it to the first with a clear deadline to accept before moving to the next. The places changes release are exactly the ones a waitlist fills.
Telling guides and drivers
A change the office knows about and the guide does not is not really made. Before the manifest freeze, a change simply updates the list the guide will receive. After it, the change goes to one named person, who tells the guide or driver directly and confirms they have seen it.
Pickup changes deserve particular care, because they alter a route rather than a number. A driver working from last night's list collects nobody at the old hotel and leaves a guest waiting at the new one. The operations best-practices checklists build this into the day-before routine.
Confirming the amended booking
Every change should produce a fresh confirmation, and it should restate the whole booking rather than describe the difference. "Your booking has been changed" sends the guest hunting through two emails to work out which details still apply.
Include the new date and start time, the meeting or pickup point, the number of guests, any price difference and how it is settled, and the cancellation terms that now apply. The test: the guest could delete the original confirmation and rely on this one alone. Sending it automatically, the moment a change is saved, removes the step most often forgotten.
How Travelity helps
In Travelity, booking management lets you edit reservations from every channel in one place, and live availability updates as changes occur, including on bookings that came from marketplaces — so a moved booking takes its new seat in the same availability your website and listings read. The channel manager keeps booking data in step across connected channels, and automated team and customer notifications are included on every plan, basic on the entry plan and advanced above. It is still worth confirming, during the 21-day trial, how each of your own channels behaves when a booking changes — that is true of any system.
Frequently asked questions
How should tour operators handle booking changes?
Treat every change as a capacity event first and a customer-service event second. Check the new date or headcount against live availability, take the new place before releasing the old one, confirm the change to the guest in full, and tell whoever is running the affected departures. Publish what changes are free, what costs something, and the cut-off after which changes are no longer accepted.
Should I charge a fee for changing a tour booking?
Changes made well ahead are usually worth allowing free, because they keep a guest who might otherwise cancel. Charge, or refuse, close to departure, when a change costs you a seat you can no longer resell. Whatever you choose, make the change terms consistent with your cancellation terms, since a late date change is otherwise a free cancellation by another name.
How do I stop date changes causing overbookings?
Remember that a date change is two operations: releasing a place on one departure and taking one on another. Check and take the new place first, then release the old one, and do both in the same system every channel reads. Doing it in the other order, or in a spreadsheet updated later, is how a moved booking lands on a departure that filled in the meantime.
How do booking changes work on Viator?
Viator documents a booking amendment interface that sends traveller changes, requested after confirmation and before travel, straight to the operator reservation system. According to its supplier documentation, operators only receive an amendment email when that automated attempt fails, so a successful change arrives silently. Check your system handles amendments rather than assuming an email will tell you.
What should a booking change confirmation include?
The complete booking as it now stands, not just a note that something changed: the new date and start time, the meeting or pickup point, the number of guests, any price difference and how it is settled, and the cancellation terms that now apply. A guest should be able to delete the original confirmation and rely on the new one alone.
Bottom line
Make change terms agree with cancellation terms, stop changes at the same cut-off that freezes the manifest, and treat every date change as two capacity events — new place first, old place second, in one shared availability.
Then close the two gaps changes fall through: the marketplace amendment that arrives without an email, and the guide or driver who is still working from yesterday's list.
Related guides
See Travelity in action. Book a Personalized Demo.
30 minutes that can completely change the way you run your travel business. See how Travelity can help you work smarter, sell more, and operate with less stress.