Barcode Label Design: Templates That Actually Scan
Label templates are usually designed once by whoever set the system up, and then inherited. Most scanning problems that get blamed on hardware originate in that template, and they are cheap to fix if you know what to look at.
Quiet zones are the most common failure
Every barcode requires clear space either side of it. That space is not decoration — it tells the scanner where the code begins and ends.
A code printed too close to the label edge, or crowded by text, product names or borders, frequently will not decode even when the printing itself is perfect.
This is the single most common cause of labels that will not scan, and it is invisible to the person who designed the template because it looks fine.
Leave clear space around every code, and be particularly careful on small labels where the temptation to use every millimetre is strongest. Our troubleshooting guide covers where this sits among other causes.
Match code size to printer resolution
The second most common origin, and it appears when someone shrinks a label to fit more on.
A printer can only render detail as fine as its resolution allows. A dense 2D code printed at 203 dpi may not render accurately enough to scan reliably, and the failure is intermittent rather than absolute — which makes it harder to diagnose than an outright failure.
Rough guidance: large linear barcodes are fine at 203 dpi; small dense 2D codes generally need 300 dpi or higher. Our printer guide covers resolution selection.
If a template is being reduced in size, the code needs checking again at the new size rather than assumed to scale.
Always include human-readable text
A small addition with disproportionate value.
Print the encoded data as text alongside the barcode. Scanners fail, codes get damaged, and someone reading a number over the phone or typing it manually is a normal occurrence rather than an exception.
A label whose only representation of the data is a barcode becomes useless the moment the barcode is scratched.
Keep the text legible — small enough to fit, large enough to read at arm’s length in a warehouse or under poor lighting.
Encode a key, not a record
A design decision that determines how well the label works.
The code should carry a short identifier that points to a database record, not the record itself. Encoding description, location, date and specification produces a dense code that needs higher resolution, occupies more space and scans less reliably.
The database holds the detail; the label holds the key. Our asset tagging guide covers this for equipment labelling specifically.
The exception is where a label must be readable by an organisation that cannot query your database — a trading partner, a carrier — and there the format is specified rather than chosen. Our compliance guide covers those cases.
Orientation and placement
Two practical points that are decided at design time and lived with afterwards.
Orientation relative to the scanner. 2D imagers read in any orientation, which removes most of this concern — but where a fixed-mount scanner reads items passing a station, the code needs to present consistently.
Placement on curved or small surfaces. A code wrapped around a vial or a cable curves with the label, which makes it harder to read. Placing it on the flattest available section, and choosing a symbology that tolerates curvature, both help. Our healthcare guide covers this for specimen labelling.
Darkness affects the code, both ways
Worth including here because it is a template-adjacent setting that people move without realising the consequence.
Too low gives insufficient contrast between bars and spaces, and the code fails.
Too high causes bars to bleed and widen, which fails element width accuracy — and it also shortens printhead life by making elements work harder than necessary on every label.
Set it to the lowest value that produces a clean, verifiable code, not to maximum. Our verification guide covers measuring rather than guessing.
Test before rolling out
Three tests that catch nearly everything.
Print at the real size on the real media. A template that works on a test print at a different size, on different stock, has not been tested.
Scan with the worst scanner in the chain, not the best. If a customer or a colleague reads the label with older equipment, your newest high-density scanner passing tells you nothing.
Test a damaged label. Scuff it, crease it, get it slightly wet. Real labels arrive in that condition, and this is where 2D codes with error correction show their advantage over linear ones.
Re-test after any change — new media batch, new ribbon type, replaced printhead, altered size, changed darkness. Each is a point where a working template can stop working.
Common questions
Why will my label not scan when the printing looks perfect?
Most often quiet zones. Every barcode needs clear space either side, and a code crowded by text or too close to the label edge will not decode however well it is printed. It looks fine to whoever designed the template.
Can I just shrink a label template to fit more on?
Not without rechecking the code. A printer renders only as fine as its resolution allows, so a code that scaled down may no longer render accurately — and the failure is intermittent rather than absolute, which makes it harder to diagnose.
Should the barcode contain all the item data?
No. Encode a short identifier pointing to a database record. Encoding description, location and dates produces a dense code needing higher resolution that scans less reliably. The exception is labels read by organisations that cannot query your database.
Is higher darkness better for scanning?
No. Too low gives insufficient contrast, but too high causes bars to bleed and widen, failing element width accuracy — and it shortens printhead life. Set it to the lowest value producing a clean verifiable code.
How should I test a new template?
Print at the real size on the real media, scan with the worst scanner in the chain rather than the best, and test a label that has been scuffed, creased or slightly wetted — because real labels arrive in that condition.
If labels have stopped scanning after a change, check quiet zones and code size against printer resolution before suspecting the hardware.
