QC Holds: Single Pallets vs Whole Lots
November 20, 2026
A quality hold can cover a whole lot or just one pallet, and the right choice depends on where the problem came from. A problem that started before the lot reached you, such as a supplier issue or a bad batch, usually calls for a lot-level hold, while damage, a temperature excursion, or a failed test on one pallet may only need that pallet held.
Most inventory systems hold stock at the lot level, and fewer let you hold or release a single pallet inside a lot. This guide explains the difference, when each one is right, the risks of releasing part of a lot, and what any hold has to do in your system to be worth having. It ends with an honest look at how holds work in Swift WMS, including what it does not do.
Lot-level holds and pallet-level holds
A lot is a group of stock that shares a history: one supplier lot, one production batch, one blend. A pallet, or license plate, is one physical unit of that lot sitting at one location. A single lot can be spread across many pallets in many locations, and some of those pallets may already be in production or on a truck.
A lot-level hold stops every unit of the lot, wherever it is. It is the broad tool. It assumes the problem is in the material itself, so every unit that shares the history shares the risk.
A pallet-level hold stops one physical unit and leaves the rest of the lot available. It is the narrow tool. It assumes the problem happened to that unit after the lot was made or received, so the other units do not share it.
If you are new to the idea of tracking stock by pallet, our explainer on what a license plate number is covers how a plate ties one unit to its SKU, lot, quantity, and location. Pallet-level control only works if every pallet already has its own ID.
When the whole lot should go on hold
Hold the whole lot when the problem could be anywhere in it. The question to ask is simple: did the problem exist before this lot was split into pallets? If yes, every pallet carries it.
- A supplier tells you a lot may be contaminated or mislabeled.
- A certificate of analysis is missing, or a value on it is out of specification.
- A sample from the lot fails a lab test for a property of the material, such as moisture, potency, or a microbial count.
- A production batch had a process problem, such as a wrong ingredient, a missed step, or an equipment fault during the run.
- A recall or a customer complaint points at the lot.
In each of these cases, holding only the pallet you tested is a guess that the problem stayed on that pallet. Material problems do not respect pallet boundaries. A lot-level hold also protects you from the pallet nobody remembered: the partial in an overflow location, or the one staged for tomorrow’s run.
When one pallet is enough
Hold only the pallet when the problem clearly happened to that unit and nothing else. These are physical events, not material events.
- A forklift damaged one pallet, crushing cases or tearing bags.
- A temperature logger on one pallet shows an excursion, and the rest of the lot was stored and shipped separately.
- One pallet was found wet, open, or exposed to a pest.
- One container in the lot failed a check that applies to that container only, such as a broken seal or a short fill.
- A label on one pallet does not match its contents, and the others check out.
The key word is “clearly.” If a temperature excursion happened in a trailer that carried four pallets of the lot, four pallets are suspect, not one. If the damage came from a supplier’s packaging that is the same on every pallet, the problem may be the lot after all. Decide the scope based on evidence, and write down the evidence.
The risk of releasing part of a lot
There is a second way to end up with part of a lot on hold: place the whole lot on hold, investigate, and then release the pallets you have cleared. This is often the safer path, because the default is “held” until someone proves otherwise. It still carries risk, and it is worth naming the risks before you do it.
- The investigation was too narrow. You cleared three pallets because they looked fine, but the real cause was in the material. Looking fine is not the same as passing a test.
- The release outlives the reason. A pallet was released for one problem, and then a second problem was found with the lot. If the earlier release still stands, that pallet can ship.
- The paperwork does not follow the stock. A released pallet is split, moved, or combined, and the new unit loses its link to the release decision, or carries a release it should not.
- People read the wrong status. Someone sees “lot on hold” on one screen and “available” on another and does not know which one wins.
A good partial release has three parts. A person with authority decides which pallets are cleared and why. The system shows, on every screen, which pallets of a held lot are released and which are still held. And any new hold on the lot cancels earlier releases, so a new problem starts from a clean, fully held state.
Document the reason, every time
A hold with no reason is a hold nobody can close. Weeks later, someone finds a held lot, cannot tell why it was held, and either releases it on a guess or leaves it to expire on the shelf.
For each hold and each release, record:
- What was held: the lot, or the specific pallets.
- Why: a category such as quality, quarantine, rework, damage, or recall, plus the specific finding.
- Who placed it and when.
- What evidence supports the decision: a test result, a photo, a temperature log, a supplier notice.
- Who released it, when, and what evidence cleared it.
Keep supporting files with the lot, so that the evidence is in one place when an auditor or customer asks. Our guide to managing certificates of analysis by lot covers how to keep lot documents findable. The same habit works for hold evidence.
Split the authority to hold from the authority to release where you can. Anyone who sees a problem should be able to stop stock. Fewer people should be able to start it again, because a release is the decision that carries the risk.
A hold must block shipping and consumption
A hold that only changes a status label is a note, not a control. Under time pressure, people ship what is on the screen. The hold has to stop the work.
At a minimum, a held lot or pallet should be blocked from:
- Shipping to a customer.
- Being consumed into a production batch.
- Being reserved or staged for a work order.
- Being transferred to another warehouse, where the hold could be lost.
The block should hold no matter which screen someone uses. If the desktop screen blocks a shipment but a handheld screen does not, the hold has a hole. Test this the same way you would test a recall: place a hold on a test lot and try to ship it, consume it, and stage it from every screen your team uses. Our guide on how to run a mock recall covers how to make a test like this part of a regular drill.
Also think about stock that is already moving when the hold goes on. A pallet staged for a run that starts in an hour, or a shipment that is packed but not yet loaded, needs someone to act. A good system tells you about that in-flight work when you place the hold.
Automatic holds for incoming material
Some plants place every new ingredient lot on hold the moment it is received and release it only after quality review. This is sometimes called positive release. It moves the default from “usable until someone notices a problem” to “held until someone approves it.”
Automatic holds suit plants where incoming material needs a COA check, a lab test, or a visual inspection before use. They add a step for every lot, so they work best when the release step is quick and someone owns it every day. If nobody owns it, released stock piles up in a queue and production waits.
How this works in Swift WMS
In Swift WMS, you place and release holds from a license plate’s action menu. The Quality page, Lot Trace, and Recall Impact are part of the Core plan. Here is what holds do, and what they do not.
Holds are placed on the lot, not on a single plate. When you place a lot on hold from a license plate, a hold reason is required: Quality, Quarantine, Rework, Damage, or Recall. A held lot cannot be consumed or shipped, and the hold is checked on the server, not only in the screen. Placing a hold also tells you about work already in flight for that lot. Changes to lots are recorded in the Audit Logs with the user and the time.
You can release one plate from a held lot. When you release a hold from a plate, Swift WMS asks whether to release the entire lot or only this plate. A released plate can be consumed and shipped while the rest of the lot stays on hold, and the license plate grid shows it as “Released (lot on hold).” A released plate can be put back under the lot’s hold later. Any change to the lot’s hold, or a recall, cancels plate releases, so a new problem starts from a fully held lot. When a plate is split, the new plates keep the parent’s release.
Swift WMS cannot place a single plate on hold while the rest of its lot stays available. If one pallet of a lot is damaged and the others are fine, the way to do it in Swift WMS is to hold the lot, then release each good plate. That leaves only the damaged plate held. For a lot spread across many plates, that means one release step per good plate, so plan for it.
Placing a hold and releasing one are separate permissions, so you can let more people stop stock than start it. Releasing a lot that is on hold for a recall needs an extra confirmation.
There is a setting to place new ingredient lots on hold automatically when they are received, for teams that want positive release. Separate settings do the same for new work-in-progress and finished-good lots. The inventory screen has an On Hold filter, and from Recall Impact you can hold every lot downstream of a problem lot in one step. See the lot traceability and recall impact page for how holds fit with Lot Trace and batch records, and the license plate inventory page for how plates are tracked.
The takeaway
Choose the scope of a hold based on where the problem started. If the problem is in the material, hold the lot. If it happened to one pallet after the fact, one pallet may be enough, but only when the evidence shows the others were not exposed.
- Hold the whole lot for supplier, batch, test, and recall problems.
- Hold one pallet only for physical events with clear limits.
- When in doubt, hold the lot and release the pallets you can clear.
- Record a reason, the evidence, and the person for every hold and release.
- Make sure a hold blocks shipping and consumption from every screen.
- Let a new hold cancel earlier releases, so old decisions do not carry over.
A hold is only as good as the record behind it and the block in front of it. Get those two right, and the choice between a lot and a pallet becomes a quality decision instead of a software limit.
