Barcode Not Scanning? A Troubleshooting Guide
A barcode that will not scan is rarely a broken scanner. In most cases the scanner is working correctly and refusing to decode something it genuinely cannot read — which is a different problem with a different fix.
This guide works through the causes in order of likelihood, covering both the scanner side and the label side.
First: does it scan anything at all?
One test separates two completely different problems.
Try a known-good barcode — the one printed on the scanner box, a product from a shelf, anything you have scanned successfully before.
If that scans: the scanner is functioning. The problem is with the specific codes you are trying to read, or with the configuration for them. Skip to the label and configuration sections.
If nothing scans at all: check power and connection first. On a corded scanner, confirm the cable type matches what the installation expects — USB, RS-232 and keyboard wedge are not interchangeable. On a wireless scanner, check pairing and battery. Most scanners give an audible and visual power-on indication; no beep and no aimer light usually means power rather than decode.
Cause one: the code is finer than the scanner can read
This is the most common genuine incompatibility, and it is fixed at purchase rather than in software.
Scanner optics are rated by the narrowest bar width they can resolve, measured in mil — thousandths of an inch. A typical entry-level imager reads down to around 5 mil. High-density optics read down to around 3 mil, which is roughly 40 percent finer.
If your codes are printed small — specimen vials, unit-dose pharmaceutical packaging, surgical instruments, electronic components — a standard-optics scanner will struggle regardless of settings.
The diagnostic tell is important: the scanner usually does not fail outright. It reads the code eventually, after two or three attempts. Nobody logs that as a fault, and the time cost accumulates invisibly across a shift.
For fine codes, see the Honeywell Xenon 1950g with high-density optics.
Cause two: the code is further away than the optics allow
The mirror image of the same problem. Standard-range optics read from a few centimetres to around a metre. Reading a location label several levels up a high-bay rack needs extended or auto-range optics, which are a different variant — up to around 20 m on the longest-range models.
Optics are fixed at manufacture. You cannot configure standard range into extended range, so this is a specification error rather than a fault. See the Honeywell Granit XP 1991iXR for extended range.
Cause three: it is a phone screen and the scanner is a laser
Absolute, and worth checking early because it explains a whole category of complaints.
Laser scanners cannot read screens at all. They read a single line of a printed barcode by detecting reflected light, and a backlit screen does not present that.
Mobile coupons, digital loyalty cards, e-tickets, click-and-collect confirmations, membership credentials, payment QR codes and digital student IDs are all screen-based. If your scanner is a laser, none of them will ever work, and no setting changes that.
Every scanner we supply is a 2D area imager, which reads screens and printed codes alike. Our scanner buying guide covers the difference.
Cause four: the symbology is not enabled
A common and easily fixed cause on new deployments.
Scanners support many barcode types — Code 128, Code 39, EAN, UPC, QR, Data Matrix, PDF417, GS1 DataBar and others — but not all are enabled by default. Manufacturers ship with common symbologies on and less common ones off, because leaving everything enabled slows decoding and risks misreads.
If one specific type of code fails while others work, this is very likely the cause. GS1 DataBar and Data Matrix are frequently disabled out of the box, and both are widely used — DataBar on retail produce and coupons, Data Matrix on components and medical items.
The fix is scanning a configuration barcode from the manufacturer’s programming guide, or using their configuration utility.
Cause five: the label is the problem
If the scanner reads other codes fine but not yours, look at what you are printing.
Faint or patchy printing. Insufficient contrast between bars and spaces. Usually darkness settings, worn printhead or poor media — see our printhead guide.
No quiet zone. Barcodes need clear space either side, and a code printed too close to the label edge or crowded by text often will not decode.
Too small for the resolution. Printing a dense 2D code at 203 dpi produces a code the printer cannot render accurately. Small codes need 300 dpi or higher.
Faded direct thermal labels. Direct thermal fades within months under heat and light. A label printed last year and stored in a warm area may simply no longer have enough contrast.
Damaged or curved surfaces. Torn, creased or heavily curved labels break the code geometry. 2D imagers tolerate this far better than lasers, which is another argument for them.
Reflective or laminated surfaces. Gloss can reflect the illumination straight back. Changing the scan angle usually resolves it.
Cause six: it scans but nothing appears
Different problem entirely, and worth separating because people report it as a scanning failure.
If the scanner beeps and lights green but no data reaches the application, the decode worked and the output path is wrong.
Check the interface mode — most scanners present as a USB keyboard by default, so the data appears wherever the cursor is. If the cursor is not in the right field, the data goes nowhere visible. Check that the correct field has focus before assuming a fault.
Also check for a missing terminator. Many applications need a carriage return after the barcode data to move to the next field, and if that suffix is not configured, everything ends up concatenated in one field.
A quick diagnostic order
Does a known-good barcode scan? If no, check power, cable type and pairing. If yes, does the scanner beep on your code? If it beeps but nothing appears, it is an output or focus problem. If it does not beep, check whether the symbology is enabled, whether the code is within the optics range and density, and whether the label has adequate contrast and quiet zones.
That sequence resolves the large majority of cases without replacing anything.
If you conclude the scanner is genuinely wrong for the job, tell us the smallest code you need to read in mil, the furthest distance, and whether phone screens are involved — those three answers determine the right model. Browse our scanners range.
Common questions
My scanner reads some barcodes but not others. Why?
Most likely the symbology is not enabled. Scanners ship with common types on and less common ones off, and GS1 DataBar and Data Matrix are frequently disabled out of the box. Scanning a configuration barcode from the manufacturer’s programming guide enables them.
The scanner beeps but nothing appears on screen. What is wrong?
The decode worked, so this is an output problem. Most scanners present as a USB keyboard, so data appears wherever the cursor is — check the correct field has focus. Also check whether a carriage return suffix is configured, since without it data concatenates in one field.
Why can my scanner not read barcodes on phone screens?
If it is a laser scanner, it never will. Lasers detect reflected light from a printed code and a backlit screen does not present that. Reading mobile coupons, e-tickets and payment QR codes requires a 2D area imager, and no setting changes this.
My scanner needs two or three attempts per scan. Is it failing?
More likely the codes are finer than its optics can resolve. Entry-level imagers read to around 5 mil; high-density optics read to around 3 mil. The scanner does not fail outright, it just needs repeated attempts — which is why the cost stays invisible.
Why will my own printed labels not scan?
Common causes are insufficient print contrast from darkness settings or worn printheads, no quiet zone around the code, a dense 2D code printed at 203 dpi when it needs 300, or direct thermal labels that have faded with heat and light exposure.
Send us the smallest code size, the read distance and whether phone screens are involved, and we will confirm whether the scanner is wrong for the job.
