POS
r_keeper integration: QR menu and tablets on top of your POS
laCafe does not replace r_keeper. The r_keeper bridge in laBox pulls the menu, tables and stop list over the RK7 XML API and pushes guest orders to the till. Your license and reports stay in r_keeper.
What connects
The free laBox goes on the till PC and downloads and starts the r_keeper bridge itself; the bridge connects to the RK7 XML API. No plugin inside r_keeper, no changes to r_keeper settings. Catalogs come from r_keeper and are never entered twice.
- Products and categories
- Price scales
- Stop list
- Tables and halls
- Employees (waiters)
- Modifiers: coming soon
How it works: polling
r_keeper has no webhooks, so the bridge polls it. The stop list is checked every 30 seconds, open orders every 10 seconds. Guest orders themselves are sent immediately, no waiting.
- 1. Guest orders from QR or laTable
- 2. The bridge opens the order on the table in r_keeper
- 3. Every 10 s: order status and total are re-read
- 4. Every 30 s: stop list refresh
- 5. The cashier closes the bill and payment in r_keeper
What stays in sync and what the guest sees
A price-scale change shows on the QR menu. The stop list arrives within 30 seconds. If the cashier adds or removes an item in r_keeper, the guest screen reflects it within 10 seconds. Photos, descriptions, 3 languages and nutrition come from the laCafe admin.
- Prices, names, categories: from r_keeper
- Stop list: up to 30 seconds
- Order status: up to 10 seconds
- Photos, video, translations, nutrition: from laCafe
Honest limits
Modifiers are not wired yet; coming soon. For now, a dish with variants can be set up as separate items: 'Plov large', 'Plov small'. Polling is not instant: the stop list can lag by up to 30 seconds. The RK7 XML API interface must be enabled by your r_keeper dealer (BUSOFT, rkeeper.uz).
- Modifiers: coming soon
- Stop-list delay up to 30 seconds
- RK7 XML API must be enabled
- laBox installs and updates the bridge itself
Questions & answers
Does the QR menu work with r_keeper?
Yes. The guest orders from the QR menu and the bridge opens it on that table in r_keeper. Prices and the stop list come from r_keeper. The cashier retypes nothing.
Do I have to replace r_keeper?
No. r_keeper stays your POS with its license and reports. laCafe adds the guest layer on top: QR, tablets, kiosk, website, Telegram. Years of your setup stay untouched.
When do modifiers arrive?
Coming soon. For now, dishes with variants can be entered as separate items. In iiko, modifiers already work.
How much does the stop list lag?
At most 30 seconds. The cook puts shashlik on the stop list in r_keeper and it closes on QR and tablets within 30 seconds.
What happens if the internet goes down?
r_keeper 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 r_keeper integration cost?
No separate integration fee, and laBox is free. Everything is part of your laCafe package: packages from UZS 600,000 a month, unlimited devices (see /pricing). The RK7 XML API license is between you and your r_keeper dealer.
Blog
Articles on this topic
Connect your first table today.
We'll set up a demo with your own menu within a day.