Digital ordering platform for restaurants

Guests order themselves. You just cook.

A tablet or QR on the table, your own delivery site, Telegram and AI — every order lands straight in iiko or r_keeper. Payme and Click payments. The register keeps working when the internet drops.

  • iiko
  • r_keeper
  • Payme
  • Click
  • Yandex Eats
  • Uzum Tezkor
  • Telegram

One system, three sides

In the dining room, outside it, and on top of it — one admin panel

Competitors usually do one thing: a QR menu or delivery. laCafe gives a restaurant its whole digital layer.

01

In the dining room

A tablet on the table (laTable), a QR on the guest's phone (laQR), a self-service kiosk (laKiosk), a waiter app (laWaiter), a register tablet (laBoard). Call a waiter or ask for the bill in one tap.

02

Outside

Your own website — on your own domain if you like. Delivery zones drawn on a map, the nearest branch picked automatically, TaxiMillenium courier dispatch. Yandex Eats and Uzum Tezkor from a single menu.

03

On top

Two-way sync with iiko and r_keeper. Reports: hourly heatmap, menu engineering, table turnover. Drop a photo of your menu into ChatGPT or Claude — it enters the dishes for you.

How it works

Live in a single day

laBranch goes on the register PC, the menu arrives from iiko on its own. Results from the first shift.

  1. 01

    Install laBranch

    Once, on the register PC (Windows). Pair it to the restaurant with a code from the admin panel. Comes with the iiko plugin.

  2. 02

    The menu arrives

    Dishes, prices and the stop-list from iiko or r_keeper — automatically. Add photos and translations in the admin panel.

  3. 03

    QR or tablet on the table

    Print the QR (it never breaks) or set a tablet in kiosk mode. Pairs with a 6-letter code.

  4. 04

    Guests order

    They choose, add a note, send. The order goes to the kitchen; the bill closes with Payme or Click.

Pricing

No plans. Pay only for what you use.

A base fee per active branch, a monthly fee per device, a small fee per external order. Disabled branches aren't billed.

A 12-table cafe on QR only: 500,000 + 12 × 10,000 = 620,000 UZS/month.

Open the calculator
  • Branch base500,000 UZS / month
  • laTable, laWaiter, laBoard100,000 UZS / device / month
  • laKiosk250,000 UZS / month
  • laQR table10,000 UZS / table / month
  • Website order1,500 UZS / order

Honest comparison

How is this different from delever, Dastur-xon, BROS?

Each has a strength. We wrote down when they fit and when we do.

See comparisons

Frequently asked questions

Do I have to replace iiko or r_keeper?

No. laCafe doesn't replace your POS — it adds the guest layer on top. The iiko plugin runs inside iikoFront; r_keeper connects over the RK7 API. Orders, stop-list and payments sync both ways.

What happens when the internet drops?

The register keeps working. laBranch is a local server inside the restaurant: tablets and QR connect to it over Wi-Fi, orders sit in an encrypted local database, and everything syncs to the cloud when the connection is back.

How much does it cost?

There are no plans. Branch base 500,000 UZS/month, laTable/laWaiter/laBoard 100,000 UZS per device, laKiosk 250,000, laQR 10,000 UZS per table, website order 1,500 UZS. A 12-table cafe on QR only is 620,000 UZS/month.

I only need a QR menu, no tablets. Possible?

Yes. laQR is a QR on the table: the guest orders on their own phone, calls a waiter, asks for the bill. No tablet needed. 10,000 UZS per table per month.

How fast can we go live?

One day. laBranch goes on the register PC, the menu arrives from iiko by itself, the QR gets printed. Guests order from the first shift.

Connect your first table today.

Write to us on Telegram or email — we'll set up a demo with your own menu within a day.