Serialised inventory vs SKU inventory
SKU inventory holds a quantity per product line. Serialised inventory holds one record per physical unit. Use serialised where units are individually identifiable, individually valuable, or carried by people.
This is not a feature comparison. It is a decision about the shape of your records, and it is far easier to make at the start than to change later.
The two shapes
SKU inventory holds a quantity against a product: 42 of SKU-1183. Receiving ten adds ten. Selling one takes one off. One row however many you hold.
Serialised inventory holds a row per physical unit, each with its own identifier. Receiving ten creates ten rows. Selling one closes one specific row.
What each one can answer
Both tell you how many you have and what the stock is worth.
Only serialised can tell you which unit a customer bought, who was holding the one that is missing, whether a specific unit is still under warranty, or what you actually made on one particular sale rather than an average across the line.
When SKU is the right answer
Interchangeable stock, low unit value, high volume. Screws, sugar, airtime, packaging, cable by the metre. Serialising these adds work and answers no question anyone is asking.
When serialised is the right answer
Units are individually identifiable and individually valuable. Or staff carry them rather than the stock sitting on a shelf. Or after-sales service attaches to the specific unit.
Phones, motorbikes, solar equipment, meters, medical devices, high-value tools. Regulated stock often decides for you, since pharmaceuticals need batch and expiry tracking, which is serialisation under another name.
The honest costs
More work at intake. Ten units means ten identifiers, and if that is typed by hand it is slow and error-prone. Scanning changes the picture completely, and any system asking you to serialise without scanning is asking too much of your staff.
More rows. A business holding 50,000 serialised units has 50,000 records rather than 400. That is a real database consideration rather than a reason not to do it.
Why switching later is hard
Moving from SKU to serialised means your history has no identifiers in it. You can serialise from today forward, but every unit already on the shelf stays unidentified until it is counted in, and every past sale stays anonymous. It is doable and it is a project.
Going the other way is easy and loses information you cannot get back.
You do not have to choose once
For most businesses the right answer is both, decided per category. A phone shop serialises handsets and counts cases. Pick a system that lets each category decide and you never have to make one ruling for the whole business.
Doing this in StockRada
Serialisation is a per-category setting: whether a unique identifier is required, what it is called, how long it is and whether it carries a checksum. See [serialised inventory management](/serialized-inventory-management/).
Questions people ask
What is the difference between serialised and SKU inventory?
SKU inventory counts interchangeable stock as a quantity per product line. Serialised inventory identifies each unit individually. SKU is cheaper to hold. Serialised is the only one that can tell you who had a specific unit or whether it is still under warranty.
Can I use both?
Yes, and most businesses should. Decide per category: serialise handsets, count phone cases. A system that forces one ruling on the whole business is making your life harder.
Is it hard to switch from SKU to serialised later?
Harder than starting that way. Existing stock has no identifiers until it is counted in, and past sales stay anonymous. It is a project rather than a setting.