#1043Dine-In
06:48Table 7 · Marco
2× Margherita Pizza
+ extra mozzarella
no basil
1× Garlic Bread
well done
Kitchen display
The kitchen screen that
survives the power cut.
A standalone Windows app for the pass — under 5 MB, station-routed and glanceable from across a hot kitchen. Bump state lives on disk, so a mid-rush reboot picks up exactly where it left off. Nothing bumped twice, nothing forgotten.
- Under 5 MB install
- Crash-resilient state
- Free with every till
Kitchen — Grill Stationlive
All Day
12×Fries6×Margherita5×Chicken Shawarma3×Onion Bhaji8×Coke4×Lamb Kebab
38 active#1044Takeaway
05:12Collection · Priya
1× Lamb Kebab Wrap
+ chilli sauce
no onions
1× Regular Fries
2× Coke
Read Carefully — Nut Allergy
#1045Delivery
02:54Deliveroo · #DR-8821
1× Chicken Korma
⚠ no nuts — separate prep
mild spice
2× Pilau Rice
3× Onion Bhaji
#1046Takeaway
01:30Collection · Sam
1× Chicken Shawarma
+ extra garlic mayo
+ pickles
1× Mixed Grill
no lamb chop
2× Fries
#1041Delivery
−02:45Overdue · Uber Eats #UE-4470
2× Lamb Kebab Wrap
+ extra chilli
1× Chicken Shawarma
no salad
4× Fries
#1047Dine-In
07:20Table 12 · Aisha
1× Pepperoni Pizza
+ jalapeños
stuffed crust
1× Onion Bhaji
2× Coke
Survives a power cut
Reboot mid-rush. It picks up exactly where it left off.
Most kitchen screens hold the night in memory. One flicker on the ring main and the board is blank, the cooks are guessing, and the pass grinds to a halt at the worst possible moment.
Zeta writes every bump, every dismissed ticket and every alert to disk the instant it happens. The screen can lose power in the middle of a Saturday and come back to the same board it had a second earlier — same tickets, same bumped lines, same countdowns. Nothing is double-bumped, nothing is lost, and no cook has to rebuild the rush from memory.
- Bump state persisted per ticket — a restart never resurrects a finished order
- Dismissed tickets and alerts survive the reboot in the same state
- Countdowns recover against the original deadline, not the boot time
- The till re-syncs the moment the screen is back on the LAN
0
tickets lost or double-bumped across a power cut — bump state is on disk, not in memory.
“The fuse board tripped on a Friday at half eight. The screen blinked, came straight back, and not one order was wrong. That's the bit nobody else gets right.”
On the line
Built around how cooks actually work.
Every decision on this screen is made for a cook with full hands and ten seconds to read it — not for a slide. Eight things it gets right.
Station routing
Each menu item is tagged to one or more stations. The grill screen never shows a milkshake.
Survives a power cut
Bump state and alerts hit the disk as they happen. Reboot mid-rush and nothing is lost or double-bumped.
Allergy “READ CAREFULLY”
A high-contrast banner on any ticket with allergy notes — the one alert a cook can’t scroll past.
Countdown that earns attention
Neutral, then amber as the deadline nears, then red and pulsing when it’s overdue.
86 & reject, instantly
A cook marks an item out of stock or rejects a ticket; the till operator knows before the next order.
Density for the rush
Comfortable three columns, or compact four-to-five when the pass is heaving. Readability stays the floor.
All-day prep strip
“12 fries, 6 burgers, 3 pizzas” across every live ticket, so the cook can batch the fryer.
Recall without chaos
The till pulls an order back to amend it; the kitchen shows a “being edited” pulse and pauses that ticket.
Collection screen
Out front, customers see exactly where their order is.
A customer-facing screen by the counter shows every live order moving from Preparing to Ready — driven by the same bumps the kitchen is already making. When the cook clears the last item, the number flips columns by itself.
- The counter stops fielding “is mine done yet?” — the board answers it
- Updates the instant the kitchen bumps; no extra taps for staff
- Readable across a busy shop floor — big numbers, two columns
- Included in the Standard plan alongside the kitchen screens
Zeta POS — Collection · The Spice Garden
Preparing
- 047
- 048
- 051
Ready
- 045
- 046
Order 045 just bumped — it crossed to Ready on its own.
Station routing
Every screen shows only its own work.
One ticket can feed three stations at once, and each cook should only see the part that's theirs. Tag each menu item to the stations that make it, and the board does the splitting — the grill screen never carries a salad, the cold line never carries a burger.
System map
How the pieces fit together.
Your shop's LAN — no internet requiredsource of truth
AD101 Caller-ID Bridge
USB · 4 phone lines
Decodes incoming calls and pushes ring events straight into the host.
Host Till
the anchor
POS app
Tauri + React
WebSocket server
:7172
SQLite database
orders · customers · menu
Client Till
no local DB · RPC over WebSocket
Kitchen Display
standalone app · station-routed
Survives a power cut — bump state on disk.
live data pathphone events inresilient — fails & re-syncs independently
If the kitchen screen reboots mid-service, it picks up exactly where it left off.
- Tag every menu item to one or more stations — grill, fryer, salad, drinks — once, in settings.
- Each screen subscribes to its own stations and renders only that work; the grill never shows a milkshake.
- A density toggle swaps comfortable three columns for compact four-to-five when the pass is heaving.
Readability stays the floor. Density flexes for the rush; it never shrinks past what a cook can read at arm's length.
Setup
A separate installer and a four-step wizard.
The kitchen app is its own download — a single sub-5 MB installer, nothing for IT to schedule. Double-click, then walk the pairing wizard. A second screen is live in about a minute.
1
Name the station
Give the screen a name the cooks recognise — “Grill”, “Pass”, “Cold line”. It tags every ticket the screen claims.
2
Pair with the host
Enter the host till on the LAN. A test-connection probe confirms the screen can reach it before you go any further.
3
Pick a sound preset
Choose an alert tone and volume for new tickets — quiet for a small kitchen, sharp for a loud one.
4
Confirm and go
Review the summary, confirm, and the board is live. The whole wizard takes under a minute per screen.
See it ride out a power cut, live.
A 20-minute demo shows the board surviving a mid-rush restart faster than any page can explain it.