Barcode Scanner Troubleshooting: Causes & Fixes

Not your exact symptom?

Describe it in the symptom finder and search the whole directory.

Problems on this page:

No-reads on the line Wrong code read Scanner not triggering Communication errors Handheld scanner problems Lighting and reflections Code verification failures Scanner replaced without settings

No-reads on the line

Hits OEE: Quality

Symptoms: The scanner fails to read codes, and products go to reject or are recorded manually.

Print quality of the code poor

Check the code print contrast and quiet zones with a verifier or the scanner diagnostics.

Code outside the reading window

Check the product guiding and the scanner position for every product size.

Scanner window dirty

Clean the scanner window on a set interval.

Line speed higher than the scanner setting

Check the scan rate and exposure settings for the line speed.

Prevention: Read rate tracked per shift from the scanner statistics.

Wrong code read

Hits OEE: Quality

Symptoms: The scanner reads a different code than the one intended, such as a supplier code.

Code type filter not set

Limit the scanner to the code types and lengths expected.

Two codes in the field of view

Narrow the reading area or change the scanner position.

Match code not loaded for the batch

Check the expected code in the control system for the batch.

Old labels on reused packaging

Check reused packaging.

Prevention: Mismatch rejects reviewed per batch.

Scanner not triggering

Hits OEE: Availability

Symptoms: The scanner does not read because it never receives a trigger.

Trigger sensor misaligned or dirty

Clean the trigger photo-eye and align it to the product.

Trigger delay wrong for the line speed

Set the trigger delay so the code is in the field of view when the scanner reads.

Trigger cable or connector fault

Check the trigger cable and connector.

Scanner left in a configuration or test mode

Check the scanner status and return it to run mode.

Prevention: Trigger counts compared with product counts each shift.

Communication errors

Hits OEE: Availability

Symptoms: Read results do not reach the control system or the traceability database.

Network or fieldbus fault

Check the network link, the switch port and the scanner address.

Output data format changed

Check the output format the receiving system expects.

Too many results sent at high line speed

Check the communication settings and buffer for the speed.

Firmware update changed settings

Check the scanner settings after every update.

Prevention: Communication errors logged per scanner.

Handheld scanner problems

Hits OEE: Availability

Symptoms: Handheld scanners fail to read, run flat or lose their connection.

Battery worn

Replace batteries that no longer last a shift.

Base station out of range

Check where the base station is placed and how far operators walk.

Scan window scratched

Replace the scan window.

Scanners dropped and damaged

Provide holsters or tethers at workstations.

Prevention: Handheld faults recorded per device.

Lighting and reflections

Hits OEE: Quality

Symptoms: Glare from shiny packaging or room lighting stops the scanner reading.

Shiny film reflecting the illumination back

Tilt the scanner a few degrees so it does not look straight at the reflection.

Strong ambient light or sunlight on the reading area

Shield the reading area.

Illumination or exposure setting wrong

Adjust the illumination and exposure for the packaging.

Code on a curved surface

Reposition the scanner to read the flattest part of the code.

Prevention: Read rate checked per product type.

Code verification failures

Hits OEE: Quality

Symptoms: Code verification gives low grades, and customers may reject the labels.

Printer darkness or speed set wrong

Check the printer settings for the label and ribbon.

Label material not suited to the printer

Check the label and ribbon combination with the supplier.

Ribbon wrinkling

Check the ribbon path and tension.

Print head dirty or worn

Clean the print head and replace it if lines are missing.

Prevention: Codes graded on samples per batch.

Scanner replaced without settings

Hits OEE: Availability

Symptoms: A replacement scanner fails to read or sends data the system does not expect.

No settings backup

Back up the scanner settings and store them against the asset.

Different model fitted

Check the model and its options against the original.

Network address not set

Set the address and check communication.

Not tested with real products

Test the replacement with real products before releasing the line.

Prevention: Settings backups kept for every fixed scanner.

Guidance only. Always follow lockout/tagout and your site's safe-work procedures, and verify against OEM manuals before acting.

Related equipment guides: inkjet coder · print and apply labeller · vision inspection · labelling machine · PLC · HMI panel · serialisation system · pallet labeller

Stop the same fault coming back

Recurring barcode scanner stops usually trace to a cause you cannot see by hand. The partner we recommend is Fabrico: it tracks OEE and downtime live from PLCs, IoT sensors or AI cameras; where cameras are fitted, the video of a stop sits next to its machine data so the cause can be reviewed; and a technician opens the work order from the stop in the same system. Data is hosted in the AWS EU region, and Fabrico and the company behind it hold ISO/IEC 27001, ISO/IEC 20000-1 and ISO 9001.

Book a Fabrico demo

The directory stays free.

Methods that cut recurring stops: the six big losses · root cause analysis · preventive vs predictive maintenance · TPM · SMED & changeover