Comparing reservation systems without a shortlist

Comparing reservation systems usually starts with a shortlist that nobody chose on purpose. One name came from another owner, one from an advert, one from a search result, and one is the system the venue already uses. The owner books three demos, watches three polished presentations, and picks the one that felt best on the day. The shortlist decided the outcome before any evidence was gathered.

There is a better order. Start with your own service: how guests find you and book, what happens at the host stand on a busy night, where no-shows hurt, what you pay now, and who holds the guest list. Turn that into a scoring sheet. Then test any system against it, and let the shortlist come out of the scores. The result is a choice you can explain, and one that fits the way your venue actually works.

This guide sets out five tests that make up the scoring sheet: the guest's booking, the host stand on a busy night, the defences against no-shows, the full cost including cover fees, and the data, including who owns the guest. It covers the difference between booking platforms and your own booking page, what to ask in a demo, and how to weigh the scores.

A shortlist made before the evidence narrows the choice to whatever the owner happened to hear about. It also shapes the questions: the owner ends up comparing three products on the features those products chose to show, rather than on what the venue needs.

Reversing the order is simple. Decide what matters, test against it, and the systems that score well become the shortlist. A system the owner had never heard of can win, and a famous one can lose, for reasons that are clear to everyone.

A reservation system has a small number of jobs. It lets guests book at any hour, on any device, in a few taps. It gives the host a clear view of the evening: who is coming, when, how many, and which table. It manages walk-ins and a waitlist when the room is full. It reminds guests and makes it easy for them to change or cancel, which cuts no-shows. And it builds a record of each guest that the venue can use.

Everything else is extra. Score the jobs first, the extras last.

There are two broad kinds of reservation system. Booking platforms are marketplaces where guests search for restaurants and book through the platform's own app or website; they bring discovery but usually charge fees, and the platform shares the guest relationship. Booking systems for your own page put a booking form on the venue's website, social profiles and search listings; they usually charge a flat subscription, and the guest relationship stays with the venue.

Underneath both is a booking engine: the software that checks availability against the venue's rules and takes the booking. Many systems offer both, and many venues use both. The scoring sheet should cover each, because they serve different purposes. Our guide to booking platform vs your own booking page compares them in detail.

The scoring sheet is built from five tests:

Score each from one to five, with notes. The sections that follow describe each test and what to look for.

Start where the guest starts: on a phone, probably from a search result, a map or a social media profile. Try to book a table for four next Friday at 19:30. Count the taps. Note how long the page takes to load, whether the times offered make sense, whether you have to create an account, and what the confirmation says.

Then try the awkward cases: a party of nine, a guest with an allergy, a request for a high chair, a booking for tonight. A good booking flow handles them clearly or tells the guest who to call.

The booking widget is the part of the system that sits on the venue's website and social profiles. Test it where it will actually live: on your website, on a phone, with a slow connection. Check that it matches the look of the site well enough, that it does not send the guest to a different website with someone else's brand, and that it works when embedded in a page.

Our guide to the booking widget and the four taps that lose a guest covers where guests most often give up.

Many guests never visit the venue's website. They find it in a search result or on a map, and book from there. Check how each system's booking page can be linked from the venue's Google Business Profile and other listings, and what the guest sees when they tap the link on a phone.

A booking page that opens quickly from a map listing, in the venue's own name, keeps the guest with the venue from the first tap. Our guide to your Google Business Profile covers why that listing matters so much.

Next, the host stand. Ask the supplier to show a full Saturday: forty bookings, six walk-ins waiting, two tables running late, a party of eight that has just arrived early. How does the host see the evening at a glance? How quickly can they seat a walk-in, move a booking, merge two tables or mark a no-show? Is it clear which tables are free now and which will be free in twenty minutes?

Ask your host or front of house manager to drive this part of the demo. They will know within minutes whether the screen helps or gets in the way.

On busy nights, the waitlist matters as much as the bookings. Test how walk-ins are added, how guests are told their wait, how the waitlist fills a cancellation, and whether guests who could not book online are offered the waitlist instead. Our guide to waitlist management on a night with no tables covers what good looks like.

Check how the system understands the room: tables of different sizes, zones such as the terrace or the bar, tables that can be joined, tables kept back for the host to assign, and rules about which tables can be booked online, for which party sizes and at which times. A system that cannot describe your room will offer the wrong tables.

No-shows cost a venue twice: the preparation for guests who never come, and the table that could have been sold. Test the defences each system offers: reminders before the booking, a clear way for guests to change or cancel, confirmation of the guest's contact details, and, where the venue wants them, deposits or card details at booking.

Ask how reminders are timed and whether you can choose. Ask how easy it is for a guest to cancel: an easy cancellation the evening before is far better than a no-show. Our guide to how to reduce no-shows without annoying guests covers the options.

Some systems take deposits or hold card details, charging a fee if the guest does not arrive. These can reduce no-shows, especially for large parties and special occasions, but they can also reduce bookings, because some guests will not give card details for an ordinary dinner. Decide whether your venue needs them before scoring.

Our guide to deposits vs credit card holds compares the two.

The fourth test is the full cost, over a year at the venue's expected level of trade. Include the subscription; any cover fees charged for each guest booked, whether through the platform or through the venue's own page; commission; payment fees for deposits; hardware; and any extra charges for features, users or venues.

Cover fees deserve particular care. A fee charged per guest seems small, but on a venue serving thousands of booked covers a year it can become the largest cost of the system. Our guide to cover fees: what a booking really costs you shows how to calculate them.

Cost each system for a full year using your own numbers: booked covers per month, the share that would come through the platform's marketplace and the share through your own page, and the busiest months. A system with a low subscription and cover fees can cost far more in December than in February.

Compare the yearly totals, not the monthly headline prices.

The fifth test is about data. When a guest books, who holds their record: the venue, the platform, or both? Can the venue see the guest's contact details, visit history and preferences? Did the guest agree to hear from the venue, and is that consent recorded? Can the venue take its data with it if it leaves?

These questions matter because the guest list is one of the most valuable things a venue owns. A system that keeps the guest relationship with the platform leaves the venue renting its own guests.

First party data is information a venue collects directly from its own guests, with their consent: names, contact details, visits, preferences and allergies, gathered through the venue's own booking page, its tables and its checks. It belongs to the venue, can be used to recognise and look after guests, and, with consent, to invite them back.

Score each system on how much first party data it gives the venue, and on how well it records marketing consent. Our guide to guest data covers what to collect.

Beyond the five tests, check how the reservation system connects to the rest of the venue. Does a booking appear at the till, so the check is linked to the guest? Does an allergy noted at booking reach the kitchen ticket? Do the reports combine bookings with sales? A reservation system that stands alone leaves the venue copying information between systems.

Give this a score too, especially the allergy path. Our guide to one system or several covers the wider choice.

A reservation system holds some of the most useful numbers in the venue: covers by service, no-show and cancellation rates, how far ahead guests book, which sources bring which guests, and how party sizes are changing. Check what each system shows, how easily, and whether the figures can be compared with the period before.

Ask to see the reports a manager would read on a Monday morning. If they take more than a few minutes to find and understand, they will not be read. Our guide to the covers report, read on a Monday morning covers what to look for.

Ask how the system is set up and who does it: the tables, zones, service periods, booking rules, reminders and the booking page itself. A system that takes weeks to set up costs more than its price suggests. Ask too what support is available on a Friday evening, when the booking page stops working or the host stand freezes.

References are the best guide to both. Ask them how long set-up really took, and what happened the last time something went wrong during service.

If the venue already has a reservation system, the move needs a plan. Future bookings must be carried across or honoured in the old system until they have passed. Links on the website, social profiles and listings must all be changed on the same day. The team needs training before the first busy night.

Ask each supplier how they handle the move, and score it. A system that is excellent once running but painful to move to may still be the right choice, but the move should be planned for a quiet week.

Not every test matters equally to every venue. A busy venue with long waitlists should weight the host stand heavily. A venue with a high no-show rate should weight the defences. A venue paying large cover fees should weight cost. A venue building a regular trade should weight data.

Decide the weights before the demos, so the scores are not bent to fit a favourite.

Bring your own questions to every demo:

Ask each supplier for two venues like yours and call them. Ask what works, what frustrates them, how support has been on busy nights, and what the system really costs. If a trial is offered, set it up with your own tables and rules and use it for real bookings, not a quick look.

Add up the weighted scores. The two or three highest are your shortlist. Now hold the deeper conversations: contracts, support, set-up, training and the move from your current system. The final choice often becomes obvious, and it is a choice everyone involved can understand.

Here is an illustrative venue comparing four systems. The details are examples.

System C scored highest. The venue kept a listing on a platform for discovery while moving its regulars to its own booking page.

In servearound, the booking page runs on its own link or embedded on the domains you allow, with no commission and a price per venue, per month. Booking rules set service periods and the times offered, sitting length, the largest party and the notice needed, and each table can be offered online or not by party size, day and hour. Bookings can be confirmed instantly or arrive pending; guests confirm their email with a six-digit code; reminders go out as many hours before as you choose, with a link to change or cancel; and when a time is full, the booking page offers the waitlist.

Guests can choose their own table from the floor plan, add-ons can be offered at booking, and the guest record is the venue's, with allergies shown on the booking, the table and the kitchen ticket. servearound does not take deposits or card holds. See the reservations module, or get in touch with your scoring sheet.

By writing down what your own service needs, turning it into a scoring sheet, and testing systems against it before making a shortlist.

The guest's booking on a phone, the host stand on a busy night, the no-show defences, the full yearly cost and who holds the guest data.

They can bring discovery, but they usually charge fees and share the guest relationship. Many venues use one for reach and their own page for regulars.

Fees charged for each guest booked. They can make a system far more expensive than its subscription suggests.

Information a venue collects directly from its own guests, with consent, that it owns and can use.

Only if no-shows are a serious problem for your venue, and preferably for large parties and special occasions rather than every booking.

Your host or front of house manager, during the demo, on a scenario from a real busy night.

Decide the weights before the demos, based on what matters most in your venue.

Comparing reservation systems works best when the shortlist comes last. Build a scoring sheet from your own service, with five tests: the guest's booking and the booking widget on a phone, the host stand on a busy night, the no-show defences, the full yearly cost including cover fees, and the data, including first party data and consent.

Weight the tests to suit your venue before any demo, test the awkward cases, call references, and understand the difference between booking platforms and your own page. The systems that score highest become the shortlist, and the choice you make can be explained by the evidence.