What is a food receiving log?

A food receiving log records what arrived, what temperature it arrived at, whether it was accepted or rejected, and which staff member checked it. It is the first control point in the flow of food. The product moves from the truck to the dock to the walk-in, and the receiving log is the record that says someone looked before it went into storage.

The receiving log is not the same as two records it gets confused with. Operators who run all three keep them separate to avoid mixing up what each one proves.

• Receiving log equals the at-the-dock check. One reading, one decision, per delivery, per product. This is different from the recurring in-storage hold check covered in the walk-in cooler temperature log, which monitors product after it is already put away.
• Receiving log is not a CCP monitoring log. It is different from HACCP temperature logs, which record recurring critical-control-point monitoring on a fixed cadence like cook, cool, and hold.

A standard receiving log has six columns, confirmed against the canonical templates that rank for this term, including the FoodDocs receiving temperature log template:

1. Date and time of delivery
2. Product or item received
3. Recorded temperature of the shipment
4. Accept or reject decision
5. Staff signature (who checked it)
6. Notes (reason for rejection, supplier, lot, use-by date)

Here is the operator problem. The temperature number is the easy part. The hard part is the decision and the signature. On a paper log, a cook writes "38 F" in a box and moves on. Nobody records whether the lot was accepted or sent back. Nobody signs. The driver is gone in four minutes, and the only proof the check happened is a number in a box that nobody verified. When the health inspector pulls receiving records, the question is not "what was the temperature." It is "show me you checked it and made a call." That is the column paper loses.

Regulatory framework

The receiving temperature rule comes from FDA Food Code 2022, section 3-202.11 (Temperature, received food). Cold TCS food must be received at 41 F (5 C) or below. Hot TCS food that was cooked and shipped hot must be received at 135 F (57 C) or above. All food received must be free of evidence of previous temperature abuse. TCS stands for time and temperature control for safety, the category of food that grows pathogens when it sits in the danger zone.

Every receiving threshold traces back to a specific Food Code line. The numbers below are confirmed in the FDA Food Code 2022 and the Chapter 3 (Food) text.

| Item | Receiving requirement | Source |
|---|---|---|
| Cold TCS food | 41 F (5 C) or below | FDA Food Code 3-202.11 |
| Hot TCS food (cooked, shipped hot) | 135 F (57 C) or above | FDA Food Code 3-202.11 |
| Frozen food | Received frozen solid, no thaw evidence | FDA Food Code 3-202.11 |
| Shell eggs | 45 F (7 C) ambient air or below on receipt | FDA Food Code 3-202.11 |
| Shellfish, shucked shellfish, milk, shell eggs | 45 F (7 C) or below, then cooled to 41 F within 4 hours | FDA Food Code 3-202.11 |
| All received food | Free of evidence of previous temperature abuse | FDA Food Code 3-202.11 |

Why the number matters: a product that traveled in the danger zone of 40 F to 140 F may have grown pathogens before it reached your dock. The FDA Food Code uses 41 F and 135 F as the compliance thresholds. USDA FSIS uses the 40 F and 140 F framing for consumer guidance. Cite the FDA numbers as the compliance line. The stakes are not paperwork theater. The CDC estimates 1 in 6 Americans, about 48 million people, get a foodborne illness each year, with 128,000 hospitalized and 3,000 deaths.

Receiving is where your documented chain of custody begins. The supplier controls the food until the dock. After the signature, you own it. An accepted lot that was already temperature-abused becomes your liability the moment the receiving clerk signs. That is the legal and food-safety weight behind the signature column. For the full picture across FDA Food Code, FSMA, and HACCP, see the food safety regulatory frameworks guide.

Accept-or-reject criteria at the dock

Reject a delivery when the temperature is out of range, the packaging is compromised, or the product shows signs of time-temperature abuse or spoilage. The decision happens at the dock, before the driver leaves. Once the product is signed for and put away, the operator owns the problem.

The reject criteria below are confirmed against the ServSafe Receiving Criteria from the National Restaurant Association. Reject when you see any of these:

• Temperature out of range. Cold TCS above 41 F, hot TCS below 135 F, or frozen product that is not frozen solid.
• Ice crystals or fluid stains on frozen product. Large ice crystals mean the lot thawed and was refrozen, which is time-temperature abuse.
• Dented, bulging, swollen, leaking, or rusted cans. Severe seam dents, deep body dents, swollen ends, leakage, or rust signal contamination or botulism risk.
• Torn, punctured, or compromised packaging. Tears, holes, leaks, dampness, stains, or missing and incorrect labels.
• Bloated or leaking reduced-oxygen packs. Vacuum-packed or MAP product that is bloated or leaking has lost seal integrity.
• Abnormal color, odor, or texture. Moldy, off-color, slimy, or foul-smelling product.
• Past or unclear use-by date. Product without clear date marking or a verifiable source.

| Category | Reject when | What it signals |
|---|---|---|
| Temperature | Cold TCS over 41 F, hot TCS under 135 F | Danger-zone exposure in transit |
| Frozen | Ice crystals, fluid stains, soft product | Thawed and refrozen, temp abuse |
| Cans | Swollen ends, deep dents, seam dents, leaks, rust | Botulism or contamination risk |
| Packaging | Tears, punctures, dampness, bloated vacuum packs | Loss of seal integrity |
| Sensory | Off-color, off-odor, slime, mold | Spoilage or decomposition |
| Documentation | Missing use-by date, unapproved supplier | Traceability failure |

Inspectors check this step. As StateFoodSafety notes on what health inspectors look for, "inspectors will scrutinize your receiving process, supplier documentation, and storage organization," and unapproved suppliers or disorganized storage can lead to critical violations. The National Restaurant Association confirms receiving and documentation are scored items.

How does Xenia handle food receiving logs?

Xenia turns the receiving log into a dock checklist that forces the accept-or-reject decision, captures a photo on a rejected lot, and timestamps the staff signature. The decision and the proof live in the same record as the temperature, which is exactly the part paper loses.

The receiving log maps to four Xenia capabilities, each tied to the column paper drops.

• Follow-up questions with required photo. When the recorded temp is out of range, the form auto-presents a follow-up: "Out of range, what did you find? Photo required." On a rejected lot, the receiver photographs the dented can, the ice crystals, or the thermometer reading. Temperature out of range automatically asks what the receiver found and requires a photo, so the evidence is captured at the moment of rejection, not reconstructed later when the inspector asks.
• Corrective action workflow. A rejected lot triggers a corrective task: notify the manager, flag the supplier, log the credit. Most platforms collect audit data. Few drive it to closure. When a supplier repeatedly ships out of range, the pattern becomes visible instead of buried in a stack of clipboards. See food safety corrective action for how the after-the-reject workflow runs to closure.
• Bluetooth thermometer integration. A Bluetooth probe at the dock pushes the receiving temperature straight into the log. No transcribing a number off a thermometer onto paper while the driver waits. Pairing the probe auto-logs the temp and alerts on out-of-range readings, the top driver for Dave's Hot Chicken across 321 locations. See the Bluetooth thermometer setup guide for the dock pairing steps.
• Custom dashboards on issues. The dashboard surfaces repeat-offender suppliers and out-of-range receiving trends across locations, so a one-off rejection becomes a vendor conversation backed by data.

The decision column is the wedge. A static checklist or paper template records a number. A conditional audit branches on that number and demands proof. The difference is the same logic behind weighted audit scoring: a temp failure is a critical item that drives a corrective action, not a box that gets a checkmark and forgotten.

| Step | Paper receiving log | Bluetooth-integrated Xenia log |
|---|---|---|
| Temperature entry | Hand-written off the probe | Auto-written from the dock probe |
| Accept or reject | Often left blank | Required field, cannot skip |
| Reject evidence | None | Photo required at the moment of rejection |
| Supplier pattern | Buried in a binder | Surfaced on the dashboard across stores |
| Inspector pull | Find the binder, hope it is updated | Filtered record on screen |

Multi-location receiving compounds the gap. A C-store area manager runs food service across four stores. Cooler-bound deliveries land at each store on different schedules. With paper, the manager cannot see that one store's dairy vendor trends warm on arrival until a customer complaint. With a digital receiving log feeding a dashboard, the out-of-range pattern surfaces as a vendor issue, not a one-off. This matters most across the restaurant operations platform where dock checks run on every shift.

Where do operators see results?

Operators see results in three places: a complete dock-side audit trail when the inspector asks, a visible record of which suppliers ship out of range, and the elimination of the "we checked it, I swear" gap that paper leaves.

• Audit-ready trail. Every delivery has a temperature, a decision, a signature, and on a reject, a photo. When the health inspector pulls receiving records, the answer is in the system, not in a binder nobody updated.
• Repeat-offender supplier visibility. The dashboard shows which vendor's cold deliveries trend warm across stores. That converts a one-off rejection into a vendor conversation backed by data.
• Paper-to-digital speed. Tempstop went paperless in 14 days. Power Market went live across 360 locations with QR deployment and reported 40% faster task resolution. These are the time-to-value and speed anchors, not invented receiving-specific numbers.
• Bluetooth at scale. Dave's Hot Chicken runs Bluetooth thermometers across 321 locations after migrating from RizePoint. The same probe model that logs walk-in temps logs the dock check.

The receiving log is one step in a chain. After the accept decision, the next control point is rotation, covered in food date labeling and FIFO rotation. Refuel runs receiving across 200-plus C-stores, including rural fuel stops where the dock check happens on a tablet offline and syncs when connectivity returns. The pattern holds whether you run a single kitchen or a fleet: the temperature was never the hard part. The decision and the signature were, and those are the columns a digital receiving log finally captures.

How to set up a receiving log in Xenia

Build the receiving log once as a template, add the accept-or-reject logic and the photo requirement, then assign it to every location. Setup is a numbered procedure, not a custom build.

1. Start from the receiving log template. Use the Xenia food receiving log template or upload your existing receiving SOP. The AI Template Agent converts a receiving SOP PDF into a digital form in minutes, with conditional logic and required fields, not just a PDF reader. It transforms an SOP you already have. It does not invent one from a vague brief.
2. Add the log columns. Date and time, product, recorded temperature, accept or reject, staff signature, and notes.
3. Set the temperature thresholds. Cold TCS at 41 F or below, hot TCS at 135 F or above, frozen received frozen solid, per FDA Food Code 3-202.11.
4. Add the follow-up question on reject. If "reject" is selected or the temp is out of range, require a description and a photo of the issue.
5. Wire the corrective action. An out-of-range or rejected lot creates a task: notify the manager, flag the supplier, record the credit.
6. Pair the Bluetooth thermometer (optional). The dock probe writes the temp directly into the log. See the Bluetooth thermometer setup steps.
7. Assign to all locations. Set the receiving frequency to as-needed (per delivery), not a fixed cadence.
8. Test at one store, then roll out. Confirm the photo and corrective-action triggers fire before pushing the template across the fleet.

This is part of a complete food safety operations program, where receiving feeds the same audit-ready trail as your daily temp logs and HACCP monitoring.