Does a small restaurant need table booking on its website?

Only if the guests actually book. If you take a couple of bookings a week on the phone and the rest walk in through the door, the phone number and the opening hours, clearly at the top on a phone, are enough. If instead you get parties who want to know the table is theirs on Friday, or Christmas tables booked months ahead, a booking the guest makes herself in the evening when she decides pays off.

What does table booking through a platform cost?

It depends on the platform and the agreement: a fee per seated guest, a monthly fee or both, and the prices change. Read their current terms and do the sum on your own bookings per month. The cost that is not on the price list is the guest data: at a marketplace the guest is their customer first, and the list does not come with you if you switch.

Can I have both a platform and my own booking on the website?

Technically yes, but do not. Two booking routes give double bookings and staff who do not know which list counts. Choose one route and let the Google profile, the site and the QR code on the table lead to the same place. If you want to move from a platform to your own booking, do it on a set date and move the bookings already in the system.

How do I reduce no-show parties?

A reminder the day before that the guest can reply to, a cancellation link in the same email so it is possible to cancel without calling and feeling ashamed, and a confirmation that can be found again. For large parties and Christmas tables it is reasonable to take a request instead of a direct booking, so that you call and confirm. There is no public Swedish statistic for restaurants specifically, so trust your own numbers: count the no-shows a month before and a month after.

Can the guest cancel and change the table booking herself?

She should be able to, via a link in the confirmation email. The link should carry a key that exists only in the email, so that nobody can cancel someone else’s table by guessing a booking number. The number alone should show only day, time and party size, because it is read out on the phone and shown on the till screen.

← All guides

23 October 2026 · 8 min

Table booking on a restaurant website 2026: your own system or a platform?

Table booking on the website is one of the few choices where I give two different answers to two restaurants in the same village. Rökeriet i Åhus books its tables through a platform, and when I built their new site I left it alone: the floor plan and the staff rota live there, so the site links out and keeps its hands off. A bar a few hundred metres away got its own booking engine built into the site, with the guest data in its own hands and the reminder in its own voice. Which is right for you comes down to three questions: who owns the guest data, what a booked guest costs, and whether the booking connects to the rest of the business, the newsletter, the events and the kitchen. Here is how I reason, what a booking of your own actually has to do, and where Google comes in.

Three questions that decide

Who owns the guest data? Name, phone, how often the guest comes and whether they said yes to the newsletter. If it sits with you, you can use it; if it sits with a platform, the guest is the platform’s customer first.
What does a booked guest cost? A platform charges per seated guest, per month or both; your own booking costs in the build and the running and nothing per cover. Do the sum on your own bookings per month, not on a brochure.
Does the booking connect to the rest? A party booking for match night, a Christmas table booked in September, a guest who should get the reminder and then the newsletter. That is where a booking living in the same system as the site wins.

When the platform is right: Rökeriet kept theirs

Rökeriet i Åhus takes its table bookings through a booking system they have had for a long time. When I rebuilt the whole site, shop, restaurant, catering in three languages, replacing it was never on the table. The reason is written in the code as a note to myself: the floor plan and the staff rota live in that system, and the two are tied to the booking in a way a new site should not pull at. So "Boka bord" on rokeriet.se leads to their booking page, and the site tells Google that this is where you book, so the button in the search result points the right way.

That is the most common picture at an established restaurant: the booking is already part of the till system or the rota, the staff know it, and the guests find it. Then the right move is to let the site link to it and put the effort into what the site actually lacks: the menu as text, the lunch that switches day by itself, the newsletter. Platforms that are also marketplaces, where the guest finds you in their app, bring in new guests too, and that has value. The price is the relationship: that guest is theirs first, and the fee per cover follows every booking. What the platforms cost varies and changes; read their current terms rather than a figure from me.

When your own booking is right: the bar that wanted to own its guests

For a bar in Åhus I built the booking into the site instead, because there the questions were answered the other way: no platform to take into account, the members club and the newsletter were to connect to the booking, and a booking for match night or the Christmas table should sit in the same system as the event. A booking of your own looks simple on a sketch. What makes it usable are the rules, and there are more of them than you think. This is what they look like in the build:

Quarter-hour slots within opening hours, and a closing after midnight belongs to the evening before, so Saturday’s late bookings do not land on Sunday in the staff list.
The party holds the table for two hours, two and a half from seven people, and the last seating is an hour before closing. The owner changes the numbers in the panel, not me.
On the web no earlier than an hour ahead and no more than ninety days out. Ninety, not sixty: the Christmas tables had to be bookable already in September.
Up to ten people book directly, more becomes a request the staff answer. If no single table is free, two or three neighbouring tables in the same room can be joined.
Confirmation immediately, reminder the day before at ten, or three hours before if the booking was made the same day. A thank-you mail the day after exists, but is off until the owner turns it on.
The guest changes and cancels herself via the link in the mail, gets a calendar file, and a time of 00.30 is written "the night to Sunday" so that nobody turns up a day early.

Two details say more about the value than the list. The booking number is read out on the phone and shown on the till screen, so the number alone shows only day, time, party size and table; the guest’s name and the cancellation link require a key that exists only in the confirmation mail. And every booking carries whether the guest said yes to the newsletter and which event or match it belongs to. That is how the booking becomes part of the members club instead of a list in another system. Honestly, the bar chose to launch with the booking switched off; it sits ready behind a switch until the door is no longer enough.

What decides in daily life: the reminder and the cancellation

Whatever the system, two emails make the difference between a booked table and a filled one. The reminder the day before, which can be replied to and has a cancellation link without shame, and the confirmation the guest can actually find again when the party asks "what time was it?". A party that does not show up on a Friday is pure loss, and most of it is not down to bad guests but to nobody reminding them. How reminders and a waiting list work in detail I have written about for salons; the mechanics are the same for a restaurant. So check, whichever system you choose: does it send the reminder itself, can the guest cancel without calling, and can the staff see that the reminder went?

Google and the "Book a table" button

Many bookings do not start on your website but in Google, on the map or in the business profile. There are two routes there. Google’s own booking button right in the search result goes through Google’s partner platforms, so it assumes you book through one of them. If you have your own booking, you add your booking page as the booking link in the business profile instead, and the site tells Google with structured data where to book, just as Rökeriet’s site points to their platform. What matters is that every route leads to the same place: the profile, the site and the menu on the table should not offer three different ways to book.

Honest about when neither route is needed: if you run a lunch place or a neighbourhood restaurant where guests walk in through the door, and the few bookings that come are taken on the phone in a minute, then you should not pay for any booking at all, neither per cover nor in a build. A booking button fills no tables by itself; it removes the friction for the party that has already decided and sits with a phone at 10pm. And if you have a platform that works, like Rökeriet, the cheapest advice I can give is to keep it and put the money into what the site lacks. More on what a restaurant website must do is in the guide on AI for restaurants and cafés.

Checklist before deciding

Count your bookings per month and what they cost today in fees and in phone time.
Ask where the floor plan and the rota live. If they live in the booking system, that is a reason to keep it.
Ask to export the guest list. If you cannot export names, phones and last visit, you do not own it.
Require a reminder and a cancellation link in any system, and that the staff can see the reminder went.
One booking route everywhere: the same link in the Google profile, on the site and on the QR code on the table.

I build both routes: a site that links to the platform you already have and tells Google where to book, or a booking of your own built into the site with the rules above, the reminders and the guest data in your hands. The same trade-off applies to salons choosing between their own booking and a marketplace. What it costs is listed openly under services, and you can read who builds it under about me.

Frequently asked questions

Does a small restaurant need table booking on its website?
Only if the guests actually book. If you take a couple of bookings a week on the phone and the rest walk in through the door, the phone number and the opening hours, clearly at the top on a phone, are enough. If instead you get parties who want to know the table is theirs on Friday, or Christmas tables booked months ahead, a booking the guest makes herself in the evening when she decides pays off.
What does table booking through a platform cost?
It depends on the platform and the agreement: a fee per seated guest, a monthly fee or both, and the prices change. Read their current terms and do the sum on your own bookings per month. The cost that is not on the price list is the guest data: at a marketplace the guest is their customer first, and the list does not come with you if you switch.
Can I have both a platform and my own booking on the website?
Technically yes, but do not. Two booking routes give double bookings and staff who do not know which list counts. Choose one route and let the Google profile, the site and the QR code on the table lead to the same place. If you want to move from a platform to your own booking, do it on a set date and move the bookings already in the system.
How do I reduce no-show parties?
A reminder the day before that the guest can reply to, a cancellation link in the same email so it is possible to cancel without calling and feeling ashamed, and a confirmation that can be found again. For large parties and Christmas tables it is reasonable to take a request instead of a direct booking, so that you call and confirm. There is no public Swedish statistic for restaurants specifically, so trust your own numbers: count the no-shows a month before and a month after.
Can the guest cancel and change the table booking herself?
She should be able to, via a link in the confirmation email. The link should carry a key that exists only in the email, so that nobody can cancel someone else’s table by guessing a booking number. The number alone should show only day, time and party size, because it is read out on the phone and shown on the till screen.

Unsure whether to keep the platform or book yourselves?

Book a free 30-minute call. I look at how your bookings run today, do the sum on your own numbers, and tell you straight whether the platform you have is the right one to keep.

Book a free call →