4

Our company makes software for restaurants but we are facing a problem. we dont know the correct words in English for two things

  1. The message that goes to the kitchen, this is printed on a receipt printer in the kitchen and contains what the kitchen will start cooking. our best guess is KOT, Kitchen order ticket.

KOT / bong in our language can look like this

  1. what do you call these extra messages that can be on the KOT or what its called. This can be on meat for example, "Rare", "medium" or maybe "extra fries" or "No onions". these messages modify the things the customer has ordered. we do not agree on this one. the guesses are. "KitchenNotification", "KitchenMessage" or "CookingMessage"

Do anyone that maybe works or have worked in restaurants tell us the correct terms for this,

thank you :)

  • 2
    The message received by the kitchen (which used to be torn from the wait staff's notebook of course) is usually referred to as a _check_ or _ticket_. I'm not sure there's a specific term for 2. I would refer to them as _notes_, literally something the chef should taken note of/notice. – ElendilTheTall Dec 09 '15 at 09:53
  • Not having worked in a kitchen, I'd have called it an 'order' if it's given to the kitchen staff to cook. I would associate 'check' with the bill given to the customer. As for the second one, I doubt there's an official term for it, unless there's some other software that has a large portion of the market and help to standardize the language. Anything like 'Notes', 'Info', 'Extra', or similar would probably work. – Joe Dec 09 '15 at 10:08
  • yea i agree, i think ticket or order is best for the first one. – Mattias Delin Dec 09 '15 at 10:10
  • we use check or bill to describe what the customers gets as you say :) – Mattias Delin Dec 09 '15 at 10:10
  • You might even want to survey existing software in the niche you're working on ... and see what terms they've assigned for those concepts. If nothing else, it'll make it easier on restaurant staff to convert to your software if you can help standardize. (especially if you call the ticket for the kitchen staff what other software calls the bill for the customer, or something else that would require people to need to un-learn the old software). – Joe Dec 09 '15 at 10:12
  • Yea i have been trying to see other pos software, the things i learned are that most use "Tickets" or "Orders" and i see alot of buttons called "Notes" or "Messages" but i dont know if those buttons do the same that we do. – Mattias Delin Dec 09 '15 at 10:38
  • "KOT" or "KOTs" would have unfortunate alternate meanings in some languages ;) – rackandboneman Dec 09 '15 at 13:03
  • Ticket is the piece of paper the kitchen gets. The order is what is printed on the ticket. I would just call #2, notes. Are you writing a user's manual for English speakers? – Escoce Dec 09 '15 at 14:28
  • Also, are you Swedish? – Escoce Dec 09 '15 at 14:29
  • @Escoce Yes i am swedish – Mattias Delin Dec 11 '15 at 09:35

1 Answers1

5

This is a rather long answer, as terms need to be applied correctly and it is unclear what your software actually can do.

In a professional setting, the customer makes an order and the wait staff creates tickets which are handed to the expediter. The expediter receives the tickets from the wait staff (or the printer) and sets the pace and flow in the kitchen and communicates which menu items need to be cooked. The expediter is also responsible for verifying that the wait staff receives the correct plates with the correct items from the ticket. The wait staff again verifies the plate with the order (not the ticket!).

"Orders" and "tickets" are therefore two different things. Your kitchen printer generates "tickets" for the kitchen, but your wait staff enters "orders" into the system. When this is tightly coupled, "one order - one ticket", it is therefore often combined as "Kitchen Order Ticket". This tight coupling is a bad habit though, invented by software developers who couldn't imagine a n:m relationship. A smart system is able to generate multiple kitchen tickets per table or order, taking f.e. preparation times and courses into account.

The item you print is therefore either a Kitchen Ticket or Kitchen Order Ticket, depending on whether you can print multiple tickets per order or not.

Any deviation from the default menu is usually a "Special Order". Let's assume all people ordered their menu "without onions" for a week, then the inventory management needs to know that there is no need to buy onions, because there weren't any used. If you merely checkout the default menu, someone will buy new onions and you end up with pounds of onions discarded.

The ticket should therefore generate a "Special Order" with descriptive text what is special about it, so this menu can be treated differently by the expediter, cashier and inventory manager. Cooks are busy cooking, tickets are the problem of other people.

If it is not a deviation from the item, but a necessary detail, for example the doneness of a steak - it is an "Item note" or "Order note", which is printed right by the ordered item. If it is a steak restaurant though, it would be more correct to have multiple entries in the system. While the customer would order the menu "#64 rare", the wait staff would enter f.e. "#641", while "#642" would be #64 medium-rare - as I said, advanced systems usually know the preparation times of dishes and a note can't be used to tell the system to calculate this. If your wait staff has to enter a note manually for every order, you have done something wrong as restaurant manager.

An "Expediter message" is an additional information for the expediter from the wait staff. This message is not about the items, but about everything that affects the work of the expediter - for example:"Customer is a Michelin restaurant tester!" This is printed apart from the menu items and you wouldn't want them to appear on the customer receipt. As your target group might be more mundane restaurants, "Expediter message" would confuse Aunt Annie's diner, so "message" would be sufficient. A message is text for someone else the customer should not see.

A note is something you write down to not forget it. The wait staff would write a note for themselves, f.e.:"Customer does not drink alcohol." when an alcoholic appetizer was offered. This way the wait staff can make appropriate suggestions later. As you can see, this information would be useless for the expediter.

John Hammond
  • 3,094
  • 11
  • 21
  • Thank you very intressting reading. i think we have enough to make our decision, thank you! – Mattias Delin Dec 11 '15 at 10:38
  • 1
    I have generally heard the OP's #2 (what you call a "Special Order" or "Order Note" here) referred to as a *modifier* or simply *mod*. That could be a local thing, but it was consistent at the places I worked (including the one where I worked as expo). – logophobe Dec 11 '15 at 19:24
  • i think that sounds good. and its good to know that you have worked in different places where they used this. – Mattias Delin Dec 15 '15 at 09:26