1. Schedule
Use the published shift version, planned hours, roles, breaks, and the wage-cost scope selected for the period.
How restaurant schedules and POS revenue work together
Combine the published schedule and its planned wage cost with POS revenue from the same location and period. The result is an operational labor-cost ratio for review—not payroll or a universal staffing target—and dates, currencies, and cost scope must stay aligned.
Keep three records connected
2. POS revenue
Use completed sales for the same venue, timezone, and cutoff. Keep refunds, voids, and card tips identifiable.
3. Comparison
Divide the chosen same-period labor cost by revenue, then investigate both inputs before changing coverage.
Align the period before calculating
-
Define the operating day
Choose the venue timezone and a clear cutoff for services that run past midnight.
-
Lock the planning basis
Record whether the numerator uses published hours, confirmed worked hours, gross wages, or a broader loaded cost.
-
Reconcile the POS total
Wait for completed transactions and account for later refunds or voids before treating the revenue as final.
-
Compare like with like
Use one currency, one location, one date range, and the same cost definition for every comparison.
Worked example: one restaurant day
These figures demonstrate the workflow only. They are not a recommended labor-cost benchmark.
| Record | Source | Example value | Control check |
|---|---|---|---|
| Scheduled wage cost | Published schedule | 48 hours × €18 = €864 | Same venue and operating day |
| POS revenue | Completed POS sales | €4,800 | Same cutoff and currency |
| Operational ratio | €864 ÷ €4,800 × 100 | 18.0% | Planning ratio, not a universal target |
| Card tips | POS tip record | €240 | Kept separate for the agreed tip pool |
The example produces an 18.0% scheduled-wage-to-revenue ratio. The €240 card-tip record stays separate from that calculation and follows the business's documented tip-pool process.
Square, SumUp, or manual revenue
ShiftPriority supports Square and SumUp today. The useful workflow is the same, but each source should be reconciled according to the data it supplies.
Square
Square sales and card tips can sync automatically. Mapped Square categories can also support food and drink revenue splits, while ShiftPriority reads rather than changes the POS setup.
SumUp
SumUp sales and card tips can sync through transaction polling. Reconcile the returned totals and timing before closing the comparison period.
Manual
A POS connection is optional. Enter a documented same-period revenue total manually and preserve its source and cutoff.
Review before changing the schedule
- Confirm location, timezone, operating-day cutoff, currency, and date range.
- Reconcile refunds, voids, incomplete transactions, and late POS adjustments.
- Distinguish published hours from confirmed worked hours.
- State whether the numerator is wage cost or a broader loaded labor cost.
- Keep one accounting basis when comparing periods.
- Check the operational cause—revenue timing, demand, role coverage, wage mix, or hours—before changing staffing.
Limits and assumptions
This is an operational planning workflow, not payroll, accounting, tax, employment, or legal advice. There is no universal ratio that fits every restaurant. POS totals can change after refunds or timing adjustments, and scheduled hours can differ from worked hours.
Continue with the calculation or integration details
Use the labor-cost guide to define the formula and cost scope, or review the Square integration workflow and its current data flow.
Sources
Give your team back their Sundays
Stop wrestling spreadsheets. Build your first schedule this afternoon — and see your labor cost the moment you publish.
Get started free →Free during our open beta · Set up in minutes · No credit card