Receiving checklist: catching short weights, missing items and uncredited returns

Why receiving fails: the person who signs is not the person who ordered

Most receiving losses come from a broken handoff, not one dramatic theft. One person places the order and a different person signs the delivery ticket while doing prep. A third person pays the statement weeks later. Each one assumes someone else checked. The original poster in a r/restaurantowners thread about invoice prices that change from week to week described this exactly: they neither place orders nor receive them. In the same thread, other commenters said substitutions arrived without notice, and one described finding a case of portion cups that held 200 instead of the 250 they expected. These are individual forum accounts, not audited findings. They still show how easily nobody owns the check.

A second discussion, about a major distributor acquisition shared to r/restaurant, included a commenter passing on what restaurant owners had told them during consulting work for a produce wholesaler. The list included deliveries short on weight or count, produce that arrived frozen from cold truck temperatures, failure to issue credit, and billing for products never delivered. That is secondhand and unverified. It is not evidence against any named company. It is useful as a list of the failure types a receiving routine has to catch, whoever your supplier is.

Assign one receiver and set delivery windows you can staff

Name a primary receiver and a backup for every scheduled delivery, and write their names on the delivery calendar. The receiver needs three things: the order or order guide for that delivery, a scale, and a calibrated probe thermometer. They also need authority to refuse product and to ask the driver to write a credit without first calling the owner. If the receiver has to get permission to refuse a thawed case, the truck will be gone before anyone answers.

Ask each supplier for a delivery window that avoids your rush. A delivery that arrives during lunch gets signed blind because the line can't spare anyone. If a supplier can't commit to a window, keep in mind that the risk is higher on those deliveries and check them after service, before anything goes into storage. Keep the invoice and the product together until the check is finished.

Count, weigh and temperature-check in a fixed order

Use the same order on every delivery so nothing gets skipped. The sequence and the table below are operational suggestions, not code requirements. The code-based points are covered in the next paragraph. Check cold and frozen product first, because it's the most time-sensitive and the most costly to get wrong. Next, weigh the catch-weight and high-value lines: proteins, seafood, cheese, and anything billed by the pound. Then count cases against the invoice. Last, open a sample of cases to confirm the pack size and the actual item. A case can carry the right label and the wrong count inside, which is the portion-cup problem described in the forum thread above.

For temperature, know which standard you're checking against. In Washington, DC, the DC Health Food Establishment Plan Review Guidance Packet (Dec 2019, ver. 8) asks applicants whether they have adequate, approved freezer and refrigeration capacity, and it gives 41°F (5°C) or below as the figure for refrigerated food. Don't read that as a frozen-storage standard. Refrigerated holding of time/temperature-controlled foods and keeping frozen food frozen are separate checks. A frozen delivery should arrive and stay frozen, with no sign of thawing. The same packet asks whether all food supplies come from inspected and approved sources. That packet is a plan review form, not the full regulation. DC Health's guidance page Understanding Food Establishment Inspections (updated June 27, 2018) summarizes the District's food code, DCMR Title 25. It states that cold foods must be held at 41°F or below. Under a "cold receiving" heading, it says that foods the law allows to be shipped above 41°F must be cooled to 41°F within 4 hours, and that shell eggs should be stored at 45°F. The same page lists food from approved sources among the foodborne illness risk factors inspectors look at. That page is a 2018 summary, so check product-specific details against the current Title 25 text or with DC Health. Outside DC, receiving criteria come from the code your own jurisdiction has adopted. The FDA model Food Code is not automatically local law.

Safety failures and commercial shortfalls are handled differently. A short count or a light case is a billing problem, and a credit fixes it. A delivery that fails a temperature or condition check is a safety problem, and no credit makes it acceptable to use. Reject it so it goes back with the driver. If it has already been accepted, separate it, label it so nobody uses it, and dispose of it or return it under your regulator's or supplier's instructions. The credit only settles the bill. Treat a quick probe between packages as a screening step where your code allows it. If a reading is questionable, check it with the product-specific method your code and food safety plan require before you decide.

Weigh against the invoiced weight, not the label on the box. For case-weight products, a tare check works: weigh one empty box of the same type once, write it down, and subtract it. Record every variance, even the small ones. A single light case may be normal product variation. The same supplier showing the same direction of variance week after week is a pattern worth raising.

Write the credit before the truck leaves

A shortfall you discover after the driver has left becomes a phone call, then an email, then a he-said-she-said about whether the case ever arrived. Get the credit in writing on the spot. Most suppliers give drivers a way to note refusals and shorts on the delivery ticket, as a pick-up or credit memo, a handwritten note signed by both people, or an entry on the driver's handheld. Ask your rep how their system works before you need it.

Write the specific line, the quantity or weight, and the reason on the ticket, then have both the receiver and the driver initial it. Photograph the annotated ticket next to the product. If a driver won't sign a refusal note, write what happened on your copy along with the time and the driver's name, and email your rep the same day with the photo. That record is what lets you resolve the dispute later without accusing anyone of anything.

• Refused product goes back on the truck. Don't put it in your walk-in to sort out later.
• A short line gets a credit note even if the rep promises to send it on the next truck.
• Pick up returns only against a written pick-up memo listing items and quantities.
• Keep a running list of open credits, with the date requested and the memo number.

Reconcile the invoice to the order and to open credits

Delivery checks catch physical problems. Reconciliation catches billing problems. Once a week, the person responsible for purchasing compares each invoice with three things: the order that was placed, the annotated delivery ticket, and the open-credit list. For each line, ask: was it ordered, was it received, and is the price the one quoted or contracted? Then check whether every open credit has appeared on a later invoice or statement.

Credits are where money quietly disappears. A return is picked up, the memo goes in a drawer, and the statement two weeks later shows no credit. Nobody notices because the person paying the statement never saw the memo. Fix this by making the open-credit list a document with an owner, not a pile of paper. Close a credit only when it appears on a statement, never when someone says it's been handled.

Worked example: one delivery, four separate problems (hypothetical)

The following numbers are invented to illustrate the arithmetic. They don't describe any real restaurant or supplier. A small restaurant receives a 22-line delivery. The receiver finds a case of chicken thighs invoiced at 40 lb that weighs 37.2 lb net. At a hypothetical $3.10 per pound, the 2.8 lb shortfall is worth $8.68. A case of romaine on the invoice isn't on the truck: $38.00. A case of berries shows ice crystals and has clearly frozen in transit, so the receiver refuses it: $27.50. Finally, the weekly reconciliation shows that a $46.20 credit for a return picked up nine days earlier hasn't appeared on any invoice.

Together these are $8.68 + $38.00 + $27.50 + $46.20 = $120.38 on one delivery. If the restaurant had signed blind, it would have paid all of it. Suppose a similar total slipped through once a week for a year. The loss would be $120.38 × 52 = $6,259.76. That figure is an illustration of scale, not a prediction. In real operations, many deliveries will be clean, and some problems will be bigger. The point is that each problem is small enough to ignore on the day and large enough to matter over a year.

The fix in this example is ordinary. The weight shortfall and the missing romaine go on the ticket as a credit, initialed by the driver. The berries go back on the truck with a refusal note. The missing $46.20 credit goes to the rep by email, with the photo of the pick-up memo attached, and stays on the open-credit list until a statement shows it.

Escalate with records and keep a simple vendor scorecard

When a problem repeats, escalate with records rather than adjectives. Send the rep a short summary: dates, lines, amounts, and the credit status of each. If that doesn't resolve it, ask for the rep's manager. A commenter in the pricing thread linked above suggested escalating to the rep's boss after a direct conversation. That's a reasonable sequence, and it works best when you can show a log.

A scorecard turns individual complaints into a pattern you can act on. Keep one row per supplier per month: number of deliveries, number with any discrepancy, total value of discrepancies, credits requested, credits received, and average days to credit. Over a quarter, this tells you whether a supplier has a process problem worth fixing, whether your own receiving is getting better or worse, and whether a switch is justified. It also protects you. If you ever need to dispute a statement, the scorecard and the photos are your evidence. Any contract remedies depend on your supplier agreement and local law, so read your account terms before deciding how to handle a disputed balance.

Failure modes that undo a good checklist

Checklists fail in a few predictable ways. The checklist exists, but the receiver signs it without weighing anything. The backup receiver was never trained. The scale is never checked against a known weight. Credits are tracked on the back of an invoice that gets filed. Or the owner reviews the scorecard once and never again. Each of these can be fixed with a small habit: spot-check a receiver's log against the scale once a week, test the scale against a known weight, keep credits in one shared list, and put the scorecard on a recurring calendar review.

The opposite failure is treating every discrepancy as an accusation. Drivers and reps deal with picking errors, warehouse shorts, and route problems that have nothing to do with bad faith. A receiving routine works best when it's routine: check, note, credit, close. Save escalation for patterns the records support.