Barcode Scanner Not Reading? The Troubleshooting Guide That Works Through It Properly

"The scanner's stopped working" usually turns out to mean "the scanner reads nine labels out of ten and we can't work out what's different about the tenth". Genuinely dead scanners are rare. Almost everything else comes down to one of five things, and you can work through them in a few minutes if you know the order. Last updated: September 2026. Step 1: is it reading at all, or reading and not typing? Point it at a label and watch. Does it beep and light up but nothing appears on screen? Then the decode is fine and your problem is the interface, not the scanner — jump to step 4. No beep, no green light? It's a decode problem — carry on here. This one distinction saves more time than anything else, because the two halves have completely different fixes. Step 2: the label is usually the culprit If the same scanner reads your own labels fine but fails on a supplier's, the scanner is telling you something true about the label. Print quality. Faded ribbon, a dying print head, or a label printed too fast produces bars that bleed into each other. Print a fresh one and try that — if the fresh label reads, you have a printer problem, not a scanner problem. Our barcode label printer guide covers ribbon and media choice. Quiet zones. A barcode needs clear white space either side — roughly ten times the narrow-bar width. Labels designed to fit a small space often get cropped, and a cropped quiet zone kills the read stone dead even though the barcode looks perfect to a human. Contrast. Black on white is what the decoder expects. Black on dark blue, silver-on-grey foil, or anything printed on a busy background will be marginal. Red barcodes are effectively invisible to a red-illumination laser scanner. Curved, shiny or wrinkled surfaces. A label around a small bottle, or on crinkled shrink-wrap, distorts the bars. Move the scanner further back and try a shallower angle. Damage and wear. Warehouse location labels get scuffed. If one shelf fails consistently, look at the shelf. Step 3: check the symbology is enabled This catches people out constantly and looks exactly like a fault. Most scanners ship with common symbologies on (EAN-13, UPC, Code 128, QR) and the rest off. The day a supplier sends stock labelled Code 39, ITF-14 or DataMatrix, your scanner ignores it silently. The fix is a configuration barcode from the manufacturer's manual — scan it once and that symbology is enabled permanently. Worth doing at the same time: check whether the scanner is set to transmit check digits and prefixes the way your software expects. The classic version of this is a GS1-128 or ITF-14 carton label on an inbound delivery when only retail EAN was enabled. A related trap: a 1D-only laser scanner cannot read a QR code or DataMatrix, ever, no matter what you configure. If you're being asked to read 2D codes or codes off a phone screen, you need an imager. That's the whole substance of our 1D vs 2D scanner guide. Step 4: it beeps but nothing appears Now you're in interface territory. Wrong keyboard layout. A scanner set to US layout on a UK system will scramble certain characters — hyphens, slashes and anything involving shift. Set the scanner's country/keyboard setting to UK and retest. No terminating character. If codes land in the field but never submit, the scanner isn't sending an Enter. Scan the "add CR/LF suffix" configuration barcode. Typing too fast for the application. Some web-based and remote-desktop systems drop characters when a scanner types at full speed. There's a configurable inter-character delay for exactly this — add 5–10ms. Wrong mode entirely. HID keyboard, USB serial (COM) and SPP/BLE modes all behave differently. A scanner switched into serial mode will look completely silent to an application expecting keyboard input. The focus isn't in the field. Obvious, and worth ruling out before anything else on a touchscreen till. Step 5: wireless-specific problems If it's a Bluetooth or wireless scanner, the failure pattern is usually range or pairing rather than decode. Out of range, storing to memory. Many scanners switch to batch mode when the link drops — they keep beeping and keep scanning, and the data arrives in a lump when you walk back. That looks like "it worked but nothing showed up". Paired to the wrong host. A scanner that reconnected to yesterday's tablet will happily type into it from across the room. Flat battery behaving oddly. Below about 10% some scanners decode but fail to transmit reliably. Charge it fully before diagnosing anything else — see our battery and charging strategy guide. Step 6: the environment Direct sunlight near a shop door washes out the illumination on imagers. Shade the label with your hand to test. Very cold or condensing conditions — a chiller or a yard in winter — fog the scan window. If reads fail for the first minute after coming indoors, that's condensation. A dirty window. Fingerprints, dust and label adhesive on the scan glass. Clean it with a soft cloth, not a solvent. When to stop troubleshooting and change the hardware There's a point where the scanner is simply the wrong tool: You need to read 2D codes, phone screens or damaged labels — move to a 2D imager. Reads are fine but the device keeps failing physically in a warehouse or yard — you need a rugged device, not a retail-counter scanner. Pickers are scanning hundreds of items an hour and the ergonomics are the bottleneck — a ring scanner changes the throughput maths entirely. You're counting rather than identifying — at which point UHF RFID does in minutes what scanning does in hours. Still stuck? Tell us the scanner, the label and what the software is expecting, and we'll work out which of the above it is — we do this most weeks. Talk to our UK team or open a trade account. Free UK delivery and lifetime technical support on every order.