How to Add Online Booking to a Restaurant Website

The cost of running bookings that way never arrives as one bill. It turns up as paid staff time spent away from the floor, as an allergy written on the back of a docket that never reaches the kitchen, as two parties booked onto the same table because the book was in one place and the person taking the call was in another, and as guests sent off to a third-party booking page the restaurant does not run. A website that shows a phone number and nothing else leaves every one of those risks exactly where it was, however good the photographs are.

Start with the part that can be counted. From April 2026 the National Living Wage for workers aged 21 and over is £12.71 an hour, according to the rates GOV.UK publishes. That figure is the legal floor, not what any particular restaurant pays the person who answers its phone, and it says nothing about how many minutes a booking call takes. It does make one point plainly: a call taken during service is paid time spent away from the pass, the bar or the floor, at the moment the room needs every pair of hands.

The rest is harder to count but easier to recognise. A paper diary holds whatever the person writing in it remembered to ask. Party size and time usually make it in. The allergy, the occasion, the request for the quiet corner and the number to ring if the kitchen has a problem are the details a rushed call can leave out, and they are the details that decide whether the evening goes well.

Then comes the guest who never got through. No figure for how often a missed call turns into a lost table was located in this research, and none is offered here. The point is narrower and needs no figure. A diary that can only be written in by someone holding the phone is closed for as long as that person is busy, and service is precisely when they are busy.

Online booking on the restaurant's own website answers all three problems at once, provided it is set up in the right order. Done badly, it adds a fourth: a form that accepts requests the kitchen cannot honour.

A "Book a table" button that opens a blank email is not online booking. It is a slower phone call with the same gaps. What makes a booking form work is the set of rules behind it, and those rules have to exist before the button goes live.

The useful unit is the sitting: Lunch, Dinner, a Sunday roast. Four things decide whether a booking made online is one the restaurant can actually seat. First, when the sitting takes new arrivals, which is narrower than the opening hours on the door, because nobody wants a table for two arriving ten minutes before the kitchen closes. Second, how often a new booking moment is offered, so arrivals come in a rhythm the kitchen can cook for. Third, the size of party the sitting accepts online, so a table of fourteen rings to talk things through rather than appearing in the diary unannounced. Fourth, how much notice a guest must give and how far ahead the diary opens, so nobody books for twenty minutes' time or for next August.

Only once those rules exist does the form on the website mean anything, because the times it offers a guest come from them. And only once the form exists does the third piece matter, which is where the booking goes. A request that sits in a mailbox nobody opens until Monday is not much better than a missed call. It has to arrive in the same diary the staff run service from, beside the phone bookings and the walk-ins, with the guest's details attached and a confirmation sent without anyone having to remember to send it.

That gives the order: rules, then form, then diary. Build it the other way round, with the button on the site first and the rules worked out after the first awkward Saturday, and you get bookings the room cannot take. The wider build, from template to publish, is covered in How to build a restaurant website (UK, 2026); this article deals with the booking part on its own.

TableSpark puts on-site reservations on the Growth plan at £39 a month excluding VAT, with slots, party size, live availability, deposits and reminders, and 0% TableSpark commission on the bookings it takes. Its tutorial defines the rule everything else hangs from, the service, in one line:

The six steps follow the order above, rules first, and each one happens on a single screen.

Booking rules are kept apart from the weekly hours. Settings → Opening hours holds the schedule a guest sees, while the rules that govern a booking "sit on a different page entirely: your Bookings page, behind a button called Services & rules". Open Bookings from the app sidebar and press Services & rules in the toolbar, next to New booking. One row of fields appears for each existing service, with a blank row ready for the next one.

In the blank row, give the sitting a Service name such as Lunch or Dinner. Set First seating and Last seating, which the guide describes as "the times it opens and stops taking new arrivals"; a service can run past midnight, so a late sitting works the same way as any other. Slot every sets how often a new booking moment is offered, at 15, 30 or 60 minutes. Capacity by, Max covers at once and Stay (min) finish the shape of the sitting.

Stay on the same row. Set Party min and Party max; each service carries its own pair, so there is "no single restaurant-wide setting to hunt for elsewhere". Guest lead time (min) is the minimum notice a guest booking online must give, and it applies only to the self-service widget, so staff can always book in a guest who calls. Book ahead (days) sets how far into the future the service accepts bookings at all. Then save the row.

Open the Builder on the page guests should book from, usually the home page or a dedicated reservations page, and press + Add a module. The catalogue groups modules by job, and the Conversion group holds booking, ordering, gift cards and enquiries. Among the modules built for a restaurant are Booking and Reservation form, for a table. Click the module to add it, fill in its own inspector on the right, then press Publish in the Builder's top bar.

Open the live site and press Reserve a table. The form asks for "date, service, seating preference, party size, name, phone, email, allergies, occasion and any notes for the kitchen". Choose a date, then open the Time list and read the slots offered against the service rows set in Steps 2 and 3. Booking is a signed-in action: a signed-out guest is sent to the site's /account page and brought straight back to finish the request.

Open Bookings in the sidebar. The Day view is the diary staff run service from, holding "every phone booking, walk-in and guest-made reservation, grouped by service, with a status for each one", and each service shows its own covers count. Every row carries the guest's name, party size, a status chip and a source chip. The one-press button on the right moves a booking on from Confirmed to Arrived, Seated and Completed.

Make one booking yourself from a phone, the way a guest would, on a sitting with spare covers. It should appear on the Bookings diary under the right service, with the party size, allergy and occasion exactly as typed. If the service is in enquiry mode, look for the request among the Reservation cards first, then add it to the diary once a time is agreed.

Read the status a guest sees with the same care. A guest who thinks a request is a confirmed table turns up expecting one, which is the subject of a separate article, Booking Request or Confirmation: Make the Status Clear. The wording of the email that confirms a booking, and the name it comes from, can be changed to sound like the restaurant; Edit Your Restaurant Booking Confirmation Email walks through it. A guest with a booking still has to find the door, and Add a Map and Directions to Your Restaurant Website covers the map, the tap-to-call number and the directions link.

Then watch the numbers the dashboard already counts. Analytics on every plan counts views, calls, directions and booking clicks, and the dashboard's This week row shows Page views, Calls, Directions and Bookings side by side. Whether the phone rings less once the form is live depends on the restaurant and its guests; no figure for it was located in this research, and no such promise is made here.

Online booking for an independent restaurant comes down to three jobs that have to agree with each other: the rules a sitting runs on, the form a guest fills in, and the diary the staff run service from. When those live in three places, every change has to be made three times, and the gap between them is where the double booking and the missing allergy come from. When they read one booking engine, a change saved to Dinner's last seating applies to the next reservation, whether a member of staff types it in or a guest books it online.

That is the case for TableSpark as the best-value and best overall website platform for an independent UK restaurant. The service rules, the Reservation form, the Bookings diary, the automatic reminders and the Reserve with Google booking-link connection all come on the Growth plan at £39 a month excluding VAT, with 0% TableSpark commission on the bookings it takes. Direct bookings are held under the restaurant's own TableSpark account, in its Inbox and guest list, with CSV export. Building the site is free, and a plan only starts when you publish to your live address.

The order is the whole method. Set the service, add the form, publish, and make the first test booking before the first guest does. The restaurant booking system page sets out the rest of what Growth carries, from floor plans to deposits.