Someone shouts "this one won't scan," and eight times out of ten the scan engine is fine.
You still need an order to work through though. Otherwise you are just swapping parts and hoping.
Look at the code first, the device second
When a unit fails to read, the first move is not opening the housing. It is looking at the code itself.
Take a photo. Zoom in.
The answer is often right there in the picture — the print is smudged, the edges have bled, the label sits on a creased box corner, or stretch film is reflecting light across the surface.
No scan engine reads any of those, however many you swap in.
Print quality matters more than the engine
A few print parameters drive read rates directly.
Resolution too low and the boundary between bar and space is not sharp enough for the engine to tell them apart. Thermal printers with a dirty head start printing codes that are fuzzy on one side.
Code density too high — too much data packed into the same area — narrows the bars and raises the bar for both printing and reading.
Then there is the quiet zone. A barcode needs clear margin on both ends. Plenty of "won't scan" cases turn out to be a label placed against a border, quiet zone gone.
One-dimensional or two-dimensional
Old question, but every new person on the job trips on it.
1D is the vertical bars. Small capacity, usually just an identifier. 2D is the square block, holds more, and carries error correction — you can lose a corner and still read it.
If your labels are already 2D, the engine has to support 2D decoding. Spell that out at purchase time; not every standard configuration includes it.
The reverse happens too: a 1D-only engine pointed at a QR code will never read it. We have seen that enough times, and it usually traces back to a configuration mismatch at ordering.
Imager or laser
Put simply, a laser sweeps a line across the code; an imager takes a picture and decodes it.
Lasers stay very reliable on 1D, especially long-range 1D, and they cost less.
Imagers read 2D, and they read codes off screens — phone coupons, digital waybills. Lasers mostly cannot handle screen codes.
That is why imagers dominate now, unless the job is nothing but long-range 1D.
Distance gets overlooked
Every engine has a working range. Further is not automatically better, and neither is closer.
Press too close and you fall inside the minimum distance and get nothing. Too far and you are past the depth of field, same result.
What usually happens: people get used to one device's sweet spot, a new model arrives with a different range, muscle memory does not change, and suddenly nothing scans.
Give the operators a few days. It often resolves itself.
Curved surfaces and glare
Codes on cylinders or curved panels are read at an angle, and read rates drop.
Codes printed straight onto metal reflect enough light to interfere. Those usually need a purpose-made label, or a change in scan angle.
Continuous or triggered
Some units support presentation scanning — hold it near and it fires, no button. On sort lines and assembly lines that is a real gain.
For walking work like stocktaking or inspection rounds, presentation mode mis-fires: anything passing nearby gets read in.
Stick with trigger mode for those.
If you actually need to know whether the engine is dead
Same code, other device reads it, this one does not — the problem is likely this unit. Could be a dirty scan window, could be genuinely failed.
If nothing reads it, reprint the label and try again.
Most of the time, a fresh label is the whole fix.
You still need an order to work through though. Otherwise you are just swapping parts and hoping.
Look at the code first, the device second
When a unit fails to read, the first move is not opening the housing. It is looking at the code itself.
Take a photo. Zoom in.
The answer is often right there in the picture — the print is smudged, the edges have bled, the label sits on a creased box corner, or stretch film is reflecting light across the surface.
No scan engine reads any of those, however many you swap in.
Print quality matters more than the engine
A few print parameters drive read rates directly.
Resolution too low and the boundary between bar and space is not sharp enough for the engine to tell them apart. Thermal printers with a dirty head start printing codes that are fuzzy on one side.
Code density too high — too much data packed into the same area — narrows the bars and raises the bar for both printing and reading.
Then there is the quiet zone. A barcode needs clear margin on both ends. Plenty of "won't scan" cases turn out to be a label placed against a border, quiet zone gone.
One-dimensional or two-dimensional
Old question, but every new person on the job trips on it.
1D is the vertical bars. Small capacity, usually just an identifier. 2D is the square block, holds more, and carries error correction — you can lose a corner and still read it.
If your labels are already 2D, the engine has to support 2D decoding. Spell that out at purchase time; not every standard configuration includes it.
The reverse happens too: a 1D-only engine pointed at a QR code will never read it. We have seen that enough times, and it usually traces back to a configuration mismatch at ordering.
Imager or laser
Put simply, a laser sweeps a line across the code; an imager takes a picture and decodes it.
Lasers stay very reliable on 1D, especially long-range 1D, and they cost less.
Imagers read 2D, and they read codes off screens — phone coupons, digital waybills. Lasers mostly cannot handle screen codes.
That is why imagers dominate now, unless the job is nothing but long-range 1D.
Distance gets overlooked
Every engine has a working range. Further is not automatically better, and neither is closer.
Press too close and you fall inside the minimum distance and get nothing. Too far and you are past the depth of field, same result.
What usually happens: people get used to one device's sweet spot, a new model arrives with a different range, muscle memory does not change, and suddenly nothing scans.
Give the operators a few days. It often resolves itself.
Curved surfaces and glare
Codes on cylinders or curved panels are read at an angle, and read rates drop.
Codes printed straight onto metal reflect enough light to interfere. Those usually need a purpose-made label, or a change in scan angle.
Continuous or triggered
Some units support presentation scanning — hold it near and it fires, no button. On sort lines and assembly lines that is a real gain.
For walking work like stocktaking or inspection rounds, presentation mode mis-fires: anything passing nearby gets read in.
Stick with trigger mode for those.
If you actually need to know whether the engine is dead
Same code, other device reads it, this one does not — the problem is likely this unit. Could be a dirty scan window, could be genuinely failed.
If nothing reads it, reprint the label and try again.
Most of the time, a fresh label is the whole fix.
