Food Safety

Food Receiving Checklist for Restaurants

A food receiving checklist restaurant teams can run at the door: FSSAI temperatures in °C, a clear rejection protocol, and a vendor scorecard that works.

The 7:40 AM Delivery Nobody Checked

The chicken arrives at 7:40 in a tempo with no chiller, stacked under a crate of coriander. The commis is halfway through tandoor prep, the steward signs the challan without opening a single bag, and forty kilos of poultry that spent ninety minutes in traffic goes straight into the walk-in. If it arrived at 12°C, your cold room now has to do a job it was never designed for: pulling warm stock down while holding everything else safe.

Receiving is the one control point where you can refuse a problem instead of managing it for the next three days. Yet almost every guide that ranks for this search quotes US FDA numbers, 41°F and the rest. Indian kitchens run on FSSAI numbers, in Celsius. This is the India-first version.

The Numbers That Decide Accept or Reject

From the FSSAI Catering Guidance (2018), these are the thresholds worth laminating at the receiving door:

  • Chilled food: 5°C or below at the point of receiving.
  • Foods of animal origin (raw chicken, mutton, fish): 4°C or below.
  • Frozen food: −18°C or below, with no evidence of thaw and refreeze. Ice crystals inside the pack, product frozen into one solid slab, or deformed and misshapen packs all mean it melted somewhere between the plant and your door.
  • In transit, high-risk food is expected to move at 65°C or above if hot, 5°C or below if chilled, −18°C or below if frozen.

Anything warmer is not a discount conversation. It is a rejection. Keep the full set of storage and holding numbers handy in the FSSAI food temperature chart.

The Receiving Checklist

Run this on every delivery, in order. Once the team has done it for a week, it takes six to eight minutes per vehicle.

  1. Vehicle and carrier check
  • Owner: Steward or commis on receiving duty | Timing: Before a single crate is unloaded
  • Evidence/Proof: One photo of the vehicle interior if it fails; a tick against the vendor's name if it passes.
  • Escalation: Chemical smell, visible pest activity, or raw meat travelling loose against vegetables: reject the affected items and record "vehicle condition" as the reason.
  1. Probe check a sample of every chilled delivery
  • Owner: Commis with a calibrated probe thermometer | Timing: At the door, before signing
  • Evidence/Proof: Item, reading in °C, time and vendor logged on the receiving sheet. Probe between packs for milk and paneer crates; go into the thickest part of one sacrificial pack for meat and fish.
  • Escalation: Above 5°C, or above 4°C for animal-origin items: reject that line. Never "accept it and use it first".
  1. Frozen goods: look for thaw and refreeze
  • Owner: Commis | Timing: On unloading; frozen packs come off the vehicle first and go into the freezer first
  • Evidence/Proof: A logged reading of −18°C or below, plus a squeeze test note. Packs should be hard, not slushy.
  • Escalation: Ice crystals inside the bag, deformed packs, liquid pooling in the carton: reject and photograph immediately, before the pack melts flat and the evidence disappears.
  1. Packaging, labels and dates
  • Owner: Steward | Timing: During unloading
  • Evidence/Proof: Intact packaging, legible manufacture and use-by dates, batch numbers where printed. Dented tins, bloated pouches and torn sacks noted item by item.
  • Escalation: No date, no acceptance. Short-dated stock is accepted only with the manager's initials next to the line.
  1. Weights and counts against the invoice
  • Owner: Steward with the kitchen scale | Timing: Before the rider leaves
  • Evidence/Proof: Actual weight written beside invoiced weight for at least the five highest-value lines: protein, paneer, ghee, oil, dry fruit.
  • Escalation: Shortage written on both copies of the invoice and signed by the rider.
  1. Into storage, in the right order
  • Owner: Commis | Timing: Chilled and frozen items within 15 minutes of acceptance; dry goods after
  • Evidence/Proof: Fridge stacking respected (ready-to-eat and dairy on top, raw meat at the very bottom) and FIFO date marking done at receiving, not "later".
  • Escalation: If the walk-in reads above 5°C as stock goes in, that becomes a temperature-log event with its own corrective action, not just a receiving note.

The Rejection Protocol: Before the Rider Leaves

A rejection raised after the vehicle has left is just a complaint, and vendors know it. Sequence the protocol around the rider still standing at your door:

  1. Photograph the item, with the probe reading in frame where possible. Ten seconds of effort ends every "it was fine when it left us" argument.
  2. Write the rejection on both copies of the invoice: item, quantity, reason ("received at 9°C", "thaw-refreeze", "torn packaging"), with the rider's signature.
  3. Call or WhatsApp the vendor before the rider leaves, photo attached. The rider carries the rejected stock back. Nothing rejected stays in your kitchen "for now".
  4. Log it on the receiving sheet so the month's pattern stays visible.

Indian Realities That Break Receiving Discipline

Three things kill door checks in practice. First, the morning clash: deliveries land between 7 and 10 AM, exactly when prep is heaviest. Fix it with an agreed receiving window per vendor and one named owner per shift; a check owned by "whoever is free" is owned by nobody. If mornings are chaos, give receiving a fixed slot inside your restaurant opening checklist so it has a time, not a hope.

Second, the monsoon. Cartons arrive soft, condensation hides thaw evidence, and the minutes between tempo and door do real damage in wet-season humidity. From June to September, probe more packs per delivery, not fewer.

Third, the last mile itself. Plenty of suppliers quote a refrigerated chain and then subcontract the final leg to a non-refrigerated tempo. Your probe at the door is the only instrument that catches this, which is exactly why the reading must be logged rather than eyeballed.

Vendor Discipline: The Scorecard That Ends Arguments

Arguing with a supplier about one bad delivery is noise. A monthly scorecard is not. Track three numbers per vendor:

  • Rejections this month, as a count and a ₹ value
  • Temperature failures, including deliveries you accepted with manager sign-off
  • Short weights, as a count

Share it with each vendor every month. Suppliers fix cold-chain and weighing problems remarkably fast once they can see they are being measured, because the same scorecard decides who gets next quarter's order. The data costs nothing extra; every line comes off the receiving sheet you already fill.

Paper Register or Digital Log

A paper receiving register on a clipboard at the back door genuinely works for one site with one disciplined steward. It breaks in predictable ways: the sheet gets oil-soaked, rejection photos live on someone's personal phone disconnected from the record, and the owner discovers a month of 8°C paneer deliveries only when the food cost does. Across two or more locations, or wherever you want the photo, the probe reading and the vendor tally in one reviewable record, a digital checklist with timestamps closes those gaps. Either way, pair the door check with a proper food temperature log inside the kitchen, because receiving is only the first temperature checkpoint of the day.

Every item in this article can be set up as a mobile checklist with photo evidence and automatic escalation in the Food Ops demo; build it once and tomorrow's first tempo gets received properly.