Shift-level restaurant labour economics, exposed through an authenticated hours-and-wages endpoint. Every record is a single worked shift carrying: clock-in and clock-out timestamps at minute precision, paid versus unpaid break segments with their own times, the location, the role label (for example Line Cook), an hourly wage rate, a salaried versus hourly flag, a shift status code, and compliance exceptions; plus a fully decomposed pay vector splitting regular, overtime (premium and non-premium), holiday and compliance-exception pay from hours, and a tip ledger separating cash tips, card tips, tip-out, declared versus POS-declared tips, auto-gratuity, amounts withheld, tips earned and tips still to be paid. Weekly and daily aggregates roll these per employee, per location and per role. The commercial significance is the granularity: realised wage rates, true hours worked, overtime incidence and tip-pool economics per shift — the variables that labour-cost models and QSR benchmarking currently estimate from surveys or from payroll aggregates published months late. Access is per-tenant and authenticated, so the aggregated cross-location panel is a licensable product rather than an open endpoint.
Equities in US, Canada. Related tickers CMG, YUM, SBUX, DRI, BNRI, WYNN.
Tabular JSON via a versioned REST API (versioned release namespace on the developer portal), with per-shift records rolling up to day, week, user, role and location aggregations
Extremely high cardinality — one record per worked shift, and a full-service restaurant location generates on the order of 1,000-3,000 shifts per year, so a five-year retained panel across a five-figure location count implies hundreds of millions of shift records, each carrying a wage vector, a break structure and a tip ledger
Labels generated free by scheduling and timekeeping operations: role classification per shift, location identity, hourly wage rate and salaried/hourly employment-type flag, paid-versus-unpaid break structure, overtime classification split into premium and non-premium, holiday-hours designation, compliance-exception flags generated by labour-law rules, tip-out and declared-versus-POS-declared tip reconciliation labels, and shift status codes. Break and compliance flags are especially valuable because they encode labour-law rule violations detected by the software at the moment of recording.
7shifts — Shift-level restaurant labour economics, exposed through an authenticated hours-and-wages endpoint. Every record is a single worked shift carrying: clock-in and clock-out timestamps at minute precision, paid versus unpaid break segments with their own times, the location, the role label (for example Line Cook), an hourly wage rate, a salaried versus hourly flag, a shift status code, and compliance exceptions; plus a fully decomposed pay vector splitting regular, overtime (premium and non-premium), holiday and compliance-exception pay from hours, and a tip ledger separating cash tips…
Not yet on file: Sample · Data dictionary · Data frequency · Reporting lag · Point-in-time · License