POS errors and offline mode

Last reviewed: 2026-07-14

On this page

Most of the time, tapping the Team Shift tile just works. Here's what to check when it doesn't.

The tile is greyed out and won't tap

Team Shift's POS tile requires an internet connection. If the POS device isn't connected, the tile itself is disabled — you won't even be able to open the clock-in screen. There's no offline mode: Team Shift doesn't cache or queue clock-in/out actions locally to sync later, so a shift's clock-in and clock-out both need to happen while the device is online.

Fix: reconnect the POS device to the internet, then tap the tile again.

"No staff found for this location. Contact your manager."

This shows up when Team Shift has no one it can offer on the clock-in roster for that location. Common causes:

  • Nobody is assigned to that location. The tile shows staff assigned to the register's location (plus any staff assigned to no location at all). Check each person's staff detail page in Shopify Admin and confirm the location is checked under Assigned Locations.
  • The staff member has been archived. Archived staff no longer show up as eligible to clock in — see Troubleshooting and frequently asked questions for what archiving does.

When more than one person can clock in at a location, Team Shift no longer has to guess who's at the register — it shows a roster and asks for a 4-digit PIN. If your register is shared, that's expected; see Clocking in with a PIN on shared registers. If a name on the roster says "needs a PIN", an admin has to generate one before that person can clock in there.

"Unable to connect. Check your network and try again."

This is a generic network error shown when the tile fails to load staff or status information, distinct from the disabled-tile offline state above. Try again once the connection is stable.

Action failed toasts

If clocking in, clocking out, or starting/ending a break fails partway through, you'll see a toast message like "Clock-in failed" or "Break start failed," often with a specific reason such as "Staff member already has an active timesheet" or "Already on break." These reflect a rule being enforced (for example, you can't clock in twice without clocking out first) rather than a bug — check Clocking in and out on POS and Taking breaks on POS for how those flows are supposed to work.

Next steps

Was this article helpful?

Still need help?

Reach out and our team will get back to you.

Contact us