Foodhub for Business is now Touch2Success.

touch2success

Running a multilingual kitchen: how to get orders right across languages

In a kitchen where the team speaks several languages, order mistakes often start with shouted instructions, handwritten notes and modifiers in small print. Fix it by moving orders onto a screen set to a language the cooks read well, using colour, numbers and position for anything urgent, writing menu items and modifiers the same way every time, and training with real test orders.

By the Touch2Success KDS team · Published · 9 min read

Key points

  • The risk is in the small words. No, extra and without change a dish completely, and they are easy to miss in a second language.
  • Colour and numbers need no translation. A red ticket is late in every language.
  • Set each screen to the language its station reads best. Touch2Success KDS runs in English, Spanish, French, Albanian, Chinese and Turkish, with a second language for the kitchen.
  • Train by doing. A test order before service teaches more than a page of instructions.

Written by the Touch2Success KDS team. We make a kitchen display system, so read this as a vendor's view. Where we describe other products, we say where the information came from.

Where language trips a kitchen up

A kitchen can run well with four first languages on the line. Cooking is mostly watching and doing, and the vocabulary is small. The trouble starts when an order has to cross from one person to another in a hurry.

Where it happensWhat goes wrongWhy language makes it worse
Shouted ordersA call from the pass is half heard over the extraction fans.In a second language you can't guess the half you missed.
Small words on the ticketNo onions is cooked with onions.The dish name is familiar. The short word in front of it is not.
Handwritten notesNobody can read the pen on the slip.Handwriting is hard enough in your first language.
AbbreviationsO/S, w/o, xtra and the till's own shorthand.Abbreviations are local habits that nobody teaches.
Questions that don't get askedA cook is unsure, guesses, and carries on.Stopping to ask in front of everyone is harder in a second language.
Allergy informationA warning is passed on by word of mouth.The one message that must not change is the one being translated on the spot.

Notice that none of these is about cooking skill. They are all about how the order is carried. That is good news, because it is the part you can redesign.

What a screen can say without words

A good fix for a language problem is to need less language. A kitchen display system helps here because much of what it shows is not text at all.

SignalWhat it tells the cookOn Touch2Success KDS
Colour of the ticketHow urgent the order is.The header starts green, turns yellow when the order is running late and red when it is late.
A number in a boxHow many to cook.Each quantity sits in a black count, and a running count totals every item across open orders.
Colour of a modifierThat something about this dish has changed.You set a colour for any keyword. To begin with, no is red, less is yellow, extra is green and on side is grey.
A red borderStop and read this one carefully.Priority and Allergy orders get a red border and a strip on the ticket.
A logoWhere the order came from.The delivery partner's logo sits on the ticket.
PositionWhat to cook next.Tickets can be sorted by time remaining, with priority tickets kept at the front.
SoundA new order has arrived.You choose the new order sound and its volume, and a separate sound for priority orders.

Once a cook has learned that a coloured modifier means the dish has been changed, they are looking for it on every ticket. They still have to read the word. But they know to read it.

Put each screen in the language its station reads

Buttons and labels matter too. Hold, Recall, Priority and Complete are pressed in a split second, and a cook who has to translate first will hesitate.

Touch2Success KDS runs in six languages: English, Spanish, French, Albanian, Chinese and Turkish. You can also set a second language for the kitchen team. The language is the first thing the Setup Wizard asks on a new screen, and it changes straight away.

Because the wizard runs on every screen, the choice is made screen by screen. Think about who stands in front of each one.

  • The pass or packing screen is read by whoever also talks to drivers and customers. English usually makes sense there.
  • A prep station is read by the one or two people who work it. Pick the language they read fastest.
  • A shared screen such as the one at the pass should follow the majority. Ask us on a demo how the second kitchen language can help everyone else.

Screen language is only half of it. The other half is how your items and modifiers are written in the first place, because that is what lands on the ticket. A few habits make them readable to someone working in their second or third language.

  • One name per dish, everywhere. If the menu says Chicken Burger, the till should not say Chk Brgr and the cooks should not have their own name for it.
  • Lead with the word that differs. Spicy Chicken Wrap and Chicken Wrap are told apart by the first word, not the last.
  • Use the same few words for every change. No, extra, less, on side. Four words to learn, not forty.
  • Make common requests into buttons. A modifier arrives spelt the same way every time. A typed note is at the mercy of whoever typed it.
  • Cut the shorthand. If an abbreviation has to be explained to a new starter, write it out.
  • Put numbers as digits. 2 is read faster than two.

This pays off on paper as well. If you want the full anatomy of a ticket, see how to read a kitchen order ticket. For the words kitchens use out loud, the KDS glossary is a good thing to hand a new starter.

Allergies: the message that can't be translated on the spot

An allergy warning passed along by voice is retold at every step. In a mixed-language kitchen, each retelling is also a translation. That is too many chances to change it.

Put it on the ticket instead, where every cook who handles the order can read it. On Touch2Success KDS an order can be flagged as Allergy, which adds a red border and a strip on the ticket, and item notes appear right under the dish they belong to. Then agree one house rule that needs no words: a red-bordered ticket is never started until the person cooking has read the whole thing.

A screen does not replace your allergen procedures. It makes sure the warning arrives in one piece. More in handling allergen orders on a kitchen display.

Training a mixed-language team

Written instructions are a weak way to train a kitchen, and weaker still across languages. Show, then let people do it.

  1. 1

    Run test orders before service

    Put an order through and let each person try every action once: begin it, tick off an item, complete it, bring it back. It takes a couple of minutes.

  2. 2

    Teach the colours first

    Green, yellow, red on the header. Then the modifier colours. These carry most of the meaning and are quick to learn.

  3. 3

    Teach four actions, not forty

    Tap to begin. Double-tap, or press bump, to complete. Recall if it was bumped too soon. Hold if it isn't ready to cook. Everything else can wait.

  4. 4

    Pair people up for the first busy shift

    Put a confident reader next to a newer one. Questions get asked quietly, in whichever language works.

  5. 5

    Make the text big enough

    Reading a second language at a distance is slower. Quick Settings on Touch2Success KDS changes the text between Small, Medium and Large from the kitchen screen itself.

  6. 6

    Check the first week

    Watch for the same ticket being recalled again and again, or one item being remade. It usually points to one word nobody has explained.

There is a fuller plan for the first days in training kitchen staff on a KDS and going live.

What to ask a KDS vendor about languages

Not every vendor lists its languages on its public pages. A list would not tell you much anyway. These questions will.

  • Which languages does the kitchen screen itself run in? Not the website, and not the till. The screen the cooks read.
  • Can each screen have its own language, or is it one setting for the whole shop?
  • Is there a second language for a team that reads two?
  • What is shown without words? Timers, colours, counts and flags work in any language.
  • Can I see it with my own menu on it, in the language my team needs?

The last one matters most. Thirty seconds of watching your grill cook read a ticket tells you more than a feature list. For how Touch2Success KDS compares on everything else, see the feature-by-feature comparison.

A checklist for a multilingual kitchen

  • Orders reach the cooks in writing, on a screen or a ticket, never only by voice.
  • Each screen is set to the language its station reads fastest.
  • Modifiers use the same few words every time, and stand out in colour.
  • Allergy orders are flagged on the ticket, not passed on by word of mouth.
  • Item names are the same on the menu, at the till and in the kitchen.
  • Text is large enough to read from where people stand.
  • Every new starter runs a test order before their first service.
  • Settings are locked, so a screen can't be changed by accident.

Running several sites with different teams? See Touch2Success KDS for groups and franchises, how it fits takeaways and quick-service kitchens, and the full Touch2Success KDS page.

Questions people ask

Which languages does Touch2Success KDS support?

+

Touch2Success KDS runs in English, Spanish, French, Albanian, Chinese and Turkish, and you can set a second language for the kitchen team.

Can different kitchen screens use different languages?

+

The language is chosen in the Setup Wizard on each Touch2Success KDS screen, so you pick it screen by screen. A prep station can be set to the language its cooks read fastest.

How do I change the language on a kitchen display?

+

On Touch2Success KDS the Setup Wizard asks for the language first on a new screen, and the screen changes straight away. Everything chosen in the wizard can be changed later in Settings.

How do I reduce order mistakes when kitchen staff speak different languages?

+

Send orders to the kitchen in writing rather than by voice, set each screen to the language its station reads best, use colour for modifiers and urgent orders, write items and modifiers the same way every time, and train with real test orders before service.

How should allergy orders be handled in a multilingual kitchen?

+

Put the warning on the ticket so every cook who handles the order can read it, rather than passing it on by word of mouth. On Touch2Success KDS an order can be flagged as Allergy, which adds a red border and a strip on the ticket. A screen supports your allergen procedures but does not replace them.

Do colour-coded tickets help staff who don't read English well?

+

They can. Colour, numbers and position carry meaning without words. On Touch2Success KDS a ticket turns yellow when it is running late and red when it is late, quantities sit in a black count, and modifiers are highlighted in the colours you set.

Who wrote this

The Touch2Success KDS team

We build and support Touch2Success KDS, the kitchen display system for restaurants and takeaways that take orders with Touch2Success. Everything we say about our own product is on the Touch2Success KDS page. Spotted something out of date? Tell us and we'll fix it.

A multilingual kitchen?

See it in your team's language.

Book a demo and we'll show you Touch2Success KDS in English, Spanish, French, Albanian, Chinese or Turkish.

Book a demo