Grocery Receiving Damaged Goods Log

Use it as soon as damaged product is discovered at the dock or during receiving, before the shipment is put away or mixed with sellable inventory. It is meant for inbound damage only, not in-store shrink, customer returns, or vendor quality complaints discovered later. Logging it immediately helps preserve the condition details and supports a cleaner credit claim.

The receiving associate, dock lead, or inventory control team member who first identifies the damage should complete the entry. A supervisor can review and confirm the disposition, especially when the product needs to be quarantined, returned, or written off. If your process separates receiving from claims, this form can still capture the facts needed for the claims owner.

This template fits physical damage such as crushed cases, broken seals, leaking packages, temperature abuse indicators, or missing product caused during transit or unloading. It also works when only part of a case pack is affected, since the quantity_affected field lets you separate damaged units from usable ones. If the issue is a pricing dispute or invoice error with no product damage, a different receiving exception log is usually a better fit.

Log each damaged shipment or line item as it is discovered, rather than waiting until the end of the shift. If multiple damaged items arrive on the same truck, create separate entries or clearly separate them by product so the claim trail stays readable. Frequent logging also makes it easier to spot recurring vendor, route, or handling issues.

Attach clear photo evidence of the damage, the shipping label or pallet tag if available, and any receiving paperwork that ties the item to the PO or invoice. The log should also capture the claim reference number and who the claim was submitted to, so follow-up does not depend on memory. If your process requires it, note whether the vendor was notified before the product left the dock.

Yes. You can add fields for temperature readings, carrier name, trailer number, quarantine location, or internal write-off codes if those are part of your process. Keep the form focused on what you actually use for disposition and claims, and avoid collecting extra fields that do not change the outcome. If you operate both stores and DCs, the store_or_dc field helps route the entry correctly.

The most common issues are vague damage descriptions, missing quantities, and no clear disposition action. Another frequent problem is skipping the claim reference number, which makes follow-up hard when the vendor asks for proof. Photos taken after the product has been moved or repacked are also less useful than photos taken at the point of discovery.

An ad hoc message can alert people, but it usually leaves gaps in the audit trail and makes claims harder to track. This template standardizes the fields needed to document what arrived, what was damaged, what happened to it, and whether a credit claim was started. That makes it easier to review patterns, assign follow-up, and prove the issue later.