Reservations are placed on your restaurant’s floor plan, table by table, so the host sees who is booked where.
In short: a reservation written on a notepad is easy to lose or misread during a busy service. 4restaurants.net keeps reservations on the restaurant’s floor plan: each booking sits on its table, with the time and the party size, so the host sees at a glance what is booked and when. The reservations sit in the same platform as the digital menu and the table orders.
A paper diary tells you that four people are coming at 8pm, but not which table to set for them. 4restaurants.net places every booking on your floor plan, on the table the host chooses, with its date, time and party size. The plan follows the real layout of the room, so the host sees which tables are booked for each service.
Each booking carries its party size, its time and the table it is placed on, so the host can see at a glance which table a group is booked on. The host chooses the table, so the decision about who sits where stays with the team. The day’s list is built from the same records, and bookings for future dates stay on the same floor plan.
Each booking occupies its table for a time slot, so the floor plan shows which table is free and which is booked at a given hour. The team sees from one record who is coming, how many people and when the table frees up.
A large party is placed on the floor plan with its party size, date and time, like any other booking, so the host finds it on the floor plan and on the day’s list.
The restaurant’s team does. The host records each reservation on the hall map, with its date, time, party size and table, and it appears on the day’s list.
Yes. The floor plan shows which table is booked and for which time slot, based on the reservations recorded in the platform.
Yes. The floor plan follows the layout of your restaurant, with each table in its place. Bookings are placed on those tables, and the host sees which ones are booked for each service.
Yes. The host sees the day’s bookings in one list, with the time and party size of each, next to the hall map.
A large party is placed on the floor plan like any other booking, with its date, time and party size.
Yes. Bookings for future dates are kept in the platform, on the same floor plan as those of the current day.
Tell us the layout of your room and we will set up the floor plan with your tables.
4restaurants.net places each reservation on the real floor plan, with the party size and time for every table.
We are transparent — here is where 4restaurants.net is not (yet) the best fit:
A fit for restaurants that want bookings kept on a floor plan rather than in a diary, and that want group bookings in one place. If the venue does not take reservations, the module is mainly useful for the floor plan itself.
| Feature | Limit / scope | Availability |
|---|---|---|
| Table reservations & floor management | Reservations on the floor plan, with table, party size and time | available |
| Digital menu, recipes & food cost | QR menu, portion weights, food cost per dish | available |
| Table orders | Orders taken at the table and sent to the kitchen | available |
| Ingredient stock | Ingredient stock levels, in the same platform as the recipes | available |
| Goods receipt & HACCP | NIR for goods received, HACCP logs, allergens declared per dish | available |
| Table bill & sales reports | Non-fiscal table bill (the fiscal receipt stays on your own cash register), reports by day, dish and waiter | available |
4restaurants.net brings into a single platform table reservations on the floor plan, the digital menu with recipes and food cost, table orders sent to the kitchen, ingredient stock levels and sales reports.
The reservation is entered in the platform, on the table where the party sits, with the party size and time. It appears on the floor plan.
From the recipe. You enter the ingredients with portion weights, and the platform calculates the production cost (food cost) of the dish from the ingredients and quantities in the recipe.
Yes. The server enters it at the table, and the order reaches the kitchen from the platform, with its items and the table it came from.
No. The platform is used alongside the restaurant’s own cash register: it gives a non-fiscal table bill, and the fiscal receipt stays on the cash register.
Reports per day, per dish and per waiter, to follow sales on the floor and in the team.
Yes, 4restaurants.net is part of the 4b2b ecosystem but works as a standalone product; other ecosystem products, such as 4invoices or 4notify, are separate.
