From an empty account to bookings, in four steps
Setup is guided and reversible. Nothing goes live to guests until the location can genuinely deliver the times it is offering.
Sections and tables defined
Opening periods and turn times set
Party sizes and table capacity checked
Published and accepting bookings
Getting a location live
Create the organisation and first location
Guided onboarding creates your organisation, its first property and a location in one step, with its timezone and restaurant settings established from the start.
Describe the space
Add sections and tables with capacities and a layout that matches the real dining room. Block anything that is out of service.
Set service hours and booking rules
Define opening periods, booking duration, lead time, party-size limits and the rules that control which tables can be offered.
Publish the booking page
Choose a layout, set your colours and hero image, then link to the hosted page or embed the widget on your own site.
What a guest actually experiences
The public journey is short by design, and every step is validated against live availability rather than a static calendar.
- Lands on your branded page from your site, a link or a QR code
- Chooses a party size, then a date and a real available time
- Enters their details, passes an invisible bot check and confirms
- Receives a confirmation, then a reminder before arrival
- Can cancel or reschedule from a signed self-service link
- After the visit, is invited to rate the experience
Adults and children in the reservation
Closed days and blocked dates removed
Only times a suitable table is available
Name, email, phone and requests
What the team does each day
The staff app is designed around a shift, not a settings screen.
Open on today
Arrivals in order, current status per space, covers still to come, and completed visits kept visible until the end of the day.
Change things quickly
Create, move, seat and complete bookings in a couple of clicks, log walk-ins, and manage the waitlist with quoted times.
Communicate without leaving
Send or resend confirmations, see exactly which emails a guest received, and let guests handle their own changes.
Things that stop the day going wrong
Readiness checks
A location cannot publish a booking page it cannot honour; missing setup is named explicitly.
Conflict guards
Double-bookings and bookings on blocked dates are refused at the database level, not just in the UI.
Unsaved-edit protection
Background refreshes never overwrite something a staff member is halfway through typing.
Scoped access
People only see the locations they work in, and changes are recorded in the audit log.
Practical questions
How long does setup take?
A single restaurant with its sections, tables and opening hours can usually be live the same afternoon.
Can we run several venues from one account?
Yes. Organisations contain properties, which contain locations. Settings cascade downward and each location can override what differs.
Do we have to replace our website?
No. Keep your site and embed the widget, or link to the hosted booking page for each location.
Can each restaurant keep different booking rules?
Yes. Group defaults can cascade to each restaurant, while an individual location can override its hours, capacity and guest-booking settings.
See PlateStack running in your restaurant
We set up a working restaurant with your tables, service hours and booking rules, then walk the guest journey end to end with you.