Restaurant Table Management System: Merge, Split and Turnover

This guide is for owners and managers of dine-in restaurants, thali dining halls and family restaurants in India who want tighter control of the floor. By the end you will know how to lay out areas and tables in software, when to merge and when to split, why the billed status matters for cash control, and how to read a table turnover report without a spreadsheet.

What a restaurant table management system does: status colours, areas and floors

On a paper system the floor lives in the cashier's head. Table 9 has ordered, Table 4 has asked for the bill, Table 11 paid and left. It works until the cashier goes on leave or the restaurant fills up on a Sunday night.

Table management puts that picture on a screen that everyone shares. Every table is a tile, and the colour of the tile is its status.

Three states are enough. Each one answers a question someone on the floor asks fifty times a shift: where can I seat people, who is still eating, and who has not paid.

Setting up areas and floors

Group tables the way your staff already talk about them: ground floor, first floor, family section, garden, AC hall. Areas keep each screen short and let you assign captains to their own sections. They also make reports useful, because you can compare the AC hall with the garden.

Number tables so that no two areas share a number. If the ground floor has Table 1 to Table 15, start the first floor at 21 or use a prefix such as F1. Two tables called "Table 4" will receive each other's food within a week.

When you first set up, create tables in bulk and adjust afterwards. A 40-table restaurant should not need 40 separate entries. Good restaurant POS software lets you create many tables at once for an area.

How to merge tables for a large group with one bill

A family of 14 arrives for a birthday dinner. You push Tables 5, 6 and 7 together. On paper, three captains may end up writing on three pads, and at the end someone adds three bills by hand while the family waits.

Merging does in software what you did with the furniture. The three tables become one group with one running order and one bill.

1. Select the tables to join and merge them before the first order is taken.
2. Take the order against the group. It does not matter which end of the table the captain is standing at.
3. The kitchen receives tickets with one table reference, so the food comes out together and goes to one place.
4. Print one bill for the group. If the family wants to pay partly in cash and partly by UPI, use split payment on that one bill.
5. Settle the bill. All the merged tables turn free together.

Two habits make merging work. Merge at seating time, not at billing time, because joining three half-finished orders at the end is where mistakes creep in. And tell the group at the start that it will be one bill. If they want separate bills by family, do not merge: run the tables separately.

Merging also keeps your reports honest. A party of 14 on one bill is one large bill, not three medium ones, and your average bill value and table turnover numbers stay meaningful.

How to split one table for two parties with separate bills

The opposite case is just as common in Gujarat. In a thali dining hall in Rajkot or a South Indian outlet in Surat at 1:30 PM, two unrelated parties share a six-seater. They ordered separately, they will pay separately, and neither wants the other's dosa on their bill.

Without a split function, staff improvise. They put both orders on one table and separate them by memory at billing, or they use a spare table number that does not exist on the floor. Both end in a wrong bill sooner or later.

Splitting creates sub-tables. Table 1 becomes Table 1A and Table 1B. Each sub-table has:

• Its own order, taken by the captain against 1A or 1B.
• Its own kitchen tickets, printed with the sub-table name so the runner knows which side of the table gets which plate.
• Its own bill and its own invoice number when settled.
• Its own status, so 1A can be billed and paid while 1B is still eating.

Train captains to say the sub-table out loud when serving: "1A, two masala dosa." It sounds fussy for a day and then it becomes normal.

Split table or split bill

These are different things. A split table is for two parties who order separately from the start. One party that wants to pay by two methods needs a split payment on one bill, not a split table. Friends who want to divide one bill by person are easier to handle by taking the order on sub-tables from the beginning, if they tell you early.

Why a table should stay occupied until the bill is settled

This is the control that owners most often overlook. In many setups the table turns free the moment the bill is printed. It looks tidy, and it hides the most important fact on the floor: who has not paid yet.

Billing should have two steps. Printing the bill gives the guest a provisional bill, and the table stays occupied in billed status. Settling records the payment, assigns the final invoice number, and only then frees the table.

The gap between those two steps is where money goes missing in a restaurant. A bill printed, cash collected by hand and never entered. A guest who walked out during a rush. A bill reprinted with a discount after the guest paid in full. If the table stays in billed status until settlement, each of these leaves a tile on the screen that someone has to explain.

Make it a closing rule: no table in running or billed status when the day-end report is printed. Any table still open at close is either a guest still seated or a question for the manager. Our post on discount control and billing leakage covers the other controls that work alongside this one.

Table turnover report and how to read it

Table turnover is the number of times a table is used in a period. If 20 tables produce 90 settled dine-in bills in a dinner service, the turnover is 4.5 turns per table. The report breaks this down so you can see which tables and which hours carry the business.

Four readings worth your time

• Turns by table. Tables near the entrance and the window usually turn more. A table that turns far less than its neighbours is badly placed, wobbly, or under an AC vent. Go and sit at it.
• Turns by area. If the first floor does half the turns of the ground floor on a full night, guests are being seated downstairs first and waiting, while upstairs sits empty. That is a seating problem, not a demand problem.
• Turns against bill value. A slow table with a high average bill is fine. A slow table with a low bill is the one costing you covers on a weekend.
• Turns by day. Compare Saturday with Tuesday. If Saturday dinner is at the limit of what the tables can turn, more marketing will not raise sales. Faster service or more seats will.

Read turnover next to the hour-wise sales report. Turnover tells you how hard the tables worked, hour-wise sales tells you when. Together they show whether the 8 PM to 10 PM window is truly full or only feels full because billing is slow. The post on sales reports owners should check lists the other reports worth a weekly look.

One caution. Turnover numbers are only as good as your table discipline. Parcels billed against a dine-in table, or tables left in billed status for an hour after the guests left, will distort the figures.

How Dhandhaan handles this

Dhandhaan is the restaurant POS software built by JK Tech Hub in Rajkot. Its table features cover the cases above:

• Tables are organised by areas or floors, and many tables can be created at once.
• Each table shows a colour status: free, running or billed.
• Several tables can be merged into one group with one bill.
• One table can be split into sub-tables, such as Table 1A and Table 1B, with separate orders and separate bills.
• Billing is in two steps. "Print Bill" gives a provisional bill and the table stays occupied. "Settle" takes payment, assigns the final invoice number and frees the table.
• Captains using the Android captain app can be limited to certain floors.
• Parcel and takeaway orders are counter orders with no table, so they do not block or distort the floor.
• Reports include table turnover, hour-wise sales and captain-wise sales, in Excel and PDF.

What it does not include at present: customer accounts, a customer loyalty module, and guest ordering from the QR menu. The price is ₹12,999 a year for a single branch and ₹23,999 a year for multi-branch, with no charge per bill. Hardware is bought separately.

What we learned building table management for a multi-branch restaurant in Gujarat

JK Tech Hub built Dhandhaan for a multi-branch South Indian and fast food restaurant business in Gujarat that was moving off a hosted POS. Staff wanted screens that felt familiar, so the table view stayed close to what a cashier expects: tiles by area, one tap to open a table.

The decision that mattered most was the two-step bill. Freeing the table at print would save the cashier one tap. We kept the table occupied until settlement, because the owner's view of unpaid bills matters more than one tap at the counter.

The second lesson was about shared tables. In a fast food outlet at lunch, strangers sharing a table is normal, not an exception. Sub-tables had to be quick to create, or staff would go back to working from memory.

How to decide

If you run fewer than eight tables with one person handling floor and counter, basic table tiles are enough and you will rarely merge or split. From about 15 tables, or with more than one floor, you need all of it: areas, merge, split, and the billed status that holds a table until payment.

In a demo, ask the vendor to do three things live: merge three tables and print one bill, split a table and settle one half while the other is still running, and show you where an unpaid printed bill appears on the screen. Those three tests tell you more than a feature list.

Related reading and next step

• Dhandhaan restaurant POS software: features and price
• Captain ordering app for restaurants
• Restaurant discount control and billing leakage
• Restaurant sales reports owners should check
• Restaurant POS software in Ahmedabad

To see merge, split and the table screen with your own floor plan, ask for a demo or a quote through the contact page or on WhatsApp at +91 7265004040.