Table of Contents
How do core concepts map to Tenzo? #
Key: ✅ Supported · 🚸 Work in Progress · ❌ Not supported
| Stint concept | Tenzo concept | Status |
| Site | Locations | ✅ |
| Paid shift (clocked-in / out) | Shift (actual) | ✅ |
| Scheduled shift | Shift (planned) | ❌ Stint’s SFTP feed delivers actuals only; scheduled shifts are not currently included |
| Worked Duration / Calculated Paid Hours | Hours | ✅ |
| Salary pay type | Salaried workers (Pay Rate /year) | ✅ |
| Profile / employee record | Employee | ✅ |
| Position | Role | ✅ |
| Schedule Group (e.g. “Front of House”) | House Part | ✅ |
| Flat-rate on-cost percentage applied per shift | Overheads | ✅ Stint applies a flat percent on top of pay; Tenzo carries it through as the other_overhead_cost field |
| Holiday accrual | Holiday | ❌ Not delivered in the SFTP feed currently |
| Unpaid / paid breaks | Breaks | ❌ Not delivered in the SFTP feed currently |
| Overtime hours / overtime pay | Overtime | ❌ Not delivered in the SFTP feed currently |
| One-off costs (bonuses, exceptions) | Exception costs | ❌ Not supported |
| Borrowed / loaned employees | Borrowed / loaned employees | ❌ Not supported |
Data Ingestion #
| Real-time available? | ❌ Not supported |
| Transport | Nightly SFTP push from Stint to Tenzo |
| Default delivery frequency | Once per day, overnight |
| Data retrieved on each push | Recent days through the latest closed payroll week |
| Historical data | From the date Stint was connected for the customer |
How do I connect this data to Tenzo? #
Stint is connected by your Tenzo Customer Success Manager. They will need the following details from Stint:
- The customer’s Stint tenant identifier
- An SFTP destination at Stint configured to push the customer’s labour data to Tenzo’s secure receiving endpoint
Additionally, you will need to provide a date to start pulling data from.
How do I compare Stint data to data in Tenzo? #
Tenzo’s labour cost for your venue should align closely with the headline “Actual labour cost” you see in Stint Reporting. To verify:
- Log into reporting.stint.co.
- On the Reporting dashboard (the default landing page), use the granularity selector in the top-right to pick the period you want to compare. Options are Week, Month, Quarter, Year, and Multiple Weeks.
- Use the period chip (e.g. “Week of 11 May 2026”) to choose the specific window. The dashboard updates live.
- If you have multiple venues, switch to the site you want by clicking the sites selector (look for the venue name above the metric cards).
-
The headline cards show:
- Actual labour cost (WTD) — total labour cost for the period
- Actual hours (WTD) — total worked hours for the period
- Actual labour % (WTD) — labour cost as a % of sales
- Compare these to Tenzo’s labour view for the same venue and date range. The numbers should match within ~1% if the Overheads setting in Tenzo is enabled and the Stint Reporting view is showing Week-to-Date (not Run-Rate).
If you only see the dashboard “Welcome” view rather than the cards, you may need to switch to Week-to-Date mode (the tab next to “Run-Rate” near the top of the dashboard) — Run-Rate is a forward projection and will not match Tenzo’s actuals view.
Exceptions #
- No planned-shift comparison. Stint’s SFTP feed delivers actual (paid) shifts only, not scheduled / forecast shifts. Tenzo’s “Planned vs Actual” panels will only populate the Actuals side for Stint customers. If you need planned vs actual comparison, check the schedule in Stint Reporting directly.
- No separate break / holiday / overtime breakdowns. Stint does not currently ship these as distinct fields in the SFTP feed. Worked hours include all paid time; if a shift records 8.5 paid hours, Tenzo treats it as 8.5 hours of worked labour regardless of whether some of that was overtime or paid break time.
- Pay rate changes mid-period. Stint applies the rate that was in effect on the day of each shift. Tenzo’s per-employee aggregates take the latest non-zero rate seen across the loaded window. If an employee’s pay rate changed during the period being compared, the per-employee cost figures may differ slightly between Stint Reporting and Tenzo — the totals at the venue level should still match.
- Non-service shifts. Stint distinguishes between service and non-service shifts; Tenzo includes both in the “Actual labour cost (incl. non-service)” rollup. If you’re cross-referencing with Stint’s “Service-only” view, the numbers will be lower by the non-service component.
- Newly added employees without a contracted rate. Stint may emit shift rows for employees who have been created but not yet had a pay rate assigned. These rows carry £0 cost in both Stint and Tenzo. If your reports look light, check Stint’s employee admin for any rows missing a Pay Rate field.
- The “Lock Week” requirement does not apply. Unlike some other labour partners, Stint pushes shift data continuously through the period — you don’t need to lock the week before Tenzo will see it. Data refreshes automatically each night.
