How should schools label and barcode their devices?

The numbering scheme: shorter and dumber is better

The strongest recommendation in this whole topic is to use a meaningless sequential number. Not a code that encodes the building, the purchase year, the funding source, or the device type — just a number, unique across the district, that never changes and never means anything. Every attribute you might have encoded belongs in a database field where it can be edited when it changes, and all of them change. Devices move between buildings, get reassigned to different programs, and get reallocated against different funding sources; a tag that says ELEM-2022-CART3-014 becomes a lie the first time any of that happens, and it will not be reprinted.

Make the number long enough to never run out and short enough to read aloud and type. Six digits covers a very large district for a very long time. A short alphabetic prefix identifying the district is harmless and helps when devices show up somewhere they should not be, but resist the urge to add a second meaningful segment.

Decide the relationship between the tag and the serial number explicitly. The serial is the manufacturer's identifier, it is what the Google Admin console and MDMs key on, and it is authoritative for that purpose — but it is inconsistently placed, often unreadable when the sticker wears, and different per manufacturer. Your asset tag is the identifier your processes use; the serial is a field on the record, and both should be stored and both should be searchable. Devices should be findable by either.

Do not reuse numbers when a device is retired. The record persists after disposal, and reusing a number silently merges two devices' histories. Sequence forward forever; the space is effectively unlimited.

Include a human-readable version of the number on the label in a legible size, not only the barcode. Scanners fail, labels get scratched, and someone will be reading it off a device over the phone. The barcode is for speed; the printed digits are the fallback that makes the tag survive.

Barcode or QR: what to encode and why

For a simple numeric or alphanumeric asset ID, a linear barcode is entirely adequate. Code 39 is the traditional choice in K-12 because nearly every scanner reads it without configuration, though it produces a wide label for a given number of characters. Code 128 encodes the same data in noticeably less width and is equally well supported by modern hardware, which makes it the better default for a small label on a Chromebook lid.

QR codes have become the more common choice, for two reasons that matter operationally. They are two-dimensional, so they fit far more data in a compact square, and — more importantly — they are what a phone camera reads reliably. If any part of your workflow involves staff scanning with a phone rather than a dedicated scanner, QR removes a hardware purchase from the plan. They also tolerate partial damage through error correction, which is meaningful on a label that will be handled by teenagers for four years.

What you encode matters as much as the symbology. Encode the asset ID itself, plain, with no URL wrapper and no extra fields. A tag encoding a URL means a scan opens a browser instead of entering a value in a field, which is wrong for the counter workflow where speed is the point, and it permanently couples your labels to a hostname you may not control in five years. If you want a scan to be able to reach a page, let the software do that lookup from the ID.

Size the code for the shortest scan distance you actually use, then verify by scanning a printed proof — not a screen — with the exact hardware and phones your staff will use, at the angle and the lighting of a real check-in station. A code that reads perfectly on a desk under fluorescent light and fails in a dim library at arm's length is a discovery you want to make before you print four thousand labels.

Label material, and where it goes on the device

Paper labels do not survive a school year. The standard for device tagging is a polyester or polypropylene label with a permanent adhesive, printed thermal transfer with a resin ribbon so the print itself does not abrade. Direct thermal labels — the kind that darken with heat, common in shipping — fade and will blacken against a warm device, so they are the wrong technology here even though the printers are cheaper.

Tamper-evident labels are available and worth considering for higher-value equipment; they fracture or leave a residue pattern when removed. For a student Chromebook fleet, most districts find a strong permanent adhesive sufficient, but if removal has been a recurring problem, tamper-evident stock changes the incentive. Some districts also apply a clear laminate over the label, which adds durability at the cost of a slower application.

Placement should be standard across the fleet, because the entire value of a tag is that a person knows where to look without turning the device over. The two workable conventions are on the lid, in a consistent corner, and on the bottom case near an edge. Lid placement is faster to scan — a device on a counter can be read without being picked up — but is exposed to more wear and to student attention. Bottom placement survives longer and slows the line.

Avoid a few specific spots regardless of convention: over vents, over rubber feet, across the hinge, over any regulatory or serial label from the manufacturer, and anywhere on the keyboard deck or palm rest where hands and heat will lift the edges. Clean the surface before applying, since the failure is almost always adhesion to a dusty or oily surface rather than the adhesive itself.

Tag the accessories too if you issue and bill for them. Chargers in particular are high-loss, functionally interchangeable, and constantly swapped. A tag on the brick makes a returned charger attributable, and that alone resolves most disputes about what came back.

Printing and applying at scale

A desktop thermal transfer label printer is the right tool and is not expensive relative to the fleet it labels. Printing from a sheet on an office laser printer works and is what many districts start with, but sheet labels waste the remainder of a sheet on partial runs, and the material options are worse. If you tag more than a few hundred devices a year, the dedicated printer pays for itself in material and frustration.

Generate the labels from the asset system rather than from a spreadsheet, so that the number printed is the number recorded, in the same act. The failure mode of spreadsheet-driven labeling is a printed range that drifts out of sync with the database, which produces duplicate tags — the single most annoying condition to unwind, because two physical devices now claim one identity and the history of both is suspect.

Do new devices in a receiving batch rather than at deployment. When a shipment arrives, unbox, scan the manufacturer serial, print and apply the asset tag, and record model, serial, tag, purchase order, funding source, warranty term, and auto-update expiration in one pass. That is a few minutes per device once, and every one of those fields is expensive to reconstruct later.

Staff the batch as an assembly line — one person unboxing, one scanning serials, one applying labels — and it moves quickly. Districts that spread tagging across the year, device by device as they are deployed, do the setup cost repeatedly and get inconsistent placement.

When a device arrives already tagged by the vendor, decide deliberately whether to adopt their numbers or apply your own. Vendor tagging services can be genuinely useful if they will print your sequence in your format and give you the mapping file; adopting a vendor's own numbering scheme means your identifiers are set by a company you may not buy from next cycle.

Scanning hardware, and what to do when a label comes off

Dedicated barcode scanners are fast, cheap, and dumb in the useful sense: they act as keyboards, so they work with any web application without integration. For a fixed station handling hundreds of devices — check-in during collection, receiving a shipment — a corded or Bluetooth scanner is the right tool and the throughput difference is real.

Phone cameras have changed the calculus for everything that is not a fixed station. Scanning with the phone staff already carry means an inventory sweep in a classroom, a spot audit in a closet, or a second check-in station during a busy week costs nothing in hardware. It is slower per scan than a dedicated gun and it is enormously more flexible, and QR codes are what make it reliable. Most districts end up with both: guns at the counters, phones everywhere else.

Expect to replace labels, and make it easy. Tags come off, get peeled off, and get scratched illegible, and if replacing one requires finding somebody who knows how to run the printer, devices circulate untagged for months. The replacement rule is simple and important: reprint the same number. A device that has been through three labels is still one asset with one identity and one history, and issuing a new number because it was faster creates the duplicate-identity problem from the other direction.

For a device whose tag is gone entirely, the serial is your recovery path — which is why storing both from receiving matters. Look up the serial in your management console or read it off the manufacturer label, find the asset record, reprint the tag.

Audit tag legibility as part of whatever physical inventory you already run. A sweep that scans a building is also a survey of which labels no longer scan, and reprinting a handful during the sweep is far cheaper than discovering an unreadable fleet segment during year-end collection.