A reservation is not a separate agenda next to the service. Time, party size, and table belong to the same order.
ALLRECA keeps reservations in the restaurant environment. The host sees who is coming, which table is free and what is already running. The online widget writes to the same environment; the reservation stays alongside the table and the service.
Illustrative host display. No current reservations or guest data.
The host does not work from an export or a paper list. The reservation, the table status and the running order sit side by side. That way the question "is this table free?" is not something someone has to look up separately.
The host flow rechecks availability at the moment of booking. A reserved table is not blindly assigned.
See how table status and reservations come togetherTijd, gezelschap, notitie en tafelvoorkeur staan bij elkaar. De host ziet wat vandaag verwacht wordt.
The host opens the reservation and sees the available tables in the business. A walk-in can go on the waitlist.
The chosen table is linked to the reservation. The table status goes into the service with it.
Order, table and reservation stay linked. After departure the table becomes available again.
The guest sees a widget. The host sees the arrival. The manager sees the overview and the trend. All three refer to the same reservation.
List and detail with date, time, party size, status and table. Filter by status or date; view the reservation without losing the context of the business. The trend view shows demand per period.
Date · time · party size · status · table
Expected arrivals, free tables, seats, no-shows and waitlist. The host sees the dining room as it is at that moment.
Arrival · seating · no-show · waitlist
A widget on your own website with availability, party size and optionally a deposit. Settings determine the window, duration, party size and deposit rules.
Widget · availability · deposit · window
The reservation does not live alongside the rest of the business. It determines which table must remain free, which guest is seated and which order starts next.
Tables, zones, and statuses are in the same room. The host sees the reservation reflected in the floor plan.
To Table LayoutOnce the guest is seated, ordering at the table can begin. The reservation remains the context of the table.
To Mobile OrderingTables, zones, and opening hours are the basis for availability. The host sees them in the same venue.
To Restaurant ManagementThe reservation list determines the expected busyness. The host keeps tables free and service knows which guests are coming.
Reservations and the waiting list sit side by side. A free table is visible before the next guest arrives.
The host chooses the zone that fits at that moment. The reservation stays linked to the chosen table, not to a loose list.
The business environment contains its own integration screen for the website. There you create an embed code that is pasted once into WordPress, Shopify, Wix, Webflow or another site — no plugin needed. The button is configurable: text or icon, position, size, colour and corner radius.
ALLRECA checks availability against the tables and existing reservations of that location. A change to the button takes effect immediately; the embed code stays the same. With the availability check you can check a date and party size without a booking being created.
The guest stays on your domain and books there. The reservation then appears in the same overview as walk-ins and phone bookings — not in a separate calendar or a standalone booking system.
Embed code · button style · live preview · availability test
See how Website & Design manages the digital presentationIn the business environment, the reservations overview shows date, party size, table, payment status and source. The source column shows whether a booking came in via the website widget, an account or another channel.
The status filters cover the entire lifecycle: pending, awaiting payment, confirmed, seated, completed, no-show and cancelled. The trend view shows demand per period; the host flow remains the place where the guest is seated.
Overview · source · status · trend
Every reservation has its own detail: guest, party size, time, table or zone and the status. The host sees here whether a booking is confirmed, on the waitlist or converted.
The same reservation can be found in the schedule, on the table in the floor plan and in the reporting. There is no separate “reservation admin” that gets out of sync.
Reservation · guest · table · status
Reservations belong to the restaurant environment. This page describes the components that exist today: the overview, the host flow, the widget, the settings and the trends.
Tijdens een walkthrough kijken we hoe reserveringen, host en tafelstatus nu naast elkaar werken — en waar de eerste winst zit.