Your team takes the order at the table and, once it is sent from the same application, it reaches the kitchen tied to the table it came from.
In short: each walk to a till to key in an order pulls a server away from the tables, and a handwritten ticket can always be misread. 4restaurants.net lets the team take the order at the table. Dishes are chosen from the menu, and the order goes to the kitchen when the server sends it, together with its table. Staff clock in and out for each shift, and reports by day, by dish and by waiter show how the service went. Orders live in the same application as your bookings and stock levels.
On a busy night, a server who leaves the floor to type up a pad of notes spends time that belongs to the guests, and each trip risks a typing slip. With 4restaurants.net the team takes the order at the table: dishes come from the menu, and the order reaches the kitchen once the server sends it. The server stays with the guests and every order stays tied to its table.
When the server sends an order, the kitchen receives the dishes and quantities for that table. Orders from other tables are kept apart, each under its own table, so the kitchen can tell what belongs where.
After a service you want to know what sold, not just how many covers came through. Reports give sales per day, per dish and per waiter, so you can compare services, see which dishes sell and how sales are shared across the team. The figures come from the orders taken in the application.
The app records how each bill was settled (cash, card, voucher or other) and closes it. It does not process card payments, and any fiscal receipt comes from your own till or card terminal. The application also keeps the record of what each table ordered, and staff clock in and out in the same place.
The server enters the order at the table in the application and sends it to the kitchen. Its items show up on the kitchen display for their station only after it is sent, and the order stays tied to its table.
Yes. Every order remains linked to its table and feeds the reports per day, per dish and per waiter.
Yes. Staff clock in and out for each shift, and the app stores the time entries for every team member in the same application as the orders. It does not calculate pay.
No. It does not process card payments and is not connected to a till or card terminal. It records how a bill was settled (cash, card, voucher or other) and produces a non-fiscal table bill, never a fiscal receipt. Use your own till or card terminal for fiscal receipts, and ask your accountant which receipt rules apply to your venue.
Yes. Reports give sales per day, per dish and per waiter, so you can review each waiter's sales and compare services.
Yes. Per-day reports show the sales of each day, and per-dish reports show which dishes sold the most.
Start with your menu: once the dishes are entered in the application, your team can take the first order at the table.
4restaurants.net lets the waiter take the order at the table and send it to the kitchen from the platform, with statuses from new to served, and gives a non-fiscal table bill (the fiscal receipt stays on your own cash register), with reports per day, per dish and per waiter.
We are transparent — here is where 4restaurants.net is not (yet) the best fit:
A fit for venues with a dining room and a kitchen, where paper tickets get lost and orders are written down twice. For a small bar with few orders, a simpler order process may be enough.
| 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.
