Platform · Kitchen display
A screen on the pass instead of a printer. Tickets by state, course firing and per-station routing, on a tablet you own.
Every kitchen chit the POS produces lands here, moves through the cook and clears when it is done.
The kitchen advances each chit: start it, mark it ready, bump it off the board. Recall a bumped ticket and it returns to ready.
Every chit shows its age from when it was fired: green in time, amber at five minutes, red once overdue. A venue can tune those thresholds.
Items are tagged by course, and the kitchen sees a course only when the server fires it. Firing again sends the new items alone.
You flag products as kitchen and set which registers print bar tickets. Kitchen items are subtracted from the bar ticket, so one sale serves both stations.
Tickets arrive over a live feed, so a fired course shows in seconds. If it drops, the board polls and an indicator says live or polling.
The creating device prints the ticket and records the outcome: pending, printed or failed, with a time. A failed chit waits for someone to press retry.
One system
No separate password. A KDS screen is a device paired through the POS on that same tablet, so the POS pairs it and the kitchen sees the venue's tickets. An owner can also preview the same board from the dashboard. If a screen is not paired yet, it says so and asks you to open the POS on the device and pair it first.
Nothing gets cooked twice. Each fire compares the course against a snapshot of what already went to the kitchen and sends only the difference. Pressing Fire again, or firing after a guest adds a late dish, produces a ticket for the new items alone, never a fresh copy of the whole course.
Two settings decide it. A product is flagged as a kitchen item when you build the menu, and a register is set to print bar tickets when you set up the POS. Anything flagged kitchen is taken out of the bar ticket, so one sale can produce a kitchen chit and a bar chit that never overlap.
Each chit shows its age from when it was fired. It stays green while it is in time, turns amber at five minutes, and red once it passes ten. Those thresholds can be tuned for a venue that runs faster or slower than the default.
The board arrives over a live feed and falls back to polling if that feed drops, reconnecting on its own. A small indicator shows whether it is currently live or polling, so a short dropout does not leave the kitchen blind or make a fired course disappear.
Yes. Recently bumped tickets stay within reach, and recalling one returns it to ready so it can be worked and bumped again. Bumping is optimistic on the screen and reconciles on the next refresh, so the board stays responsive during a rush.
A real person on the phone, not a ticket queue. Pair a spare tablet to the POS and the kitchen can be reading tickets tonight.
0,99% on cards, no monthly fee and no binding. Or 500 kr a month for software only.