How it works

Build a plate. Prove it. Ship it.

A license plate is a claim — "this pallet holds exactly these goods." ContainerQ's job is to keep that claim true from the moment it's created to the moment it leaves the dock, by checking it against Business Central's own ledger at every step.

Build the plate

Create a pallet, tote, carton or container and give it an identity you can print and scan — a GS1 SSCC-18. From here on it's a single object your team and your system both recognize.

Pack items onto it

Add stock to the plate. Lot, serial and package numbers — plus expiration dates — are attached the way Business Central requires, so tracked goods never lose their tracking as they join the plate.

Move it as one unit

One instruction relocates the whole plate to a new bin or location. Business Central's inventory moves with it in the same transaction — no reconciling two systems afterward.

Nest and unnest

Stack totes on a pallet, pallets in a container, many levels deep. Operating on the outer unit reaches everything within it — including holds.

Label & ship

Print a GS1-128 shipping label carrying the plate's SSCC and its contents, so anyone downstream can scan it. Ship the unit and the ledger reflects exactly what left.

Confirm against the ledger

Behind every one of those steps: an independent second read of Business Central's records confirms the rows actually landed before the operation is reported complete. If the ledger doesn't agree, it doesn't claim success.

Why a plate stays honest

Two ways to bind identity — both keep the plate from drifting.

How a plate's identity is anchored depends on how the goods are tracked. Either way, the plate can never quietly disagree with the ledger.

Platform-enforced

For package-tracked goods, the plate rides on Business Central's own tracking kernel. The platform itself won't let the record and the goods come apart.

Continuously re-verified

Otherwise the plate is attested by a registry that keeps re-reading the ledger to check it still matches what it claims — and visibly flags it the moment it doesn't.

The point of both

A container list that always looks green only proves nothing is checking. In ContainerQ, a plate's status can change to something other than "fine" — because a specific, disclosed comparison against the ledger produces it.

By design

Things ContainerQ will never do.

No shadow inventory

It never keeps a private copy of your stock. The ledger is the only source of truth.

No direct writes

It never pokes inventory tables behind Business Central's back — everything posts through BC's engine.

No "probably fine"

An operation isn't complete because no error appeared. It's complete because a second read said so.

Request a demo   See the use cases