Articles · Nov 19, 2026

Aggregator vs. Your Own Delivery: 8 Criteria and the Math on an 80,000 UZS Order

On an 80,000 UZS order, an aggregator takes 16,000–24,000 UZS in commission, and packaging costs another 3,000–5,000 UZS. We compare aggregators, your own website and a Telegram bot across 8 criteria and show when your own channel pays off.

Aggregator vs. Your Own Delivery: 8 Criteria and the Math on an 80,000 UZS Order

At a 20–30% commission, an aggregator takes 16,000–24,000 UZS from an 80,000 UZS order, and packaging costs another 3,000–5,000 UZS. That leaves 51,000–61,000 UZS before food costs. Your own website or Telegram bot has no aggregator commission, but you need couriers, advertising and a steady flow of orders. That's why many cafes use both: the aggregator brings in new guests, and your own channel keeps them coming back for repeat orders.

Below you'll find a formula, a worked example on an 80,000 UZS order, and 8 criteria for comparing channels. The numbers in the example are illustrative. Plug in your own commission rate, food cost and courier cost, and you'll get the answer for your venue.

Inputs: where the numbers come from

Market participants estimate that delivery services in Uzbekistan charge 20–30% of the order value, and packaging adds 3,000–5,000 UZS per order (zira.uz, 2025). These are estimates, not a published rate. Your actual rate depends on your contract and on whether you join promotions. Before you run the numbers, pull up your contract and last month's reconciliation statement: divide all deductions by turnover, and that's your real rate.

The math on an 80,000 UZS order: formula and table

The formula works for any channel:

Order margin = price − channel commission − packaging − delivery you pay for − card processing − food cost

Assumptions for the example (replace with your own):

  • order: 2 portions of plov, lagman and a drink for 80,000 UZS;
  • food cost per recipe card: 40,000 UZS (50% food cost);
  • packaging: 4,000 UZS;
  • your own courier: roughly 15,000 UZS per trip if the guest doesn't pay for delivery;
  • card processing in your own channel: roughly 1% (check the rate in your payment provider contract).
Item, UZSAggregator 20%Aggregator 25%Aggregator 30%Website/bot, cafe pays for deliveryWebsite/bot, guest pays 10,000 for delivery
Order price80,00080,00080,00080,00080,000
Channel commission16,00020,00024,00000
Packaging4,0004,0004,0004,0004,000
Courier paid by cafe00015,0005,000
Card processing (approx. 1%)000800800
Food cost40,00040,00040,00040,00040,000
Order margin20,00016,00012,00020,20030,200

The key takeaway: your own channel doesn't win because there's no commission. It wins depending on who pays the courier. If you cover delivery in full, your own bot earns almost the same margin as an aggregator at 20%. If the guest pays for at least part of the delivery, the gap reaches 10,000–18,000 UZS per order.

8 criteria: aggregator, website or Telegram bot

CriterionAggregatorOwn websiteTelegram bot
1. Cost per order20–30% commission plus packagingCard processing, courier, packagingCard processing, courier, packaging
2. New guestsBuilt-in user baseAdvertising and word of mouth onlyAdvertising, in-venue QR codes, word of mouth only
3. Control of guest dataContacts stay with the platformThe database is yoursThe database is yours
4. Time to launchContract, menu and photos to platform standardsSlowest: design, development, paymentsFaster than a website, no-code builders available
5. Fixed costsAlmost none, it's all in the commissionHosting, support, advertisingSubscription or support, advertising
6. Kitchen loadPrep speed affects your rankingYou manage peaks yourselfYou manage peaks yourself
7. Refunds and disputesUnder platform rulesUnder your public offerUnder your public offer
8. Receipts, data, compliancePlatform handles part of itAll on you: receipts, consent, public offerAll on you: receipts, consent, public offer

1–2. Costs and new guests

An aggregator takes a commission on every order but brings you a ready stream of guests. For a new cafe or a location in a new neighborhood, it's one of the fastest ways to get orders coming in. A sign it's time to run the numbers: the aggregator's share of your delivery revenue is high, but the order margin in your reports is low.

3. Control of guest data

As a rule, an aggregator doesn't give you the guest's phone number, so you can't invite them back. The platform may also show your competitors in the same search results. In your own channel, every order grows your database: after a month, you can send regulars a Friday plov offer. There's one condition: you need the guest's consent (more on this in the compliance section).

4–5. Launch and fixed costs

A Telegram bot launches faster than a website, and guests don't need to install a separate app. A website takes longer to build, but people can find it through search. Be sure to account for monthly costs: the bot or website subscription, advertising and a salaried courier. You pay these even if only 10 orders come in a month.

6. Kitchen load

On an aggregator, prep speed affects your ranking and conversion. If the dining room is full at 1 p.m. and orders keep pouring in from the platform, the kitchen may fall behind, and your ranking suffers. In your own channel, you can cap orders per hour or pause delivery temporarily. Every channel needs a shared stop list: an order for lagman that has run out ends in a cancellation and a lost guest.

7. Refunds and disputes

If an order arrives cold or incomplete, aggregator disputes are settled under the platform's rules. Check your contract for compensation terms. In your own channel, you write the rules. Spell out in your public offer how guests report a problem, how long you're responsible for the order, and how you refund (replacement dish or refund to card). Keep a compensation log so you can see what share of revenue it takes.

8. Receipts and legal obligations

In your own channel, you are the seller. The Tax Committee reminds businesses that they must use an online cash register or virtual cash register and issue a receipt with a QR code and fiscal mark. Card-to-card transfers without a receipt violate tax law (gov.uz, Tax Committee). For delivery, the receipt is either printed at the cafe and sent with the order, or issued by the courier on handover.

Website or Telegram bot: which to start with

  • A bot suits cafes that already have regular guests and an active Telegram channel. It launches quickly and makes reordering easy. A QR code linking to the bot on tables and delivery bags helps turn dine-in guests into delivery customers.
  • A website makes sense if you want to attract guests from search queries like "plov delivery Chilanzar" or you run a chain with several delivery zones.
  • Both channels make sense once your own channel has plenty of orders and one storefront isn't enough.

Important: don't lure aggregator guests away with flyers in their orders until you've checked your contract. It may prohibit this. It's safer to bring dine-in guests and your Instagram and Telegram followers into your own channel.

When your own channel pays off: the break-even point

Minimum orders per month = your channel's fixed costs ÷ (your channel's margin − aggregator margin)

Example: fixed costs for the bot, advertising and part of a courier's salary come to roughly 3,000,000 UZS a month. The margin difference at a 25% aggregator rate with the cafe paying for delivery is 20,200 − 16,000 = 4,200 UZS. So you need 3,000,000 ÷ 4,200 ≈ 715 orders a month, or about 24 a day. If the guest pays 10,000 UZS for delivery, the difference grows to 14,200 UZS, and the threshold drops to 212 orders a month, roughly 7 a day.

Count only orders that genuinely came through your own channel. If a guest simply switched from dining in to delivery, that's not new revenue.

What to do before December 12, 2026: checklist

Law No. ZRU-1173 of 10.09.2026 amends the e-commerce law and takes effect on December 12, 2026 (full text on lex.uz). According to analyses by accounting and business publications, it introduces the concept of an order aggregator. Primary liability for defects stays with the seller, meaning the cafe, while the platform operator may bear secondary (subsidiary) liability under certain conditions. Check the wording against the text of the law before changing any contracts.

Your own guest database falls under the Law "On Personal Data" No. ZRU-547 of 02.07.2019 (lex.uz). Consent must be obtained in a form that lets you prove it was given. If the purpose changes, for example from "order delivery" to "promotional messages", you need new consent. For more on messaging, see "SMS Marketing Requires Consent from November 1: 6 Steps for Cafes".

What to do:

  1. Calculate your real aggregator rate for last month, including all deductions.
  2. Run your own numbers through the margin formula for your 3–5 best-selling dishes.
  3. Add a data processing consent checkbox to your bot or website, plus a separate checkbox for marketing messages.
  4. Publish a public offer covering delivery, timing, refunds and compensation.
  5. Set up a fiscal receipt for every order in your own channel.
  6. Review your aggregator contract in light of ZRU-1173: who is responsible for quality and disputes.

What not to do: accept payment by transfer to a personal card without a receipt, collect guest phone numbers without consent, or drop the aggregator before your own channel has a steady flow of orders.

How to run all delivery channels from one POS

When orders come from several places, the biggest loss is confusion: an order from a platform goes to the kitchen, but the dish is already on the stop list. The AliPos Pro plan ($59 a month) includes a delivery module, aggregator integrations and a call center, so aggregator orders land in a single POS and on the kitchen display. Setting up the integration costs a one-time $100, then $10 a month. We covered how to sync menus, prices and stop lists in "POS Integration with Aggregators: 5 Steps". A customer database (CRM) is available from the Standard plan, and a branded mobile app for guests costs a one-time $1,000 on the Pro plan and above. Learn more on the AliPos for delivery page.

FAQ

Which is more profitable for a restaurant: an aggregator or its own delivery?

You may keep more per order in your own channel, especially if the guest pays for delivery. But your own channel only pays off with a steady flow of orders. Aggregators work better for launching and reaching new guests; your own channel works better for repeat orders.

How much is left from an 80,000 UZS order after commission and packaging?

With a 20–30% commission and 3,000–5,000 UZS for packaging, you keep 51,000–61,000 UZS. Food cost still has to come out of that.

How many orders a day does your own delivery need to break even?

Divide your channel's fixed costs by the margin difference versus the aggregator. In our example, that came to 7 to 24 orders a day, depending on who pays the courier.

Can you work with an aggregator and your own channel at the same time?

Yes. Keep a single menu and a shared stop list, and compare prices across channels with commission factored in.

Do you need a fiscal receipt when delivering with your own courier?

Yes. A receipt with a QR code is printed at the cafe and sent with the order, or issued by the courier on handover.

Want to calculate the margin of each channel using your real numbers? Check out AliPos plans or submit a request. We'll call you back, show you how platform orders land in a single POS, and help you pick the right plan for your format.

#доставка#агрегаторы#прибыль кафе#Telegram-бот#выбор решения
All articles

Your next shift starts here

Try AliPos, and you’ll be surprised you ever worked any other way!

Leave a request: we’ll call back in 15 minutes and set up the till in 1 day.

+998 55 704-99-99Live in 1 day

Get a demo — we’ll help set up your menu

Enter the full number: +998 XX XXX-XX-XX

We’ll call you back within 15 minutes

  1. 1Video
  2. 2Request
  3. 3Online demo
Want this in your venue?