Package Tracking vs. Lot and Serial Tracking in Business Central
Business Central doesn’t have one item-tracking mechanism with an on/off switch. It has three, and they answer three different questions — which item, which batch, which physical unit is this — and an item can carry any combination of them at once. Getting the distinction right matters before you evaluate anything, ContainerQ included, that’s built on top of it.
Three dimensions, three questions
Business Central’s own documentation frames all three as ways of assigning “unique numbers as identification” to stock as it moves through purchasing, sales, and warehouse operations. Each one is really answering a different question about the same physical item:
| Dimension | The question it answers | Typical grain |
|---|---|---|
| Serial No. | Which individual unit is this? | One number per physical unit — a single chair, a single piece of equipment. |
| Lot No. | Which production or receipt batch did this come from? | One number per batch — a run, a shipment, a harvest. |
| Package No. | Which physical package, box, or container is this currently in? | One number per package — which can itself hold several lots, several items, or both. |
None of the three is “better” than the others in some general sense — they’re orthogonal facts about the same stock, and Business Central tracks all three the same structural way: a number gets assigned to a quantity of an item, that assignment travels with the item through receiving, put-away, movement, and shipping, and — where the item’s setup requires it — the posting engine won’t let a transaction post without it.
How they combine on one item
The clearest way to see this is Microsoft’s own example from the setup documentation. Say you manufacture a chair, item number 1900-S. A single chair carries its own serial number, 1001. Four chairs from the same production run get bundled into one lot, LOT0001. When it’s time to ship, several lots go out together in one physical container, CONTAINER010 — which, in the same shipment, also happens to carry a lot of side tables and a lot of lamps, each a completely different item with its own lot number.
That’s serial, lot, and package all present in one small scenario, each doing a different job: the serial number identifies one chair, the lot number identifies the batch of four chairs it came from, and the package number identifies the physical box that happens to be carrying that lot alongside two unrelated items’ lots. None of the three numbers substitutes for either of the other two — a package number tells you nothing about which specific chair is inside without also reading the serial number, and a serial number tells you nothing about what else shares its container without also reading the package number.
What decides which dimensions apply
An item doesn’t get to use any of these numbers by accident. Whether an item is tracked by lot, serial, package, or some combination is set on that item’s Item Tracking Code — a setup record with its own Serial No., Lot No., and Package Tracking sections, each independently switched on or off. Setting up item tracking walks through configuring all three.
The setting that actually changes behavior, for all three dimensions, is Specific Tracking — SN Specific Tracking, Lot Specific Tracking, Package Specific Tracking. Turn one on, and Business Central requires you to specify which serial number, lot number, or package number an outbound transaction is drawing from before it will let you post — the number assigned when the item entered inventory has to follow it out again. Leave a dimension’s Specific Tracking off, and Business Central still lets you record a number for informational purposes (useful for something like a warranty record you want on file even though you don’t enforce it downstream), but it doesn’t require the number to match on the way out, and it doesn’t stop a mismatched transaction from posting.
That single toggle, repeated per dimension, is what separates “we write this number down” from “the platform’s own posting engine refuses to let this number go missing or get swapped.” It’s the same distinction does Business Central have license plates? makes about package tracking specifically — and it’s true of all three dimensions equally, not just package.
Why “package” isn’t a lesser dimension
It’s tempting to read “lot” and “serial” as the real tracking mechanisms and “package” as some kind of afterthought bolted on for logistics convenience. That’s not how Business Central actually implements it. Structurally, Package No. is enforced exactly the same way Lot No. and Serial No. are — the same Specific Tracking toggle, the same posting-time requirement, the same item ledger entry field. The difference isn’t in how strongly the platform enforces it; it’s in what physical fact each dimension is naming. A lot number names a batch. A serial number names a unit. A package number names a container.
That’s exactly why package tracking is the dimension a license-plating layer can build the strongest guarantee on top of: it’s the one BC dimension whose entire job is naming a physical container, rather than naming a batch or a unit that merely happens to sit inside one. What is a license plate in warehousing? covers why that container-shaped identity is the whole point of license plating in the first place.
The honest boundary
None of this makes Business Central’s native tracking a substitute for a real container entity. Package tracking answers which items carry this package number — it doesn’t give the package number its own lifecycle, its own nesting relationship to other packages, or its own hold you can place independent of the items inside it. Lot and serial tracking answer their own narrower questions just as precisely, and just as narrowly. All three dimensions are real, enforced facts about items — none of them is a fact about a container as a thing you manage on its own. Does Business Central have license plates? covers that gap in full, and binding modes explained covers how a container-identity layer built on top of these three dimensions has to answer for the gap between what BC enforces natively and what it doesn’t.
The practical takeaway
Before evaluating any container or license-plating tool against a specific item, check which of the three dimensions that item actually uses, and whether Specific Tracking is turned on for it. An item with Package Specific Tracking on gives a container-identity layer something real and platform-enforced to stand on. An item tracked only by lot or serial, with no package dimension in play at all, gives that same layer nothing native to lean on — whatever container relationship exists for that item has to be a claim the app itself maintains and re-checks, not a fact Business Central’s own posting engine already refuses to let go wrong.