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 hall keeps running when the internet drops.
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, laPay. 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 with the laBranch server built in. No PC required.
05laBranch
A local server on the POS PC. Works without internet, talks to iiko and r_keeper.
06laGuestWeb
The restaurant’s own website: menu, delivery, pickup, reservations. On your own domain, unlimited sites.
Price example
Monthly cost for a 20-table restaurant
Two options. QR only: branch base 500,000 + 20 tables × 10,000 = UZS 700,000. Add 1 laBoard (100,000) and 3 laWaiter (3 × 100,000 = 300,000) — UZS 1,100,000 a month. A tablet on every table: 500,000 + 20 laTable × 100,000 + 100,000 + 300,000 = UZS 2,900,000 a month. No plans — you pay only for the devices and tables you actually use. If you already run iiko, you do not need laBoard.
- QR only + laBoard + 3 laWaiter: UZS 1,100,000/month
- 20 laTable + laBoard + 3 laWaiter: UZS 2,900,000/month
- Delivery through your own site: UZS 1,500 per order
Questions & answers
How much does restaurant automation cost?
Branch base is UZS 500,000 a month, a table QR is 10,000, laTable 100,000, laWaiter 100,000, laBoard 100,000. A 20-table restaurant pays 1,100,000 with QR or 2,900,000 with tablets. No bundles, and a disabled branch is not billed.
Does it work without iiko?
Yes. laBoard is a POS tablet of its own: hall view, order screen, with the laBranch server built in. 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?
laBranch runs locally on the POS computer with an encrypted database (SQLCipher). laTable and laWaiter connect over Wi-Fi, so orders and calls keep flowing. Only QR waits for the internet to return, since the guest phone comes through the cloud.
Tablet or QR — which one should I pick?
Both do the same: menu, cart, order, waiter call, bill. QR costs UZS 10,000 per table and runs on the guest phone. laTable costs 100,000 per table, 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.
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.
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.