Field notes

Operations writing for operators.

No "5 ways AI will transform restaurants" filler. We write about specific service problems and how the right system solves them.

Featured
Why per-device pricing has aged badly.

Why per-device pricing has aged badly.

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 →
Floor plans

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.

86 lifecycle

86'ing an item: a 200ms problem.

What happens when a server taps "86 burrata"? We trace the request from POS → DB → realtime broadcast → KDS → kiosk → delivery channels.

AI on the floor

What we learned shipping AI insights to a 64-cover bistro.

The first version was a dashboard. Operators ignored it. The second version was a notification. Different story. A field note.

Receipts

Why your printer is silent on Saturdays.

Browser print pipelines, ESC/POS, and how we replaced 'em with direct-byte dispatch on Sunmi. With code.

Allergens

A pragmatic guide to Natasha's Law for software builders.

What it actually requires, what guests actually need, and where compliance tooling helps the kitchen — versus annoying it.

Onboarding

A new server gets your software in 12 minutes. Or they don't.

Designing for muscle memory. The two-tap rule. Why training matters less than discoverability.