Understand the POS device heartbeat
A configured terminal sends an automatic device heartbeat with online state, viewport, app version, and pending transaction count, using retry backoff when delivery fails. Keep POS signed in and loaded, confirm the terminal remains online, and use the register sync indicator for pending transactions. Test the device on the intended terminal and keep manual fallback procedures available during service.
Before you start
- The POS terminal is assigned to the intended branch.
- The operating system and browser can access the printer, scanner, camera, microphone, scale, or heartbeat feature used by the task.
Steps
- Keep POS signed in and loaded.
- Confirm the terminal remains online.
- Use the register sync indicator for pending transactions.
- Ask an administrator or support agent to verify device status when the terminal appears offline remotely.
Expected result
Remote device status reflects the terminal online state, viewport, app version, and pending transaction count after delivery. Use the documented manual fallback until the device test succeeds on the intended terminal.
Permissions
- POS access is required; operating-system device permission or installation rights may also be required on the terminal.
Troubleshooting
The workflow stops while staff keep POS signed in and loaded, before they can confirm the terminal remains online.
A safe retry starts by confirming: The POS terminal is assigned to the intended branch. The operating system and browser can access the printer, scanner, camera, microphone, scale, or heartbeat feature used by the task. Return to /billing without changing user, branch, or record. Try the blocked step once; if it remains unavailable, stop and provide Support the device, terminal ID, branch, permission state, test result, and time. Capture the displayed state produced when staff keep POS signed in and loaded.
The device test, browser permission, physical output, or related POS record is inconclusive after the final checkpoint: Ask an administrator or support agent to verify device status when the terminal appears offline remotely.
Check the intended terminal, cable or connection, operating-system selection, browser permission, and test output. Run one more device test only after those checks; use the documented manual fallback until it succeeds. If those records still disagree, stop and send Support the device, terminal ID, branch, permission state, test result, and time. Check the saved state after staff ask an administrator or support agent to verify device status when the terminal appears offline remotely.
Related articles
TajerGo uses a stable local terminal identifier for shift and sync attribution, while current branch configuration controls enabled capabilities.Understand POS offline and sync status
The register displays connectivity, local queue depth, sync progress, last error, and recovery state; queued does not mean completed on the server.Recover failed or blocked queued work
Sync recovery distinguishes retryable connectivity failure from business rejection and protects queued work during branch switch or logout.
Open in TajerGo
Sign in with the appropriate role and confirm your Business Account and branch before continuing.
Read as Markdown · Guidance for support agents
Last reviewed 2026-09-06 · Send documentation feedback