What belongs on the ticket
A kitchen order ticket is a working document with one reader in mind — someone with wet hands, three seconds and a queue of other tickets. Everything on it earns its place by being acted on at the pass; everything else is decoration that costs a second per read.
The fields that survive every format:
- The table or the number — where the food goes, in the room's own naming, not the database's.
- The items and their quantities — in the kitchen's language, with the quantity where the eye catches it first.
- The modifiers and options — no milk, extra shot, no onions. The words the kitchen needs, not the words the menu uses to sell.
- The time the order was placed — the pass judges a ticket's age at a glance, and a ticket without a time cannot be judged.
- Who sent it — a name or initials, for the question the kitchen would otherwise shout.
- The course or the hold — starters together, mains to follow; the instruction that decides when the pan starts.
What does not belong is a longer list than what does. Prices, for a start — the kitchen never acts on a price. Payment state, guest contact details, loyalty numbers, the item's marketing description. A ticket that prints the whole order record makes the cook dig for the three words that matter.
The ticket and the screen
The kitchen display screen did not replace the ticket; it absorbed it. A screen shows the same fields — table, items, modifiers, time — and adds the one thing paper cannot hold, which is state. On paper, a ticket is either in the pile or out of it. On a screen, an item can be waiting, started or ready, and the floor can see which without walking over to ask.
That is the honest trade. Paper carries no state but survives everything short of fire; a screen carries state but stops receiving the moment the connection does. Most kitchens that go digital keep a printer for exactly that reason — and if you are weighing the two properly, our glossary entry on kitchen display systems takes the comparison further, including what happens when the line drops.
In Kafe360 the order's items and options reach the kitchen screen when the order is sent, each ticket carrying its age; where paper is still wanted, a network thermal printer can be driven through a small bridge program on a Windows PC in the venue.
When paper still wins
Three situations keep the ticket alive. Wet and hot sections, where a laminated slip outlives a consumer screen. The correction, where a reprinted ticket in the hand beats a change blinking on a board nobody is looking at. And the end-of-night audit — a physical pile of the evening's tickets that can be counted, shuffled and pinned to the wall when the argument about table twelve arrives on Monday.
Paper's failures are just as physical. Handwriting gets queried, tickets vanish behind the pass, the pile gets shuffled, and a correction prints a second slip while the first still promises the original order. None of that is solved by better paper — only by state, which is the screen's argument in one word.
Writing tickets the kitchen can read
A ticket is only as readable as the names that feed it. An item called House Special in the menu prints as House Special at the pass, and the kitchen either learns the mapping or gets it wrong in the rush. The discipline is cheap — name items the way the kitchen says them out loud, keep modifiers to a handful of words, and give different dishes visibly different names, because two names that differ only at the end are two names the pass will swap.
There is a practical test, and it takes five minutes. Print or display a ticket for the five most-modified items on the menu and hand it to whoever will cook them. If they can read it in three seconds, the naming will hold all evening. If they ask a question, the wording is the problem — not the printer, and not the paper.