Quality Holds
A Quality Hold is how you quarantine a container — a quality issue, a suspect lot, anything awaiting inspection — before it can move any further through your warehouse.
What a hold is for
You place a Quality Hold on a container when something about its contents needs to be resolved before that container is trusted with any further posting — a quality issue found on inspection, a lot under investigation, damage discovered on a re-count, or simply stock that needs a second look before it’s picked, shipped, or moved. It’s the mechanism for saying “don’t act on this yet” at the container level, rather than relying on a note in a separate system or a verbal heads-up between shifts.
A hold applies to any container, at any nesting level: a hold on a pallet reaches every tote nested inside it, and a hold on a tote inside a pallet doesn’t need the pallet itself to be held. That matters in practice because quality issues are rarely tidy — a single suspect lot might sit on one tote among several stacked on a pallet, and the hold needs to reach exactly that tote and whatever’s nested inside it, without freezing everything else on the pallet unnecessarily, or without requiring you to hold every container individually up and down the structure by hand.
What a hold is designed to do
A hold placed on a container is designed to block every posting action against it, and against everything nested underneath it — not just change a status a worker can scroll past. The intent is that a held container simply isn’t something you can act on until the hold is released, regardless of which action you’re attempting or how deep in a nested structure the held container sits.
That’s a deliberate design choice: a quality hold that only changes a status field, and still lets an operator pick or ship from the container anyway, isn’t really a hold — it’s a note nobody is required to read. ContainerQ’s intent is the stronger version, where the hold itself is what stands between the container and any further posting, in the same spirit as the nesting propagation an action placed at the top of a structure is supposed to reach all the way to the bottom.
| Placing a hold | Releasing a hold |
|---|---|
| Applied directly to a container. Reaches everything nested inside it automatically — you don’t need to hold each child container separately. | Removing the hold restores normal posting on the container and its nested contents, once whatever prompted the hold has been resolved. |
Where this fits into a normal day
The most common trigger is inspection: stock comes off a truck, something looks off, and the receiving operator holds the container before it ever reaches a shelf. The next most common is a downstream discovery — a quality issue traced back to a specific lot after the fact, where the hold is placed retroactively on whatever container still carries that lot, wherever it’s nested. Either way, the hold is meant to travel with the container rather than requiring anyone to remember which shelf or bin the affected stock ended up on.
A less common but important case is a hold that spans a partial structure: a supplier recall affecting one lot that happens to be split across two totes on the same pallet. The hold reaches both affected totes and anything nested inside them, while the rest of the pallet — carrying unrelated lots — stays available for normal operations. That’s the practical payoff of holds being scoped to the container (and its nested contents) rather than to the whole document or the whole pallet: an operator doesn’t have to manually work out which parts of a mixed load are actually implicated.
What a hold does not do
A Quality Hold is not the same thing as a Binding Mode, and it doesn’t change one. Holding a Positional-bound container doesn’t make its record any more or less continuously re-checked; holding a Package-bound container doesn’t add a second layer of platform enforcement on top of the one Business Central’s posting engine already provides. The hold is a separate, orthogonal control: it’s about whether posting is currently permitted at all, not about how strong the underlying identity guarantee is. A held container can be Package-bound or Positional-bound just like any other; the hold simply refuses to let either kind move forward until it’s lifted.
A note on how to read this page
As with everything in this Help Center, present-tense claims describe designed, intended behavior. If you’re evaluating this for a compliance-critical process, verify current behavior in your own environment first, rather than assuming a description here has already been proven against a live tenant.