Guide: Revel Labor
How Do Core Concepts Map to Tenzo?
Key: ✅ Supported 🚸 Work in Progress ❌ Not Supported
 |
|
|---|---|
| Location | ✅ Establishments |
| Shift (actual) | ✅ Shifts |
| Shift (planned) | ✅ Scheduled Shifts |
| Hours | ✅ Shift duration |
| Employee | ✅ Employees |
| Role | ✅ Roles |
| House Part | ✅ Role grouping |
| Pay rate | 🚸 Pay Rate — sent for some employees only |
| Labour cost | 🚸 Cost — sent for some employees only |
| Breaks | 🚸 Unpaid break length — sent where recorded |
| Employer taxes | ❌ Not Supported |
| Pension | ❌ Not Supported |
| Overheads | ❌ Not Supported |
| Holiday | ❌ Not Supported |
| Overtime | ❌ Not Supported |
| Salaried workers | ❌ Not Supported — every employee is costed at an hourly rate |
This guide covers Revel's labour data. Revel's sales data is covered in the Revel guide.
Data Ingestion
| Real-time optionally available? | ❌ |
| Default polling frequency | Every 8 hours |
| Data retrieved on each poll | Two weeks back and two weeks forward |
| Historical data | All data since you started using Revel |
How Do I Connect This Data to Tenzo?
Revel is connected directly inside the Tenzo app using your Revel API Key, API Secret and Page Name. The same connection covers Revel's sales and labour data — you choose which datasources to ingest when it is set up.
If you have an Enterprise Account, you can talk to your Customer Success Manager, who will connect this for you.
How Do I Compare Revel Labor Data to Data in Tenzo?
Compare against your Revel labour reporting for the same date range and establishment. Hours worked and scheduled hours per employee should reconcile.
Pay rate and labour cost are only reported for employees where Revel holds them, so Tenzo's labour cost can read low while hours are complete — check a handful of employees in Revel before treating a gap as a Tenzo problem. Employer taxes, pension, holiday and overtime are not part of the feed, so labour cost is base pay only.