IT Asset Tagging: Labels That Survive to the Next Audit

IT asset tags get printed on whatever label stock is nearest, applied, and then found unreadable at the next audit. The tag is the cheapest part of an asset management system and the part that decides whether the rest of it works.

This guide covers how to produce tags that survive.

Why asset tags fail

Almost always one of three reasons, and all three are avoidable at printing time.

Direct thermal printing. Direct thermal uses heat-sensitive paper with no ribbon, and the coating that reacts to the printhead also reacts to ambient heat and light. Tags fade over months. A tag printed this year on direct thermal and applied to equipment in a warm server room may be illegible at the next audit — which is precisely when you need it.

Paper facestock. Paper absorbs moisture, tears, and degrades under handling and cleaning. Equipment gets moved, wiped and knocked, and paper does not survive it.

Wrong adhesive. A tag applied to textured plastic, a curved surface or a cold item with standard adhesive comes away. It fails silently — the tag is found on the floor rather than on the asset, if it is found at all.

The fix for all three is the same and it is not expensive.

The correct specification

Thermal transfer, not direct thermal. Thermal transfer melts ink from a ribbon onto the label, producing an image that survives years rather than months. This is the single most important choice.

Polyester facestock. Resistant to chemicals, solvents, abrasion and temperature extremes, and dimensionally stable. Paper is fine for a shipping label read in three days; an asset tag needs to last the life of the asset.

Resin ribbon. Resin bonds with synthetic facestocks and resists abrasion, solvents and heat. Wax ribbon on polyester will not bond properly and smudges. Our media and ribbon guide covers the pairings.

Adhesive matched to the surface. Permanent for most equipment. High-tack for textured plastics and rough surfaces. Consider tamper-evident stock where removal should be visible — it destroys itself on removal, leaving a pattern behind.

That combination costs marginally more per tag than paper and direct thermal, and it is the difference between an asset register that works and one that quietly decays.

Print resolution and code size

Asset tags are usually small, and small tags mean dense codes.

A 203 dpi printer handles standard shipping labels well but may not render a small 2D code accurately enough to scan reliably. For compact asset tags, 300 dpi is generally the right choice. Our printer guide covers resolution selection.

Whatever the resolution, respect quiet zones — the clear space required around a barcode. A code crowded against the edge of a small tag will not decode even when perfectly printed, and this is one of the most common causes of tags that will not scan.

Which symbology

Asset tags are internal, so nobody outside your organisation needs to parse them. That means you are free to choose on practical grounds rather than compliance.

Code 128 for linear codes. Compact, encodes full ASCII, handles variable-length data.

Data Matrix where the tag is small. It holds a useful amount of data in a very small square with strong error correction, so it decodes even when partly worn or scuffed — which matters on equipment that gets handled.

That error correction is the real argument for 2D on asset tags. A linear barcode with a scratch through it fails; a Data Matrix with the same damage usually still reads.

Our symbologies guide covers the options, and note that Data Matrix is frequently disabled by default on scanners — check it is enabled before concluding tags do not work.

What to put on the tag

Two principles.

Include a human-readable version. Print the asset number in text alongside the barcode. Scanners fail, phones are not always to hand, and someone reading a number over the phone is a normal occurrence.

Keep the encoded data short. The tag should carry an identifier that points to a record, not the record itself. A short asset number keeps the code small and legible; encoding a description, location and purchase date produces a dense code that needs high resolution and scans poorly.

The database holds the detail. The tag holds the key.

Where to place tags on IT equipment

Practical placement decides whether audits are quick or miserable.

Servers. Front face where it is readable without pulling the machine out of the rack. Behind a bezel is common and defeats the purpose. Consider a second tag at the rear for cabling work.

Switches and network equipment. Front, clear of ports and status indicators.

Drives and components. On the carrier where visible when installed, not on the drive body where it is hidden.

Laptops and mobile devices. Somewhere that survives handling and is not covered by a case.

Avoid placing tags over ventilation openings on any equipment. It sounds obvious and it happens, and blocked airflow shortens component life — see our airflow guide.

Scanning them back

The tags are only half the system.

Asset tags in a rack are frequently in awkward positions, so a cordless scanner is considerably easier than a corded one for auditing. A rugged model is worth it if the same device is used in stores or plant rooms.

If the auditor needs to see and confirm information rather than only capture a code — confirming location, recording condition, flagging discrepancies — that is a mobile computer rather than a scanner. If the scan simply goes into a system elsewhere, a scanner is far cheaper and sufficient. Our scanner buying guide covers the choice.

One optics point: asset tags are small, so codes are dense. Standard optics may need repeated attempts where high-density optics read first time, and that cost accumulates invisibly across an audit of several hundred assets.

Common questions

Tell us your tag size, surface and environment and we will confirm the printer, media and ribbon combination.