Skip to content

Integration · POS systems

Orders from every channel — straight into r_keeper

ORDR connects to your r_keeper. Orders from your website, aggregators and messengers go to the kitchen without manual re-entry, and the r_keeper menu becomes the menu for every channel.

How we integrate with r_keeper

ORDR connects to r_keeper with access issued by your r_keeper. The kitchen and the till work as before.

Sales channels

  • Website
  • App
  • Wolt Marketplace
  • Yandex.Eda
  • WhatsApp
  • Call centre
ORDRAn order with a number and history
  • ORDR → r_keeperOrdersItems, modifiers, address and payment go to r_keeper as a regular order.
  • r_keeper → ORDRMenus and stop listsDishes, prices and modifiers come from r_keeper, and anything sold out disappears from every channel.
  • r_keeper → ORDRStatusesCooking, ready, handed to the courier: visible on the order board and to the guest.
r_keeper

What changes in the restaurant

Without integration

  • Tablet orders are re-entered into r_keeper by hand
  • The menu on the website and at aggregators drifts from the till
  • Order mistakes surface only once the guest has the food

With ORDR

  • An order from any channel lands in r_keeper on its own
  • One r_keeper menu across every channel
  • The kitchen gets the order exactly as the guest placed it

How we connect r_keeper

The ORDR team does it all — you only provide access to the POS.

  1. 1

    Request and demo

    We show on your menu how an order reaches the kitchen.

  2. 2

    Access to r_keeper

    You issue an access key to r_keeper, and we add it to ORDR.

  3. 3

    Menu and locations

    We match dishes and locations, then check with a test order.

  4. 4

    Orders go to r_keeper

    We switch on the channels. The kitchen works as before.

We'll connect r_keeper to your channels

On the demo we'll show how an order from your website, Wolt Marketplace or WhatsApp reaches the kitchen without re-entry.