Place each reservation on your restaurant’s floor plan, table by table, so the host sees who is booked where and the team works from the same records as the orders.
In short: a booking written in a notebook does not tell you where to seat people. 4restaurants.net places each reservation 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 front of house can see at a glance which tables are booked for each service. Reservations sit in the same application as the digital menu and the table orders, so hosts, servers and the kitchen work from one set of records.
A paper diary tells you four people are coming at 8 pm, but not which table to set for them. 4restaurants.net shows your room as a floor plan, with every table numbered, and places each booking on the table the host chooses. The plan shows which tables are reserved for each time slot, so seating decisions are made from the room itself, not from memory.
Each booking carries its party size, its time and its table. The host decides who sits where, and the application keeps the record. The day’s list is built from the same records, so the floor plan and the list always agree. Bookings for future dates stay on the same plan.
Restaurants with a terrace or a bar area can divide the plan into rooms. Each room shows its own tables, with the same booking records behind them. A host can plan a busy patio evening without mixing it up with the dining room, and a café with a patio can run it the same way.
A party of eight or a birthday is placed on the same floor plan as any other booking, with its size and time visible. The host can see at a glance whether the room has the tables to take it, and the arrangement stays on the booking record for the team to read.
Your team does. The host records each reservation on the floor plan, with its date, time, party size and table, and it appears on the day’s list.
Yes. The plan follows the layout of your restaurant, with each table in its place, so 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 floor plan.
Yes. Tables can be grouped by room, and each room shows its own tables and bookings on the same plan.
Yes. Bookings for future dates are kept in the application, on the same floor plan as those of the current day.
A reservation sits on a table, and orders taken at that table are recorded against the same table, so the host and the servers see the same picture.
Send us the layout of your room, and we will help you set up the floor plan, the table numbers and any rooms or zones.
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.
