Overview
Reasons to transfer:- A group asked to move (e.g. from a small table to a booth).
- You need a specific table for a reservation and the current occupants agreed to switch.
- A temporary walk-in table is now moving to a permanent table because seating opened up.
Transfer a table
- Open the source table by tapping its card.
- In the Table Session modal, tap Transfer / Merge.
- The Transfer Merge modal opens in Transfer mode by default.

Transfer / Merge modal in Transfer mode — only free tables shown
- The candidate list shows only free tables in the branch. Merged, active, and reserved tables are hidden in Transfer mode.
- Each row shows the target table’s name, section, and capacity.
- Pick your target. Confirm.
What moves
Everything transfers as a single atomic operation:Split lock rule
If the source table has an active split payment, transfer is blocked:Cannot transfer — this table has an active split. Clear the split first.Same reason as merge: split payments reference specific items. Resolve the split (pay or clear) before moving.
Candidate filtering
DishInk shows only valid targets. A table is a valid transfer target if it is:- Free (no active session).
- Not merged.
- Not reserved for a different group (see Reservations).
- Not the source itself.
Kitchen coordination
Kitchen tickets already sent are retagged to the new table on the KDS. This is automatic — no re-print needed.Runners may already have the food. Tell the kitchen verbally when you transfer a table mid-preparation so runners deliver to the right seat.
Tips & best practices
Common mistakes
- Trying to transfer to an active table. Use Merge instead.
- Transferring with an active split. Blocked. Clear the split.
- Transferring a table that has kitchen items still preparing without telling the kitchen. Food may go to the old seat.
- Using Transfer to fix a wrong table. If items were added to the wrong table by mistake, use Item Transfers — it’s the surgical tool.

