> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ofatoura.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Kitchen Tickets (KOT) and Printing

> Use the web Kitchen Tickets view to track prep status, mark items ready, bump, recall, and cancel tickets, and print orders and tickets directly to your kitchen and receipt printers.

A Kitchen Ticket (KOT) is the prep order your kitchen works from. The web Kitchen Tickets view lets your kitchen and floor staff see every active ticket, track each item from pending to ready, and clear finished tickets. You can also print order receipts and kitchen tickets straight to your printers without a browser dialog.

This page covers the browser dashboard. If your kitchen uses the tablet/phone display instead, see [Kitchen Display (KDS) on the ePOS App](/epos-app/kitchen-display).

<Info>
  Open the Kitchen Tickets view from the left menu under **KOT / Kitchen**.
</Info>

## Permissions

The actions on this page require, in plain terms:

* **Manage KOT** to open the Kitchen Tickets view, mark items, start cooking, cancel tickets, and print kitchen tickets.
* **Bump KOT** to clear a finished ticket from the kitchen.
* **Recall KOT** to bring a bumped ticket back into the kitchen.
* A **manager override PIN** to recall a ticket after the recall window has passed (see [Manager Override PINs for Sensitive Actions](/staff/manager-override-pins)).
* **Delete Order** to cancel a ticket where required by your setup.

## How tickets are created

Kitchen Tickets are created automatically. When an order is moved to **KOT** status (for example from the POS or the order detail screen), the system builds the ticket for the kitchen. If you run multiple kitchen stations, the items are split by their assigned kitchen place so each station only sees what it needs to make.

A new ticket starts in one of two states depending on your settings:

* **Pending confirmation** — the kitchen confirms the ticket before starting.
* **In kitchen** — the ticket goes straight into active prep.

<Tip>
  Which starting state is used is set by your **KOT default status** option. If you want tickets to begin cooking the moment they arrive, set the default to start in the kitchen.
</Tip>

## Reading the Kitchen Tickets view

Tickets can be grouped by **table**, **order type**, or **kitchen place**, so each station or section sees a focused list. You can also search tickets and filter by status.

Each ticket shows:

| Detail               | What it tells you                                                  |
| -------------------- | ------------------------------------------------------------------ |
| KOT number           | The ticket's reference number                                      |
| Order number         | The order this ticket belongs to                                   |
| Order type           | Dine-in, takeaway, or delivery                                     |
| Table name           | The table, for dine-in tickets                                     |
| KOT status           | Pending confirmation, in kitchen, food ready, served, or cancelled |
| Items and quantities | What to make and how much                                          |
| Item status          | Cooking or ready, per item                                         |
| KOT note             | Special instructions for the kitchen                               |
| Created time         | When the ticket arrived                                            |
| Kitchen place        | The station the items belong to                                    |

### Item statuses

Each item moves through a simple flow:

<Steps>
  <Step title="Pending">
    The item is on the ticket but prep has not started.
  </Step>

  <Step title="Cooking">
    Prep is underway. Use **start cooking** to move all items on the ticket into the cooking state at once.
  </Step>

  <Step title="Ready">
    The item is done. Mark items ready one at a time as they come up.
  </Step>
</Steps>

### SLA breach indicator

If a ticket or item is taking longer than its target prep time, the ticket shows an **SLA breach indicator** so staff can see at a glance which tickets are running late. Target times are set per item or per kitchen place in your KOT settings.

## Working a ticket

<Steps>
  <Step title="Start cooking">
    Open the ticket and choose **start cooking** to move all its items into the cooking state.
  </Step>

  <Step title="Mark items ready">
    As each item is finished, mark that item **ready**. The ticket reflects which items are done and which are still cooking.
  </Step>

  <Step title="Bump the ticket">
    When every item is ready, **bump** the ticket. This marks the food ready and clears the ticket from the active kitchen list. Bumping requires the Bump KOT permission.
  </Step>
</Steps>

### Recalling a ticket

If you bump a ticket by mistake or need to send it back, you can **recall** it to return it to the in-kitchen state.

<Warning>
  Recall is only free within the **recall window** (300 seconds, or 5 minutes, by default). After the window passes, recalling a ticket requires a manager override PIN. Adjust the recall window in your KOT settings.
</Warning>

### Cancelling a ticket

You can **cancel** a ticket and record a reason, chosen from your configured cancel reason list or typed in as free text. Set up your cancel reasons under [KOT Settings, Cancel Reasons, and Marking Items 86](/kitchen/kot-settings-and-86).

## Printing orders and kitchen tickets

You can send an order receipt (the customer bill) or a kitchen ticket directly to a printer without opening a browser print dialog. Print from the POS, the order detail screen, or the Kitchen Tickets view using the print action.

### How direct printing works

oFatoura supports several printer types, and falls back gracefully when a direct printer is not reachable:

<Columns cols={2}>
  <Card title="Direct thermal (ESC/POS)" icon="printer">
    Sends the formatted ticket straight to a network or USB thermal printer. Fastest and most reliable for kitchen and receipt printing.
  </Card>

  <Card title="Windows spooler" icon="monitor">
    Routes the ticket through a shared Windows printer when you print from a computer connected to that printer.
  </Card>

  <Card title="Browser print fallback" icon="globe">
    If a direct printer is not available, the standard browser print dialog opens so you can still print.
  </Card>
</Columns>

Every print is recorded as a print job log entry, so you have a history and can reprint when needed.

<Tip>
  Choose between direct printing and the browser print dialog, and set your paper width (characters per line), in your printer settings. See [Printer Configuration and Devices](/settings/printers-and-devices).
</Tip>

### Multi-kitchen routing

If you run multiple kitchen stations, a single order's kitchen ticket is split by kitchen place and each part is sent to that station's printer. A grill ticket goes to the grill printer, a bar ticket to the bar printer, and so on, with no manual sorting.

To set this up:

* Create your stations under [Setting Up Kitchen Stations](/kitchen/kitchen-places).
* Assign each menu item to a station under [Assigning Menu Items to Kitchens](/kitchen/routing-items).
* Assign a default printer per kitchen place in your printer settings.

<Note>
  Multi-kitchen routing depends on the multi-kitchen feature being enabled for your setup.
</Note>

## Related

<CardGroup cols={2}>
  <Card title="Viewing Kitchen Tickets" icon="list" href="/kitchen/web-kot-views">
    All-kitchens and per-kitchen ticket views.
  </Card>

  <Card title="KOT Settings and 86" icon="settings" href="/kitchen/kot-settings-and-86">
    Default status, recall window, cancel reasons, and marking items 86.
  </Card>

  <Card title="Printer Configuration" icon="printer" href="/settings/printers-and-devices">
    Set up printers, transport, and paper width.
  </Card>

  <Card title="Receipts and Printing Basics" icon="receipt" href="/essential-setup/receipts-and-printing-basics">
    Receipt formatting and printing fundamentals.
  </Card>
</CardGroup>
