# No-show fees in UK restaurants: what operators actually do

> Whether to charge, how much, and how the good operators make it stick — plus the two questions worth putting to your accountant before you set a policy. Practice, not legal advice.

_Canonical: https://seatsat.com/guides/restaurant-no-show-fees-uk_

---

The question almost every UK operator arrives at eventually is not _should we charge for no-shows_ — it is _would ours actually hold up, and is it worth the friction_. This is what restaurants in the UK are doing in practice, and where the genuinely local questions sit.

None of what follows is legal or tax advice. The rules that bind you depend on how you take bookings, how you take money, and who your guests are, and they are set by your own advisers and the consumer-protection regime that applies to your business — not by us. What a guide _can_ usefully do is describe the shape of what works, and be specific about which questions to take elsewhere.

## What operators actually charge

There is no standard UK figure, and the range in the wild is wide enough that quoting an average would be misleading. What is consistent is where the number comes from.

The operators who are comfortable defending their policy derive the amount from something real — the covers lost, at a per-head figure the kitchen can justify — rather than choosing a round sum because it sounds like it will deter people. That derivation matters twice: it keeps the number proportionate to the actual loss, which is the principle every fairness test in this area circles around, and it gives you something to say when a guest disputes it.

> **The pattern, not the number**
>
> - Charge per **cover**, not per booking — an empty two-top and an empty ten-top are not the same loss.
> - Set it against **what you lost**, not what the booking was worth. The margin on covers you could not resell is the honest basis.
> - Larger tables and **set-menu or tasting services** carry higher amounts, because the commitment behind them is larger and the resale window shorter.
> - Round numbers invented to deter people are the ones that get argued about.

## The three things that make a policy stick

Across every operator who reports being comfortable enforcing a policy, the same three properties recur — and they are all about what happened _before_ the guest failed to arrive.

**The guest saw it before they confirmed.** Not in a footer, not on a terms page nobody opens — on the booking step itself, in the same view as the date and the party size. A policy discovered after the fact is the one that generates a chargeback and a review.

**The guest actively agreed.** A tick, a step, an explicit confirmation. The difference between "it was on the page" and "they agreed to it" is the difference between a term and an assertion.

**The amount is proportionate, and applied consistently.** Operators who waive for genuine emergencies and apply it otherwise report far less friction than those who enforce rigidly or arbitrarily. Consistency is what makes it read as a policy rather than a punishment.

> The policy that works is the one the guest saw coming.
>
> _— — THE COMMON THREAD_

## Deposit or charge — they behave differently

UK operators use two mechanically different things and the distinction matters more than the vocabulary suggests.

A **deposit** is money taken up front, usually against a set menu or a large table, and set against the final bill. It changes the guest's relationship to the booking at the moment they make it, which is most of its value — the deterrent works before anyone fails to show.

A **charge after the fact** — whether against stored card details or invoiced — leaves the booking frictionless and only bites on failure. It is easier to sell to guests and harder to collect.

Which you choose changes the guest experience, the collection rate, and — importantly — the tax question below. Operators running set menus and large groups tend toward deposits; à la carte rooms taking a policy for the first time tend to start with a stated charge and no card at all.

## The two questions for your accountant

This is the genuinely UK-specific part, and the part a guide should not answer.

**Is the money inside or outside the scope of VAT?** The treatment turns on whether what you have received is compensation for a loss or payment for a supply — and HMRC has revisited its position on retained payments and cancellation charges more than once. The answer can differ between a forfeited prepayment and a sum charged after the event, which means it can differ between your deposit policy and your no-show policy even though you think of them as one thing.

**Does the answer change with what you call it?** Because the analysis follows the substance rather than the label, "deposit", "cancellation charge" and "no-show fee" are not interchangeable for this purpose even where they are interchangeable in your dining room.

> **Ask it in this shape**
>
> Not _"is a no-show fee VATable?"_ — that question has no single answer. Ask:
>
> - For the way **we** take the money — before service, or after the guest fails to arrive — is it inside or outside the scope of VAT?
> - Does that change if the amount is set against the final bill rather than retained?
> - Should the figure we publish be stated **inclusive or exclusive** of tax?
>
> That last one is the practical output. It determines the number that goes on the booking page.

## What operators do before they charge anything

The uncomfortable finding from operators who have been through this is that the fee is rarely the thing that moved the number. The interventions that did are cheaper and earlier.

A **confirmation that feels like a commitment** rather than a receipt. A **single well-timed reminder** — one, not three — carrying a one-tap way to cancel. And making release **trivially easy**, because the guest who cannot find the cancel link becomes a no-show by default rather than by choice.

Operators who fix those three first commonly report the residual rate drops far enough that a fee becomes a policy for the tail: something you have, state clearly, and rarely invoke.

> **The order most operators end up in**
>
> 1. Confirmations and one good reminder, with an obvious cancel.
> 2. A **stated policy** — published, agreed to at booking, no card taken.
> 3. Card capture, once the policy has proven itself and the volume justifies the friction.
> 4. Deposits, for set menus and large tables only.
>
> Very few rooms need step four for ordinary service.

## The honest summary

A no-show policy is not primarily a revenue instrument, and operators who introduce it expecting one are usually disappointed. It is a commitment device, and it works through the moment the guest reads it — not the moment you charge it.

That is also why disclosure keeps appearing in every version of the answer: the same clarity that makes a policy fair to the guest is what makes it worth having at all.

_General orientation for UK operators, not legal or tax advice. Rules vary with how you take bookings and payment, and change over time — confirm anything specific with your own advisers before you publish a policy or a figure._