Ticket
The kitchen's own copy of an order — what was ordered, how it's being fulfilled, and anything the kitchen specifically needs to know — distinct from the order itself.
A ticket and an order are related but not identical: an order is the whole transaction (what, payment, status), while a ticket is one artifact derived from it, aimed at the kitchen. That gap is exactly why a well-run kitchen handles a change with a replacement ticket rather than a silently edited one — the order moved on, and the first ticket is now out of date on its own.
A customer calls back fifteen minutes after ordering to add a drink. What reaches the line isn't a correction scribbled onto the first slip — it's a second, clearly marked ticket referencing the same order, with the original still sitting exactly where it was for anyone checking what the first version actually said.
The easiest mix-up is confusing a genuine replacement ticket, issued because an order changed, with an automatic reprint attempt triggered because a device failed to produce it the first time — both can put a ticket in front of a kitchen twice, but one reflects a material change and the other a mechanical failure.
When an order changes after acceptance, Dohos issues a new, clearly marked replacement ticket rather than editing the original in place, with the full mechanism covered on Orders.
BACK TO THE FULL GLOSSARY · OR THE WORKED GUIDES
Open the line.
Tell us about your restaurant. We load your menu, you place a call, and you hear it answered yourself.