Blog
QR Menu iiko Integration: What Syncs, What Doesn't
You run iiko and want guests to order from a QR or a tablet. One question matters: does the order land in iiko by itself, or does the cashier retype it? This article covers how the laCafe plugin works inside iikoFront, what syncs, and where things can trip you up.
How the iiko integration works: a plugin inside iikoFront
laCafe does not replace iiko. It sits on top of it. A plugin installs into iikoFront on the till PC, with the laBranch local server next to it. The table tablet (laTable), the QR (laQR) and the waiter phone (laWaiter) connect to laBranch, and laBranch talks to iiko through the plugin.
The link runs both ways. A guest at table 7 orders lagman, and iiko opens an order on table 7 while the kitchen printer prints the ticket. The cashier closes the order in iiko, and the tablet frees the table. Not two systems, one flow.
What syncs from iiko: menu, prices, stop-list
Catalogs come from iiko: dish name, price, category. Change a price in iiko from 42 000 to 45 000 and the QR menu follows. Photos, descriptions in three languages, nutrition data and video are added in the laCafe admin panel, since iiko has no such fields.
The stop-list is live. The cook marks 'Plov — sold out' in iiko, and plov vanishes from laTable and laQR. Guests never order something that's gone, then hear 'we're out' from the waiter. For a choyxona this is the most useful part: plov runs out at 14:00 and leaves the menu at 14:01.
- Order create, add items, pay, close — all inside iiko
- Receipt and kitchen printing through iiko's printers, no extra hardware
- Catalogs and stop-list flow from iiko to laCafe
- Webhook: a change in iiko reaches the tablet and QR right away
How a tablet or QR order reaches iiko
The guest scans the QR on table 12 or picks up the laTable tablet. Menu, cart, 'Order'. The order goes over the local network to laBranch, and the plugin creates it in iiko on table 12. If the guest adds tea later, the plugin appends it to the same order instead of opening a new one.
Payment goes two ways. The guest taps 'Request bill', Dilshod comes over and closes it in iiko with cash or card. Or the guest closes it alone: pays online via Payme, Click, UzQR or laPay, and the plugin marks the order paid in iiko.
Modifiers pass through as well: 'Shashlik — 2 skewers, extra onion' shows up in iiko exactly like that. Min/max limits are set in laCafe.
iiko integration pitfalls: what to expect
The first trap is the till PC. The plugin lives inside iikoFront, and laBranch runs on Windows 10/11 64-bit. If iikoFront is closed, the plugin sleeps too. When the cashier shuts the PC down at night, the first morning order waits. Turn off sleep mode.
Second: Wi-Fi. laTable and laWaiter find laBranch only on the local network. The guest Wi-Fi and the till Wi-Fi need to be one network, or the router must route between them. Many choyxonas run guest Wi-Fi in 'isolation' mode, and then the tablet can't see the till.
Third: a messy iiko nomenclature. 'Plov', 'PLOV' and 'plov (large)' show up on the QR as three separate dishes. Spend an hour cleaning iiko before integrating. It's not a laCafe problem, but the guest is the one who sees it.
Launch checklist and pricing
There's no separate fee for the iiko integration. It's part of the branch base at 500 000 UZS a month. On top: QR table 10 000, laTable 100 000, laBoard 100 000, laWaiter 100 000, whichever you need. r_keeper works the same way, except modifiers aren't there yet; coming soon.
- Clean the iiko nomenclature, merge duplicates
- Till PC: Windows 10/11 64-bit, sleep mode off
- Tablets and the till on the same Wi-Fi network
- Test: one tea → appears in iiko → kitchen ticket prints → closed
- Stop-list test: stop a dish in iiko, watch it disappear from the QR
You've spent years tuning iiko; there's no reason to drop it. The laCafe plugin sits inside iikoFront, and orders, stop-list and payments move both ways. Preparation is an hour of cleanup in iiko and a Wi-Fi check. The rest we connect in a day: hello@lacafe.app.