How to Launch a Restaurant Delivery Website in 6 Steps

Why your own delivery site: aggregator commission and the customer base

Aggregators have their place. A new guest discovers you on Uzum Tezkor or Yandex Eats. But you pay commission on the second and third order too, and the guest belongs to the aggregator, not to you. Phone number, address, favourite dish: all theirs.

Your own site changes that equation. A guest who came through an aggregator moves to your site via a card tucked into the bag. Their next order carries no commission. The guest CRM shows a profile, order history, cashback and the source: site, QR, iOS, Android, Telegram.

An honest caveat: the site doesn't bring guests by itself. Instagram, the card in the bag, a line on the table QR saying 'next time, order to your door': that's your job. The site only takes the orders.

Step 1: site and domain — guest.lacafe.app or your own

The laGuestWeb site is created in the admin panel. The default address is chorsu-osh.guest.lacafe.app. If you have your own domain, say devcafe.uz, you connect it and the SSL certificate is issued automatically. Sites per organisation are unlimited: one per brand, or one per branch.

Personalisation comes with a live preview: logo, cover image, colour, text. Pick the service modes: delivery, pickup, dine-in, reservations. Guest sign-in: none, SMS, or Telegram. For delivery, SMS or Telegram is the better choice, since the courier needs a phone number.

Step 2: draw delivery zones on the map

A zone is a polygon on the map. It has a name, a price, and an on/off switch. For example: 'Yunusabad' 15 000 UZS, 'Chilanzar' 20 000, 'Sergeli' 30 000. A zone can be served by several branches, and a branch can cover several zones.

When a guest enters an address, the system picks the nearest branch on its own. An order from Chilanzar goes to the Chilanzar branch, not Yunusabad. If the address falls outside every zone, the checkout says so and the order isn't accepted.

• Delivery price per zone, with a 'free from ... UZS' threshold
• Minimum order amount, so you don't dispatch a courier for a single 50 000 UZS samsa
• Switch a zone off temporarily: close Sergeli in the rain and it vanishes from the site
• Map provider: Google, Yandex or OSM, whichever is more accurate in your district

Step 3: courier — your own or a TaxiMillenium call

Up to 10 orders a day, your own courier is fine: a guy on a moped, paid per shift. The order shows in the admin panel or in iiko, the courier takes the address and goes. Simple, but at 30 orders one courier isn't enough, and keeping two on payroll is expensive.

laCafe has TaxiMillenium courier dispatch: one button in the admin panel or in the iiko plugin, with live status. For Yandex Delivery, Uzum Delivery and Noor you enter your account details. Dispatcher rules, deciding which order goes to which service, aren't there yet; coming soon. For now it's connection only.

Step 4: online payment — Payme, Click, UzQR, laPay

Prepayment matters in delivery. When a guest has already paid for an 80 000 UZS order, the chance of a door that never opens drops. Payme, Click and UzQR connect separately, with bank details per branch. laPay puts Payme, Click, Paylov, Uzum and cards behind a single QR.

Keep cash too. In Tashkent plenty of guests still pay at the door. Leave a 'cash' option on the site and make sure the courier carries change.

Steps 5–6: the order flow and the cost math

Where does a site order land? With iiko, the plugin puts it into iiko and a receipt prints. With laBoard, it hits the till tablet. The Telegram group gets a 'New order' message, routed by branch. Statuses: sent, cooking, ready, handed over. The guest follows along on the site.

Pricing: branch base 500 000 UZS a month (already paid if you use QR or tablets) plus 1 500 UZS per site order. At 300 orders a month that's 450 000 UZS. Compare that with the aggregator's cut: 300 orders × average bill × their percentage. The numbers speak for themselves.