The waiter takes the order at the table and sends it to the kitchen from the same platform, where each order has a status from new to served. The table bill is non-fiscal, and the platform issues no fiscal receipt.
In short: passing an order on from a notepad costs time, and invites mistakes. 4restaurants.net lets the team enter the order at the table, with the dishes and quantities, and send it to the kitchen when the waiter sends it. The kitchen display shows the items by station, with the statuses new, in preparation, ready and served. The bill is non-fiscal: the platform records the settlement method and closes it, but issues no fiscal receipts and has no cash-register link. Reports per day, per dish and per waiter show what sold and who sold it.
On a busy night, every minute a server spends away from the guests counts, and passing on what was written on a pad is a chance to mistype. 4restaurants.net lets the team take the order at the table, with each dish and its quantity, and send it to the kitchen when the waiter sends the order. The server stays with the guests, and each order is linked to the table it was taken at.
Items reach the kitchen only when the waiter sends the order, with the dishes and quantities of that table. The order stays linked to its table in the platform, so the team knows where each dish belongs. Orders for other tables are kept apart, each under its own table.
At the end of a service you want to know what sold, not only what was billed. Reports show the sales per day, per dish and per waiter, so you can compare services, see which dishes sell and how the sales are spread across the team. The figures come from the orders taken in the platform.
The kitchen display shows the items by station, with the statuses new, in preparation, ready and served. The table bill is non-fiscal: the platform records the settlement method (cash, card, voucher or other) and closes the bill, but it does not process card payments and issues no fiscal receipt. Clock-in and clock-out record the team’s time entries in the same platform.
The waiter enters it at the table, with the dishes and quantities, and sends it to the kitchen from the platform. Items reach the kitchen only at that point, and the kitchen display shows them by station. The order stays linked to its table.
Yes. Each order stays in the platform, linked to its table, and it feeds the reports per day, per dish and per waiter.
Yes. Staff clock in and clock out, and the platform records these as time entries. It does not calculate pay, overtime or penalty rates.
The platform provides a non-fiscal table bill and records the settlement method (cash, card, voucher or other), then closes the bill. It does not process card payments and issues no fiscal receipt.
No. The bill is non-fiscal. The platform does not issue fiscal receipts or company invoices, and it has no cash-register integration.
Yes. Reports show sales per day, per dish and per waiter, so you can review what each waiter sold and compare services.
We set up the menu, the table orders and the kitchen screen, so 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.
