Understand POS offline and sync status

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. Read the sync status before taking action.
2. When offline, note the queue reference and allowed method.
3. Reconnect the terminal.
4. Wait for synchronization and verify Orders, Payments, or Shifts.

Expected result

The sync indicator distinguishes offline, queued, syncing, failed, and fully synchronized states with queue depth. 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

The workflow stops while staff read the sync status before taking action, before they can when offline, note the queue reference and allowed method.

First confirm the following access and record state: An authenticated POS session on the intended branch and terminal. The local sync indicator and queued transaction count are visible before recovery begins. Return to /billing without changing user, branch, or record. Try the blocked step once; if it remains unavailable, stop and provide Support the queue reference, terminal ID, branch, action, safe record reference, error, retry count, and time. Keep evidence of the result when staff read the sync status before taking action.

The local queue and server order, payment, or shift record do not establish one synchronized result after the final checkpoint: Wait for synchronization and verify Orders, Payments, or Shifts.

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. When no single result can be proved, pause and provide Support the queue reference, terminal ID, branch, action, safe record reference, error, retry count, and time. Before another attempt, establish whether staff could wait for synchronization and verify Orders, Payments, or Shifts.

Related articles

Open in TajerGo

Sign in with the appropriate role and confirm your Business Account and branch before continuing.

/billing

Back to POS