The most common cause: print scaling, not the barcode itself

Nine times out of ten, a shipping label barcode that won't scan wasn't broken when it was created — it got distorted on the way to paper. The single biggest culprit is a print dialog set to "Fit to Page," "Shrink to Printable Area," or any auto-scaling option instead of 100% / Actual Size. That setting quietly shrinks or stretches the whole label, including the barcode, and a scanner reading bars and spaces at the wrong proportions simply fails. This is especially common when a 4x6 label PDF gets sent to a printer loaded with Letter paper, or opened in a browser preview instead of a dedicated PDF viewer. Before anything else: open the PDF, go to print settings, and confirm scale is locked to 100% and paper size matches what's loaded in the tray.

The barcode is enlarged past the scanner's window, or too small to resolve

Scanners at postal counters read through a fixed-size window, and a barcode that's been enlarged — even without visible distortion — can print larger than that window can capture in one pass, so parts of it fall outside the scan zone. Going the other direction, aggressively shrinking a label to save label stock can push the bars below the resolution a standard laser or camera scanner can resolve, especially on a low-DPI printer. Both problems trace back to the same root cause as scaling issues: something between label creation and paper changed the barcode's physical size. Reprinting at the label's native size, generated at full resolution rather than a low-DPI draft or web-preview export, resolves nearly all of these cases.

Not enough blank space around the barcode (the "quiet zone")

Every barcode needs a clear margin of blank space — the quiet zone — on either side before the bars begin. Industry guidance puts the minimum at roughly 10 times the width of the barcode's narrowest bar. If a label design crops the barcode too close to its edge, tapes over part of that margin, or a badge/text element gets placed too close to it, the scanner can't tell where the barcode actually starts and stops, and the read fails even though every individual bar printed cleanly. This is a design problem, not a printer problem — it has to be fixed in the label layout itself, not by reprinting.

Thermal printer problems: low ribbon, faded print, or dust

If you're printing on a dedicated thermal label printer (Zebra, Rollo, and similar), a barcode that scanned fine last week can stop scanning for reasons that have nothing to do with the file. A thermal transfer printer running low on ribbon prints progressively lighter bars until contrast drops below what a scanner needs. Direct thermal printers (no ribbon) fade with heat-head wear or if the darkness/heat setting is too low. Dust and label-stock particulate — which thermal printers generate constantly — can also settle into the print head and create voids inside the bars or gaps in the quiet zone. Cleaning the print head, replacing ribbon before it's fully spent, and printing a test label under bright light to check for washed-out bars catches most of this before it reaches the counter.

Physical damage, and printing on the wrong side of the label

A barcode that printed perfectly can still fail if the label gets bent around a box edge, smudged before the ink or thermal print fully sets, or creased across the bars — any of which breaks the continuous lines a scanner needs to read. On rolls of pre-cut label stock, it's also easy to load the sheet backwards and print on the adhesive side or the liner instead of the coated face, which produces a barcode that looks fine on screen but never transfers cleanly to paper. Letting a freshly printed label sit flat for a few seconds before handling, and double-checking which side of blank stock is print-ready, avoids both.

A squashed barcode: why aspect ratio matters as much as size

A subtler version of the scaling problem is a barcode that's the right overall size but the wrong shape — stretched wider or squashed shorter than it was generated, which distorts the width ratio between bars and spaces that the scanner actually decodes. This happens when a label layout forces a barcode into a fixed box instead of letting it keep its native proportions. It's a real enough failure mode that pixeltools' own Shipping Label Generator was built around avoiding it: its PDF export renders the barcode from its actual pixel dimensions and always scales height and width together to preserve that native aspect ratio, rather than stretching it to fill whatever space is left on the label, with barcode height clamped between roughly 28 and 80 points so it's never squeezed thin or blown out oversized either. (Note: this tool's barcode encodes the label's own reference number, not a live USPS/UPS/FedEx tracking code — it's a label template, not a carrier's postage system.)

What actually happens if the counter can't scan it

This is the part worth not panicking over: an unreadable barcode does not mean a lost or refused package. Postal and carrier staff can manually key in the tracking number printed under the barcode, and the package still ships normally — it just moves through the system a little slower, and tracking updates may lag or skip a scan event until the package reaches a facility where it gets rescanned or relabeled. As long as the address text on the label is legible, the package is handled like any other. It's an inconvenience for tracking visibility, not a shipping failure — but it's still worth fixing before drop-off so you're not relying on a clerk's patience for manual entry.