What drives the price
The QR menu tier is a menu with photos, prices and languages behind a QR code on the table, plus table ordering. The Ordering and delivery tier adds a cart, Payme, Click and Uzum payments, delivery with the courier on a map, rewards and notifications. The Chain tier is for several branches: a kitchen display, a courier app with routes and payouts, and sales analytics by dish, hour and branch. Table reservations, tips and reviews, delivery status on the phone’s lock screen, AI dish recommendations and aggregator orders in one window are separate lines in the configurator. The total depends most on the number of branches and on integrations with the till and courier services.
How the work runs, week by week
We start with the menu: photos, descriptions, modifiers, languages and the stop list. If you run iiko, R-Keeper or Poster, we pull the menu and prices from the till so nobody maintains them twice. The QR menu goes live first, because it takes load off the waiters straight away. Then we connect payments, delivery zones and fees, couriers and rewards. Before launch we test the system on a real shift: table orders, delivery, cancellations, refunds, a Friday evening. You see a working version every two weeks. The next tier plugs in on top of the running one: one venue first, then delivery, then the chain — no rewrite.
Local specifics: iiko, payments, languages, Telegram
Guests in Uzbekistan read menus in Uzbek, Russian and English, so the languages are built in from day one rather than translated later. Payment is Payme, Click and Uzum in two taps, with a fiscal receipt through the online cash register. The iiko, R-Keeper or Poster integration sends table and delivery orders straight to the till and the kitchen with no manual entry, and returns the stop list. Couriers can be called through Yandex Delivery, or you can run your own team with an app. For delivery the fastest start is a Telegram bot or Mini App: the guest installs nothing, and your own app makes sense once you have plenty of regulars.
Risks and common mistakes
The first mistake is a menu that lives apart from the till: a dish runs out and guests keep ordering and paying for it. The second is retyping orders from a bot or website into the till: at peak hour that means errors and lost orders. The third is commissioning a large app before testing delivery demand with a bot or Mini App. The fourth is ignoring peak load: a system that slows down on Friday night is worse than none. The fifth is your own delivery with no rewards or notifications: the guest has no reason to leave the aggregator. Finally, poor photos: with a QR menu guests choose with their eyes, so food photography pays back fastest.