Restaurant no-shows in Spain fell to 3.3% in 2025, according to TheFork. 21% of restaurants already ask for a card as a guarantee. The question is in which system.

Picture this: Saturday, half past nine in the evening, a Michelin-starred restaurant on the coast near Málaga. Table eight, four covers on the tasting menu, is still empty. That booking came through the restaurant’s website, without a card. Table ten came through a platform, with a guarantee. Table ten is already on the second course. Table eight is not answering the phone.

The conversation about no-shows usually ends with an average. I think the useful question is a different one: in which system does the guarantee on your table live, and who remembers the people who did not come?

What the figures say.

According to figures TheFork published in February 2026, the average no-show rate in Spanish restaurants fell to 3.3% in 2025, from 3.6% in 2024. By province, it ranges from 3.1% in Alicante to 3.7% in Seville, with Málaga and Madrid at the average and Barcelona at 3.5%.

Defences are growing. 21% of restaurants use a bank card as a booking guarantee, twice as many as in 2023, and 7% take prepayment, three times as many as two years earlier. The platform also offers card pre-authorisation and a feature that analyses each customer’s history to flag risky bookings. And since the end of 2024 it has removed users who rack up four no-shows in twelve months: in 2025, according to the platform itself, that was 2%.

What the average does not say.

These are a platform’s figures on bookings made through it, across every kind of restaurant. They say nothing about bookings that come through your website or by phone, or about fine dining in particular. I do not know the rate for a tasting-menu restaurant, and I have found nobody who publishes it. Nor does an average say when it happens: an empty table on a Tuesday and one on a Saturday with a waiting list do not cost the same.

An example with round numbers, not a statistic: in a 40-cover restaurant with a 180-euro menu, a 3.3% rate means on average slightly more than one empty cover per service, about 240 euros. Over 300 services a year, about 71,000 euros, with the produce already bought and the team already on the floor. Your own numbers are in your hands.

The blind spot: the memory belongs to the platform.

When the platform removes someone who has failed to turn up four times, it is using a memory that spans thousands of restaurants. Your restaurant’s memory only spans its own bookings, and often not even that: a booking by phone or through the website form asks for no card and is kept in no history.

The result is a paradox. The best-protected booking is the one that comes through an intermediary, and the least protected is the one that comes direct. If your website takes bookings less well than the platform, you are pushing your best guests towards the intermediated channel yourself.

A booking without a guarantee is a promise made by one side only.

Where I stand.

I do not think everyone should be charged in advance. In fine dining, a badly explained guarantee annoys the people who were always going to come. I think the direct booking should be at least as well protected as the platform’s, and better explained: what is guaranteed, when it is charged and how to cancel, in the guest’s language. And the message confirming the table before service should be sent by your system, not by someone on the floor with a good memory. If your website books worse than the platform, your best guests will learn to book on the platform.

What I would check.

• The guarantee on your website. Whether a direct booking asks for a card in the same cases as the platform does.
• The policy, in writing. Cancellation deadline, amount and when it is charged, visible before booking and in all your languages.
• The confirmation. An automatic message before service, with a button to cancel without having to explain.
• The waiting list. Whether a timely cancellation reaches someone who wanted that table.
• Your own figure. How many tables were left empty last quarter, by channel and by day of the week.

Where to start.

1. This week

   Measure

   Empty tables over the last three months, by channel: website, phone and platform.

2. This month

   Match the guarantee

   Make booking on your website at least as protected as booking on the platform.

3. This quarter

   Automate the confirmation

   A message before service, one-tap cancellation and a notice to the waiting list.

4. Every season

   Review the policy

   Adjust deadlines and amounts with your own data, not someone else’s average.

Count last week’s empty tables and split them into two piles: those booked through a platform and those booked on your website or by phone. Which pile is bigger? And which one had a guarantee?

If the direct booking is the least protected, your most loyal guest is receiving less care than a stranger. And the question this note leaves open remains: on the day you leave the platform, what will it know about your guests that you do not?

If you would like me to review how your website takes bookings today and what it protects, start with the Strategic Diagnostic. Which guarantee to ask for and how to inform guests of it is for you and your adviser to decide, not a designer.