Foundations

How to create an asset numbering system that lasts

A good asset numbering system is boring on purpose. It should still make sense after a department is renamed, a branch closes and half the assets move. The asset number is the one decision in this whole exercise you cannot cheaply reverse, because it is printed on a physical label attached to a physical thing. This is how to choose a scheme you will not regret.

Asset numbering system in practice: stacks of printed barcode asset tags carrying sequential unique asset numbers
Every tag carries one number that means nothing except that asset, which is the point.

Asset numbering system: the short version

  • The asset number has one job: uniquely and permanently link an object to a register row.
  • Short, unique, stable. Nothing in the number should be able to become false.
  • A category prefix plus a padded sequence works: IT/0142, FUR/0871.
  • Do not encode site, department or year. Those are fields, and fields can be edited.
  • Allocate number ranges, not site codes, when teams tag in parallel.

What the asset number is actually for

An asset number does one job: it links a physical object to a row in a register, uniquely and permanently. That is the whole specification.

It is not a description. It is not a filing system. It is not a place to store the department, the location or the year of purchase. Every additional job you give it makes it longer, harder to read aloud, and more likely to become wrong.

The three properties that matter

Unique. No two assets, ever, including assets that have been disposed of. Never reissue a retired number; a reused number makes historical records ambiguous.

Short. Someone will read this over the phone, type it into a search box, and write it on a form. Ten characters is comfortable. Twenty is not.

Stable. Nothing in the number should be capable of becoming false. That rules out location, department, custodian and, in most cases, the year.

A scheme that works

The pattern we recommend has two parts: a short category prefix and a sequence number.

Example Reads as
IT/0142 IT equipment, asset 142
FUR/0871 Furniture and fittings, asset 871
VEH/0007 Motor vehicles, asset 7
MED/1204 Medical equipment, asset 1204

The category prefix earns its place because it is stable. An asset almost never changes category, whereas it very frequently changes room, department and holder. It also makes a printed register readable at a glance and makes it obvious when something has been filed in the wrong class.

Pad the sequence with leading zeros so numbers sort correctly. Four digits covers up to 9,999 assets in a category, which is enough for most organisations. Use five if a single category will exceed that.

How many categories to use

Match your accounting categories, not your imagination. Most organisations need somewhere between six and twelve: furniture and fittings, computer and accessories, office equipment, plant and machinery, medical equipment, motor vehicles, land, buildings, and perhaps one or two sector-specific classes.

Thirty categories feels precise and creates constant filing disputes, drives inconsistent depreciation treatment, and produces reports finance cannot reconcile. If two categories would be depreciated identically and reported together, they should probably be one category.

Not sure which tag belongs on each asset?

Send a short asset list and a few photos of the surfaces and environment. We will recommend the right tag material and code type. Send your asset list →

What about multi-site organisations

The instinct is to add a site code. Resist it for the same reason as always: assets move between sites, and a branch closure or merger makes every tag in that building misleading.

If you genuinely need to allocate ranges so that two teams can tag in parallel without colliding, allocate number ranges rather than encoding the site. Team A gets IT/0001 to IT/0499, Team B gets IT/0500 to IT/0999. The register still records the site as a field, and when an asset moves, the field changes and the tag stays true.

Practical rules to write down

  • One number per physical asset. A desk and its chair are two assets, not one.
  • Components that are only ever used together, and would be disposed of together, can share a number. A monitor that is routinely swapped between machines should not.
  • Never reissue a number from a disposed asset.
  • Record the convention in a one-page document and give it to whoever tags next.
  • Decide who allocates numbers. One person or one system, never two people improvising.

What to do if your numbering is already a mess

You have two options and the right one depends on scale.

If the existing tags are physically sound and the numbers are merely ugly, keep them. An ugly number that is unique and attached to the right asset is doing its job. Fix the register fields around it.

If the numbers are duplicated, or the tags are failing anyway, re-tag. Do it as one exercise, keep a mapping table from old number to new so historical records stay traceable, and do not run both schemes in parallel for longer than the exercise takes.

Common questions about asset numbering system

Should we include the year of purchase?

No. It ages badly, adds characters, and duplicates a field that already exists in the register. The only common exception is organisations whose regulator explicitly requires it, and even then it belongs in the register rather than on the tag.

Can we use barcodes without a human-readable number?

You can, but do not. Scanners fail, tags get dirty, and people need to read numbers aloud. Every tag should carry the number in text as well as in the barcode or QR code.

How long should the number be?

Aim for eight to twelve characters including the separator. Long enough to be unique, short enough to say over a phone without repeating yourself.

What if we run out of numbers in a category?

Extend the sequence length for new assets rather than restarting. Mixing four and five digit sequences is untidy but harmless; reusing numbers is not.

Do disposed assets keep their numbers?

Yes, in the register, marked as disposed. The number is retired permanently. This is what lets you answer questions about assets that existed three years ago.

Can STL print tags to our existing scheme?

Yes. Tags are produced to whatever numbering convention you give us. Tell us the scheme at quoting stage rather than after production.

If you are replacing an existing asset numbering system, do not renumber retrospectively. Run the new numbers from the next asset onwards and keep the old number as a secondary reference field.

Not sure which tag belongs on each asset?

Send a short asset list and a few photos of the surfaces and environment. We will recommend the right tag material and code type.

Scroll to Top