How to give a batch a status that keeps it from shipping or being used until an authorized person releases it on real evidence — and why that block is the piece a lot-tracking field cannot do on its own.
Do these first
Real help from real food people
Chef Diego runs a real food plant. If this page didn't get you there, tell us — a person reads every message.
After this lesson you can lay out the states a batch moves through, write the triggers that drop it into a hold, and name who may release it and on what evidence — so a batch that was never cleared cannot quietly ship, and one that failed cannot be picked by accident.
A hold is not a sticky note on a pallet. It is a status you attach to a specific lot or batch that says one thing plainly: this cannot leave, and it cannot be used, until it is released. That status is a , and the whole point of it is to stop product between the moment something looks wrong and the moment you actually know whether it is.
It helps to see how a hold differs from the rotation rule you set in the previous lesson. FEFO sorts the good lots — of the lots you could ship, it picks the one that expires soonest. A hold is the control for a lot you should not ship at all, whatever its expiry. FEFO ranks the pool; a hold pulls a lot out of the pool entirely, and no expiry date overrides it.
The standards give the physical half of that control its own name. Keeping suspect material apart and marked so no one grabs it by mistake is . A hold and a quarantine are two halves of one thing: the status in your records says "blocked," and the physical separation on the floor makes that status true. Neither half is enough alone.
A batch is never just "made." At any moment it sits in one of a few states, and knowing which one it is in is the difference between confidence and a guess.
Pending — made, but not cleared
A fresh batch exists and is counted, but it has not been checked and signed off. It is not automatically good to ship. Treating a batch as sellable the instant it comes off the line is the mistake this whole discipline exists to prevent.
Released — cleared to ship or use
An authorized person has confirmed the batch meets its specification, and only now can it be shipped or consumed in another batch.
On hold — frozen until resolved
Something is wrong or unknown, so the batch is blocked until it is worked out. A batch can drop into hold from pending — it was never cleared — or even after release, when a problem surfaces later.
Rejected — it will not ship as-is
The batch failed. What happens to it next — reworked, downgraded, or destroyed — is a separate decision called its disposition.
The habit that ties these together is to make "not cleared" the default. A batch should stay un-shippable until someone actively releases it — that is . Without it, a batch nobody checked ships simply because nobody stopped it.
Holds are not rare emergencies; they are a routine part of running production. The triggers are worth writing down in advance so a hold happens by rule, not by whoever is paying attention that day:
The law behind this is more direct than people expect. FDA's preventive-controls rule for human food, 21 CFR 117.150, requires corrective-action procedures that make sure all affected food is evaluated for safety and that affected food is prevented from entering commerce whenever you cannot ensure it is not adulterated under the Federal Food, Drug, and Cosmetic Act. The hold is how "prevented from entering commerce" becomes an actual thing on your floor rather than a sentence in a plan.
HACCP frames the same move as its fifth principle, corrective actions. FDA's HACCP guidelines say a corrective action should determine and correct the cause, determine the disposition of the non-compliant product, and record what was done. "Determine the disposition of the non-compliant product" is the hold in other words: you park the affected batch while you figure out whether it can ever ship.
A hold is only trustworthy if the release at the other end is. Two things make a release worth believing: a named person with the authority made it, and the evidence behind it is written down.
The certification schemes are blunt about this. Under the SQF Food Safety Code, Edition 9, product release is a mandatory element: product may be released only by authorized personnel, and only after all inspections and analyses have been successfully completed and documented. The meat and poultry world puts the same idea in federal rule. 9 CFR 417.5(c) requires a pre-shipment review — before product ships, the establishment reviews the production records to confirm they are complete, that every critical limit was met, and that any corrective action, including the proper disposition of product, was taken. That review is a release gate by another name.
Put plainly: the release decision names who made it, points at the evidence — a passing COA, a negative test, a completed records review — and gets recorded. "It looked fine" is not evidence, and an unrecorded release is one you cannot prove happened when an auditor asks.
Here is where a lot of systems quietly fail. Many can record that a lot is "on hold" — the status sits in a field — but nothing in the system stops that lot from being picked, invoiced, or shipped. The record says blocked; the floor and the order desk never hear about it. A status that only warns is not a control.
A real hold has to be true in two places at once: on the floor, where the lot is physically segregated and tagged so no one can reach it, and in the system, where the lot is un-pickable and un-shippable so it cannot slip onto an order. The seafood HACCP rule spells the physical half out in so many words — 21 CFR 123.7 tells processors to "segregate and hold" the affected product until they have determined it is acceptable. That clause is specific to seafood, but the principle behind it is universal: a held lot is out of reach, not merely flagged.
This is the gap the operators who have been burned describe most sharply — a stock tool that stores the lot but has no quality status that can stop a sale. Software built for food can carry a status that picks and shipments actually respect, so a held lot cannot be pulled or sold by accident. A tagged quarantine cage plus a firm rule that nothing ships without a signed release reaches the same place with more hand-work. What matters is that the block is real in both places — on the floor and in the records the pick runs on — not which tool enforces it.
Not every hold ends in a release. When a batch is rejected, you still have to decide what becomes of it — its disposition — and there are usually three honest options: rework it back to specification and re-inspect before any release, downgrade it to a lower-grade use where that is safe and legal, or destroy it. Whichever you choose, record which and why. SQF Edition 9 requires exactly that: quarantine records and records of the handling, corrective action, or disposal of non-conforming product, kept on file.
A hold is the cheap version of a much more expensive instinct. It catches product before it leaves your control. Once product has already shipped, pulling it back is a recall or a withdrawal — a slower, costlier exercise covered in the lesson on recall versus withdrawal. The earlier you catch the problem, the smaller and cheaper the fix, which is also why a hold usually opens a broader corrective action — the deeper treatment of corrective actions belongs to the Getting Certified track and goes further than the disposition step alone.
The smallest, earliest place to catch a bad input is before it ever reaches a batch — at the receiving dock, the moment it arrives. That is where this course turns next.
Do this in your operation