Written by Marcus Rivera — Former Amazon Warehouse Manager. I ran fulfillment operations across three FCs and generated thousands of barcodes. More about me →
I spent six years managing inventory across three Amazon fulfillment centers — first in San Bernardino, then Dallas, then a 1.2-million-square-foot AR-sortable facility in Tampa. In that time I watched barcodes fail in ways you wouldn't believe: labels that scanned fine at 8am but refused to read by 3pm under different lighting, UPC codes printed so small the handheld scanners needed five passes, and — my personal favorite — an entire pallet of ITF-14 cases labeled with Code 128 barcodes because someone used the wrong barcode generator setting. That pallet sat in problem-solve for four days.
Barcodes look simple. They're not. And the difference between a barcode that scans first time every time and one that doesn't comes down to a few decisions most people don't know they're making.
GS1, the global standards organization that governs barcode formats, reports that scanning errors cost the retail industry an estimated $2 billion annually. Most of those errors come from using the wrong symbology for the job. Here's what I actually used where:
UPC-A for retail products. If your product is going on a store shelf or into Amazon FBA, it needs a UPC. Not a Code 128, not an EAN (unless you're selling in Europe). A 12-digit UPC-A barcode. I rejected three inbound shipments in one month because the supplier generated Code 128 barcodes and stuck them on retail-bound units. The system read them, but Amazon's fulfillment centers flag anything that doesn't match the ASIN's registered barcode type.
Code 128 for internal logistics. This is the workhorse of warehouses because it encodes alphanumeric data and prints more compactly than any other linear symbology. We used Code 128 barcodes on every tote, every cart, and every inbound pallet label. GS1-128 (a Code 128 variant with application identifiers) handled everything from batch numbers to expiration dates.
ITF-14 for case-level shipping. Thick black bars on a white background, printed directly on corrugated cardboard. ITF-14 barcodes survive the rough handling that would tear a printed label. I learned this the hard way when a truckload shipment arrived with paper UPC labels that had been scraped half-off by pallet straps.
In the Tampa facility we ran Zebra DS3678 scanners — industrial-grade, rated for 60,000 drops onto concrete. Even those couldn't read barcodes that were printed too small. The rule of thumb is 80% magnification of the nominal size for the symbology. UPC-A nominal width at 100% magnification is 1.469 inches. If you generate a barcode at 60% because the label template has a narrow column, you're creating a future problem-solve ticket.
I also discovered that a bulk barcode generator that runs in the browser is infinitely more practical than any desktop software. No license fees, no IT approvals, no software that stops working when the vendor updates their licensing model. When I had to generate 200 carton labels for a new product launch, the browser-based tool finished before the ERP system had even loaded the label template.
One more thing: always test-scan with the same scanner model your receiving team uses. A barcode that reads perfectly on your iPhone camera might fail on an industrial laser scanner. I've seen it happen more times than I can count.
Written by Marcus Rivera — Former Amazon Warehouse Manager. I ran fulfillment operations across three FCs and generated thousands of barcodes. More about me →