Guide: r_keeper
How Do Core Concepts Map to Tenzo?
Key: ✅ Supported 🚸 Work in Progress ❌ Not Supported
![]() |
![]() |
|---|---|
| Location | ✅ Restaurants |
| Order Type | ✅ Order Types |
| Revenue Center | ❌ Not Supported |
| Product Item | ✅ Menu Items |
| Product Category | ✅ Menu Groups |
| Product Division | ✅ Menu Groups (upper levels) |
| Tender Type | ❌ Not Supported |
| Employee | ✅ Cashiers |
| Customer | ❌ Not Supported |
| Discount (Names) | ❌ Not Supported — discount amounts arrive without a name |
| TicketItemDiscounts (Amounts) | ✅ Item Discounts |
| TicketDiscounts (Amounts) | ❌ Not Supported |
| Guest Count | ❌ Not Supported |
| Transaction Length | ❌ Not Supported — one timestamp is sent per sale |
| Delivery Timings | ❌ Not Supported |
| KDS Bump Time | ❌ Not Supported |
| Ticket Voids | ❌ Not Supported |
| Ticket Item Voids | ❌ Not Supported |
| Table | 🚸 Tables — recorded, but sales are not linked to them |
| Service Charge | 🚸 Reported as a menu item on the sale rather than as a separate charge |
| Tips | ❌ Not Supported |
| Comps | ❌ Not Supported |
| Modifiers | ❌ Not Supported |
This guide was derived from r_keeper's live output rather than from a test fixture. Every row was checked against the sales Tenzo has actually received.
Data Ingestion
| Real-time optionally available? | ❌ |
| Default polling frequency | Every 4 hours |
| Data retrieved on each poll | Everything sent since the previous poll |
| Historical data | All data r_keeper has sent us since the integration was connected |
How Do I Connect This Data to Tenzo?
r_keeper sends its sales data to Tenzo, so there are no credentials for you to enter in Tenzo. Tenzo issues SFTP credentials for the feed, which are configured on the r_keeper side. Your Customer Success Manager arranges this and confirms when the feed is live.
If you have an Enterprise Account, you can talk to your Customer Success Manager, who will connect this for you.
How Do I Compare r_keeper Data to Data in Tenzo?
Compare against your r_keeper sales reporting for the same date range and restaurant. Net and gross sales, item quantities and item discounts should reconcile.
Service charge is the one to watch when reconciling. r_keeper sends it as a line on the sale rather than as a separate charge, so it appears in Tenzo as a menu item and is counted in sales alongside food and drink — it is not broken out as a service charge figure.
Several things are not part of the feed, so they read as empty rather than zero: guest counts, tips, payment method, revenue centre and any customer detail. Sales carry a single timestamp rather than an open and a close, so Tenzo cannot show how long a sale took, and table numbers are received as a list but individual sales are not linked to a table.
