QR menu and delivery app for restaurants Restaurant and delivery

A guest scans the QR code on the table, sees a menu with photos in their language, orders and pays without waiting for a waiter. The same catalogue powers delivery — in Telegram, a Mini App or your own app — with no aggregator commission on every order, a courier on the map and rewards that bring the guest back.

Price
from $2,500
Timeline
from 2 weeks

Price and deadline are fixed in the contract before work starts

Cone. Marble

What is included

  • 01A QR menu with photos, prices and languages
  • 02Table ordering and payment via Payme, Click and Uzum
  • 03Delivery: cart, address on a map, courier and estimated delivery time
  • 04Rewards and “order ready” notifications
  • 05Integration with iiko, R-Keeper or Poster
  • 06Aggregator orders in one window
  • 07A kitchen display and a courier app for chains
  • 08Sales analytics by dish, hour and branch

Who it is for

  • Restaurants and cafés where guests wait for a waiter at peak hours to order and pay
  • Venues with delivery that hand aggregators a cut of every order
  • Chains that need one menu, a kitchen display and analytics by branch
  • Coffee shops and fast food, where speed and repeat visits matter most

Three levels and prices

Pick the level that fits the task and budget. The exact scope is assembled in the configurator and fixed in the contract.

QR menu

QR menu with photos, prices and languages

$2,500–5,000

≈ UZS 30M · from 2 weeks

Ordering and delivery

Cart, payments, delivery, rewards

$12,000–25,000

≈ UZS 144M · from 8 weeks

Chain

Branches, kitchen, courier app, analytics

$35,000–80,000

≈ UZS 420M · from 16 weeks

UZS amounts are indicative, at the Central Bank of Uzbekistan rate on 14.11.2026. Contracts are in USD, or in UZS at the rate on the invoice date.

In detail

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.

What the contract says

2%

for every day we are late

If we are late, your invoice drops by 2% a day, up to 10% of the contract. So we only name deadlines we can keep.

1

company per niche per city

For a year we do not take on your competitor in your city. What we build for you does not end up next door.

10%

refund after an outside review

Bring your own engineer. They check the code against the contract. If a contracted item is missing, we refund 10%.

Questions

How much does a QR menu and restaurant app cost?

A QR menu starts at $2,500, with a timeline from 2 weeks: a menu with photos, prices and languages behind a QR code, plus table ordering. Ordering and delivery with payments, couriers and rewards, and the Chain tier with a kitchen display and courier app, cost more; their prices are in the tier table. The amount is fixed in the contract.

How quickly can a QR menu go live?

From 2 weeks. Delivery and chain set-ups take longer; the timeline of each tier is in the table. You see a working version every two weeks; for every day of delay the invoice drops by 2%, up to 10% of the contract.

We already use iiko. Will it work?

Yes. We integrate with iiko, R-Keeper or Poster: the menu, prices and stop list come from the till, and table and delivery orders land there with no manual entry. It is a separate line in the configurator.

How much does our own delivery app cost?

Delivery is part of the Ordering and delivery tier: cart, Payme, Click and Uzum payments, courier on a map, rewards and notifications. You can start with a Telegram bot or Mini App, which is faster and needs no install. Your own app and a courier app are added once delivery has grown.

Can aggregator orders come into one window?

Yes, as a separate module, for aggregators that provide API access to orders: orders from aggregators and from your own delivery arrive on one screen, so the kitchen does not juggle tablets.

Why run our own delivery if aggregators exist?

An aggregator brings new guests but takes a cut of every order and keeps the customer base. Your own delivery pays off with regulars: there is no aggregator commission, and rewards, newsletters and order history stay with you. Most venues run both channels, with orders from each landing in one window.

Other solutions

Practice: Industry solutions