Draw the room the team actually works
Create a table with its number or name, seat capacity, and circle, square, or rectangle shape. Edit mode lets an authorized operator drag each table to a stored grid position, so the digital floor can reflect the practical layout instead of forcing every restaurant into the same list.
Read service state without walking the room
Available, occupied, reserved, and cleaning are distinct live states. The floor can show party size, guest name, how long an occupied table has been seated, counts by state, and average seated time. A table marked reserved is a floor status; LiftedPOS does not represent it as a full online reservation book.
Move a guest from the waitlist to a real table
The waitlist can retain guest name, party size, phone, notes, and a quoted wait while the team sees queue size, average wait, seated guests, and no-shows. When a table opens, staff can select that actual table and seat the waiting party in one guarded operation.
Open the table's order in context
An occupied table can open its register order with the table already selected. Staff can tag items by seat and course, add modifiers and kitchen notes, and fire the whole order or a selected course to the kitchen. The source order retains that detail; the production team verifies the active ticket from the fields visible on its configured station view.
Split by seat without losing the rest of the check
Seat-tagged items can be paid as an independent split check. Earlier seat payments remain scoped to their items and do not intentionally close the whole table; the final seat can complete the table closeout. The rollout test maps that procedure to the restaurant's configured terminals and staff roles.
Protect active checks through bussing and closeout
Table actions are permission-gated. Clearing a table with an active party or linked sale requires an explicit confirmation and the server refuses an unconfirmed clear. Staff can move the table into cleaning, then return it to available after bussing without silently discarding a live check.
Build the floor around the service model
Use the configured floor, waitlist, table states, party details, orders, seats, courses, checks, and bussing procedure as one acceptance workflow. Testing the actual service model keeps every handoff clear before rollout.
Open the restaurant floor, seat a table, build a check, and compare table state before and after close. Availability can depend on enabled modules, hardware, payment setup, role, location, and rollout configuration.
Move from the feature to the operation
This capability shares customer, employee, product, location, transaction, and reporting context with the rest of LiftedPOS. The value is not a checked box. It is the handoff the operation no longer has to rebuild.