Waiting
0
Queued or with a printer
Setup
Printing
Failed
0
Nothing stuck
Printers
0
Active
Unseen
0
Not collected from recently
Queue
What has been sent
Nothing yet. Tickets appear here the moment a course is fired — firing prints, so there is no separate button to forget.
Hardware
Printers
None yet. A venue with one printer routes everything to it — tickets, drinks, bills and reports — and that is the setup most rooms start with.
The agent
Print relay
Your printers are on the restaurant’s own network and nothing outside the building can reach them — which is exactly right, and the reason a small agent has to run on a machine inside. It collects work and prints it. It never accepts a connection, so nothing needs opening on the router.
No relay yet. Issue one, then run tools/print-relay.js on any always-on machine on the venue’s network.
The token is shown once and stored hashed. If it is lost, issue another and revoke the old one — there is no way to read it back.
How it behaves
When it goes wrong
A job is claimed, not taken
If the relay dies mid-print the claim lapses after ninety seconds and the job comes back. Nothing is lost and nothing prints twice.
Five attempts, then it stops
A printer out of paper is not hammered until somebody refills it. The job fails, waits here, and prints when you send it again.
A reprint says so
Every bill after the first carries COPY at full height. Two bills that look identical is how a guest is charged twice.
Firing prints
Tickets are queued by the act of firing a course, not by a second button. A printer that is unconfigured or unreachable never stops an order going to the kitchen.