Unit-level tracking: when to track each item individually
There’s a quiet difference between knowing you have “four drills” and knowing you have “Drill 01 through Drill 04.” The first is a number. The second is four real things you can name, hand out, get back, and repair. For a lot of inventory, the number is plenty. But the moment someone asks “which drill is in the shop for repair?” a single count can’t answer, and that’s exactly where unit-level tracking earns its keep.
This guide walks through what unit-level tracking actually is, when a plain count is the right call, the signs you’ve outgrown counting, and how it works in Simple Inventory Management step by step.
What unit-level tracking is
Most inventory is tracked by quantity. An item has a count: 12 boxes of gloves, 200 screws, 4 drills. When you use one, the number goes down. When you restock, it goes up. Simple, fast, and correct for things that are interchangeable.
Unit-level tracking is different. Instead of a single count, each physical item becomes its own named record with its own status. “4 drills” becomes four units: Drill 01, Drill 02, Drill 03, and Drill 04. Each one can carry an asset tag, and each one has a status that says where it is in its life right now: in stock, receiving, sending, or damaged. The item still shows you a number, but that number is now derived from the units underneath it.
If you want the deeper distinction between this and how serial numbers work, we covered it in serialized vs quantity tracking.
When a plain count is perfectly fine
Don’t turn this on out of habit. Counting is the right tool when your items are interchangeable and you don’t care which specific one moves. A plain quantity count is the better choice when:
- The items are identical and disposable, like screws, gloves, label rolls, or printer paper.
- You buy and consume in bulk and never need to point at one specific unit.
- Nobody borrows or returns the item, so there’s no “who has it” question.
- Tracking each piece would cost more time than it ever saves.
For these, a count is faster to maintain and just as accurate. Unit-level tracking would only add noise.
Signs you need per-unit tracking
The flip side is a set of questions a count simply can’t answer. If any of these sound like your week, you’ve probably outgrown counting:
- You need to know which specific item is out on loan, in for repair, or shipped.
- Items have real value or a serial or asset tag worth attaching to a record.
- Different units of the “same” item are in different states at the same time: one in stock, one damaged, one on its way back.
- You hand items to people and expect them back, like a tool crib or equipment pool.
- An auditor, a client, or a warranty claim might ask you to prove the history of one particular unit.
Two common shapes here are running a tool library unit by unit and the broader question of asset tracking vs inventory tracking, both of which lean on per-unit records.
How it works here
In Simple Inventory Management, unit-level tracking is a switch on the item, not a separate module you have to set up. Here’s what happens when you use it.
You flip one switch. On any item, turn on “Track units individually.” That’s the whole opt-in. Items you don’t flip keep working as plain counts, so you can mix both styles in one catalog.
It seeds one unit per item in stock. When you turn the switch on, the app reads how many you currently have in stock and creates that many units for you automatically. If the item showed 4 in stock, you immediately get 4 units to name. No bulk data entry to get started.
Each unit gets a name, an optional asset tag, and a status. Every unit has a name (Drill 01, Laptop-A7, whatever fits your shop), an optional asset tag for a serial or barcode, and a status from four choices: in stock, receiving, sending, or damaged. As a unit moves through real life, you change its status, and that one change tells the whole story of where it is.
The item’s totals are derived from the units. The item shows four totals: in stock, receiving, sending, and damaged. Once units are turned on, you don’t edit those totals by hand. They are counted up from the units’ statuses. Mark a unit damaged and the item’s damaged total ticks up while in stock ticks down, all on its own.
Every change is logged in history. Each unit’s status change is written to history, so you can answer “when did this go out and when did it come back?” for any single unit. That trail is what makes audits, warranty claims, and “who had it last” questions easy instead of stressful.
How to get started
You can turn this on for one item in a couple of minutes:
- Open the item you want to track per unit, and make sure its in-stock count is accurate first.
- Turn on the “Track units individually” switch. The app seeds one unit for each item currently in stock.
- Give each unit a clear name. Short and consistent beats clever: Drill 01, Drill 02, and so on.
- Add an asset tag to any unit that has a serial number or barcode worth recording. This is optional, but it pays off later.
- Set each unit’s status to match reality right now: in stock, receiving, sending, or damaged.
- From here on, update a unit’s status as it moves. The item’s four totals and the history trail update themselves.
The short version
Track by count when items are interchangeable and you only care how many. Track by unit when you care which one, when items carry value or tags, and when different units of the same item live in different states. The switch is reversible and per-item, so you don’t have to decide for your whole catalog at once. Start with the one item that keeps raising “which one is it?” questions, and grow from there.
Because every unit is a real record with a status and a history, your AI assistant can read and update them too. With the built-in MCP server, you can ask Claude things like “mark Drill 03 as damaged” or “which laptops are currently out for sending?” and it works against your live inventory. See it in action in unit tracking with Claude.
Learn more: if you’re weighing the trade-offs, start with serialized vs quantity tracking and asset tracking vs inventory tracking, then see a full walkthrough in running a tool library unit by unit.