Ecommerce & retail
QR codes for inventory management
QR codes beat 1D barcodes for inventory where phones are the scanners and labels are small — a 2 cm QR holds a full item URL that any phone camera reads, while barcodes need width and dedicated hardware. Encode short IDs pointing at your inventory system, print thermal labels in bulk, and stocktake by scanning.
QR or barcode — the actual trade-off
The general comparison applies, but inventory sharpens it to a table:
| 1D barcode (Code 128) | QR code | |
|---|---|---|
| Data in 2 cm of label | ~10 digits, tightly | A full URL or 50+ character ID |
| Scanner | Laser or imager hardware | Any phone camera, plus imagers |
| Damage tolerance | One scratch across the bars kills it | Up to 30% loss at EC H |
| Scan speed on fixed hardware | Excellent | Excellent on 2D imagers |
| Reads at odd angles | Poor | Good |
| Legacy WMS hardware support | Universal | Check — older laser scanners cannot read QR |
The deciding question is usually the scanner fleet. If your operation already runs dedicated 2D imagers, either symbology works and you choose by data needs. If the "scanner fleet" is whatever phones your staff carry — true for most small and mid-size operations — QR wins outright, because the phone camera is the reader and there is no hardware to buy. The one caution: warehouses with legacy laser scanners cannot read QR at all, so audit the hardware before relabelling anything.
What to encode
Encode an identifier, not data: a short URL or plain ID that your inventory system resolves —
inv.example.com/i/BIN-A12-04
Item details, quantities and locations live in the system, where they change hourly; the label carries only the pointer, so it never goes stale. A URL payload means any phone scan lands staff in the right record with zero app friction; open-source and commercial inventory tools generally accept scanning a code into a lookup field either way. Keep IDs short — short payloads mean low-version codes with big modules that scan fast on shelf labels; a plain-text ID via the text generator also works for camera-into-field workflows.
Label everything that has an identity: bins and locations (the backbone — receiving, picking and counting all scan locations), SKUs at the shelf edge, and — only where you track units individually — serialised items, which is its own discipline. If the goods are long-lived equipment rather than flowing stock, you want asset tagging instead; the distinction matters enough that it opens that page.
Printing labels at scale
Bin and SKU labels are thermal-printer territory:
- Generate ID sets in bulk from your locations export, or
POST /api/v1/qr/batchfor up to 1,000 per request. - At 203 DPI keep modules ≥ 0.5 mm — short IDs make this easy; the thermal guide and Zebra settings page have the hardware specifics, including native ZPL QR commands for Zebra fleets.
- Direct thermal fades — fine for carton labels that live weeks, wrong for location labels that live years; use thermal-transfer or laminated stock for the permanent backbone, per direct thermal vs thermal transfer.
- Test-scan a printed label from picking distance before rolling out.
The stocktake workflow
Where QR inventory pays off visibly: counting. Scan the location code, scan or count the items, move on — each scan timestamped and attributed, no clipboards, no retyping. Two people with phones can rolling-count a small warehouse continuously instead of shutting down for an annual count, and discrepancies surface per location scan rather than per year. The label system is what makes that possible; the codes are cheap, the discipline of scanning every movement is the real cost.
FAQ
Are QR codes better than barcodes for inventory?
When phones are the scanners, yes: any camera reads a 2 cm QR carrying a full ID, with damage tolerance barcodes lack. Operations with legacy laser scanners must stay on 1D or upgrade to 2D imagers, so audit hardware first.
What should an inventory QR label contain?
A short identifier or URL resolving to the record in your inventory system — never the data itself. Quantities and locations change constantly; the label should only be a stable pointer, so it never needs reprinting.
How do I print QR labels for hundreds of bins?
Export location IDs, batch-generate codes, and print on thermal-transfer label stock — direct thermal fades within months. At 203 DPI keep modules at half a millimetre or larger, which short IDs make easy.
Can I run a stocktake with phone-scanned QR codes?
Yes — scan the location label, count or scan items, and the system timestamps each entry. Rolling counts by staff with phones replace annual shutdown counts, provided every stock movement is scanned with the same discipline.
Try it — free, no signup
Related
- QR codes for asset tagging — Fixed-asset labels that last a decade — durable materials, ID-only payloads into your asset register, and the audit-scan workflow.
- QR codes for serialised products — Unit-level codes done right — opaque serials resolved server-side, GS1 SGTIN framing, batch generation at production scale, and the use-case stack.
- QR codes on thermal printers — dots, density and fading — Module sizing for 203 and 300 dpi thermal printers, why modules must be whole printer dots, and how long direct thermal prints actually last.
- QR code vs barcode — A traditional barcode stores about 20 characters in one dimension and must be scanned in roughly the right orientation. A QR code stores up to 2,953 bytes…