Table Booking

5.0 out of 58 sold

Reservations by covers and turn time rather than party size and hope. A floor the front of house can actually work during service, and a book you own.

From$849

Open the preview Request a quote

Function: 23
User types: 3
Platform: iOS & Android

React Native
TypeScript
PostgreSQL
Expo

Inside the app

What it does out of the box

23 connected functions on one schema across 3 user types. Everything below is in the template before a line of customisation.

Book
Availability by covers and turn time, so a two-top at 19:00 and a six-top at 19:00 are different questions with different answers.
Waitlist
With a real callback rather than a form. A waitlist nobody works is a way of losing a guest politely.
Floor
Tables, seated times and turns due, readable at a glance mid-service. Seat, turn and clear in one tap.
Walk-ins
Taken against genuine remaining capacity, so the 20:00 booking still has its table when it arrives.
The book
The week ahead by service, so you know on Monday whether Friday needs work.
Covers and no-shows
Forecast covers and the no-show pattern per guest, which is the basis for a deposit policy that is fair rather than blanket.

User types

Three apps, one book.

Booking a table, working a service and running a restaurant are three different jobs at three different speeds. The floor view in particular is built to be read in two seconds while carrying something.

Customer
2 of 5 screens
The guest
Books a table for a real time that exists, joins a waitlist that actually calls back, and can change it without ringing during service.
Preview as the customer
- Availability by covers, not a request form
- Join a waitlist with a real callback
- Note allergies and occasions at booking
- Change or cancel inside your window
- A reminder the day before
Restaurant owner
2 of 5 screens
The operator
Sets the floor plan, turn times and booking rules, and sees the covers, no-show rate and how full the book is before the week starts.
Preview as the restaurant owner
- Tables, capacity and turn times you set
- Booking windows and deposit rules
- Covers forecast for the week ahead
- No-show pattern by guest
- Every guest record stays yours
Restaurant staff
1 of 5 screens
The floor
Works the book during service: seat, hold, turn, and take a walk-in without losing the table that is due at eight.
Preview as the restaurant staff
- The floor at a glance, mid-service
- Seat, turn and clear in one tap
- Walk-ins against real remaining capacity
- Waitlist with callback order
- Allergies and notes surfaced on seating

The limits

What this is not.

The same list we give for every app in the catalogue, because the fastest way to a bad project is a promise made in a meeting that nobody wrote down.

It carries no diners
A booking platform charges partly because it generates covers. This serves the guests you already reach.
We do not process payments
Deposits run through your own provider account, which is what keeps the per-cover fee at zero.
It is not a POS
It books and seats. Bills, items and payments belong to your till, and connecting the two is a fitted-build integration.
Turn times are your estimate
The app enforces what you set. Nobody can tell you how long your six-tops actually take, only your service can.

Questions

Questions, answered plainly.

If yours is not here, ask it on the call rather than guessing from a pricing page.

Not covered here?

Ask a consultant directly. No form to fill in first, and no follow-up sequence.

Book a consultant All questions

How is this different from a booking platform?

Mostly the economics and the ownership. A platform charges per cover and keeps the guest record; this charges once and the book is yours. What a platform genuinely gives you is discovery, and this does not.

Does it handle walk-ins?

Yes, and properly: a walk-in is taken against real remaining capacity so it cannot eat the table due at eight. That is the part most simple booking tools get wrong.

Can we take deposits on large parties?

Yes, by party size or service, with the rule shown to the guest before they agree to it. Collection runs through your own payment provider.

Does it work offline during service?

The floor view holds the current service on the device and syncs afterwards. Losing the wifi mid-service should not lose the book.

Do I get the source code?

Yes. All three apps, API, schema, migrations and deployment configuration transfer on delivery. No licence key, nothing that calls home.