See what Klovio costs for your operation. Tell us about your operation and we will send a quote.
New: Klovio for NetSuite, SAP, Dynamics 365, Acumatica, Sage and Prophet 21New: Klovio for your ERP

Scanner won't read barcodes

Last updated September 2026

When a handheld stops reading barcodes, the cause is almost always the label, the scanner settings, or the hardware — in that order. Work down this list before swapping devices.

1. Check the label first

  1. Try scanning a different label you know is good. If that works, the problem is the label, not the scanner.
  2. Look for damage: scratches through the bars, curled edges, glare from shrink wrap, or a label printed too small.
  3. Wipe the label and the scan window on the device — dust and tape residue are the most common culprits in a warehouse.

2. Check the symbology settings

Scan engines only read the barcode types (symbologies) they’re configured for. A scanner set up for 1D codes will stare blankly at a QR or DataMatrix code, and vice versa.

  1. Open the scanner settings on the device — DataWedge on Zebra handhelds, the scanner settings app on Honeywell.
  2. Confirm the symbology on your labels is enabled: Code 128 and EAN/UPC for typical 1D labels, QR and DataMatrix for 2D.
  3. Scan a test label of each type you use.

If a manager set up your devices with a shared profile, ask them before changing settings — one device configured differently from the rest usually means its profile was reset.

3. Test with the camera fallback

Klovio can scan with the device’s built-in camera on any Android handheld. Tap the camera icon on the scan screen and point it at the label.

  • Camera reads it, scan engine doesn’t — the label is fine; the problem is the scan engine’s settings or hardware.
  • Neither reads it — the label itself is the problem.

4. Workaround for a damaged label

Don’t let one bad label stop a receive or a pick. Tap Enter manually on the scan screen and type the SKU or code printed under the barcode. The transaction records normally, flagged as a manual entry in the audit log. Reprint the label when you get a chance.

When it’s hardware

Suspect the scan engine itself when:

  • Good labels fail on this device but scan fine on an identical one
  • The aimer beam is dim, missing, or flickering
  • Scanning works after a reboot but degrades during the shift

At that point it’s a repair or replacement conversation with your hardware provider, not a settings fix.

Still stuck? Create a ticket and tell us the device model and a photo of a label that won’t scan.

Didn't fix it?

Open a ticket and a real person from the WMSHero team will pick it up.