Every booking is attached to a real table on your floor plan, so the host can check which tables are free at any hour, room by room.
In short: a name written in a notebook does not say where the guests will sit. 4restaurants.net puts each booking on its own table, together with the time and the party size. The floor plan mirrors the actual layout of your venue, which lets the host see which table every booking uses and which ones remain free, and plan the service before the first guest walks in. A dining room, a terrace or a bar is each a zone with its own tables, and the bookings live in the same application as your menu and table orders.
A notebook says four guests arrive at 8pm, but not which table to lay. 4restaurants.net draws your room as a floor plan with numbered tables. The host assigns each booking to a table with its time and party size, and the team sees at a glance what is taken and what is open for the next sitting.
A booking holds its party size, its time and its table together. The host can notice a table for two standing empty while a group of six waits, and move the next booking to a table that fits. Seating choices remain with your staff; the application keeps the record accurate.
If you run a dining room, a terrace and a bar, each can be its own zone with its own tables. A terrace booking goes on a terrace table rather than a dining-room one. Time and party size show on the same record in every area.
A group of twelve sits at one table, so give it the largest table in the room along with its party size and time. The host then sees how much of the room the evening uses. Your team decides how to seat the group, and the plan shows what stays free and when.
Enter the date, time and party size, then pick the table on the floor plan. The booking appears on that table for the time you chose, so the host sees it immediately.
Text messages to guests are optional. You switch them on in Settings, your plan must include SMS, and you connect your own 4notify account. They cover booking confirmations, an optional reminder and cancellations. The platform sends no e-mail and no WhatsApp messages. If you leave them off, your team confirms bookings the way it does today and the booking stays on the floor plan.
Yes. The floor plan lists the status and the bookings of every table, so the host can check that a table is free before seating the next party.
Yes. Every room or terrace is its own area of the floor plan with numbered tables, and each booking goes onto the right one.
A large party is entered like any other booking, with its party size and time. A booking uses one table, so the host picks a table that seats the whole group.
Yes. Future bookings live on the same floor plan as today's, so you can plan the services of the coming week.
Draw the floor plan, number the tables as they appear in the room and add your first bookings. Your team then reads the day's tables at a glance.
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 with allergens and sold-out dishes, recipe book, food cost per portion | 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 QR digital menu, the recipe book with 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 their quantities per batch and the number of portions, and the platform calculates the production cost (food cost) per portion.
The server enters it at the table and sends it to 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.
