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
The free laBox goes on the till PC (Windows 10/11) and downloads, signature-checks and updates the iiko plugin itself. 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 through the cloud to the plugin, then 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. The plugin 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/WLCM) 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. laBox installs the plugin on the till PC; you only enter the code from the panel. Guest orders arrive through the cloud, so the till PC needs internet.
- Till: Windows 10/11 with iikoFront and laBox installed
- laBox installs and updates the plugin itself
- 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?
iikoFront itself keeps working, so the cashier enters hall orders as usual. Guest orders come through the cloud: they are kept there and reach the till once the connection is back. laBox notifies you when the connection drops and when it returns.
How much does the iiko integration cost?
There is no separate integration fee, and laBox is free. Everything is part of your laCafe package: packages start at UZS 600,000 a month with unlimited devices. You pick a package by branches and monthly orders; see /pricing.
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.
Blog
Articles on this topic
Choosing a POS: iiko, r_keeper or a Plain Tablet Till
Choosing a POS is a restaurant's longest-lived decision. Menus and interiors change; the till stays for years, with accounting, stock and staff habits hanging off it. Here is an honest comparison of three options, including "you don't need a POS yet".
Read →Dish Cost: The 30% Rule and Where It Breaks
"Keep food cost at 30%" is the most repeated rule in the restaurant trade. It is usually right, but it behaves completely differently for plov and for drinks. How to cost a dish, where to book the trim loss and how to set the price, with a worked example.
Read →Restaurant Automation: Where to Start and What to Leave Alone
Most owners start automating with the till, and that is where the expensive mistake happens. The real starting point is the guest's order path: where they sit, how they call, how they pay. Here is that path, step by step, with numbers.
Read →Connect your first table today.
We'll set up a demo with your own menu within a day.