Welcome your guests with a multilingual menu.

Start with your business’s default language, then choose the additional languages your guests need. A coastal restaurant might begin with Turkish and English before adding German or another language based on its visitors. Complete, accurate content in a few useful languages can be easier to maintain than opening every option before the translations are ready.

Orvunai provides localized guest-interface controls for supported languages. This does not automatically translate your recipes or descriptions. Interface controls and restaurant-written content are separate: your business enters translations for menu titles, categories and products in the available editing fields.

You can edit translations at menu, category and product level. If a local dish name is part of its identity, keep the name and add a brief description that visitors can understand. Explain preparation or accompaniments only when they reflect what your kitchen actually serves. A clear sentence can be more useful than an unfamiliar literal translation.

Do not introduce new claims about ingredients, preparation or portions simply to make a description sound natural in another language. A familiar foreign dish name may refer to a different recipe. In particular, prepare dietary and allergen wording from information your business has verified; changing the language does not make uncertain information more reliable.

When translated content is unavailable, the relevant field is displayed in the menu’s default language. This means a product does not disappear simply because its description has not yet been translated. However, a mixture of languages can confuse guests. Before promoting a language, check the categories and product details in that version of the menu.

Adding a new product may require more than completing the default-language fields. Include additional languages in your regular menu maintenance. When a recipe or description changes, review the other versions too. Guests should be able to choose a language without being shown an older explanation of what arrives at the table.

A menu has a chosen currency, and prices use that currency. Selecting English does not convert a Turkish lira price into dollars, nor does choosing a language create a separate price list for foreign visitors. Make sure guests can understand which currency the displayed amounts use, regardless of the language they select.

For example, a restaurant in Türkiye can offer English descriptions while keeping its prices in Turkish lira. The wording changes; the amount and menu currency remain the same. If you prepare a different menu in another currency, your business sets those prices. Orvunai does not perform automatic foreign exchange conversion.

Use the preview to select each language and check categories, search, product cards and details. Look for longer names that are hard to follow, missing descriptions and prices that are difficult to spot. For right-to-left languages such as Arabic, review reading direction and the flow of product names as well as the translated wording.

Evaluate the assistant alongside the translations in the published menu. A translated interface does not establish that all restaurant information is complete. After launch, use questions from guests and your service team to identify confusing dish names or explanations. Treat translation as part of maintaining the menu, rather than a task that ends with the first publication.