POSHardware and devices

Use receipt QR and invoice links

Receipts can include configured QR or invoice information, and public invoice links open through a tokenized route. Open or print the completed receipt, confirm the QR or link belongs to the intended invoice, and scan with a separate device. 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

Open or print the completed receipt.
Confirm the QR or link belongs to the intended invoice.
Scan with a separate device.
Verify the public invoice displays the expected transaction.

Expected result

The QR opens the public invoice for the same completed order, merchant, totals, and tax details. 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 open or print the completed receipt because the control is missing, disabled, or rejected before they confirm the QR or link belongs to the intended invoice.

Verify these conditions before another test: 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. Record the visible response when staff open or print the completed receipt.

The device test, browser permission, physical output, or related POS record is inconclusive after the final checkpoint: Verify the public invoice displays the expected transaction.

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. Confirm from the records whether staff could verify the public invoice displays the expected transaction.

Configure receipt printing
Receipt printing uses the browser print path and branch receipt configuration; verify paper width and output before serving customers.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.Use a scale with weighted products
A keyboard-output scale can fill the focused weight field; otherwise enter the measured value manually in the displayed sale unit.