There are two kinds of barcode you'll find in any well-run warehouse, and they do very different jobs. Bin tags label a place. Asset tags label a thing. Confusing the two is one of the most common — and most expensive — mistakes a growing operation makes.
Bin tags: labels for places
A bin tag identifies a location. Rack 04, level B, position 12. That label never moves, never gets re-printed because the stock changed, and never appears on a delivery note. It exists so that a person with a scanner can answer one question instantly: "where am I, and what is supposed to be here?"
Bin tags are cheap, durable, and forgettable. That's a compliment. Good infrastructure should be invisible.
Asset tags: labels for individual things
An asset tag identifies a specific unit of stock. Not the SKU — the unit. Two boxes of the same product would carry two different asset tags. Asset tags are how you say "this exact one, not one like it."
That's powerful, and it's expensive. Every serialised unit has to be printed, applied, scanned in, scanned out, and accounted for. Multiply that across thousands of units and you've signed yourself up for a lot of work — work that only pays off if the question "which exact one?" actually matters.
When serialising is worth it
Serialise when at least one of these is true:
- The item is high-value enough that losing one really hurts (laptops, tools, instruments).
- You need to prove which specific unit went to which customer (warranty, audit, regulatory).
- Units have meaningful differences you can't see — firmware versions, calibration dates, batch numbers.
- You're tracking returns, repairs, or loans where the same unit comes back to you.
When serialising is a tax you're paying for nothing
Don't serialise when the unit is genuinely interchangeable with the next one in the box. Cable ties. Mugs. Branded T-shirts. Boxes of screws. If your team's honest answer to "does it matter which one we pick?" is "no," then a SKU-and-quantity model is doing the right job, and an asset tag would just slow everyone down.
There is a real cost to over-serialising. Picks take longer because each unit needs an extra scan. Receiving takes longer because each unit needs a label. And worst of all, the discipline erodes — people start shortcutting the process, and now your serialised data is wrong, which is genuinely worse than not having it at all.
The mixed model that usually wins
Most real warehouses end up running both. Bin tags everywhere, asset tags only on the SKUs that earn them. The simplest rule of thumb we've seen work in practice:
Serialise individual items only when you'd want to be able to answer a question about that specific unit a year from now.
If the answer is "no idea why I'd ask that," leave it as quantity-tracked. Your future self will thank you.