The server takes the order at the table, and it goes to the kitchen from the same application, linked to the table it came from.
In short: every trip a server makes to a terminal to key in an order costs time and invites mistakes. 4restaurants.net lets the team take the order at the table. The dishes are picked from the digital menu, and the order goes to the kitchen with its table. Shift clock-in records who worked each shift, and reports per day, per dish and per waiter show what sold and who sold it. The application does not take payments, so the bill is settled on your POS or EFTPOS terminal.
On a busy Friday, a server who walks to the terminal to key in what they wrote on a pad loses time that belongs to guests. Every trip is a chance to mistype. With 4restaurants.net the order is taken at the table, the dishes are picked from the digital menu, and the order goes to the kitchen from there. The server stays with the guests, and each order is linked to its table.
Each order goes to the kitchen as it is taken, with the dishes and quantities for that table. It stays linked to its table in the application, 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, and who sold it. Reports show 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 recorded in the application.
The application does not take payments or issue receipts. The bill is settled on the POS or EFTPOS terminal you already use, and the application does not connect to that terminal. Shift clock-in records the team's time for each shift in the same application as the orders and reports.
The server takes it at the table from the digital menu, and it is sent to the kitchen from the application. It stays linked to its table, so nobody walks to the terminal to key it in.
Yes. Each order stays in the application, linked to its table, and feeds the reports per day, per dish and per waiter.
Yes. Shift clock-in records the working time of each team member for every shift, in the same application as the orders and reports.
No. The application does not take card, EFTPOS or online payments. The bill is settled on your POS or EFTPOS terminal.
Yes. Reports show sales per day, per dish and per waiter, so you can review what each server sold and compare services.
No. The application does not issue receipts or connect to a POS or till. Receipts come from the equipment you already use.
We set up your menu and table layout, so your team can take the first order at the table on the first night.
4restaurants.net takes the order at the table, sends 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, 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.
