Allow camera or microphone access
Camera recognition and voice notes depend on browser device permissions and remain optional POS capabilities. Open the camera or voice control, allow the requested browser permission, and capture only the product or instruction needed. 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.
Allow camera access
- Open camera recognition and respond to the browser camera prompt.
- Choose the intended camera when the browser offers a device selector.
- Review any recognized product suggestion before adding it.
Allow microphone access
- Open voice capture and respond to the browser microphone prompt.
- Record the note, stop capture, and review the transcription.
- Edit or discard incorrect text before attaching it to the order.
Expected result
The browser grants only the requested device access and captured suggestions or transcripts remain reviewable. 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
When staff open the camera or voice control, POS blocks progress before they can allow the requested browser permission.
Check the required state before trying again: 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. Reopen /billing once and read the exact validation or configuration message. If the control remains unavailable, stop and give Support the device, terminal ID, branch, permission state, test result, and time. Note whether POS changes as staff open the camera or voice control.
The device test, browser permission, physical output, or related POS record is inconclusive after the final checkpoint: Review every suggestion or transcription before use.
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. Do not repeat the action if the records conflict; ask Support to review the device, terminal ID, branch, permission state, test result, and time. The final evidence must establish whether staff could review every suggestion or transcription before use.
Related articles
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.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.
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