Move Tab to Another Table

Move an order to another table, rename the tab or merge two tabs. Moves are common in à la carte restaurants – a starter is served in the bar, guests move to the table, or the party grows and you need to switch to a bigger table.

Move to another table

1. Click Move in the quick buttons (or tap the table and choose "Move tab")
2. MoveTabDialog opens with two tabs: "Move to table" and "Rename"
3. Choose Move to table
4. The grid shows all tables with color-coded status:
   • Green = available
   • Yellow = booking within 60 min
   • Teal = occupied (active order)
   • Red = waiting / delayed
5. Click the target table
6. Confirm in the dialog
7. The order is moved and table status updates immediately

Rename a tab

The tab name is what shows in the table overview and on the ticket. Rename when:

• The guest identifies themselves ("Eriksson booking")
• A bar tab converts to a dine-in tab
• You separate "Business dinner" from "Private dinner"

Steps:

1. Click Move
2. Choose the Rename tab
3. Type the new tab name
4. Save

Merge tabs

When two tables want to combine (e.g. two friends meeting up and becoming one party):

1. Open one of the tabs
2. Click Move → choose the target table (which already has an active order)
3. Confirm you want to merge the tabs
4. All items from both tabs land on the target table
5. The source table becomes available

Important: VAT, discounts and comments come along – nothing is recalculated.

Edge cases and rules

• Paid sub-bill: Cannot be moved – it's already locked with a control code
• Partially fired tab: Moves OK, but the kitchen gets an update ticket with the new table location
• Moving to a table with a booking within 60 min: Warning appears – guests may need to move again
• Tab open on another workstation: If the tab is open on another POS it shows "locked by [name]" – wait or ask your colleague to park the tab first
• Walk-in to a table with a booking: Allowed but logs a "table conflict" in the audit trail

Audit trail

Every move is logged in the database with:

• Which staff member moved it
• From which table → to which table
• Timestamp
• Whether the tab had fired items
• Whether it was a merge (two tabs → one)

You see the history in Order history → detail view and Vendion Ops can review on dispute. This matters for Swedish Tax Authority audits – the move itself is not a fiscal event, but must be traceable.

Kitchen ticket handling

When you move an already-fired tab:

• The KDS auto-updates with the new table number
• The kitchen printer does not reprint (the kitchen sees the update in real time)
• If you use paper tickets: print a Copy (quick button) for the kitchen's reference

Tips

• Build the habit – move the tab as soon as guests switch seats; otherwise new items land on the wrong table
• Use rename instead of creating a new tab when the guest identifies themselves late
• For large parties that grow: merging tabs is faster than duplicating items
• Moves show up in Analytics under "POS activity" – if certain servers move a lot it may signal a training need