Articles · Nov 13, 2026
POS Integration with Delivery Apps: Menu, Prices and Stop List in 5 Steps
A step-by-step setup for cafés and restaurants in Uzbekistan: one menu in the POS, channel prices that cover the commission, an automatic stop list and order reconciliation at shift close. Includes worked examples with plov and lagman and a table of common mismatches.

You can run your menu, prices and stop list on Yandex Eats and Uzum Tezkor from a single POS in five steps. First, build one menu with IKPU codes and portion weights. Then set channel prices using the formula "base price ÷ (1 − commission)", turn on auto-stop based on stock from your recipe cards, check the stop list after every menu upload, and reconcile orders against receipts when you close the shift. Media reviews put platform commissions at 20–30% of the order value. So every order for a dish you've already run out of hurts both your margin and your rating.
What to prepare before you connect: Yandex Eats and Uzum Tezkor
An integration means two contracts and one setup. You sign a contract with the platform, and your POS provider connects the platform to your menu. The process differs between the two platforms.
- Yandex Eats. You request the integration through support in the partner app. By then, your menu must meet the platform's rules: dish photos, portion sizes and names that follow Yandex requirements. Otherwise, the request will be rejected. The minimum number of daily orders required to connect in Uzbekistan hasn't been confirmed, so check it with support before you start the setup.
- Uzum Tezkor. You sign the contract with the platform yourself. Technical connection details come through your Tezkor manager. We couldn't find any public documentation for POS systems. Uzum Tezkor keeps partners' financial documents in Didox, and you'll need them for reconciliation.
Keep in mind that platforms treat stop lists and cancellations as a measure of partner quality, not just your internal problem. Uzum Tezkor openly lists reducing stop lists and partner-caused cancellations as a goal for its product team.
Step 1. One menu in the POS: IKPU codes, portion weights, photos
The core rule: each dish card lives in the POS, and the platforms get a copy of it. If you edit a name or ingredients directly in the aggregator's dashboard, the next upload will either overwrite your changes or leave the platform out of sync with the POS.
- Write names and descriptions the way the platform requires, for example "Chaikhana plov, 350 g".
- Add the weight or volume of the portion for every item.
- Use one photo per dish across all platforms.
- An IKPU code (Uzbekistan's product and service classification code) is required for every dish. Under Presidential Resolution No. PP-5252 of October 4, 2021, since January 1, 2022 online cash registers and virtual registers can't issue receipts without IKPU codes. The code from the dish card goes onto the receipt, so a menu mistake becomes a receipt mistake. To learn how to choose codes for dishes, sets and combos, see "IKPU codes for restaurants in 5 steps".
- Set up modifiers and combos in the POS, not on the platform: "lagman + tea", "no onion", "double meat".
The same rule applies to chains: one dish card for all locations.
Step 2. Channel price: divide by (1 − commission), don't add a percentage
The most common mistake is to raise the price by the commission rate: add 30% for a 30% commission. But the commission is charged on the new, higher price, so this markup doesn't cover it. To keep your dine-in price after the commission, use this formula:
Aggregator price = dine-in price ÷ (1 − commission)
Take the rate from your contract. The 20–30% figure is a benchmark from a delivery market review, not an official rate. The rate can also depend on whose couriers deliver the order.
| Commission | Multiplier | Markup on dine-in price | Plov, dine-in 42,000 UZS | Lagman, dine-in 38,000 UZS |
|---|---|---|---|---|
| 20% | ÷ 0.80 = ×1.25 | +25% | 52,500 UZS | 47,500 UZS |
| 25% | ÷ 0.75 = ×1.333 | +33.3% | 56,000 UZS | 51,000 UZS (50,667, rounded up) |
| 30% | ÷ 0.70 = ×1.4286 | +42.9% | 60,000 UZS | 55,000 UZS (54,286, rounded up) |
Here's what a "simple" markup does: plov at 42,000 UZS is raised by 30% to 54,600 UZS. The platform takes 30%, or 16,380 UZS, and the restaurant keeps 38,220 UZS. That's 3,780 UZS less than the dine-in price on every portion. At 100 portions of plov a week, that adds up to 378,000 UZS, and that's just one item.
Whether to pass the commission on to customers in full or in part is the owner's call. But use the formula either way, so you can see the real margin on each channel. Keep channel prices in a separate price list and review it every time you change dine-in prices, so delivery doesn't get stuck on old prices.
Step 3. Auto-stop by stock: it all depends on the recipe card
An automatic stop list works simply: the POS knows the stock level, and when it hits zero, the item disappears from the platform. In Yandex Eats API integrations, stock levels are sent for dishes, modifiers and combos, and an item at zero is hidden from listings. But automation is only as accurate as your kitchen's stock records. Without recipe cards and recorded deliveries, auto-stop won't work.
- Count portions by the limiting ingredient. For plov, that's not the rice in storage but the cooked plov in the kazan. Track it as a semi-finished product: you cooked a kazan of 40 portions, so record an output of 40 portions.
- Track semi-finished products separately. For lagman, the limit is hand-pulled noodles, not flour. Count stock by the prepared noodles.
- Stop the modifier, not the whole dish. Out of cheese? Stop the "with cheese" option and keep the burger on sale.
- A combo stops when its scarcest component runs out. No samsa means the "samsa + tea" set is unavailable too.
- Keep a buffer. If dine-in and delivery share one kazan, take the dish off the platforms a little before it hits zero. Otherwise, the last app order will arrive at the same time as a guest in the dining room.
- Record deliveries before opening. A delivery not recorded in the morning shows a false zero, and a best-seller stays on the stop list.
To learn how to build a recipe card with portion output, see "Recipe cards in 5 steps: a plov and lagman example". In AliPos, every sale deducts ingredients based on the recipe card. Check which availability data is sent to each specific platform when you set up the integration.
Step 4. Check the stop list after menu uploads and manual stops
There are two traps here that rarely get mentioned.
Full menu upload. The documentation of at least one integration service states that a full menu upload ignores the separate stop list and makes unavailable items available again on the platform. You update prices in the morning, and the lagman that ran out yesterday is "in stock" again.
Indefinite manual stop. In the Yandex Eats dashboard, you can manually stop a dish, category or option for a set period or "Indefinitely". In the second case, the item stays hidden until someone turns it back on. The cook stops manti on Friday, and on Wednesday they're still missing from the app.
- After every full menu upload, open both platform dashboards and compare the stop list with the POS.
- Set manual stops with a specific end time, such as "until end of day", not "indefinitely".
- Assign one person per shift to manage the stop list, so the cook and cashier don't edit it at the same time.
Step 5. Reconcile orders at shift close
Reconcile three sources: orders in the platform dashboard, receipts in the POS, and payouts against the platform's documents. The manager checks the first two every shift. The accountant checks payouts and documents (Uzum Tezkor keeps them in Didox) for each platform payout period.
| Mismatch | Sign | What to do |
|---|---|---|
| Order on the platform but not in the POS | The order was accepted on a tablet or by phone and not entered | Find the order and enter it. Find out why the integration didn't accept it |
| Two receipts for one order | The order came through the integration and was also entered manually | Void the duplicate according to POS rules and record the reason |
| Order for a stopped dish | Stock wasn't recorded, or a manual stop didn't reach the platform | Check the recipe card and delivery records, log the case in the shift log |
| Cancellation caused by the restaurant | Out of an ingredient, kitchen couldn't keep up | Record the reason. Compare with the platform's cancellation report |
| Order price doesn't match the channel price | An old price list was uploaded to the platform | Re-upload the menu and repeat the check from Step 4 |
| Item hidden for no reason | A forgotten "indefinite" stop | Turn the item back on or set an end time |
The cost of these mistakes builds up quietly. Say you lose 4 plov orders a day at 60,000 UZS each. Over a month, that's 120 lost orders and 7.2 million UZS in revenue, not counting guest ratings.
How much aggregator integration costs in AliPos
AliPos connects to Yandex Eats, Uzum Tezkor and Yemak. The integration is available from the Pro plan at $59 per month, which includes the delivery module, multi-branch support and a call center. Connection and setup cost a one-time $100, covering documents, a menu built to the platform's standards and configuration. After that, the integration costs $10 per month. Inventory, recipe cards and stock counts, which auto-stop relies on, are also included in Pro. Aggregator orders go straight to the POS, with no separate tablets. Prices are listed in US dollars and paid in UZS at the Central Bank rate. Learn more on the integrations page and in the pricing calculator.
FAQ
How should I mark up prices for the commission: add 30% or divide by 0.7?
Divide by 0.7. The commission is charged on the app price, so adding 30% doesn't cover a 30% commission. The correct markup in this case is +42.9%.
Why did a dish reappear on the platform after a menu update?
In some integrations, a full menu upload can reset the stop list, as described in one service's documentation. After every upload, compare the stop list in the dashboards with your POS.
What should I do if I get an order for a dish on the stop list?
Contact the platform following its rules and offer a substitute or a cancellation. Then find the cause: a delivery may not have been recorded, or a manual stop may not have synced. Check your contract to see who covers the cost of the cancellation.
How many daily orders do I need to integrate with Yandex Eats in Uzbekistan?
No threshold has been confirmed for Uzbekistan, though one exists in other countries. Check with Yandex Eats support before you start the setup.
How do I connect my POS to Yandex Eats and Uzum Tezkor?
First, the restaurant signs a contract with the aggregator, then the POS integration is set up. In AliPos, the integration works from the Pro plan: a one-time $100 for connection and setup, then $10 per month.
Want to see how your menu, delivery prices and aggregator orders look in one POS? Leave a request at alipos.uz/en/connect. A manager will call you back, learn about your restaurant and walk through your case.
