Guests order themselves
A laTable tablet on the table or a QR code: menu, cart, order, no waiter needed. The order goes straight to the POS and the kitchen. Nothing stays in a notebook.
Restaurant
Restaurant automation: hall, waiters and POS in one system
Guests order from a tablet on the table or their own phone. The waiter sees the call on his phone. The order lands in iiko or r_keeper. The owner sees it all in one panel.
Familiar pains
- Friday night: 25 tables, 4 waiters. A guest sits with a raised hand for 15 minutes and still has no menu.
- The waiter writes the order in a notebook. One item gets lost on the way to the POS. The kitchen cooks the wrong dish and the guest sends it back.
- Asking for the bill takes 10 minutes, getting it takes 5 more. The table does not turn and the queue at the door walks away.
- A price changes in iiko and the printed menu is out of date. Guests order dishes from the stop list and the waiter apologises.
- The owner calls the cashier at night: 'How much did we do today?' Nobody knows which waiter sold what.
What you get
Calls reach the right waiter
laWaiter shows only calls and bill requests from that waiter's own tables. Table 8 calls, Dilshod sees it on his phone, nobody else gets pinged.
iiko and r_keeper stay in place
The plugin runs inside iikoFront: create, add to, pay and close orders, print receipts and kitchen tickets. With r_keeper, orders sync every 10 seconds and the stop list every 30. We do not replace your POS.
The bill in one tap
Guests request the bill from the tablet or QR, or close it themselves: cash, card, Payme, Click, WLCM. The table frees up 15 minutes sooner.
The menu always matches the POS
Prices, names and the stop list come live from the POS. A sold-out dish disappears from tablets and QR at once. Every dish has three languages, photos, nutrition facts and modifiers.
The owner sees it on their phone
Hourly heatmap, average ticket, waiter performance, table turnover. Every call and new order arrives in Telegram. No need to phone the cashier.
Recommended setup
Recommended setup
01
laTable
A tablet on the table: guests order, pay and call the waiter themselves.
02laQR
A QR code on the table: guests open the menu on their own phone, order and call the waiter.
03laWaiter
The waiter’s phone app: own tables, calls, bill requests, shifts.
04laBoard
The restaurant’s own POS tablet. Runs on the laCafe cloud, no PC required.
05laBox
A free agent for the branch computer. It installs, updates and keeps alive the apps you enable in the panel.
06laGuest
The restaurant’s own website and mobile app: menu, delivery, pickup, reservations. On your own domain, unlimited sites.
Price example
Monthly cost for a 20-table restaurant
A 20-table hall, one branch, about 1,000 orders a month. Start covers 500 orders: 600,000 + 500 × 1,200 = UZS 1,200,000, the same as Light. So Light it is: UZS 1,200,000 a month, with loyalty and SMS campaigns included. 20 laTable tablets, laBoard and 3 laWaiter phones add nothing to the bill, since devices are unlimited in every package. If you already run iiko, you do not need laBoard.
- 1 branch, ~1,000 orders: Light — UZS 1,200,000/month
- Tablets, table QR codes, laWaiter phones: included, unlimited
- At 1,500 orders: 1,200,000 + 300 × 1,000 = UZS 1,500,000
Questions & answers
How much does restaurant automation cost?
You pick a monthly package by branches and orders: Start UZS 600,000 (1 branch, 500 orders), Light 1,200,000 (3 branches, 1,200 orders), Standart 2,400,000 (5 branches, 3,000 orders). Tablets, table QR codes and waiter phones are unlimited in every package. A 20-table restaurant with ~1,000 orders a month fits Light at UZS 1,200,000.
Does it work without iiko?
Yes. laBoard is a POS tablet of its own: hall view and order screen. Tablets and laWaiter connect to it. If you add iiko later, we connect it through the plugin.
Does it work with r_keeper?
Yes, through the RK7 XML API: orders every 10 seconds, stop list every 30. Modifiers for r_keeper are not there yet — coming soon. We do not replace r_keeper; we add a guest layer on top of it.
What happens when the internet goes down?
laCafe runs in the cloud, so tablet, QR and website orders wait until the internet is back. Your iiko or r_keeper POS keeps working on its own, and waiters punch orders straight into it. laBox on the POS computer tells you the moment the connection drops and when it returns.
Tablet or QR — which one should I pick?
Both do the same: menu, cart, order, waiter call, bill. QR runs on the guest phone. With laTable an iPad or Android sits on the table with big photos and video. Most venues use QR in the main hall and tablets in VIP rooms. Price is not a factor: both are unlimited in every package.
Do I still need waiters?
Yes, but they run around less. Ordering and the bill sit with the guest; the waiter carries dishes and answers calls. laWaiter also has shift open/close, own tables and order taking for guests who prefer to order through a waiter.
Blog
Articles on this topic
Restaurant Trends 2026: Which Ones Pay and Which Are Just Fashion
Every year brings a trend list, and half of it does nothing for a restaurant. Below are five shifts, each with an honest answer to "do you actually need this?". Written for the Uzbek market, not for New York.
Read →Restaurant Terms: 50 Words Explained in Plain Language
Restaurant vocabulary is a mixture: some words from Russian, some from English, some local. A new manager confuses food cost with waste and prep with production. Here are fifty of the most-used terms, defined and placed in context.
Read →Restaurant Reports: Six Numbers, Each Changing One Decision
A till produces hundreds of numbers, which is exactly why nobody reads them. Six reports are enough for day-to-day decisions. Each answers one precise question: when is it busy, who sells more, which dish is dead weight, how often does a table turn.
Read →Connect your first table today.
We'll set up a demo with your own menu within a day.