Skip to main content

Kitchen ticket settings

What this is for

Three settings under Settings › KOT that change how the kitchen works. Small screen, real consequences.

The tickets themselves are explained in Kitchen tickets.

Default KOT Status

What a ticket starts as when a cashier or waiter sends it.

OptionMeaning
PendingCreated, waiting to be picked up.
CookingAlready being prepared.

Cooking is right for most restaurants. A human sent the ticket deliberately, so there's nothing left to confirm — starting at Pending just means someone taps a button before any food happens.

Choose Pending only if your kitchen genuinely triages incoming tickets before starting.

Default Customer KOT Status

The same setting, for tickets created by customers — the ordering site, QR ordering, a kiosk.

It's separate for a good reason, and the two usually shouldn't match.

SituationSensible choice
Orders need accepting before cookingPending
Orders should start immediately — kiosk, paid onlineCooking

A ticket a cashier sent has been seen by a human. One that arrived from a phone at 7:42 pm hasn't. Starting customer orders at Pending means someone accepts before the kitchen commits — which is what you want when you might be out of something, closing shortly, or slammed.

For a kiosk where the customer is paying at the screen, Cooking is usually right — holding it for confirmation adds a delay the kiosk existed to remove.

Whichever you pick, make sure somebody is watching. A queue of Pending tickets nobody accepts is food nobody is cooking, and the customer has no idea.

Enable Item Level Status

Off by default: a whole ticket moves through its statuses at once.

On: each dish carries its own — Start Cooking, Mark as Ready, with Undo if something is marked early.

Turn it on when:

  • Courses leave the kitchen at different times.
  • Several stations work the same ticket.
  • You want to see which single item is holding a table up.

Leave it off when:

  • One kitchen sends complete tables together.
  • Your team is small and the ticket is the unit of work.

It's more taps. The extra information has to be worth them, and in a small kitchen it usually isn't.

SettingWhere
Kitchens and routingKitchens and stations
Printers per kitchenReceipts and printers
Cancellation reasonsOrder settings
Menu item images on the POSImages and file storage

Good to know

  • These apply per branch.
  • Changing a default affects new tickets only. Tickets already open keep their status.
  • Item-level status can be turned on and off freely — it doesn't lose anything.
  • The kitchen screen is standard in every plan; more than one kitchen is an add-on. See Using the kitchen screen.

Next

Customer site