POSHardware and devices

Understand terminal identity and heartbeat

TajerGo uses a stable local terminal identifier for shift and sync attribution, while current branch configuration controls enabled capabilities. Confirm the branch label, allow the register to finish Preparing this register, and open Shifts or Support to view terminal-linked context. 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

Confirm the branch label.
Allow the register to finish Preparing this register.
Open Shifts or Support to view terminal-linked context.
Contact support if configuration cannot load.

Expected result

The stable terminal identifier and active branch shown by POS match the device used for shift and sync attribution. 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

Staff cannot confirm the branch label because the control is missing, disabled, or rejected before they allow the register to finish Preparing this register.

Before reopening the workflow, verify: 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. Check those conditions on /billing and repeat only the blocked step once. Preserve the screen and ask Support to review the device, terminal ID, branch, permission state, test result, and time. For escalation, state what happens when staff confirm the branch label.

The device test, browser permission, physical output, or related POS record is inconclusive after the final checkpoint: Contact support if configuration cannot load.

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. Use the visible and saved records to determine whether staff could contact support if configuration cannot load.

Configure receipt printing
Receipt printing uses the browser print path and branch receipt configuration; verify paper width and output before serving customers.Use receipt QR and invoice links
Receipts can include configured QR or invoice information, and public invoice links open through a tokenized route.Troubleshoot a barcode scanner
USB and Bluetooth scanners normally act as keyboard input and must send the full configured barcode terminator.Allow camera or microphone access
Camera recognition and voice notes depend on browser device permissions and remain optional POS capabilities.