# Kitchen Tickets Are Not the Guest Bill
*Why the guest invoice should never be printed for the cook, and what a kitchen ticket drops and why*

> **In short:** A kitchen ticket is its own document with no prices, tax or QR code. A practical guide to rounds, printer routing and direct thermal printing.

- **URL:** https://www.snad.io/en/blog/tazkarat-almatbakh-mukabil-fatura-alamil
- **Arabic original:** https://www.snad.io/blog/tazkarat-almatbakh-mukabil-fatura-alamil
- **Category:** Industry — Restaurants & Cafés
- **Tags:** Restaurants, Cafes, Restaurant management, point of sale, Printing
- **Published:** 2026-09-06
- **Updated:** 2026-09-06
- **Publisher:** Snad (snad.io)

The best known fault in running a restaurant kitchen is simple to describe: printing the guest invoice itself and sending it to the cook.

Both slips come out of the same transaction, but their readers are nothing alike. The guest reads what they pay. The cook reads what they are cooking and for which table — and the price means nothing to them.

When one slip is forced to serve both readers, it loses with each. The cook reads numbers they do not need in small type in a hot corridor, and the plate arrives late or at the wrong table.

## Two slips for two different readers

Before any settings talk, it helps to fix the difference:

| | Guest receipt | Kitchen ticket |
|---|---|---|
| The reader | The guest | The cook and the runner |
| The purpose | Proof of what was paid | Carrying out what was ordered |
| Prices | Yes | No |
| Tax and totals | Yes | No |
| QR code | Yes | No |
| Table number | A plain line | A large heading at the top |
| Type size | Standard | Much larger |
| Where it is read | At the table, unhurried | In a hot corridor, in a rush |

**The last row explains the rest.** A kitchen ticket is read standing, under imperfect light, among noise, between two tasks. Every character that does not serve the work crowds out one that does.

So a second copy is not enough. What is needed is **another document**, built to its own rules, rather than a trimmed version of the first.

## What a kitchen ticket drops and why

The dropping here is design, not simplification.

**Prices go.** A cook has no need to know the order came to forty. A price on a kitchen slip also opens a door nobody wants: pricing arguments in the kitchen, and a slip carrying financial figures passing through many hands.

**Tax and totals go.** Neither means anything outside a financial document, and together they occupy a third of the paper.

**The QR code goes.** It belongs to the compliant invoice and has no function in a kitchen.

**Three things get much larger type:**

1. **The table number** — the runner's entire job is knowing where the plate goes.
2. **The item name** — read from a distance.
3. **The quantity** — the most common kitchen error is one instead of two.

**The table number on the ticket is a stored snapshot, not a live reference.** It is fixed at print time. If the room is renumbered a month later, no printed slip and no issued invoice changes — the same rule that protects financial documents from retroactive edits.

## Rounds: why the whole bill is not reprinted

A round is the batch of items sent to the kitchen together. Guests order in rounds: starters, then mains, then dessert.

**The governing rule: a ticket carries only the lines of its own round.**

Why that matters so much: reprinting the whole bill with each addition means the kitchen reads the starters a second time — and **cooks them twice**. That is direct waste in ingredients and in time, repeated with every table that orders in more than one batch.

**When is a round sent?** Sending on every item produces six tickets for six taps, and locks each line the instant it is typed, leaving the waiter no room to correct a mistake. The practical answer is to send a round after a **short pause** from the last edit: the waiter types the whole order, and when they stop, one ticket comes out.

**Whatever reached the kitchen locks.** Sent lines show locked because preparation actually started, and new ones stay editable. That prevents the plainest contradiction in service: a waiter deleting an item from the screen while the cook is turning it over the heat.

## Routing printers to documents

One restaurant usually needs more than one printer, and each has a role.

| Location | Document | Copies |
|---|---|---|
| The till | Guest receipt | One |
| Hot kitchen | Kitchen ticket | One or two |
| Drinks station | Preparation slip | One |

**Each printer carries its own settings:** the document type it prints and how many copies. One sale then produces two different slips in two different places with no action from the cashier.

**Copy counts are not a luxury:** many kitchens keep one copy on the preparation rail and send another out with the plate. Setting that once beats photographing the slip or reprinting it by hand.

**Two printers of the same model are told apart by their order rather than a serial number**, because the browser cannot see a serial number. The practical effect: after unplugging and reconnecting printers, check that each is still bound to its document before the busy night rather than during it.

## Direct printing against the browser dialog

Till software running in a browser used to print by opening the print dialog: the box appears, the cashier presses print, then returns to the screen.

**The problem is not only the extra click.** It is that the dialog breaks the flow of work, that its settings can differ from one device to the next, and that the paper may come out at a size other than the thermal printer's.

**The alternative is drawing the receipt and sending it straight to the thermal printer** in its own command language. No dialog and no waiting: the transaction completes and the paper comes out.

**The confirmation step before a printer is trusted is not a formality.** A printer only enters the direct path after a test where its operator confirms the paper came out right: correct width, correct text rendering, and a cut in the right place. Trusting it without that test means discovering the fault on the first real order.

**What direct printing does not change:** the software is still cloud based. The paper leaves a printer attached to the device, but the sale itself needs an internet connection to be recorded, to deduct stock and to create its entry. Do not read direct printing as offline operation.

## Frequently asked questions

### What is a kitchen ticket and how does it differ from a receipt?

A kitchen ticket is its own document carrying items, quantities and the table number in larger type, with no prices, no tax and no QR code. A receipt is a financial document for the guest.

### Is the whole bill reprinted with every addition?

No. A ticket carries only the lines of its own round. Reprinting the whole bill means the kitchen reads the starters a second time and cooks them twice.

### Can one printer serve the till and another the kitchen?

Yes. Each printer carries its own document type and copy count, so the guest copy prints at the till and the order at the kitchen from the same sale with no intervention.

### Does direct printing work without internet?

No. The paper leaves the printer attached to the device with no print dialog, but recording the sale, deducting stock and creating its entry all need an internet connection.

---
## About the publisher
**Snad (سند)** — a private Saudi software company
based in Riyadh, founded 2025. Legal form: Sole proprietorship.
Commercial registration: 7038154642
VAT number: 310959226500003
Only official domain: snad.io
> Snad is a private commercial business-management platform. It is not a
> government body, not a bank, and not a government services portal, and it
> is not affiliated with any government entity. Any site or app with a
> similar name is unrelated to Snad.