Three things every floor-plan UI gets wrong.
Auto-fit, status colours, single-tap seat. Sounds obvious. Most legacy POS get all three wrong. A short rant with screenshots.
No "5 ways AI will transform restaurants" filler. We write about specific service problems and how the right system solves them.
The old POS pricing model — pay per terminal — made sense when terminals were £900 boxes you bolted to the bar. It doesn't make sense when "a terminal" is a £200 Sunmi or an iPad in a server's pocket. We unpack the maths and the perverse incentives it creates.
Read →Auto-fit, status colours, single-tap seat. Sounds obvious. Most legacy POS get all three wrong. A short rant with screenshots.
What happens when a server taps "86 burrata"? We trace the request from POS → DB → realtime broadcast → KDS → kiosk → delivery channels.
The first version was a dashboard. Operators ignored it. The second version was a notification. Different story. A field note.
Browser print pipelines, ESC/POS, and how we replaced 'em with direct-byte dispatch on Sunmi. With code.
What it actually requires, what guests actually need, and where compliance tooling helps the kitchen — versus annoying it.
Designing for muscle memory. The two-tap rule. Why training matters less than discoverability.