# Handle an offline shift action safely

Shift open or close can be saved locally when connectivity fails; the drawer is not open or finalized on the server until synchronization succeeds. Submit the shift action once, read whether it was queued, and keep the terminal on the same branch and user context. Queued means stored on this device, not completed on the server; reconnect and verify the final record before retrying.

Canonical URL: https://admin.tajergo.ae/help/articles/pos/offline-shifts/
Article ID: pos-offline-shifts
Surface: POS
Category: Offline and recovery
Last reviewed: 2026-09-06

## Before you start

- An authenticated POS session on the intended branch and terminal.
- The local sync indicator and queued transaction count are visible before recovery begins.

## Steps

1. Submit the shift action once.
2. Read whether it was queued.
3. Keep the terminal on the same branch and user context.
4. Reconnect and verify the shift history before proceeding.

## Expected result

The local shift action remains queued once and later reconciles to one server shift record after reconnection. Queued means stored locally, not completed on the server; do not recreate or delete the transaction while its outcome is unknown.

## Permissions

- POS access for the active branch is required; business rejections may need a manager to correct the original order, payment, shift, or configuration.

## Troubleshooting

### POS does not let staff submit the shift action once; they cannot continue to read whether it was queued.

Verify these conditions before another test: An authenticated POS session on the intended branch and terminal. The local sync indicator and queued transaction count are visible before recovery begins. Keep the same branch and record, reopen /shifts, and try the blocked action once. If it still fails, stop and send Support the queue reference, terminal ID, branch, action, safe record reference, error, retry count, and time. Record the visible response when staff submit the shift action once.

### The local queue and server order, payment, or shift record do not establish one synchronized result after the final checkpoint: Reconnect and verify the shift history before proceeding.

Keep the same branch and inspect the queue, sync status, and matching server record after reconnection. Never repeat queued or syncing work. Retry only when the queue is clear and the server proves the action absent. An unresolved mismatch needs Support review with the queue reference, terminal ID, branch, action, safe record reference, error, retry count, and time. Confirm from the records whether staff could reconnect and verify the shift history before proceeding.

## Related articles

- [Understand POS offline and sync status](https://admin.tajergo.ae/help/articles/pos/offline-status.md)
- [Handle an offline checkout safely](https://admin.tajergo.ae/help/articles/pos/offline-orders-payments.md)
- [Recover failed or blocked queued work](https://admin.tajergo.ae/help/articles/pos/sync-recovery.md)