What each POS gives SafeShift
| POS | What syncs | What you provide once |
|---|---|---|
| Toast | Employee roster, clock-in and clock-out, meal and rest break entries, declared tips | API key and secret from Toast |
| Square | Roster, time entries with corrections, tips and pay rates, paid and unpaid breaks | Connect with Square sign-in (OAuth) and pick the location |
| Clover | Roster, clock-in and clock-out, deletions mirrored as voids | Merchant API token and merchant ID |
Sync runs every five minutes. The first rest break is not due until two hours into a shift, so a five-minute lag has no effect on reminder timing. SpotOn, PAR Brink, and Gusto time sheets are available on request.
What the POS cannot do alone
- It does not know the state rule for the shift length, so it cannot say a break is late until someone audits the report weeks later.
- It sends no reminder before the break is due and no alert to the manager when one is missed.
- It records no premium pay, so missed breaks are paid late or not at all.
- It has no attestation: nothing from the employee saying the break was offered.
- Its export is a time report, not a compliance record with the reminders, decisions, and signatures attached.
What changes for your team: nothing
Employees clock in on the POS exactly as before. SafeShift matches each punch to the scheduled shift, computes the break windows, sends the reminders by push and SMS, records violations with premium pay, and alerts the manager. Employees who want their schedule and reminders on their phone install the SafeShift app; employees who do not still get SMS.
For the attestation, locations put a tablet near the time clock as an Attestation Station: the employee enters a PIN after punching out on the POS and answers the break questions on the spot, in English or Spanish. Locations that skip the station collect the attestation on the employee's phone.
The sync rules that protect the record
- A manual clock-out is never overwritten by a sync. If a manager closes a shift the POS left open, the next sync respects it.
- Corrections on the POS propagate. A time entry edited after the fact updates the shift with a before-and-after audit entry, and feeds the next payroll run as an adjustment.
- Deleted POS entries become voids, not deletions. The shift and its violations stay on file, marked void with the reason.
- Custom POS break names map to meal, rest, or working time through one normalizer, so a break called Lunch on one terminal and Meal on another counts the same way.
- Register and device accounts are excluded from compliance and payroll so a shared cashier login never generates violations.
Mixing modes, and leaving a POS
A location can run POS punches for the floor and the PIN kiosk for a crew the POS does not cover; each employee has a clock source. If a location changes POS or stops using one, the switch tool moves employees to app or kiosk clocking with a dry-run count first, and their history stays intact.
Common questions
Will my team have to clock in twice?
No. The POS stays the time clock. SafeShift reads the punches and adds reminders, violations, attestations, and reporting on top.
What if the POS is down or the sync is late?
SafeShift waits before recording a violation while a POS sync is more than fifteen minutes stale, so a late sync never creates a false miss. Once the entries arrive, breaks are judged from the actual punch times.
Can I mix POS and kiosk at one location?
Yes. Each employee has a clock source, so floor staff can punch on the POS while a crew the POS does not cover uses the PIN kiosk, and both feed the same compliance record.
Do you support SpotOn, PAR Brink, or Gusto?
Integrations are built for all three and are enabled on request with the customer's credentials. Toast, Square, and Clover are live today.
Guides
See it on your own schedule
A 30-minute walkthrough. From $69 per location per month, every feature on every plan.
SafeShift provides records, not legal advice. Operated by Daric Holdings LLC.