Blog
Connecting Uzum Tezkor and Yandex Eats: Codes, Menu, Order Flow
Connecting to an aggregator has two parts. The first is the contract with the aggregator, and that's on you. The second is technical: menu, availability, order intake, statuses. In many restaurants the second part is done by hand: an operator reads the order off a tablet and types it into the till. This article is about removing that job.
MXIK/IKPU codes: the first hurdle in aggregator onboarding
Yandex Eats and Uzum Tezkor require a fiscal code for every dish: MXIK (IKPU). A dish without a code never appears in the aggregator menu. On a 120-item menu that's 120 codes. Plenty of restaurants lose a week right here.
In the laCafe admin panel, MXIK/IKPU is a separate field on every dish card. In the menuPro table editor it's a column, so 120 codes go in on one screen. Enter them once and both aggregators get them.
A tip: enter codes by category. All shashlik share one code, all drinks another. Your accountant supplies the list, you paste it in.
Menu and availability sync: the stop-list on the aggregator
Once connected, the menu flows from laCafe to the aggregator: name, price, photo, category. Visibility is per channel, so 'Hookah' shows on the dine-in menu but not on the aggregator. One menu, one place.
Availability is the biggest pain. Plov runs out at 14:00, Uzum Tezkor keeps selling it, an order arrives at 14:20, the operator cancels, the guest drops your rating. On laCafe the stop-list is live: stop a dish in iiko or r_keeper and the aggregator marks it unavailable.
- iiko: stop-list via webhook, instantly
- r_keeper: stop-list polled every 30 seconds
- No POS: stop it by hand in laBoard or the admin panel, and it propagates
The order flow: from aggregator to kitchen
A guest on Yandex Eats orders lagman and two flatbreads. The order lands in laCafe, then goes to iiko through the plugin or to laBoard. The kitchen ticket prints. Nobody reads a tablet, nobody retypes into the till.
Statuses go both ways. The kitchen taps 'ready' and the aggregator tells the courier it's ready for pickup. The aggregator cancels the order and it's cancelled on your side too. The Telegram group gets 'New order: Yandex Eats, 3 items'.
Reports show the source: how many from Uzum Tezkor, how many from Yandex Eats, from the site, from QR. Which channel is strong on which day shows up on the hourly heatmap.
Aggregator connection pricing: 300 UZS per order
On laCafe an aggregator order costs 300 UZS. 500 orders a month comes to 150 000 UZS. That's on top of the aggregator's own commission, which laCafe can't change. The branch base is 500 000 UZS, with no extra charge if you already use QR or tablets.
What does that buy? The operator's two minutes per order. 500 orders is 1 000 minutes, almost 17 hours. Errors drop as well: 'two flatbreads' no longer gets typed as 'one'.
Connection order and pitfalls
First, the contract with the aggregator and access to their merchant cabinet. That part is on the aggregator's side, and the timeline is theirs. Second, connect on the integration page in the laCafe admin panel. Third, MXIK codes, photos, channel visibility. Fourth, a test order.
Pitfalls: a dish without a photo sells badly on aggregators, and it needs a bright shot on a white background, not a phone snap from Chorsu bazaar. Names in two languages, since most aggregator customers in Tashkent search in Russian. Modifiers: 'Plov — large/small' may unfold into separate dishes on the aggregator, so check ahead.
Connecting an aggregator is a contract on one side and the plumbing on the other. laCafe takes the plumbing: MXIK codes in one place, a live stop-list, orders dropping into iiko or laBoard by themselves, statuses moving both ways. 300 UZS per order. Ready to start? Write to hello@lacafe.app.