Catch a bad input at the dock, before it reaches a batch
How to inspect and record what arrives at receiving — condition, temperature, COA, allergen, and the supplier lot — so a bad input is caught and held before it can be used in production.
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 build a receiving check that stops a bad input at the dock: inspect what arrived against its specification, capture the supplier's lot so it stays traceable, and put anything that fails on hold before it can be moved into a batch.
Receiving is a control point, not a paperwork step
The dock is the cheapest place you will ever catch a problem. A short-dated, damaged, or wrong-allergen input caught at receipt costs you one rejected pallet and a call to the supplier. The same input caught after it is mixed into a batch costs the batch, everything that batch touched, and — if any of it shipped — the trace-and-recall work that follows. Every check you skip at the door, you pay for later at a multiple.
The law already treats receiving as a control. FDA's current good manufacturing practice rule for human food, 21 CFR 117.80(b)(1), requires you to inspect raw materials and ingredients and to segregate or otherwise handle them as needed to be sure they are clean and suitable to go into food — and to store them so they are protected against contamination, against , and against deterioration. The verb doing the work is inspect. Receiving is where that duty is met or missed.
What to check when it arrives
A receiving check is short, but each line on it is there to catch a specific failure. Run the same five every time, and record the result — not just a signature.
1
Condition and count
Look before you sign. Crushed or wet cases, broken seals, signs of pests or tampering, and the count against the purchase order. A signature on a delivery no one actually examined transfers the problem from the carrier to you.
2
Temperature, for anything cold
For refrigerated or frozen goods, take and record the arrival temperature. A reading out of range is a reason to hold or reject, not to wave the truck through — the cold chain either held or it didn't, and only a logged number proves which.
3
The Certificate of Analysis
Confirm three things about the , not one: that it is present, that it passes the spec, and that it is for this lot. A passing COA stapled to the wrong lot proves nothing.
4
Allergen and identity
Is it the material you ordered, and does its declared allergen profile match what your process and labels assume? An undeclared allergen arriving inside an ingredient is one of the surest paths to a recall. The US recognizes nine major food allergens — milk, egg, fish, crustacean shellfish, tree nuts, wheat, peanuts, soybeans, and sesame, the ninth, added by the FASTER Act effective January 1, 2023 — and a reformulation on your supplier's side can put one into a material that never carried it before.
5
The supplier's lot
Capture the lot code printed on what arrived. This is the check everything downstream leans on, and it gets its own section next.
Record the supplier lot, or the trace dead-ends
The supplier lot you write down at the dock is the first link in your . Miss it here and nothing downstream can reach the supplier: a backward trace runs until it hits your receiving dock and stops. Receiving is your "one step back" — the supplier side of the one-up-one-down chain in one step back, one step forward.
If the food is on FDA's Food Traceability List, capturing the lot stops being good practice and becomes a rule. Under the Food Traceability Rule (FSMA 204), receiving is a tracked event with a required set of records. 21 CFR 1.1345 lists what you keep when you receive a listed food: the traceability lot code, a product description, the quantity and unit of measure, a description of where the food came from and where you received it, the date of receipt, the traceability lot code source, and the reference document. The lesson on what FSMA 204 asks you to record walks the full set.
Software built for food captures the supplier lot at receipt and carries it forward as a link, so a finished lot can name the exact supplier lot behind each ingredient. Bettr Manager, the platform this site is part of, works that way — the lot you record at the dock ties through the batch to the shipment. It is one way to keep that first link honest; a paper receiving log with real cross-references reaches the same place with far more hand-work.
Confirm the compliance date at the source
FSMA 204's compliance date has already moved once — it was pushed from January 2026 to July 20, 2028. Whether a food is on the list and when the rule bites are both things to confirm on FDA's own page rather than memorize, because both have changed before (verified July 2026).
Hold anything that fails
A checklist only matters if a failed line actually stops the goods. The rule to write down is plain: nothing that fails a receiving check gets put away into usable stock. It goes on hold instead — segregated and marked so no one can pull it into a batch — until you decide to accept it, return it, or reject it, and you record which and why. This is the same quality hold from the hold-and-release lesson, applied at the earliest possible point: the moment the material arrives, before it has touched anything you make.
Making that hold real means it has to be true in two places — physically, where the pallet is separated and tagged, and in your records, where the lot cannot be picked or issued to production. A note that reads "on hold" while the goods sit in the usable rack is not a hold. For one concrete way to book in a receipt, run its QC, and hold or release it in sequence, the docs walkthrough on receiving a purchase order shows the flow end to end.
Receiving is the front door of your supplier program
A receiving inspection is not a standalone habit; it is the daily, physical edge of a broader supplier program. The certification schemes are explicit about the link. Under the SQF Food Safety Code, Edition 9, the approved-supplier program is a mandatory element: you document how you select, evaluate, approve, and monitor suppliers, and you keep a current record of approved suppliers, receiving inspections, and supplier audits together. Edition 9 expects raw-material verification to lean on certificates of conformance, certificates of analysis, or your own sampling and testing at a frequency you set — and it treats receiving from a non-approved supplier as an emergency-only move that still requires a recorded receiving inspection before the material is used.
Federal rule adds a risk-based layer on top of that universal inspection duty. Where your hazard analysis finds a hazard that a supplier is relied on to control — a — 21 CFR 117.405 requires you to run a risk-based supply-chain program for that material, and 21 CFR 117.410 says that program is built on using approved suppliers and conducting supplier verification activities. Not every material triggers this — it is scoped to the hazards your own analysis identifies — but where it applies, the receiving check is where the supplier program stops being a binder and becomes something that happens. How you qualify a supplier and choose those verification activities is its own subject, the supplier and supply-chain program; this lesson is the receiving end of it.
What clears the dock still needs a date
Everything that passes receiving becomes stock you now own and have to manage. The next question it raises is the one the packing slip can't answer for you: what expiry date will you stand behind for this lot, and how will you defend it? That is where this course turns next — setting a shelf life and an expiry you can back with evidence.