How to Track Which Table Ordered What

The owner asks what is on table 6. The floor waiter says dal and two rotis. The counter person swears it was chicken and rice. Both are guessing from half-heard rounds. Tracking which table ordered what only works when one number owns one open ticket that everyone can read.

One number, one open ticket

Assign each dining table a clear name or number and allow only one running order on it. When guests add dessert, reopen that ticket—do not start a second bill for the same sitting. Parcel tickets are separate, carry an optional reference, and must not steal the reserved name Parcel as a fake dining table. Several parcels can stay open without looking like occupied seats. Staff on a phone PWA open table 6 and see the truth instead of interviewing each other.

Free tables should look free

A table view earns its keep when empty seats look different from busy ones. Occupied tables should hint that an order is live so nobody opens every seat to hunt for guests. That glance saves walking the room twice during lunch overlap. Adding items stays on the same ticket until checkout marks UPI, Cash, Card, or Other. GST breakup can show after discount when set; staff mark paid; UPI QR stays display only.

• A second bill for the same guests
• A table name of Parcel on the dine-in grid
• Asking the waiter who already left the floor
• Opening every table just to see if it is busy

Dessert belongs on the same bill

Late sweets and drinks are the classic way floors invent two totals. Train the reopen habit until dessert never creates a sibling ticket. History filtered by date helps if the guest returns tomorrow with a question. Summary shows today’s collection, payment split, and top items when the owner wants the till story without another round of “what did table 6 have?”

Sizing a five-to-ten table room is covered in how to manage 5–10 tables in a small restaurant. That page is about running the whole small floor; this one is about ending conflicting answers for a single table.

Stop using people as the database

When answers disagree, the system failed before the people did. Put the items on the table ticket and make that ticket the only answer. Skip kitchen displays and inventory modules if your only pain is “what is on table 6.” Delivery apps stay outside this tool.

Handover without a whispered list

Shift change should not require a private briefing for each occupied seat. Open the tables view and continue from the same tickets. SpoonCub keeps one open order per table so the owner’s question has a single answer.

“

One table number should answer “what did they order?” without a staff argument.

Make table 6 boringly consistent

When every late add lands on the same ticket and free seats look free, tracking becomes routine instead of detective work.