Restaurant Table Management System: How a Live Floor Plan Fills More Seats
For restaurant and café owners running a dining room · 7 min read
A restaurant table management system is the part of your POS that shows, at a glance, which tables are free, which are occupied, which guests have asked for the bill and what each table has ordered so far. In a busy dining room across the GCC and Iraq, the minutes between "the guests have finished" and "the next party is seated" are where revenue quietly disappears. This guide explains what table management actually has to do, how to measure it with one simple formula, and how to set it up in Culina, the restaurant POS built on ERPNext. It ends with a worked example in Bahraini dinars so you can see what ten saved minutes per table is worth.
- Restaurant table management means tracking every table's status (free, occupied, bill requested) and its running order on one live floor map, so staff stop guessing.
- Table turnover rate is parties served divided by available tables. Tablein's table turnover guide cites about 45 minutes as an ideal time before turning a table, and says dinner tables usually flip every 1 to 2 hours depending on the restaurant type.
- The hidden minutes are usually at the end of the meal: waiting for the bill, and waiting for someone to notice the table is ready to be reset. Both are visible on a colour-coded floor plan.
- In Culina, Restaurant Mode adds floors and tables, a drag-and-drop layout editor, Send to kitchen that fires only new items, and an automatic dine-in service charge.
- In our 12-table BHD example, cutting 10 minutes from a 100-minute table cycle adds about 3.2 parties per dinner service, roughly BHD 185.600 a night. It is an illustration built on stated assumptions, not a guarantee.
What is a restaurant table management system?
A restaurant table management system links three things that are usually kept apart: the physical layout of your dining room, the live status of each table, and the order attached to it. Instead of a paper pad, a whiteboard or the waiter's memory, every table is a tile on a screen. Staff tap a table to open its order, and everyone else on the floor sees the same status.
It is different from a reservation book. A reservation tool decides who is coming and when. Table management decides what is happening right now: who is seated, how much they have ordered, whether the kitchen has the order and whether the bill has been requested. Most restaurants in the region need the second more than the first, because a large share of covers are walk-ins, family groups that arrive in waves and, in Iraq especially, evening peaks that fill the room within an hour.
Why table status is where minutes disappear
The standard way to measure how hard your tables work is the table turnover rate. Tablein's guide gives the method in one line: divide the number of parties served by the number of available tables. If 10 tables serve 20 parties of two in an evening, the turnover rate is 2.
The same guide points to about 45 minutes as an ideal time before turning a table, and notes that casual guests would not normally occupy a table for more than 2 hours. Your exact numbers will differ by concept, but the lesson holds everywhere: you cannot rush a good meal, so the recoverable time sits around it, not inside it.
- Guests finish, but nobody notices, so the bill is requested late or not at all.
- The bill is requested, but the cashier is busy and the table waits with no signal that it needs attention.
- The table is free, but the host does not know, so a waiting party stays at the door.
- A second round is ordered verbally and reaches the kitchen late, stretching the meal.
Table turnover rate = parties served ÷ available tablesA live floor plan does not make guests eat faster. It removes the dead time between the stages of service by making each stage visible.
Step 1: Model your dining room as floors and tables
In Culina, turn on Restaurant Mode in the Culina Profile. That adds the floor plan, tables, coursing, kitchen tickets and the dine-in service charge to that profile. A retail profile can sit beside it on the same company with Restaurant Mode off.
- Create a floor record for each area of the restaurant, for example Main Hall, Terrace or Family Section. Each floor becomes a tab in the POS.
- Add the tables to each floor with a table number and the number of seats.
- In the POS floor plan, use Edit layout to drag the tables into their real positions, so the screen matches the room your staff walk through.
- Every restaurant name, including floors, carries an Arabic field, and the ع / EN switch flips the whole POS between Arabic and English.
Once the layout is in place, tables are colour-coded by status: Free, Occupied, Bill requested and New order. Each table shows its running total and guest count. A New order is a guest's online order from the table QR menu waiting for staff to accept it.
Step 2: Run each table from seat to settle
The dine-in flow in Culina is deliberately short. The point is that every stage changes the table's colour, so the whole team can read the room without asking.
- Open a table by tapping it on the floor plan.
- Add items and attach modifiers such as size, extras or removals.
- Course the items (starters, mains, desserts) if you serve in courses.
- Press Send to kitchen. This fires a kitchen ticket to the right station and the kitchen display. Only new items since the last fire are sent, so re-firing never duplicates a dish.
- Add later rounds as the meal goes. The table shows the running total.
- Charge the table. The service charge is added automatically, you take payment and print, and the table frees up.
Two details protect turnover. First, because only new items are fired, a waiter can add a drink or a dessert at any time without worrying about repeating the main course. Second, the Bill requested status turns an invisible moment into a visible one, so the cashier can prioritise the tables that are ready to pay.
Step 3: Let the service charge add itself
Many restaurants in the region add a service charge to dine-in bills. Doing it by hand at the end of a long shift is how bills go out wrong. In the Culina Profile, set the Service Charge percentage and a Service Charge Account (an income account). The account is required for the charge to apply, and the charge is added to dine-in bills only, so takeaway and delivery are unaffected.
A note on VAT — Tax is a separate decision. Bahrain's standard VAT rate is 10% (Kreston Bahrain VAT guide), and Culina applies tax through each profile's tax template. Whether VAT applies to your service charge depends on how your accountant treats it, so confirm that before you configure the template. The example below shows the charge before any VAT.
Worked example: a 12-table dining room in Bahrain (BHD)
Assumptions for this illustration: a dining room with 12 tables of 4 seats, a dinner service of 4 hours (240 minutes), and a waiting line at the door most evenings so extra capacity can be sold. The average party is 4 guests spending BHD 14.500 each, so the average party's food and drink comes to 4 × 14.500 = BHD 58.000. These are assumed numbers for the example, not Culina results.
| Item | Before | After |
|---|---|---|
| Time per table cycle (meal + bill + reset) | 100 min | 90 min |
| Turns per table in 240 min | 240 ÷ 100 = 2.4 | 240 ÷ 90 = 2.67 |
| Parties served by 12 tables | 12 × 2.4 = 28.8 | 12 × 240 ÷ 90 = 32.0 |
| Turnover rate (parties ÷ tables) | 28.8 ÷ 12 = 2.4 | 32.0 ÷ 12 = 2.67 |
Trimming 10 minutes per cycle, by catching the bill request sooner and resetting the table as soon as it frees, lifts the room from 28.8 to 32.0 parties. That is 3.2 extra parties per service, and 3.2 × BHD 58.000 = BHD 185.600 in extra sales per night. The 2.67 above is rounded from 2.667 (240 ÷ 90 = 2.6667, and 32.0 ÷ 12 = 2.6667).
Now the service charge on a single bill. For one party of 4 with a subtotal of BHD 58.000 and a 10% service charge, the charge is 58.000 × 10% = BHD 5.800, and the bill before any VAT is 58.000 + 5.800 = BHD 63.800.
Extra nightly sales = (32.0 − 28.8) parties × BHD 58.000 = BHD 185.600The same approach works across the region. Only the currency and tax template change: dinars in Kuwait and Bahrain, dinars in Iraq, riyals in Qatar and Saudi Arabia, rials in Oman, dirhams in the UAE. Culina keeps a profile per branch, so a group with a hall in Manama and another elsewhere can set up each dining room with its own currency and tax.
See the floor plan on your own menu
Book a short Culina demo and we will set up your floors, tables and service charge on a live screen, in Arabic and English.
Frequently asked questions
What is a restaurant table management system?
It is the part of a restaurant POS that shows each table's live status (free, occupied, bill requested) and the order attached to it on a floor map. Staff tap a table to open its order, and the whole team sees the same view. It differs from a reservation book, which only plans who is coming.
How do you calculate table turnover rate?
Divide the number of parties served by the number of available tables. For example, 10 tables serving 20 parties gives a turnover rate of 2. In our example, 12 tables serving 28.8 parties give 2.4, and serving 32.0 parties gives about 2.67.
How long should a table stay occupied in a restaurant?
Tablein's guide cites about 45 minutes as an ideal time before turning a table, says dinner tables usually flip every 1 to 2 hours depending on the restaurant type, and says casual guests would not normally stay more than 2 hours. Your concept sets the real number. Focus on the time around the meal, such as the bill and the reset.
Can Culina add a service charge to dine-in bills automatically?
Yes. In the Culina Profile, set the Service Charge percentage and a Service Charge Account, which is an income account and is required for the charge to apply. The charge is added to dine-in bills only. Check with your accountant how VAT applies to it before you set the tax template.