Does Business Central Have License Plates?

Partly. Business Central has a real, platform-enforced way to track packages — but it doesn’t have a container as a first-class entity. That gap is narrower than it sounds, and worth understanding precisely before evaluating anything built to fill it.

The short answer

Business Central ships with package tracking: a package number is a dimension the platform tracks the same structural way it tracks lot numbers and serial numbers, and Business Central’s own posting engine can require that number to be present and correct before a transaction is allowed to post. That part is genuinely native and genuinely enforced by the platform.

What Business Central does not ship, out of the box, is a container as its own entity — no container lifecycle, no nesting of one container inside another, no printed container label, no hold you can place on a container. Package tracking identifies which items carry which package number. It doesn’t give you a “container” you can look up, move, or manage as a thing in its own right — there’s no card, no list page, no action that treats the package number as an object rather than a field value.

What package tracking actually does

Business Central groups item tracking into a small set of dimensions it treats consistently across the platform: lot numbers, serial numbers, and package numbers, plus an optional expiration date attached to a lot or serial. All of them work 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 the posting engine can be configured to insist the number is present before a document is allowed to post. That’s a real platform guarantee, not a convention some app layers on top; it’s built into how Business Central’s own inventory posting works, the same mechanism Microsoft Learn documents for lot and serial tracking generally.

What it doesn’t do is give the package number a life of its own as an object. There’s no page called “Package,” no place to record that one package physically sits inside another, no action that says “hold this package” and expects the platform to understand what that means for everything inside it. Package tracking answers which items carry this number. It has nothing to say about the container as a thing you manage day to day. The design details for item tracking go deeper into the underlying mechanics for anyone who wants Microsoft’s own technical description, and setting up item tracking covers how the tracking dimensions get configured on an item in the first place.

That native gap — a real, enforced way to tag items, but no first-class container — is exactly what third-party apps in this category exist to fill. See choosing a license-plate app for Business Central for how to evaluate one.

The confusion worth heading off: this is not Dynamics 365 Supply Chain Management

Here’s where a search can genuinely mislead someone. Dynamics 365 Supply Chain Management is a different, larger Microsoft product than Business Central — built for a different segment of customer, with its own separate warehousing engine — and it does ship a native license-plate warehousing module, with its own container lifecycle. Microsoft documents it directly: see license plate build in Dynamics 365 Supply Chain Management.

Business Central and Supply Chain Management are both part of the Dynamics 365 family, but they are separate products, built on separate platforms, with separate feature sets. Someone searching “Dynamics license plate” can land on Supply Chain Management’s documentation by mistake and reasonably conclude the feature exists everywhere in Dynamics 365. It doesn’t. Everything on this Help Center — and every native-capability claim on this page — is about Business Central specifically. If a colleague or a vendor is describing native license-plate behavior in Dynamics 365, it’s worth confirming which of the two products they actually mean before assuming it applies here. The two products aren’t interchangeable, and a feature described for one doesn’t imply anything about the other.

Why this gap exists at all

It isn’t an oversight. Business Central’s inventory model was built around item, location, and bin as the core storage concepts, with lot/serial/package tracking layered on as dimensions of an item rather than as objects in their own right. A container entity — with its own lifecycle, its own hierarchy, its own label — is a different kind of thing than a tracking dimension, closer in shape to a document than to a field value. Retrofitting that shape onto the base platform is exactly the kind of structural addition an extension is built for, rather than something every Business Central customer needs turned on by default. That’s a reasonable platform design choice, and it’s also precisely why a whole category of add-on apps exists around it.

What to check once you understand this gap

Knowing that package tracking is real but container identity isn’t native gives you a concrete question to ask any third-party app: does it build its container identity on top of Business Central’s package tracking where that’s available, riding the platform’s own enforcement — or does it maintain its container record entirely on its own, disconnected from anything the posting engine actually checks? That distinction, not a feature list, is what separates a genuinely trustworthy license-plating layer from one that only looks like it fills the gap. Choosing a license-plate app for Business Central turns that question, and four others like it, into a full evaluation checklist.