Working Alongside BDP WarehouseQ
ContainerQ and BDP WarehouseQ are two separate products from Business Dynamics Pro. Here’s exactly how they relate today — no more, and no less.
Two different jobs
ContainerQ is about the identity and integrity of a single container: giving it an SSCC, knowing what’s packed onto it, and knowing whether that record still matches Business Central’s own ledger. BDP WarehouseQ is a full mobile warehouse operation — receiving, put-away, picking, and shipping, run from a handheld scanner across an entire facility. They solve adjacent problems, at different scopes.
| Product | What it’s for |
|---|---|
| ContainerQ | The identity and integrity of a single container — building it, packing it, moving it, nesting it, and keeping its record honest against the ledger. |
| BDP WarehouseQ | A full scanner-driven warehouse operation, receiving through shipping, across bins and locations. |
WarehouseQ’s own license-plate capability
BDP WarehouseQ ships its own separate, first-party license-plate capability today. It does not depend on ContainerQ, and installing one is not a prerequisite for the other. If you’re already running WarehouseQ, its own license-plate handling covers the warehouse-operation side of the job on its own, without ContainerQ in the picture at all. Neither product is a component of the other; each is a complete, independently licensed application in its own right.
How to tell which one you actually need
| You need container identity | You need a full scanner-driven warehouse |
|---|---|
| You want a reliable SSCC on a pallet, tote, or carton, and a record of what’s on it that’s honest about whether it still matches the ledger — without necessarily running a full scanner-driven operation. That’s ContainerQ. | You want receiving, put-away, picking, and shipping directed from a handheld scanner across bins and locations, with license plating as one capability inside that larger operation. That’s BDP WarehouseQ, which handles its own license plating natively. |
Plenty of organizations only need one of the two. A smaller operation focused on outbound pallet integrity, for instance, might run ContainerQ on its own with no scanner-driven receiving process at all. A larger operation running a full mobile warehouse workflow may find WarehouseQ’s own license plating already covers everything it needs, without ever installing ContainerQ.
They coexist
ContainerQ and BDP WarehouseQ are built to coexist. Nothing stops you from running both in the same Business Central environment, side by side, each doing its own job — for example, a warehouse could run BDP WarehouseQ for its scanner-driven receiving and picking operations while a separate team uses ContainerQ for container-level identity on a specific outbound lane. There is no current, shipped integration where one product’s data flows automatically into the other’s — that’s not a gap in this page’s description, it’s the honest state of the two products today. Neither product is described here as an engine, component, or dependency of the other, because neither is: each does its whole job on its own.
What’s next, honestly
A deeper integration between the two products is a direction the ContainerQ and WarehouseQ teams may pursue later. It isn’t built today, and this page won’t speculate further about what it would look like. If that changes, this page will be the place that says so — and it will say so as plainly as it currently says it isn’t built yet.
None of this changes how you set ContainerQ up on its own. The setup reference covers the permissions, GS1 Company Prefix, and container-type defaults every deployment needs, whether or not WarehouseQ is also in the environment.