Cold-Chain Receiving — Per Delivery

It covers the dock-side checks you need for each refrigerated or frozen delivery: truck condition, trailer temperature, product probe temperatures, packaging integrity, lot code capture, and refusal documentation. It is designed to record what arrived, what was accepted, and what was rejected. The template is focused on receiving, not on in-storage monitoring or daily cooler logs.

Use it every time a temperature-controlled shipment arrives, especially for refrigerated dairy, produce, meat, seafood, frozen foods, or other perishable items. It is most useful when you need a consistent per-delivery record instead of relying on memory or a handwritten note. If the shipment is not temperature-sensitive, a simpler receiving checklist may be enough.

A trained receiver, dock lead, kitchen manager, or person in charge should complete it. The person doing the check should know the receiving specification for each product category and be able to refuse product when limits are not met. If your operation has a designated PIC, that person should review refusals and non-conformances.

It is performed per delivery, not on a daily or weekly schedule. Each shipment should be checked as it arrives so temperature abuse, damaged packaging, or missing traceability information can be caught before the product is accepted. Waiting until later can make refusal, supplier follow-up, and traceability much harder.

This template supports food safety controls commonly expected under the FDA Food Code and related supplier verification practices, along with internal HACCP-style receiving controls. It also helps document traceability expectations that matter during recalls or supplier investigations. Local health department requirements may add more specific receiving criteria.

Common mistakes include checking only the truck air temperature and skipping product probe temperatures, failing to record lot codes, and accepting damaged cases because the shipment is short on time. Another frequent issue is not documenting why product was refused, which weakens follow-up with the supplier. This template is meant to prevent those gaps by making each step explicit.

Yes. You can set separate receiving specifications for refrigerated, frozen, and high-risk items, and add supplier-specific notes where needed. Many teams also customize the refusal section to match their internal disposition process, such as hold, return, or destroy. The core structure should stay the same so records remain consistent across deliveries.

Ad-hoc notes usually miss one or more critical fields, especially lot codes, refusal reasons, or exact temperature readings. This template creates a repeatable record that is easier to audit, trend, and use during a recall investigation. It also makes it clearer when a shipment should be rejected at the dock instead of being moved into storage.

Yes. The lot code and supplier fields make it easy to connect receiving records to inventory, traceability, and quality workflows. Many teams link the completed template to a purchase order, receiving log, or corrective action record when a non-conformance is found. That helps close the loop between receiving, storage, and supplier follow-up.