POS
iiko integration: QR menu, tablets and website on top of your POS
laCafe does not replace iiko. The plugin runs inside iikoFront: a guest orders from a QR code, tablet or website, the order opens on the till like any other, prints to the kitchen and closes in iiko.
What connects
laBranch and the iiko plugin are installed on the till PC (Windows 10/11). The plugin runs inside iikoFront; there is no extra server. Catalogs come from iiko, so nothing is entered twice.
- Products, prices and categories
- Modifiers (with min/max)
- Tables and halls
- Waiters
- Payment types
- Stop list, live via webhook
How an order flows
A guest at table 7 picks plov and tea from the QR menu. The order goes to laBranch, then through the plugin into iikoFront: an order opens on table 7 and a ticket prints in the kitchen. If the guest adds shashlik later, it lands on the same order, not a new one.
- 1. Guest orders from QR / laTable / website
- 2. laBranch opens the order in iikoFront or appends to the open one
- 3. The kitchen ticket prints
- 4. Guest asks for the bill; the pre-check prints
- 5. Payment (cash, card, Payme/Click/UzQR/laPay) closes in iiko under its own payment type
- 6. Webhooks push every iiko change back to laCafe
What stays in sync and what the guest sees
Change a price in iiko and it changes on the QR menu and tablet. A dish hits the stop list and the guest cannot tap it: greyed card, no button. The waiter sees the order in iikoFront as if they typed it themselves. iiko reports stay as they are; every sale is still there.
- Prices, names, categories: from iiko
- Stop list: from iiko, live
- Order status and total: from iiko back to laCafe
- Photos, GIF, video, nutrition, 3 languages: from the laCafe admin (iiko has no such fields)
Honest limits
The plugin talks to iikoFront only. iikoOffice (back office, cost price, stock) is not touched; cost price is entered in laCafe by hand. The laCafe team installs remotely and needs access to the till PC. If the internet drops, orders keep reaching the till over the LAN and the cloud catches up later.
- Till: Windows 10/11 64-bit with iikoFront installed
- Plugin install: with the laCafe team, remotely
- Stock and cost price are not pulled from iiko
- New dishes are created in iiko, not in laCafe
Questions & answers
Does the QR menu work with iiko?
Yes. A QR order opens in iikoFront on that table. Prices and the stop list come from iiko. The waiter never retypes anything.
Do I have to replace iiko?
No. iiko stays your POS: reports, shifts and fiscal receipts all remain in iiko. laCafe adds the guest layer on top: QR, tablets, kiosk, website, Telegram.
How fast does the stop list update?
The moment a dish goes on the stop list in iiko, a webhook arrives. The dish closes on QR and tablets right away. History stays in the stop-list report in the admin.
What happens if the internet goes down?
Tablets and laWaiter talk to laBranch over Wi-Fi; they do not need the internet. Orders keep landing in iikoFront. Only QR (the guest's phone) and online payment depend on the internet. Cloud sync resumes when the line is back.
How much does the iiko integration cost?
There is no separate integration fee. Branch base is 500,000 UZS/month plus what you use: laTable 100,000, laBoard 100,000, laWaiter 100,000, table QR 10,000. A 12-table cafe on QR only pays 620,000 UZS/month.
Do modifiers work (extra meat on plov, say)?
Yes. Modifier groups come from iiko with min/max. When a guest picks 'extra meat' on the QR menu, the order lands in iikoFront with that modifier.
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.