- 2DOUBLE SMASH
- NO PICKLE
- Home
- Ticket Designer
Ticket Designer
Design the ticket for the station that has to read it.
Type scale, density, color rules, item grouping, modifier emphasis and alert thresholds — set per station and previewed with your own orders. Because a ticket read at six feet over a grill has nothing in common with one read at the pass.
01/Why one layout fails
Most kitchen displays were designed for a screenshot, not a kitchen.
Stock kitchen display software ships one ticket layout. It looks excellent in a product tour, on a 27" monitor, at a desk, in even light. Then it goes into a restaurant where the grill screen is eight feet up behind a heat lamp, the fry cook reads it sideways, and expo needs to see eight tickets at once.
The result is a workaround culture: people lean in, squint, ask each other, and eventually put the printer back. The software did not fail because it lacked features. It failed because it was illegible at the distance it was actually used.
The ticket designer treats layout as an operational setting rather than a brand decision. Every station gets what it needs.
What you can set per profile
- Type scale — item, modifier and header sizes, independently
- Density — tickets across the board and how much air is inside each one
- Grouping — items in the order rung, grouped by course, or grouped by station
- Modifier emphasis — inline, indented, bold, inverted, or its own line
- Allergen rules — which keywords escalate and how loudly they render
- Channel color — a color per channel so drive-thru is identifiable across the room
- Thresholds — warn and late minutes, and what changes when they are crossed
- Sorting — oldest first, threshold-first, or grouped by channel
- Header content — number, table, guest name, server, item count, channel
02/Three stations, three layouts
The same order, rendered for three different jobs
Big type, two across
Item names at maximum scale, modifiers only where they change the cook, no channel labels, no guest names. Readable from across the line without stopping.
Dense, complete, grouped
Eight tickets across, every modifier spelled out, station completion badges on each line, and the all-day count pinned in the corner.
Threshold-first sorting
Channel color on the whole ticket, aggressive warn and late minutes, sorted so the oldest car is always top-left regardless of when it fired.
Illustrative. In the designer, the preview renders at the real type scale you have selected.
03/Setting it up
A short, opinionated guide to legible tickets.
Nobody gets this right on the first try, so here is what tends to work, drawn from how operators actually end up configuring their boards.
Start from the sightline, not the screen size
Stand where the cook stands. If you cannot read the item name without moving your head, increase the type scale and reduce the tickets across — in that order. A 32" screen showing six tickets nobody can read is worse than a 10" tablet showing two they can.
Cut what the station cannot act on
The grill does not need the guest's name, the table number, the server, the channel or the price. Every element you remove makes the remaining ones bigger for free. Expo needs all of it; the line does not.
Make modifiers louder than item names
Cooks recognise item names from shape alone after a week. Modifiers are what actually get missed, and they are what generate remakes. Indent them, do not shrink them.
Set thresholds you would actually act on
If everything is orange, nothing is. Set the warn minute at roughly your current median and the late minute somewhere near your 90th percentile — both numbers are in your timing reports — then tighten from there once the board is calm.
Review it after two weeks
The layout you design in an office is a hypothesis. Go back after a fortnight of service, ask the cooks what they lean in to read, and change that one thing.
04/Questions