Dine-In Served Status and Table Numbers for Family Restaurants

A table number ordering system attaches a table to every order from the moment it is placed, so the kitchen knows where the food goes, the floor knows what each table is waiting for, and the bill is right the first time. In a family restaurant, where a table of eight orders in three rounds over ninety minutes, that number is the difference between a smooth evening and a waiter walking the floor with a plate asking "who had the paneer tikka".

This post walks a family restaurant through dine-in on Tezzu: how a customer orders from a QR code at the table, how the order carries the table number through to the KOT and the dashboard, what the served status is for and why it matters more for dine-in than any other order type, and how second rounds and the bill work.

Where a family restaurant loses track of tables

The failure is rarely the first order. It is the second and third. Table 6 orders starters at 8:05, mains at 8:25 and a second round of rotis at 8:45. The starters were written on a pad, the mains were shouted to the kitchen, and the rotis were a wave at a passing waiter. By 9:15 the kitchen has made two plates of rotis for table 6 and none for table 9, and the bill has a dal nobody ordered.

Paper KOTs with a table number written on them help, if the number is always written and the slips do not get lost. A system where the table number is captured at the moment of ordering, by the customer, and printed on every KOT and shown on every screen, removes the step where it gets forgotten. The errors this catches are the same ones listed in how to reduce order errors in a restaurant.

Scan, order, pay: the customer's side

Each table gets a printed QR code with its number encoded. Here is what the family at table 6 does.

1. One person scans the code. The store page opens with the dine-in menu, already set to table 6.
2. They add two paneer tikkas, a dal makhani, four butter naans and three lassis. Others at the table call out what they want, or scan the code themselves and add to their own cart.
3. They place the order. Depending on how you have set the store, they pay by UPI or card right there, or the order goes through to be settled at the counter later.
4. A confirmation arrives on WhatsApp if they ordered through the bot, and the order appears in the kitchen with table 6 on it.
5. At 8:25 they scan again for mains, and at 8:45 for the rotis. Each round is its own order, each carrying table 6.

No waiter was needed to take any of those orders, and nobody wrote a table number by hand. The full dine-in flow from the customer's side, including how a QR menu differs from a QR ordering link, is in QR code ordering for dine-in.

Pending to served: the status flow for dine-in

Delivery orders end at delivered. Pickup orders end at collected. Dine-in orders need their own end, and it is served: the food reached the table. Without it, a dine-in order either sits as ready forever or gets marked delivered, which means nothing to the floor and confuses the reports.

The served status does three jobs. It tells the floor manager, at a glance, which tables are still waiting; anything ready but not served for more than a few minutes is a plate going cold on the pass. It closes the order so the rating request can go out and the reports count it correctly. And it gives you a timestamp per table from order to plate, which is the number to watch on a Saturday night. The full status model, and why each order type needs its own end state, is in order status workflow: pending to served.

Table numbers on the KOT and the dashboard

The table number travels with the order everywhere it goes. On the KOT, it is printed at the top in large type, so the kitchen stacks slips by table and the runner knows where to go. In the dashboard, dine-in orders show their table number in the list, so the counter can see that table 6 has three open orders and table 9 has one that has been ready for six minutes. On the staff app, the new-order alert and spoken announcement include the table, so a cook with wet hands hears "table 6" without looking at a screen.

This is what makes multi-round ordering safe. Three orders from table 6 are three slips and three lines in the dashboard, all with the same table number, and the bill at the end is the sum of the three. The printing side, 58 mm versus 80 mm and what goes on a KOT, is in the KOT system guide.

What this looks like on Tezzu

Dine-in is switched on in the dashboard, and tables are created with their numbers. For each table, Tezzu gives you a QR code to print; scanning it opens your store page in dine-in mode with that table number already attached, so the customer never types it. The menu shown can be the same as your delivery menu or a dine-in category set, with items scheduled by time if the lunch thali only runs till 3.

Orders arrive in the live dashboard under a dine-in view, each with its table number, items and payment status, and on the staff app with the alert and spoken announcement. Accepting an order prints the KOT on your thermal printer with the table number at the top. The kitchen moves it to preparing and ready; the waiter who carries it out marks it served from the staff app or the dashboard. Dine-in orders follow their own set of statuses, so nobody is asked to mark a thali as out for delivery.

Payment is your choice per store: customers pay by UPI or card at the time of ordering, through Razorpay, or orders are settled at the counter at the end of the meal. A GST bill can be issued for the table. Once the last order is marked served and settled, the customer who ordered through WhatsApp gets a rating request in the chat, which is how a family restaurant collects reviews from tables without handing out cards. The setup steps, from creating tables to printing codes, are in dine-in with Tezzu: QR tables, served status and KOT printing, and the complete list of dine-in and kitchen features is on the features page.

Second rounds, one table, one bill

Here is table 6's evening in rupees. Round one at 8:05: two paneer tikka at ₹260, three lassis at ₹90, ₹790. Round two at 8:25: dal makhani ₹240, a mixed veg ₹220, four butter naans at ₹45, ₹640. Round three at 8:45: four more naans, ₹180, and two gulab jamun at ₹80, ₹340. Three orders, three KOTs, all marked table 6, all served by 9:05. The bill is ₹1,770, which is the sum of three orders the system already holds, not a reconstruction from a pad.

If the family paid online per round, the table is settled before they stand up and the counter has nothing to do. If they are paying at the counter, the counter sees three settled-at-counter orders for table 6 and takes ₹1,770 once. Either way, the ₹10 per order on Tezzu is per order, so the evening cost you ₹30 on this table with no commission on the ₹1,770. The cafe version of this flow, with smaller tables and faster turns, is in QR dine-in for cafes, and the restaurant setup as a whole is on Tezzu for restaurants.

Frequently asked questions

How does a table number ordering system work in a restaurant?

Each table has a QR code with its number built in. A customer scans it, the menu opens with that table attached, and every order they place carries the table number through to the kitchen ticket, the dashboard and the bill. Staff never write the number by hand, and multiple rounds from one table all show the same table so the final bill is simply their sum.

What is a served status and why does dine-in need it?

Served is the end state for a dine-in order: the food reached the table. Delivery orders end at delivered and pickup orders at collected, and neither makes sense for a table. Served tells the floor which tables are still waiting, closes the order for ratings and reports, and gives you a time from order to plate per table.

Can customers order multiple times from the same table?

Yes. Each scan or each new order from the same QR code is a separate order carrying the same table number. On Tezzu, the dashboard shows all open orders for a table together, each KOT prints with the table at the top, and the bill at the end is the total of every order placed from that table during the meal.

Do customers have to pay online when ordering from the table?

That is your setting. You can require UPI or card payment at the time of ordering, which settles each round as it is placed, or let orders go through to be paid at the counter at the end of the meal. Many family restaurants start with pay-at-counter and offer online payment as the option that lets a table leave without queueing.