Okta POSLogin

Public Guide

Table View Documentation

Complete guide for floors, table cards, table status, opening tables, KOT, bill, settle, release, unsettled orders, search, layout view, customer alerts, sync, and troubleshooting.

Open OktaPOS

Video Tutorial

Table View walkthrough

Reserve this section for a YouTube walkthrough that shows floors, table status, opening a table, customer details, waiter assignment, active orders, and table search.

YouTube video placeholder. Add the tutorial video here when it is ready.

Tutorial video coming soon

This space is reserved for the official walkthrough video.

Quick Start

First table service test

1

Create floors and tables with consistent table codes.

2

Open one empty table and assign seats, customer, waiter, and notes.

3

Add products in Table Counter and send KOT.

4

Reopen the same table and confirm the cart still loads.

5

Print bill and confirm release-on-bill behavior.

6

Settle payment and confirm the table becomes empty.

Status Rules

What staff must remember

Empty means the table is free.
Running means an active order exists for the table.
Running KOT means KOT was sent or saved and the active table order still owns the cart.
Printed means bill was printed and the table remains occupied when release-on-bill is off.
Unsettled is a payment state, not table occupancy by itself.
Waiter name is printed metadata and must not control occupancy or payment state.

Best Practices

Recommended operating habits

Use either T1/T2/T3 or T01/T02/T03 consistently. Avoid mixing both styles unless the store truly needs separate tables.

Assign waiter at table opening when service tracking matters.

Use KOT for kitchen preparation and Settle for payment completion.

Train staff that printed unpaid bills can move to Unsettled Orders.

Do not release active tables casually during rush hours; confirm the payment/order situation first.

Run one test order after changing floor layout, printer setup, or release-on-bill settings.

Workflow Maps

Common table workflows

Normal Dine-In Flow

1. Open Table2. Add Products3. Send KOT4. Print Bill5. Settle6. Table Empty

Release-On-Bill Flow

1. Open Table2. Send KOT3. Print Bill4. Table Empty5. Unsettled Order6. Settle Later

Printed Table Flow

1. Open Table2. Send KOT3. Print Bill4. Table Printed5. Reopen Order6. Settle

Cross-Device Check

1. KOT on Device A2. Verify Device B3. Release/Settle4. Sync5. Confirm Empty6. No Old Reopen

Table View

Table View Overview

Start here when a store wants to manage dine-in tables, see table availability, and move quickly from table selection to order, KOT, bill, and settlement.

Top

Table View is the live floor board for dine-in operations. It shows floors, table cards, running orders, printed bills, running KOTs, customer details, waiter information, unsettled orders, table search, and quick actions for daily restaurant service.

Steps

  1. Create floors and tables before live service.
  2. Use the floor tabs to filter all tables or one floor.
  3. Use the status legend to understand Empty, Running, Printed, and Running KOT tables.
  4. Click an empty table to open a table session.
  5. Enter seats, customer details, waiter, and notes where needed.
  6. Add products in Table Counter and send or save KOT.
  7. Print bill or settle from the counter when the customer is ready.
  8. Use Unsettled Orders for printed but unpaid bills.

Expected Result

The floor team can understand table availability, active service, and pending payment without opening every order.

Table View

Floors and Table Setup

Use this before opening the restaurant for table service or when the store changes its seating layout.

Top

Floors group tables into practical areas such as Ground Floor, First Floor, Rooftop, AC Hall, or Outdoor. Every table should have a clear code and seat count so staff can find and open it quickly.

Steps

  1. Open Table View.
  2. Create a floor from floor management.
  3. Give the floor a clear name and optional short code.
  4. Add tables under the correct floor.
  5. Use consistent table codes such as T1, T2, T3 or T01, T02, T03.
  6. Set seat count for each table.
  7. Avoid duplicate table names inside the same floor.
  8. Reload or sync other devices after layout changes.

Expected Result

The Table View becomes reliable for search, KOT, bill, customer QR, and cross-device sync.

Table View

Floor Tabs and Counts

Use this when staff need to see all tables or focus on one floor during service.

Top

The top floor tabs show each floor name and the current running count against total tables. All Floors shows the combined count across the store.

Steps

  1. Click All Floors to see every floor section.
  2. Click a specific floor tab to focus only on that floor.
  3. Use the count to understand how many tables are currently occupied.
  4. If the count looks wrong, check running KOT, printed tables, and unsettled orders.
  5. Use Sync Data if another device recently changed table status.

Expected Result

Managers and waiters can quickly scan occupancy without leaving the table board.

Table View

Table Status Meaning

Use this to train staff on what each table state means before they open, print, settle, or release a table.

Top

Table status is not only a color. It controls whether a table is free, has an active order, has a KOT in progress, or has a printed bill waiting for payment.

Steps

  1. Empty means the table is free and must not show customer or order state.
  2. Running means the table has an active order but KOT may not be printed yet.
  3. Running KOT means products were sent or saved to KOT and remain linked to that table order.
  4. Printed means the bill was printed and the table may still be occupied when release-on-bill is off.
  5. Unsettled means payment is pending. It is an order payment state, not table occupancy by itself.
  6. Released, completed, settled, cancelled, void, and refunded orders must not reopen a table.

Expected Result

Staff can choose the right action without accidentally reopening old orders or clearing active tables.

Table View

Opening a Table

Use this when a guest sits at a table and the waiter needs to begin a dine-in order.

Top

Opening a table creates the current table session. The table session links the table to one active table order so the same cart can be reopened safely from any supported OktaPOS device.

Steps

  1. Click an Empty table card.
  2. Confirm or edit the number of seats.
  3. Add customer name or phone number if available.
  4. Assign a waiter when the store tracks waiter service.
  5. Add notes only when they help the floor or billing team.
  6. Click Open Table.
  7. Add products in Table Counter.
  8. Send or save KOT when the kitchen must prepare the items.

Expected Result

The table becomes active and the order remains linked to the correct floor and exact table code.

Table View

Waiter Assignment

Use this when KOT and bills need to show which waiter handled the table.

Top

Waiter name is display metadata for the current table order. It should appear on KOT and bill when a waiter is assigned. If no waiter is manually assigned and the logged-in employee is a waiter, the employee name can be used for that table order.

Steps

  1. Assign waiter while opening the table, or let the waiter user open the table.
  2. Send KOT and confirm the waiter name appears on the kitchen slip.
  3. Print bill and confirm the same waiter name appears on the customer bill.
  4. Do not use waiter name to decide table occupancy, active order ownership, release, settle, or unsettled payment behavior.

Expected Result

The printed records show service responsibility while table-order safety rules remain unchanged.

Table View

Adding Products and KOT

Use this after the table is opened and the customer places an order.

Top

Products added to a table are saved in the active table order for the current table session. Sending or saving KOT keeps those products in the same table order and marks the table as Running KOT.

Steps

  1. Open the table.
  2. Search or browse menu items in Table Counter.
  3. Add products and adjust quantity as needed.
  4. Use Quick Item only for one-time items that are not in the menu.
  5. Click KOT or Save KOT.
  6. Reopen the table from Table View to confirm the cart still loads.
  7. Print or save more KOTs if the customer orders additional items.

Expected Result

Kitchen preparation and table cart stay connected to the same active order.

Table View

Bill, Release, and Settle

Use this when the customer is ready for billing or when staff need to free the table.

Top

Billing and release behavior depends on store settings. Release-on-bill decides whether printing a bill frees the table immediately or keeps it printed until payment is completed.

Steps

  1. Use Bill to print the customer bill.
  2. If release-on-bill is on, the table becomes Empty and the unpaid bill appears in Unsettled Orders.
  3. If release-on-bill is off, the table remains Printed and stays linked to the order.
  4. Use Settle when payment is completed.
  5. Settle saves the sale, empties the table, completes the active table order, and removes the unsettled entry.
  6. Use Release Table only when the table must be freed without completing payment through the normal bill/settle flow.

Expected Result

Payment, occupancy, and unsettled-order records remain clear for both counter staff and managers.

Table View

Unsettled Orders

Use this when a bill was printed but payment has not been completed.

Top

Unsettled Orders shows unpaid table and takeaway bills. A table can be empty while its unpaid bill remains in Unsettled Orders, especially when release-on-bill is enabled.

Steps

  1. Open the Unsettled Orders panel from Table View.
  2. Review pending order number, table, floor, customer, and amount.
  3. Use Print when the bill needs another copy.
  4. Use Settle after payment is received.
  5. Do not treat an unsettled entry as table occupancy by itself.
  6. After settlement, confirm the entry is removed from pending payment.

Expected Result

Printed bills can be paid later without keeping the physical table blocked unnecessarily.

Table View

Search and Exact Table Codes

Use this when staff need to find a table quickly by typing a code such as T2, T02, T6, or T06.

Top

Table search should respect exact normalized floor and exact normalized table code. Codes that look similar can still represent different tables.

Steps

  1. Click the table search field.
  2. Type the full table code or floor name.
  3. Use consistent naming so staff do not confuse T6 with T06.
  4. If T6 and T06 both exist, verify the correct table before opening or settling.
  5. Keyboard shortcuts should not trigger while the search field is focused.
  6. Clear the search to return to the full table board.

Expected Result

Staff can search fast without accidentally opening, printing, or settling the wrong table.

Table View

Layout and Grid View

Use this when the store wants either a compact operational grid or a visual floor layout.

Top

Table Grid is best for speed and scanning. Floor Layout is best when the store wants a more visual view of where tables are placed. Both views should use the same table and order data.

Steps

  1. Use Table Grid for daily counter work and quick status scanning.
  2. Use Floor Layout when staff need a visual seating plan.
  3. A table opened in one view should show the same status in the other view.
  4. If a layout position is missing, confirm the table was added to the layout plan.
  5. If status differs between views, sync or reload before taking action.

Expected Result

The store can choose the best display style without changing the order workflow.

Table View

Customer Alerts

Use this when customer QR approvals, service requests, or customer-side alerts need staff attention.

Top

Customer alerts are shown from the notification bell. They help staff respond to customer requests without mixing them into table occupancy or payment state.

Steps

  1. Click the customer alert bell in Table View.
  2. Review pending customer notifications.
  3. Open the related table or request where available.
  4. Complete or dismiss the notification after staff handles it.
  5. Keep admin announcements separate from customer service alerts.

Expected Result

Customer requests become visible to staff without changing the table-order lifecycle.

Table View

Cross-Device Sync

Use this when the same store is running Flutter mobile, Flutter desktop, and Next.js web together.

Top

All supported clients must write and read the same table, tableOrder, activeOrderId, tableSessionId, waiter, and status fields. Remote updates can be delayed, but old local data should not revive released or settled tables.

Steps

  1. Use the same store account across devices.
  2. Create or edit floors and tables from one device, then sync others.
  3. Send KOT from one device and confirm other devices show Running KOT on the exact same table.
  4. Release or settle from one device and confirm other devices do not reopen the old order.
  5. Use Sync Data when a device was offline or idle for a long time.
  6. Avoid editing Firestore rules for table fixes unless explicitly approved.

Expected Result

Flutter, Windows Flutter, and Next.js stay aligned for table operations.

Table View

Permissions and Staff Training

Use this before giving employees access to table service, billing, settlement, or settings.

Top

Different roles may need different access. A waiter may open tables and send KOT. A cashier may bill and settle. A manager may release tables, edit layout, or handle unsettled orders.

Steps

  1. Create employee roles based on real store responsibility.
  2. Give table access to waiters who manage dine-in orders.
  3. Give print access to users who can print KOT and bills.
  4. Give settlement access only to users who can collect payment.
  5. Give layout/settings access only to managers or owners.
  6. Test with one employee login before using it in live service.

Expected Result

Staff can complete their work without exposing actions they should not use.

Table View

Troubleshooting

Use this when table status, search, cart loading, KOT, bill, or unsettled orders do not behave as expected.

Top

Most Table View issues come from duplicate table codes, delayed sync, an old active order, wrong release-on-bill expectation, missing waiter assignment, or a device that has not refreshed after another device changed the table.

Steps

  1. If a running table opens with an empty cart, reload or sync and confirm the table still has the correct active order.
  2. If a released table becomes running again, check for stale data from another device and confirm the old table session was cleared.
  3. If T6 status appears on T06, check table naming and exact table-code matching.
  4. If KOT does not show waiter, confirm waiter was assigned or the logged-in employee is a waiter user.
  5. If a printed bill is missing from the table, check release-on-bill setting and Unsettled Orders.
  6. If payment is completed but unsettled still shows, refresh and confirm settlement finished successfully.
  7. If another device shows a different status, use Sync Data and avoid taking duplicate actions until the status matches.

Expected Result

Staff can diagnose common table-service problems without damaging the active table order.