Campsite refunds are one of those topics nobody enjoys thinking about. You have taken a booking, blocked out the dates, maybe turned away other guests, and now someone wants their money back. It is tempting to dig your heels in or, at the other extreme, hand the money back without question just to avoid the hassle. Neither approach serves you well in the long run.

A fair, clearly written refund policy protects your revenue while keeping guests on side. It reduces the number of awkward phone calls, prevents chargebacks and gives you a framework for making consistent decisions. Here is how to get it right.

Why You Need a Written Refund Policy

Many campsite owners handle refunds on a case by case basis. Someone cancels, you think about it, and you decide in the moment whether to offer a refund, a partial refund, or nothing. The problem is that this leads to inconsistency. Two guests cancel under identical circumstances and get different outcomes. That is how you end up with bad reviews and disputes.

A written policy removes the guesswork. When a guest asks for a refund, you point them to the policy they agreed to when they booked. There is no negotiation, no awkwardness, and no feeling that you are making it up as you go.

Your refund policy should be:

If you already have a cancellation policy, your refund policy can be part of it. The key is making sure guests know what happens to their money if plans change.

Set Reasonable Timelines

The most common approach for UK campsites is a tiered timeline. The further in advance someone cancels, the more they get back. Here is a straightforward structure that works for most sites:

You can adjust these windows to suit your site. A CL owner with five pitches might feel that 14 days is not enough notice to rebook, especially during shoulder season. A larger park with strong online visibility might be confident they can fill a cancellation within a week.

The admin fee on early cancellations covers your payment processing costs and the time spent managing the booking. Guests understand this as long as it is stated upfront.

Bank Holidays and Peak Dates

Consider applying stricter terms for high demand periods. If someone cancels a bank holiday weekend booking two weeks out, the chances of refilling that pitch at the same rate are slim. Many sites use a longer notice period (say, 42 days) or offer no refunds at all for peak bookings. Just make sure it is clear at the point of booking.

Partial Refunds vs Full Refunds

Not every refund request is a straightforward cancellation. Sometimes a guest shortens their stay, leaves early because of bad weather, or wants compensation because the shower block was out of order for a morning. These grey areas are where most disputes happen.

A few principles to guide you:

The key is having a position before the situation arises. When you are on the phone with a frustrated guest, it is much easier to say "our policy on early departures is..." than to make something up under pressure.

Processing Refunds Quickly

When you do agree to a refund, process it fast. Nothing damages trust more than a guest waiting weeks for their money. If they paid by card, refund to the same card. If they paid by bank transfer, send the refund the same way.

If you use a card payment system like Stripe, refunds are usually straightforward. You issue the refund from your dashboard and the money goes back to the guest's card within five to ten working days. It is worth noting that most payment processors do not refund their processing fee, so a full refund still costs you a small amount. That is one reason admin fees exist.

Keep a record of every refund you process. Note the guest name, booking reference, amount refunded, reason for the refund and the date it was processed. This protects you if there is ever a dispute, and it helps you spot patterns. If you are issuing refunds for the same reason repeatedly, that is a sign something needs fixing on your end.

CampSuite's invoicing tools keep a clear paper trail of payments and refunds against each booking, so you do not need to maintain a separate spreadsheet.

Handling Chargeback Disputes

A chargeback happens when a guest contacts their bank or credit card company to reverse a payment instead of asking you directly. This is frustrating, and it costs you money even if you win the dispute. Most payment processors charge a fee for each chargeback regardless of the outcome.

The best defence against chargebacks is a clear refund policy and good communication. If a guest knows exactly what they are entitled to and you process legitimate refunds promptly, they have no reason to go to their bank. Problems usually arise when guests feel ignored or treated unfairly.

If you do receive a chargeback, respond quickly with evidence. This means your written refund policy, proof that the guest agreed to it (the booking confirmation), and records showing any communication about the refund. A well-documented trail usually resolves disputes in your favour.

When to Make Exceptions

Policies exist to handle 90 per cent of situations consistently. The remaining 10 per cent sometimes call for judgement.

A regular guest who has visited every summer for five years and has a genuine emergency deserves a different response than a first-time booker who simply changed their mind. A family dealing with a bereavement is not the same as someone who found a cheaper site.

When you do make an exception, consider offering a credit or date transfer rather than a cash refund. This keeps the money in your business while still being fair to the guest. Many guests actually prefer this because it takes the pressure off rebooking immediately.

Whatever you decide, document it. A quick note on the booking record means you will remember what happened if the guest contacts you again or if a similar situation arises in the future.

What This Means for CL and CS Sites

If you run a CL or CS site, refund situations are less frequent simply because booking values are smaller. But they still happen, and they can feel more personal when you are dealing with just five pitches and know most of your guests by name.

The same principles apply. Write your policy down, include it in your booking confirmation, and stick to it. For CL and CS sites, a simpler version often works well. Something like: full refund with 14 days notice, no refund within 14 days, date transfers welcome at any time. Short, fair and easy to explain.

If you are still taking bookings by phone and handling payments by bank transfer, keeping track of who paid what and who is owed a refund gets complicated quickly. CampSuite is free for CL and CS sites and gives you a clear record of every payment and refund, so nothing slips through the cracks.

Getting Your Policy Right

A good refund policy is not about being strict or generous. It is about being clear. Guests do not mind reasonable terms as long as they know what those terms are before they book. The sites that run into trouble are the ones with vague wording, hidden conditions, or no policy at all.

Write your policy in plain language. Publish it where guests will see it. Include it in every booking confirmation. Process refunds quickly when they are due. And when something falls outside the rules, use your judgement and document what you decided.

Get this right and refunds become a minor administrative task rather than a source of stress. Your guests will respect you for being fair and upfront, and that trust pays off in repeat bookings and positive reviews.