Multi-Device Table Service Just Got Bulletproof

Here's the thing about running a busy restaurant with multiple terminals: things can go wrong in very subtle ways. Two servers tap the same table at the same moment. An order gets printed twice because one device didn't know the other had already sent it. A table gets cleared on one terminal but stays stuck on another. We've spent weeks tracking down every single one of these edge cases, and we're pretty happy with where we've landed.

Table locking is the headline feature. When a member of staff opens a table to add items, that table is now locked to their device for the duration of the interaction. Other terminals can see it's in use (there's a subtle lock indicator on the table map), but they can't accidentally add to it or clear it underneath someone. The lock releases the moment the order is stored or the modal is dismissed. Simple, non-intrusive, and it eliminates the most common source of multi-device chaos.

We've also added merge confirmation. If two servers do manage to build orders for the same table simultaneously (edge case, but it happens), the system now detects the conflict and presents a clear merge dialog instead of silently overwriting. You choose which items to keep, and nothing gets lost.

On the printing side, every order now carries a print state that travels with the table data. If Terminal A has already sent the starters to the kitchen printer, Terminal B knows not to re-print them when it adds the mains. No more duplicate tickets. No more confused chefs shouting "I've already got this!"

Finally, we cleaned up logout table cleanup. When a staff member logs out or their session expires, any tables they had in a draft state are handled gracefully: stored if there are items, or released cleanly if empty. No more phantom tables haunting the map after a shift change. This one's been a long time coming, and we're genuinely proud of how solid multi-device table service feels now.