Point of sale
r_keeper
The r_keeper POS integration connects delivery and pickup orders from MERGEPORT to r_keeper through a plugin configured with RK Delivery.
What this integration can do
Order intake
InboundDelivery order intake
Data exchanged
Setup at a glance
- Connection
- API connection
- Updates
- Real time
- Data flow
- Inbound
What you need
- Configuration in r_keeper and RK Delivery, together with configuration of the plugin connecting to MERGEPORT, is required for restaurant activation.
Useful for
About this integration
The r_keeper POS integration connects delivery and pickup orders from MERGEPORT to r_keeper through a plugin configured with RK Delivery. It supports automatic order acceptance and printing, as well as scheduled and ASAP orders. Table orders and delivery-time changes through timeChange are currently not supported.
How the connection works
Order intake
Receive customer orders from the connected platform.
Delivery, pickup, or marketplace orders can be passed into the connected system for further processing.
FAQs
What do I need before activating r_keeper?
Configuration in r_keeper and RK Delivery, together with configuration of the plugin connecting to MERGEPORT, is required for restaurant activation.
Which functions does r_keeper support?
This integration supports Order intake.
Why MERGEPORT
What a connected order flow can support.
What you can do depends on the systems and features in your setup.
Save manual steps
Where order forwarding is supported, teams can avoid entering the same information again by hand.
Reduce handover errors
Structured data transfer can reduce manual copying between supported ordering and point-of-sale systems.
Stay in control
A shared connection layer can make supported channels and systems easier to oversee as a setup grows.
Ready for the next step?
Plan your r_keeper integration
Discuss the systems, required data and next steps with our team.
