QR Barcode Labels: How to Specify Custom QR Asset Tags
QR barcode labels put a scannable, phone-readable identifier on every item in an asset register, which is why they have largely replaced linear barcodes on new asset-tagging projects. Specifying a custom run means settling four things: what the code encodes, how big the code has to be to read reliably, what face stock it prints on, and how the codes are serialised so no two assets carry the same one. The encoding decision comes first, because it constrains everything after it.
If you are choosing between a QR code and a Code 128 barcode, the short answer is that QR wins whenever you want staff scanning with the phones already in their pockets rather than with issued hardware.
What the code should encode
This is the decision that gets made carelessly and is expensive to reverse, because changing it means reprinting the estate.
A bare asset number. The QR code contains your internal asset identifier and nothing else. Scanning returns that string, which your asset system then looks up. Simple, compact, and the code stays small — but it is useless to anyone without access to your system, and a generic phone camera app just shows a number.
A URL. The code contains a web address that resolves to the asset record on your own system. Any phone camera opens it, no app required. This is what most organisations want now, and it is the reason QR overtook linear barcodes for asset work. The cost is a longer string, which means a denser code, which means a slightly larger label or a more forgiving scan environment.
A URL plus a redirect layer. The printed code points at a short redirect address you control, and the redirect decides where the user actually lands. This is worth understanding before you print, because it is the difference between a tag you can repurpose and one you cannot. If your asset platform changes in three years, a redirect layer means updating a mapping table. Without it, the printed codes point at a dead system and the whole estate is reprinted.
If you are new to the format itself, what is a QR code covers the basics before you commit to an encoding scheme.
Keep the encoded string short
QR codes get denser as the encoded string gets longer. More characters means more modules — the small squares that make up the code — packed into the same physical area, and denser codes demand better print quality, better lighting and closer scanning.
The practical implication for QR barcode labels: a short URL scans from further away and at worse angles than a long one. A brief path on a short domain is a materially easier code to read than a long path carrying query parameters, at the same label size. If you are setting up the redirect layer described above, use it as an opportunity to keep the printed string genuinely short rather than reproducing your internal URL structure on the tag.
Error correction is the other lever. QR codes carry redundancy so a damaged or partly obscured code still resolves, and the level is selectable when the code is generated. Higher redundancy survives more scuffing but adds modules, so it costs density. For asset tags on equipment that gets handled, the trade is usually worth making; for tags on clean indoor assets, it is less critical.
Size the code for the worst scan, not the best
A QR code that reads perfectly on a bench under good light will not necessarily read on a machine in a dim corner at an awkward angle, held at arm’s length. Specify for that second case.
Three things determine whether a code scans in the field:
Physical size of the code area. Bigger modules read from further away and tolerate more angle. The code is square, so the code area — not the overall label — is what matters. A wide rectangular tag with a small square code in the corner scans like a small tag.
The quiet zone. QR codes need clear margin around them. Crowding the code with text, a logo or the label edge causes intermittent read failures that are frustrating to diagnose because the code looks fine.
Contrast against the face stock. Dark code on a light background is what readers expect. Inverted or low-contrast codes are readable by some scanners and not others.
Because the answer depends on your scanning distance, your lighting and your devices, test before you commit to a full run. Print the actual encoded strings at the actual size, apply them to the actual assets, and have the people who will be scanning try it in the place they will be doing it.
Face stock and finish for QR barcode labels
Face finish matters more for QR barcode labels than it does for text-only tags, and it is where specifications most often go wrong.
Avoid mirror and chrome finishes for codes. Reflective faces bounce light straight back at the reader and wash out the contrast the scanner depends on. PolyCheck Chrome is a case in point — it is not a barcode-safe choice, and that applies equally to QR. It is specified for its visual finish, not for scanning.
Matte and semi-gloss white are the defaults. PolyAsset White is a white semi-gloss polyester and gives the contrast a code needs. Where you want a metallic industrial look, PolyAsset Platinum is a metallic aluminum-look polyester — sample-test it with your own scanners and your own lighting before a large run, because how a metallic face behaves under plant lighting is a question about your environment rather than about the label.
The stock QR code label is the starting point if you want to see the format in hand before ordering custom. The wider QR code labels range shows the available configurations.
Decide what happens when the tag comes off
Asset tags carrying QR codes face the same removal question as any other asset tag, and the answer determines which construction you order. A tag that can be peeled off one machine and stuck on another breaks the link between the code and the asset — which, on a QR-based system, means the scan returns the wrong record with complete confidence.
PolyBreak uses an aggressive solvent-based adhesive with a destructible face, so the tag fractures rather than lifting away in one piece. PolyVoid leaves a VOID pattern on both the equipment and the label, making removal visible from either side. Standard PolyAsset constructions remain intact if removed with effort, which is fine where transfer is not a realistic risk.
The removal decision is covered in more depth in industrial asset tags, alongside the surface and adhesive questions.
Serialisation: every tag unique
The point of QR barcode labels on assets is that each one is different, which makes this a variable-data print job rather than a repeat print.
Supply the data as a list — one row per tag, with the encoded string and whatever human-readable text goes alongside it. Settle these before the order:
The encoded value per tag. Either the full URLs, or the ID values plus the URL pattern they slot into. Sending a pattern and a range is usually cleaner than sending several thousand assembled URLs.
The human-readable line. The code is for the scanner; printed text is for the person standing in front of the asset when their phone battery is dead. An asset number, and often a site or department abbreviation, is enough.
Sequence and spares. Decide where numbering starts and order above the asset count — applications get spoiled, and a short reorder of serialised labels costs more per unit than the original margin.
All of this assumes the register the codes resolve to is already structured — because the numbering scheme on the tag is only as useful as the record behind it. If that groundwork is not settled, this guide to building an equipment asset register covers what to capture per asset and how to organise it before you commit to a scheme. On the label side, what is an asset tag label sets out the basics.
Getting custom QR barcode labels quoted
Custom QR barcode labels are quote-led rather than off-the-shelf, because the price depends on the size, the face stock, the quantity and the variable-data setup. To get a useful number back, tell us: the quantity, the label size or the assets it has to fit, the face stock if you have settled on one, and the encoded format — full URLs, a URL pattern with an ID range, or bare asset numbers.
Request a quote with those four details and we will come back with pricing and a recommendation. If you would rather test the format on your own equipment first, ask for samples with the quote and scan them where the tags will actually live.
