QR Code Asset Tags: How to Tag Your Whole Inventory

QR code asset tags give every item in your inventory a code that opens its record. The practical way to tag a whole inventory is to start from the asset list you already keep, with one row per asset, and make one code per row. Use a static code when the record's address lives on a domain you control and you can redirect it yourself, and for volume. Use a dynamic code when the record's address may change. For a single tag, the QR code for an asset tag page makes one in the generator.

Why tag the whole inventory from a list

Most teams already keep an asset list: a spreadsheet or an export from a system, with one row per laptop, tool, monitor or vehicle. Tagging by hand, one generator session per item, doesn't scale past a handful of assets.

Working from the list also keeps the tags consistent. Every tag follows the same rule, and the list stays the source of truth for what exists.

What the tag opens

A tag should open the asset's record: the page where someone sees what the item is, who has it, when it was last serviced and what to do if something is wrong. The code holds the address of that record, so each row needs a URL.

If your asset system gives every item an address, use it. If not, a shared page or a form that takes the tag number in its address works too. What matters is that one scan leads to one asset.

Static or dynamic for asset tags

A static code holds the address itself. A scan opens it directly and never passes through CodeQR, so CodeQR records no scans for it and the destination can't be edited after printing. A dynamic code holds a short link, so you can change the destination later, and every scan is counted.

The single-tag page recommends a dynamic code, so the tag keeps working when the record moves and nobody has to reprint it. The same reasoning applies to a whole inventory: choose dynamic when the record's address may change, because you may switch systems or the record may move. Choose static when the URL is on a domain you control and you can redirect it yourself, and for volume. A whole inventory is volume: static codes are unlimited on Pro, Business, Scale and Enterprise and count toward the monthly limit on Free and Starter, while dynamic codes count toward it on every plan. See the pricing page. Our guide on whether QR codes expire explains the trade-off.

Keep the list as the source of truth

Decide who owns the asset list and where it lives, because every tag will come from it. When a new asset arrives, it gets a row, a tag number and a URL, and the code follows from the row. When an asset is retired, mark the row instead of deleting it, so a tag that turns up later still leads to a record that explains what it was.

Give the tag numbers a fixed format from the start, and never reuse a number for a different item. Two assets with the same number would send one scan to the wrong record.

Name the tag: the tag number and the asset name

Give each code a name that people can search for. A pattern that works is the tag number followed by the asset name, such as "AT-0042 Monitor, front desk". The tag number is the unique part. The name tells you what the item is when you scan a list of codes in the dashboard.

Print the tag number next to the code as well. When a tag is scratched beyond reading, someone can still type the number.

Print tags that last

Tags live on equipment, so they face scuffs, cleaning products and sun. Use durable label material suited to the surface and keep a clear margin around the code. The QR code needs to be big enough to scan from the distance people will hold their phones. Our guide on QR code size for print has the rules.

QR codes have four error correction levels: L, M, Q and H. The default is M. A higher level tolerates more damage, and the pattern gets denser. For tags on items that get handled a lot, raise the level and test a printed sample.

The logo, colors and contrast

By default a code has a logo in the middle. On the Free plan it is the CodeQR logo and it stays; on a paid plan it is your workspace logo, and you can turn it off. On a small tag, turning it off leaves more room for the pattern. Our post on QR codes with a logo covers the trade-off. Keep black on white or another high-contrast pair.

Roll out in batches

You don't have to tag everything on day one. Start with one room, one team or one category of equipment, print those tags, and scan each one on the real item. Fix what the first batch shows, such as a URL pattern that is too long or a label that peels, and then tag the rest. Because the codes come from the list, the later batches are the same process with more rows.

Re-tagging when systems change

Your asset records may move to a new tool, and old addresses may stop working. Plan for it before you print.

With dynamic codes, you edit the destination and the physical tags keep working. With static codes pointing at your own domain, you keep the old addresses alive and redirect them to the new records. If neither is possible, you reprint, so keep the list: because each tag came from a row, you can regenerate the full set from it.

Create your account

To try this on your list, create a free CodeQR account and connect it to Make. The help article on connecting CodeQR to Zapier, Make, n8n and IFTTT shows the options, and the automation solutions page gives an overview.

Use the Make template for asset tags

The Make template creates one tag code per row of your asset list in Google Sheets: create an asset tag QR code for each Google Sheets row.

Each row has an Asset Tag, an Asset Name and a URL. The template creates a static code from the URL, names it with the tag followed by the asset name, and writes the QR Code ID and the PNG link back to the row. The guided setup asks for your Google connection and spreadsheet, your CodeQR connection (sign in to CodeQR and allow Make to access the project) and the fields to map.

The Google Sheets trigger checks for new rows on the scenario's schedule, every 15 minutes in the template. When you turn the scenario on, Make asks where to start, and "All" processes the assets already in the sheet. Make counts each module run as an operation, so a large inventory needs a Make plan with enough monthly operations.