# 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.

Canonical URL: https://admin.tajergo.ae/help/articles/pos/device-heartbeat/
Article ID: pos-device-heartbeat
Surface: POS
Category: Hardware and devices
Last reviewed: 2026-09-06

## 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

1. Keep POS signed in and loaded.
2. Confirm the terminal remains online.
3. Use the register sync indicator for pending transactions.
4. 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

- [Understand terminal identity and heartbeat](https://admin.tajergo.ae/help/articles/pos/terminal-identity.md)
- [Understand POS offline and sync status](https://admin.tajergo.ae/help/articles/pos/offline-status.md)
- [Recover failed or blocked queued work](https://admin.tajergo.ae/help/articles/pos/sync-recovery.md)