No-show fees for restaurants: legally compliant in the EU and UK in 2026

A no-show is not "annoying" for an independent restaurant — it is a direct loss. Industry surveys put no-show rates in DACH and Western Europe at 5 to 15 percent of all reservations, depending on location and segment. At an average ticket of €50 per guest and 600 covers per month, that is €1,500 to €4,500 in lost margin — every single month.

Most restaurants know the problem. Few know the legally-clean answer. This post explains how to set up a no-show fee in 2026 so it survives a small-claims dispute and stays GDPR-compliant.

What a no-show fee actually is, legally

A no-show fee is not a penalty — it is a claim for damages or a liquidated, lump-sum compensation for the operator's actual loss. The distinction is not academic: penalty clauses are scrutinised harder than damages clauses in nearly every EU jurisdiction.

In the UK, the framework is the Consumer Rights Act 2015 plus the older Unfair Terms in Consumer Contracts Regulations — the clause must be "transparent" and represent a "genuine pre-estimate of loss." In Germany, the equivalent hooks are §§ 280 + 309 No. 5 BGB. In France, art. 1231-5 of the Code civil treats it as a clause pénale, which the court may reduce if manifestly excessive. The substance is the same everywhere: realistic amount + clear disclosure + opt-in by the guest.

A workable clause needs four elements:

Explicit T&Cs on the booking page that the guest must actively accept (checkbox).
Realistic amount — the comfortable range across EU jurisdictions is €15 to €25 per person. Higher figures are routinely struck down as penalties.
A clear cancellation window — typically 24 hours before the reservation. Cancellations earlier than that incur no fee.
An express right for the guest to prove the actual loss was lower — this is mandatory in most EU consumer law frameworks (in Germany under § 309 No. 5b BGB; an equivalent rule exists in nearly every member state).

Template clause for booking T&Cs

The text below is a starting point; we recommend a short review by a local lawyer in your market:

If the guest fails to appear without cancelling at least 24 hours before the reserved time, or does not honour the reservation, the restaurant will charge a flat compensation of €20 per reserved person. The compensation is a lump-sum estimate of the damage caused by the no-show (lost table capacity, prepared food, scheduled staff). The guest reserves the right to prove that no damage occurred or that the actual damage was substantially lower.

Three details are non-negotiable across jurisdictions:

The word "compensation" (not "fine" or "penalty") — the term you use steers the legal classification.
"Lump-sum estimate" keeps the clause out of the penalty-clause regime.
The express right to prove a lower actual loss is mandatory in most EU consumer-protection statutes; without it the clause is unenforceable.

Implementation: card-on-file, not pre-payment

The most effective technical form is card-on-file: the guest stores a card at booking; the restaurant charges it only in the no-show case — no pre-payment, no cash tied up on the guest side.

Tablario uses Stripe Connect with the setup_intent flow:

At booking, the card is verified; nothing is charged.
Stripe stores a reusable Payment Method on the restaurant's own Stripe Connect account — not on a Tablario master account. This is PCI-DSS-clean and GDPR-clean.
If the guest no-shows and the restaurant confirms the no-show in the Tablario back office, the compensation is charged. The guest receives an automated email with the receipt and dispute instructions.

Why not pre-payment? Three practical reasons:

Conversion killer. Pre-payment measurably drops booking-widget conversion — by 18 to 24 percent in our beta tests.
Admin overhead. Every legitimate cancellation requires an active refund.
Trust signal. Pre-payment signals distrust. Card-on-file is neutral: "We trust you, but we are covered for the rare exception."

The General Data Protection Regulation imposes three requirements:

Legal basis. The card storage is justified by performance of the contract (Art. 6(1)(b) GDPR) — the booking is the contract, the card is the security for the potential compensation.
Data minimisation. Tablario stores no card data locally — only a Stripe token. The actual PAN data lives only at Stripe (PCI-DSS Level 1).
Access and deletion rights. Once the reservation is closed (guest arrived or cancelled in time), the Stripe setup intent expires or is deleted automatically. Tablario does this per booking — there is no "card stored for 12 months".

When a no-show fee makes sense in practice

Not every restaurant needs the fee. Our pragmatic guideline:

Bistro / casual dining (< €30 ticket): no-show rate under 5 % — usually not worth the setup; the conversion hit dominates.
Mid-range restaurant (€30 – €70 ticket): no-show rate 5 – 10 % — card-on-file from group size 6 pays off.
Fine dining / tasting menu (> €70 ticket): no-show rate often > 10 % — card-on-file from group size 2, plus a deposit for groups of 8+.
Event reservations (NYE, Valentine's, Mother's Day): always secured, regardless of usual ticket — that table time is not replaceable.

What Tablario's no-show protection module ships with

The Tablario no-show protection plugin (€14 / month) includes:

Card-on-file via Stripe Connect — the restaurant is the recipient of the compensation, not Tablario.
Threshold configuration — per shift, group size, or reservation value.
Automated 24-hour reminder SMS / email — the single largest no-show reduction lever (industry studies put it at up to 60 % fewer no-shows just from automated reminders).
Legally vetted T&Cs template — you do not write it yourself; the template above ships with the module.
Audit log — every charge is recorded with reason, timestamp and Stripe charge ID, in case the guest later disputes.

Frequently asked questions

Do we need to see the guest's card? No. Stripe Elements renders the card field iframe-based; the data goes from the browser session directly to Stripe, not through Tablario or the restaurant. You only see the last four digits.

What if the guest disputes? The Stripe charge can be refunded by the restaurant within 14 days. In a formal chargeback, Stripe investigates; the T&Cs clause plus the audit log are the strongest evidence.

Does this apply outside the EU? The logic (lump-sum damages estimate, express right to prove lower loss) is recognised in nearly every common-law and civil-law jurisdiction. The statutory hooks differ (Consumer Rights Act in the UK, Restatement (Second) of Contracts § 356 in the US). The technical implementation is identical.

Does the fee actually lower the no-show rate, or only recover the loss? Both. Industry data (DEHOGA, OpenTable) shows that simply communicating that a fee exists lowers no-show rates by 30 to 50 %. The actual charge is rarely triggered.

Sources: German Civil Code (§§ 280, 309 BGB) · UK Consumer Rights Act 2015 · French Code civil art. 1231-5 · GDPR Art. 6 · Stripe Connect documentation (developer.stripe.com).