Reservations and table management

How to choose a restaurant booking system

Choose a table booking system for a restaurant or pub: write requirements, compare fee models, check EPOS links, deposits and who controls guest data.

Ava research teamPublished 7 min read

On this page
  1. Start with your venue, not the vendor
  2. Write your requirements first
  3. The criteria that matter
  4. Understand the fee models
  5. Integrations: check what is live
  6. Guest data and the contract
  7. Security basics
  8. Trial it on a real service
  9. If you are switching systems
  10. Example: scoring two shortlisted systems
  11. Frequently asked questions
  12. References

Key takeaways

  • Write down your covers, channels, deposit rules and integrations before you look at any vendor.
  • Compare the total yearly cost under each fee model using your own booking mix, including any fees on bookings from consumer apps or Google.
  • Check who controls guest data, how you export it and what happens to it when you leave; the processor contract should say.
  • Run a short trial on a real service before signing, and score every shortlisted system against the same criteria.

Start with your venue, not the vendor

Booking systems are sold on features, but most venues use a fraction of them. The right choice depends on how your restaurant or pub actually trades: how many covers you take, how guests book, whether you take deposits, how complex your floor is, and how much time anyone has to manage the system.

Most operators are small. Of the 108,500 restaurant and mobile food service enterprises registered in 2026, 57,375, about 53%, had 0 to 4 employees[1]. For businesses like that, the best system is often the one that is quickest to set up, cheapest to run at their volume and easy for a part-time host to use, not the one with the longest feature list.

UK restaurant and mobile food service enterprises with 0 to 4 employeesShare of 108,500 enterprises, 2026
UK restaurant and mobile food service enterprises with 0 to 4 employeesDonut chart. 0 to 4 employees: 53%.0 to 4 employees: 53%53%
  • 0 to 4 employees 53%

Source: Office for National Statistics, 2026[1]

Show the data
ItemValue
0 to 4 employees53%

Larger and multi-site operators need different things: central reporting, guest profiles shared across sites, event and group tools and links to the EPOS and marketing systems. Knowing which group you are in narrows the field before you take a single demo.

Write your requirements first

  1. Count your covers

    Take average and peak monthly covers from your EPOS, and the share that are booked rather than walk-in. Fee models that look similar can differ a lot at your volume.

  2. Map your booking channels

    List how bookings arrive today: phone, your website, Google, Instagram, consumer booking apps, email and walk-in. Estimate the share for each.

  3. Set your deposit and card rules

    Decide when you take a deposit or card guarantee, for which party sizes and dates, and how refunds work. The system must support those rules without manual workarounds.

  4. Describe your floor

    Number of tables, which combine, any areas such as a terrace or private room, and how you turn tables across sittings.

  5. List the systems it must talk to

    EPOS, payment provider, email marketing, website and any phone assistant or call tracking you use.

  6. Name the users

    Who will use it, on which devices, and how much training time you can give a new starter.

Put this on one page. It becomes the brief you send to vendors and the scoring sheet you use at the end.

The criteria that matter

Booking system criteria, the questions to ask and the warning signs
CriterionWhat to askRed flag
Fee modelWhat do we pay each month, per booking or per cover, and on which channels?Fees that depend on where the guest found you, with no channel report
Deposits and cardsCan rules vary by party size, date and time? Who holds the money?Deposits only through a separate tool you must reconcile by hand
Table managementCan it combine tables, set turn times by party size and handle sittings?One fixed duration for every booking
Google and websiteDoes it connect to Google and embed cleanly on our site?A widget that is hard to use on a phone
EPOS linkWhich EPOS systems does it integrate with, and what data flows each way?Integration on a roadmap, not live
Guest dataWho is the controller? Can we export everything, in what format, at any time?Export only on request, or a charge for your own data
Marketing consentHow is consent captured and recorded, and can we see it per guest?Pre-ticked boxes or no record of when consent was given
ContractMinimum term, notice period, price rises and exit helpLong automatic renewals with short notice windows
SupportHours, channels, response times on a Saturday nightEmail-only support during service hours

Understand the fee models

Booking platforms charge in a few common ways, and many combine them: a fixed monthly subscription, a fee per booking above an included allowance, a fee per cover, or a fee only on bookings that come through the platform's own consumer app or network. Some charge nothing per booking but more per month, and some offer a free tier with limits.

Channel matters. Google, for example, warns that when guests book through Google, your booking provider might charge you[2]. Ask each vendor for a written fee schedule that shows the charge for every channel: your website, phone bookings entered by staff, Google and any consumer app.

Example: work out a year's cost for each shortlisted system using your own numbers, for instance 2,000 covers a month with 40% from your website, 25% by phone, 20% from Google and 15% from a consumer app. The cheapest headline price is often not the cheapest total.

Integrations: check what is live

Integrations are where booking systems differ most and where sales claims are hardest to check. Some vendors list long integration directories; ResDiary, for instance, cites more than 70 certified integrations with EPOS, CRM and PMS providers[3]. What matters is whether the integration with your EPOS is live today, what it actually does and who supports it when it breaks.

  • Ask for the name of another venue on your EPOS using the integration, and call them.
  • Ask what data flows: covers and spend back to the guest profile, table status, or just the booking.
  • Check whether the integration costs extra on either side.
  • Ask who you call when it fails on a Friday night: the booking vendor, the EPOS vendor or both.

Guest data and the contract

Your guest list is one of your most valuable assets, so be clear about who controls it. Where a booking provider processes guest data on your behalf, UK GDPR requires a contract that says the processor acts only on your documented instructions and, at your choice, deletes or returns all the personal data at the end of the service[4]. Read that part of the contract before you sign, not when you leave.

  • Can you export all guest records, booking history and consent records at any time, in a standard format such as CSV?
  • Does the platform also use guest data for its own purposes, for example marketing its consumer app? If so, the guest may have a separate relationship with the platform.
  • What happens to the data, and to your booking widget links, on the day the contract ends?
  • How are marketing opt-ins captured? Marketing emails and texts to individuals need their prior consent[5], so the system must record it properly.

Our guide to who owns guest data on booking platforms covers controller and processor roles in more depth.

Security basics

A booking system holds names, numbers, dates and sometimes card guarantees, which makes it a target. In 2025, 30% of food or hospitality businesses had identified a cyber breach or attack in the previous year[6]. Check that every user gets their own login, that roles can limit who exports data, that two-step sign-in is available and that leavers can be removed instantly. Ask where the data is hosted and whether the vendor holds recognised security certifications.

Trial it on a real service

  1. Shortlist two or three systems against your one-page brief.
  2. Ask each for a trial or a sandbox with your floor plan loaded.
  3. Have your busiest host take ten real-style bookings on a tablet during a quiet service, including a large party, a change, a cancellation and a walk-in.
  4. Test the guest side on a phone: book, change and cancel as a guest would.
  5. Check the reports you would use weekly: covers by channel, no-shows and cancellations.
  6. Score each system out of five on every criterion, weight the ones that matter most to you, and add up.

If you are switching systems

Moving from one booking system to another is where bookings get lost. Plan the switch like a small refit rather than a software update, with a date, an owner and a checklist.

  • Export every future booking, with contact details and notes, before you start, and check the count against the old system.
  • Pick a cut-over date in a quiet week, well away from December, Mother's Day and Valentine's Day.
  • Run both systems side by side for a few days, with one named person keeping them in step.
  • Update every booking link on the same day: website, Google, social bios, email signatures and the voicemail greeting.
  • Contact guests with future bookings only if their change or cancel link will stop working, and tell them what to expect.
  • Keep read-only access to the old system for a few months, for disputes and visit history.

Ask the new vendor what help it gives with migration and whether it can import future bookings and guest profiles directly. A vendor that leaves you to retype bookings by hand is telling you something about the support you will get later.

Example: scoring two shortlisted systems

Example: a fictional 80-cover neighbourhood restaurant shortlisted System A and System B. It weighted fees, deposits and ease of use at three times, guest data and EPOS link at twice, and everything else at once. System A scored higher on features but charged on every Google booking, which made up a fifth of the restaurant's covers. System B had a simpler table plan but included Google bookings in its monthly fee, offered a full CSV export and had a live link to the restaurant's EPOS.

Example: on the weighted sheet, System B won by a clear margin, mostly on cost at the restaurant's real booking mix and on data control. The owner signed a one-year term with a 60-day notice period and diarised the renewal date. For more detail on specific platforms, see our comparisons of ResDiary, OpenTable and SevenRooms and of tools built for bars and pubs, and our look at free and paid systems.

Frequently asked questions

What is the most important thing to check in a booking system?

The total cost at your real booking mix and who controls the guest data. Features matter, but these two decide whether the system still suits you in two years.

Do we need a booking system that links to our EPOS?

It helps if you want spend and visit history on guest profiles, or table status shared with the till. Many small venues manage well without it. If you do need it, confirm the integration is live for your EPOS today.

Should we take deposits through the booking system?

If you take deposits at all, it is simpler when the booking system handles them, so refunds and no-show charges follow your rules automatically and staff never handle card numbers.

How long should a booking system contract be?

Shorter is safer until you know the system works for you. Look for a reasonable notice period, clear terms on price rises and a guaranteed export of your data on exit.

References

  1. Office for National Statistics (2026). UK business: activity, size and location, 2026 (workbook) (opens in a new tab) ↑

  2. Google Business Profile Help (2026). Set up bookings through a provider (opens in a new tab) ↑

  3. ResDiary (2026). ResDiary: Restaurant Booking System (opens in a new tab) ↑

  4. legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 28: Processor (opens in a new tab) ↑

  5. legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22 (opens in a new tab) ↑

  6. Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo