Website, QR and delivery orders are created on your r_keeper 7 cash server with the right dish codes. The stop list follows online, and orders opened at the register can come into Ordering.Tools too.
r_keeper runs the register, the halls and the kitchen in many restaurants and hotels. Ordering.Tools adds the guest side: your own ordering website, QR menus on the tables, pickup and delivery. The integration connects to your r_keeper 7 cash server through its XML interface and creates every online order there, dish by dish, with the codes from your r_keeper menu.
It reads back as well. Dishes on the r_keeper stop list show as sold out online, orders opened at the register can be imported into Ordering.Tools, and an order closed on r_keeper is completed for the guest. Changes are read on a schedule, so none of this depends on r_keeper's paid notification module.
Online orders are created on r_keeper directly. Nobody re-enters them at the register, so the kitchen gets exactly the dishes the guest chose.
When a dish goes on the stop list in r_keeper, it turns sold out on your online menu. Guests can't order what the kitchen can't make.
Online orders and orders opened at the register can sit in one list in Ordering.Tools — for reports, follow-up and the end-of-day check.
No reliance on a notification licence that drops events when the cash server restarts. Ordering.Tools checks the cash server on a schedule, so a lost notification never means a lost change.
Your r_keeper dealer enables the XML interface on the cash server and creates a user for Ordering.Tools.
Enter the cash server address, user and password in Admin → Integrations. Optionally add the station and the waiter code online orders should carry. A test button checks the connection straight away.
Ordering.Tools reads your r_keeper menu, and you link each online dish to its r_keeper code. Every dish is mapped once.
Sending orders, sold-out sync and importing register orders are separate switches. Start with orders and add the rest when you are ready.
Every confirmed online order becomes an r_keeper order with its dishes, quantities and notes, placed on the station and waiter you chose.
Ordering.Tools reads the dish balances r_keeper keeps for its stop list and marks the matching dishes sold out on your menu.
Orders opened directly on r_keeper can be brought into Ordering.Tools, so the whole day is in one place.
Ordering.Tools fetches your r_keeper menu so every online dish can be linked to its code. Your online menu keeps its own photos, descriptions and translations.
Delivery and pickup orders go to the same register as the hall. The kitchen works from one system.
A cash server that runs several halls keeps doing so. Online orders arrive on the station you pick.
Put a dish on the stop list and online guests stop ordering it.
Register and online orders together in Ordering.Tools, by channel and by day.
Guests order from their phones; the order is created on r_keeper like any other.
Our sister product for bookings, Reservation.Tools, also connects to r_keeper, so reservations and orders work next to the same register.
r_keeper 7 is a restaurant POS used by restaurants, hotels and chains across Eastern Europe, Bulgaria included. It runs the register and the kitchen well. A guest-facing ordering website is not its job. Ordering.Tools gives you that website, QR menus and delivery — and puts every order back on r_keeper.
Every order that has to be re-typed is a chance to get it wrong. With online orders created directly on r_keeper, kitchen tickets, the bill and the reports all come from one source, and staff don't juggle a tablet and a register during service.
r_keeper can push notifications, but only from version 7.6.5 with a paid licence, and it drops queued events when the cash server restarts. Ordering.Tools reads changes from the cash server on a schedule instead. If you have the notification module it only makes updates faster — the integration never depends on it.
r_keeper holds dish codes and prices for the register. Online, guests need photos, descriptions, allergens and several languages. Ordering.Tools keeps those online and links each dish to its r_keeper code once, so the register and the website each do their own job.
Yes, with r_keeper 7 through its XML interface. Online orders are created on the cash server with your r_keeper dish codes, dishes on the stop list show as sold out online, and orders opened at the register can be imported.
No. Ordering.Tools reads changes from the cash server on a schedule. If you already have the notification module, updates can arrive faster, but nothing depends on it.
Access to the r_keeper 7 XML interface — the cash server address, a user and a password — which your r_keeper dealer sets up. Optionally a station and a waiter code for online orders.
Yes. Each online dish is linked once to its r_keeper code, and every order is created on the cash server with those codes, the quantities and the guest's notes.
Ordering.Tools reads the dish balances r_keeper uses for its stop list. A dish on the stop list shows as sold out online and becomes orderable again when it comes off.
Yes. Website, QR, pickup and delivery orders all go to r_keeper. Delivery zones, fees and couriers are handled in Ordering.Tools.
Your own ordering website, QR menus and delivery — with every order created on the r_keeper register you already run.
Other tools restaurants use alongside this one.
Every online order lands in your POS automatically. No re-typing. No missed items. Your staff works from one screen, whether the order comes from a table or a phone.
Learn moreOrders from your website, QR menus and delivery land in Barsy in about a second. Menu, sold-out dishes, table bills and payments stay in step between Barsy and Ordering.Tools — nothing is entered twice.
Learn moreOrders from your website and QR menus land on your Hype till as new orders, with every item and note. Staff accept them where they already work — and status and sold-out dishes come back on their own.
Learn moreEvery online order prints on your kitchen thermal printer the moment it arrives. Auto-print runs in the background. No tapping screens, no refreshing tabs. Paper does not crash.
Learn more