Writing a Cancellation Policy That Protects Margin Without Losing Bookings

Two forces pull in opposite directions here and both of them are real.

Generous cancellation converts. A traveller three weeks out, uncertain about their itinerary, will book the tour with free cancellation and not the one without. That is not a preference, it is close to a rule.

But at some point before departure your costs stop being hypothetical. The guide is booked. The boat is fuelled. The permits are bought. Refunding in full after that point means you paid to run a trip you did not sell.

The policy is where you draw that line, and the mistake most operators make is drawing exactly one.

Build a ladder, not a wall

A single cutoff is a cliff. Free until 24 hours, nothing after, means a traveller cancelling at 25 hours costs you nothing and one cancelling at 23 hours loses everything. That asymmetry generates disputes, chargebacks and bad reviews, and it does not reflect your actual costs, which ramp rather than jump.

A ladder has tiers. Each tier is defined by a cutoff expressed in hours before departure and a refund percentage. Something like:

Four tiers is usually plenty. Two is too blunt and six is more than a traveller will read.

It has to be data, not prose

This is the part that separates a policy that works from one that generates support tickets.

If your cancellation terms live in a paragraph in your product description, then nothing can act on them. Your booking system cannot calculate a refund. A reseller's website cannot display the deadline. Your own staff have to read it and interpret it, and two staff will interpret it two ways.

Expressed as structured tiers, all of that becomes automatic. The traveller sees a countdown to their free cancellation deadline. The reseller displays it correctly on their own site. The refund is calculated the same way every time by every channel.

Write the prose too, because people read prose. But the prose should be generated from the data, not the other way round.

Fees, and where they belong

Two kinds, and they are not the same thing.

A cancellation fee is a percentage of the booking, deducted from the refund. It scales with the value at stake, which is usually what you want.

A service fee is a flat amount covering the administrative cost of processing the cancellation. It should be small, and there is one decision to make about it: per booking or per traveller.

Per booking is fairer and easier to defend. Per traveller is defensible only when your cost genuinely scales with headcount, for example when each traveller holds an individually issued third-party ticket you have to void separately.

The clauses that save you

Weather and operational cancellation

If you cancel, the traveller gets everything back or a free move. No exceptions, no tiers, no service fee. This is not generosity, it is the single most reliable way to protect a rating.

Be specific about who decides and when. "The skipper makes a final call at 07:00 on the morning of departure based on the harbourmaster's forecast" removes an entire category of argument.

Minimum numbers

If a departure needs six people to run, say so on the product page, say when you decide, and say what happens. "If fewer than six are booked by 48 hours before, we will contact you to move to another date or refund in full."

Operators are often reluctant to publish this because it sounds like uncertainty. Publishing it is far better than a traveller discovering it by phone the night before .

No-shows

A no-show is not a cancellation and should be its own line. The standard is no refund, and that is reasonable.

But define the grace period, because the alternative is a guide making a judgement call in the rain. "We wait fifteen minutes from the departure time." Then, separately, mark the booking as a no-show in your system rather than as a cancellation, because they are different things for your reporting and for the traveller's record.

Late arrival to a timed slot

Different from a no-show and worth handling explicitly, particularly for attraction tickets. Many venues will admit a late arrival on a standby basis. Saying so converts a refund request into a mildly inconvenienced but satisfied visitor.

Different terms for different buyers

A trade partner booking a group of twelve on a contract is not the same counterparty as a traveller booking two seats at midnight, and the terms need not be identical.

Trade partners generally accept, and often prefer, longer cancellation windows in exchange for a better rate. They are planning further ahead and their own client terms are usually stricter than a consumer's.

What must not vary is which terms apply to a given booking. The rule is absolute: the terms in force at the moment the booking was made are the terms that govern it, forever. If you tighten your policy in March, every booking made in February keeps February's ladder. Store the applicable tiers on the booking itself rather than looking them up at cancellation time, because the lookup will eventually return the wrong answer.

What to write today

1. Work out the point at which your costs genuinely commit. That is your first cutoff.
2. Build three or four tiers between there and departure.
3. Add a weather and operational clause with full refund and a named decision point.
4. Add a minimum numbers clause if any product has one.
5. Add a no-show line with a stated grace period.
6. Put all of it into your system as structured tiers, not as description text.
7. Generate the prose from the data so the two cannot drift apart.

Then leave it alone for a season and look at what actually happened. Policies written from data beat policies written from anxiety, and you will not have the data until you have run the season.