Compare
r_keeper + laCafe: the till stays, the guest layer is added
This is not "laCafe versus r_keeper". r_keeper is the till; laCafe is the QR, tablets, kiosk, waiter app, website and aggregators on top of it. Below: what you have with r_keeper alone and what changes when laCafe is added.
r_keeper
r_keeper is a classic professional POS, represented in Uzbekistan by BUSOFT. It is sold under licence and installation is costly and slow, but it runs the till and settlements reliably. laCafe does not replace it.
| Criterion | laCafe | r_keeper |
|---|---|---|
| Till (POS) | r_keeper stays. laCafe does not replace it; it works on top. | r_keeper, a professional POS under licence. |
| How it connects | laBranch (on the Windows 10/11 till PC) talks to r_keeper over the RK7 XML API: stop-list every 30 s, orders every 10 s. | — |
| Table tablet, QR, kiosk | Orders from laTable, laQR and laKiosk land in r_keeper. Guests order, call a waiter and ask for the bill themselves. | In the standard r_keeper package — no data. |
| Menu and stop-list sync | Names, prices and stop-list come from r_keeper. Stop-list refreshes within 30 s. Photos, GIFs, video, uz/ru/en translations and nutrition are added in laCafe. Modifiers coming soon. | Menu is maintained inside r_keeper. |
| Waiter app | laWaiter: calls and bill requests for the waiter's own tables, order taking, shifts. Guests pick the staff type (barman, hookah master). | No data. |
| Own website and delivery | laGuestWeb on your own domain, polygon zones, nearest branch, TaxiMillenium couriers. Website order 1,500 UZS. | No data. |
| Aggregators (Yandex Eats, Uzum Tezkor) | Menu and availability, order intake, two-way status, MXIK/IKPU codes. 300 UZS per order. | No data. |
| Online payments | Payme, Click, UzQR, laPay (one QR for Payme, Click, Paylov, Uzum and cards). Guests close the bill themselves. | No data. |
| Offline operation | laBranch is offline-first: if the internet drops, tablet and QR orders continue; the local database is encrypted (SQLCipher). | No data. |
| Marketing (cashback, promo codes, stories) | Cashback (percent, your own unit name), promo codes, automatic discount rules (weekday + time), stories, guest CRM. Automatic cashback and promo validation at checkout are coming soon; today the cashier applies them by hand. | No data. |
| AI and Telegram | laCafe MCP (ChatGPT/Claude/Gemini fill the menu from a photo), Telegram AI bot takes orders, Telegram notifications (call, bill, new order, payment). | No data. |
| Reports | On top of r_keeper reports: hourly heatmap, menu engineering, cross-sell, order source (QR/site/tablet), table turnover, call statistics. 10 reports ready, the rest coming soon. | r_keeper's own reports. Details — no data. |
| Price | On top of the r_keeper licence: 500,000 UZS per branch a month plus devices you use (laTable 100,000, QR table 10,000, laKiosk 250,000, laWaiter 100,000) and orders. No plans. | Licence. Installation is costly and slow. |
| Rollout | No need to reinstall r_keeper. laBranch goes on the till PC, tablets find it over Wi-Fi and pair with a 6-letter code. | Installation is costly and slow. |
When they're the better fit
If you need a till, r_keeper is exactly that. laCafe is not a POS and does not replace r_keeper. If waiters take orders themselves, guests do not ask for QR or tablets, and there is no delivery or aggregators, r_keeper alone is enough.
When laCafe is the better fit
You already run r_keeper and do not want to touch it, but guests should order at the table themselves, close the bill with Payme or Click, and order delivery from your website. Yandex Eats and Uzum Tezkor orders should land at the till on their own. That is r_keeper + laCafe.
Questions & answers
Can I use laCafe instead of r_keeper?
No, that is not the goal. laCafe works on top of r_keeper: orders go into it, prices and the stop-list come from it. If you have r_keeper, it stays.
Does laCafe work without r_keeper?
Yes. laBoard is laCafe's own till tablet with the laBranch server inside. But where r_keeper is already installed we do not recommend removing it: laCafe is added on top.
How does the r_keeper connection work?
laBranch sits on the till PC (Windows 10/11) and polls r_keeper over the RK7 XML API: stop-list every 30 s, orders every 10 s. Tablet and QR orders reach r_keeper this way.
Do r_keeper modifiers show in laCafe?
Not yet. r_keeper modifiers are planned and coming soon. Names, prices and the stop-list already sync.
How fast does the stop-list arrive from r_keeper?
Within 30 seconds. When the cashier stop-lists a dish in r_keeper, it disappears from laTable, laQR and the website within half a minute.
Do I need to reconfigure r_keeper?
No reinstall is needed. laBranch goes on the till PC and connects over the RK7 XML API. For exact setup steps write to hello@lacafe.app.
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.