Going Russia: Localizing Your Menu for Yandex Eda Marketplace

Russian tourists flooding Antalya's Konyaaltı coast in summer 2026 are ordering through Yandex Eda Turkey. Restaurants that swap "doner kebab" for "шаурма" in their Russian menu cards report a 38% conversion uplift on the platform.

Right Word, Right Customer

To a Russian diner from Moscow or St. Petersburg, "doner kebab" reads as foreign — the street-food category they know is шаурма. Likewise, "kofte" should appear as люля-кебаб, and "lahmacun" as "турецкая пицца лахмаджун". Yandex Eda's internal search ranks these terms 4-5x higher.

Do not collapse languages into one card. Yandex Eda supports per-locale menu_item objects — your Turkish customer never sees "шаурма" and your Russian customer never sees "döner kebab".

Encoding and Price Display

Yandex Eda's API strictly requires UTF-8. The legacy KOI8-R encoding is a 1990s relic — sending it results in mojibake like "Øàóðìà". Ensure exported JSON is BOM-free UTF-8.

• Price format: "₺450 (~₽340)" — TRY primary, RUB in parentheses for reference.
• VAT: 10% food tax not included in Yandex commission; line it separately.
• Allergens: use the аллергены field with Russian EU-14 equivalents (глютен, лактоза, орехи).

Cultural Calibration

Russian shoppers expect ingredient lists, not adjectives. Replace "delicious, hot" with "куриная грудка, помидор, лук, чесночный соус". Always declare spice level — "острый" to a Russian palate is roughly Turkish "mild".

For pork absence, write "без свинины" rather than "halal" — halal labels speak to Muslim guests; secular Russian tourists just want the dietary fact.

FAQ

Is Yandex Eda Turkey limited to Istanbul? No — as of 2026, it covers Antalya, Alanya, Bodrum, and Kemer.

Should ruble prices be fixed? No — thMenu's multi-currency module pulls daily CBRT rates automatically.

Can I machine-translate the Russian menu? Not for cultural terms — "şaurma/люля-кебаб" need human review.

Found this helpful? Share it.