Why one language still leaves a queue
A Dutch board is enough for the regular who already knows the snack. For a hotel guest, a visitor or a colleague who does not read the language, that board becomes a conversation. “What is this?” and “does it have milk in it?” take longer than the order. In the rush that conversation is the queue again: not because the kitchen is slow, but because one person is translating while the next guest waits. The kiosk only removes that conversation if the language is on the screen, not on a note beside the till.
The guest picks the language at the start, before the menu opens. After that the item, the extras and the sauce question continue in that language. If they switch halfway, the basket has to stay. Nothing is as clumsy as a basket that empties because someone tapped a flag. The languages you switch on are the languages you actually meet at that site. A list of twenty languages nobody chooses makes the start screen noisy. Three languages your guests use make the queue shorter.
You maintain the translation in the CMS, on the item, not as a loose file someone emails once a season. A dish whose name does not translate literally, you check yourself. A wrong dish name is worse than a missing language, because the guest then orders something other than what the kitchen makes. An automatic translation can supply the first draft. The name of the snack, the sauce and the warning stay your responsibility. That is the same work as the board in the window, only in one place.
In a hotel, or in a shop with many international guests, that first language choice is not a luxury. It is the difference between a counter that keeps translating and a counter that is left with hand-over and questions. How the kiosk fits the rest of a hospitality shift is on self-order for hospitality. For the hotel lobby, where check-in and ordering meet, look at hotels.
Allergens on the screen, before anyone pays
Guests need to be able to check which allergens are in a dish before they order. That belongs to serving food, not to an optional feature of the kiosk. On a busy counter the information often sits in a folder, or in the head of the colleague who just went on a break. The guest who does not dare to ask skips the dish, or orders it anyway. Both are a poor outcome. On the screen the information is there at the moment of choice, on the item, before anyone pays.
Show what you would also say at the counter: the allergens in that product, visible without an extra trip to the kitchen. A guest with a nut or milk allergy has to be able to see that without holding the queue. The kiosk does not replace the kitchen’s knowledge. If the CMS has the wrong allergen, that mistake is on the screen, as firmly as on a wrong board. Someone who changes the recipe changes the menu as well. One record, not a screen and a folder that drift apart.
Not every question fits in an icon. “Can this be without the sauce?” or “is there a trace of it in the fryer?” is a conversation. That conversation stays with your team. The kiosk exists so the standard information does not depend on that conversation, and so the guest who can read it does not have to wait until someone is free. Place the kiosk where a colleague can step in when the guest waves, not behind a wall. Allergens on the screen and a person nearby belong together.
In a bakery that is especially visible, because guests often look up nutrition and allergens before they take something away. That use is on bakeries. In a restaurant or a snack bar it is the same agreement, only with a shorter menu and a higher pace. The information belongs on the product, in the language the guest just chose. A Dutch warning under an English dish name is half the job.
Languages and allergens in the same menu
Keep the name, the price, the photo, the allergens and the translations on the same product. A separate translation list and a separate allergen list drift apart the moment you change a sauce. The guest then sees an English name with a Dutch warning, or a warning that belongs to the old recipe. In the CMS it is one card. Change the composition and you change the text on the kiosk, in every language you keep for that product.
Price and extras follow the same language choice, otherwise the guest does not understand the sauce question while the dish itself is translated. An upsell that only appears in Dutch is invisible or meaningless to a guest in another language. If you want that extra question, it belongs in the language of the screen, with the allergen of that extra beside it. A mustard sauce that is not on the screen is exactly the add-on that goes wrong. More on that extra question is in upsell on the order kiosk.
Sold out works the same way. Remove a product and it disappears in every language, with its allergens and its suggestions. You do not swap a sign per language. That is also why you do not run loose screens that someone translated locally. One menu, the languages you switch on, and the allergens on the product. The kiosk shows what is in the record. It does not invent it.
For a restaurant with a set menu and a dish of the day, that means the daily dish gets the same treatment as the set menu, including language and allergens. Otherwise guests in another language only order the menu that is actually complete. Restaurants and the hospitality setup are about that floor. The multilingual kiosk is not a side project. It is the same menu, readable for the guest standing in front of you.
