Warehouse Receiving Checklist: Record Deliveries, Damage and Discrepancies

A warehouse receiving checklist creates a traceable bridge between what arrived physically, what the organization expected and what the inventory system records. It should expose damage, shortage, overage, identity mismatch and status restrictions before goods disappear into storage or production.

Adapt the fields to approved site procedures, product risks and contract terms. A generic checklist does not determine legal acceptance, dangerous-goods handling, quality release or claim liability.

Define the receiving control point

Specify where custody, initial count, detailed inspection, system receipt and quality release occur. These may be different events. Record the site, dock, appointment, purchase or transfer order, advance shipment notice and carrier reference.

Receipt ID:
Date / arrival time / timezone:
Site / dock:
Supplier / sender:
Carrier / vehicle reference:
Purchase, transfer or return order:
Delivery note / shipment reference:
Receiver / reviewer:

If arrival timing or custody has contractual consequences, use the approved commercial process and source timestamps rather than relying on this operational record alone.

Prepare the dock and expected record

Before unloading, confirm the appointment, expected items, quantities, units of measure, handling needs, available space and required inspection or quarantine location. Resolve obvious order or destination mismatches before goods are dispersed.

Check that trained people and suitable handling equipment are available. Follow site traffic, unloading, emergency and product-specific procedures. Do not turn the checklist into improvised safety instructions.

Review prior alerts such as temperature-control needs, known supplier issues, return authorization or inspection sampling. Restrict sensitive customer and route data to approved systems.

Copy this warehouse receiving checklist

ARRIVAL
[ ] Appointment, order and shipment references match
[ ] Carrier, vehicle and seal details recorded where required
[ ] Immediate hazards, leaks or instability routed correctly

VERIFY
[ ] Item, description, lot/serial and unit of measure checked
[ ] Quantity counted at the defined control point
[ ] Packaging and goods condition inspected
[ ] Required documents and status evidence present

CONTROL EXCEPTIONS
[ ] Damage, shortage, overage or mismatch identified
[ ] Affected goods segregated and status marked
[ ] Evidence preserved and responsible owner notified

RECORD AND PUT AWAY
[ ] System receipt matches verified physical state
[ ] Quality or availability status is accurate
[ ] Putaway location and movement confirmed
[ ] Open actions have owners and deadlines

Add item-specific checks from controlled procedures. Require a reason and owner for any skipped field.

Verify carrier, load and seal condition

Where the process requires it, record vehicle or container reference, arrival condition, seal number and seal state before opening. A seal mismatch is evidence requiring escalation, not automatic proof of tampering or fault.

Observe load stability, visible damage, moisture, contamination, odor, temperature indicator state or other relevant conditions without entering an unsafe area. Photograph only when authorized, useful and permitted. Avoid capturing faces, license information or neighboring shipments unnecessarily.

If unloading cannot proceed, record the observable condition, time, people notified and decision authority. Preserve original evidence and do not ask a driver to accept wording beyond their knowledge.

Match item identity and documents

Compare the physical item, packaging label and documents with the expected record. Check SKU or part number, description, revision where relevant, lot, batch, serial, expiry or date code, country or compliance document only where the approved process requires it.

Do not infer identity from appearance when a controlled identifier is required.

Count quantities with a defined method

Record pallets, cases, inner packs, pieces, weight or volume using the approved unit. State whether the count was full, sampled, weighed, scanner-derived or based on sealed packaging. Preserve conversion factors and instrument references where relevant.

Separate expected, delivered-document, physically observed, accepted and system-received quantities. These values can legitimately differ while an exception is open. Do not alter a physical count merely to match the purchase order.

Use a second count or supervisory review according to thresholds and product risk. If goods moved before counting finished, record locations and the limitation.

Inspect condition and preserve evidence

Check packaging integrity and the defined product characteristics accessible at receipt. Describe dents, tears, wetness, broken bands, crushed corners, exposed product or indicator status precisely. “Damaged” alone is hard to investigate.

For structured condition evidence, adapt the equipment inspection checklist principles or use the applicable product inspection record. Record image filename, timestamp, item scope and photographer when photographs form evidence.

Protect evidence without delaying required safety or containment actions. Never open, sample or test goods outside authorization or competence.

Control discrepancies and quarantined goods

Create one discrepancy reference linking order, item, quantity, lot, observed condition, evidence and affected physical units. Mark and segregate goods so they cannot be consumed or shipped accidentally. Physical labels, location and system status should agree.

Discrepancy type and exact scope:
Observed evidence:
Temporary status / location:
Supplier, procurement or quality contact:
Decision owner and due date:
Claim / return / disposition reference:

Use an event incident report template when the arrival created a consequential operational event. Do not assign blame before evidence and contractual responsibilities are reviewed.

Post the receipt accurately

Enter only the verified quantity and status permitted by the procedure. Record transaction ID, user, time and any partial receipt, quarantine or blocked-stock state. A system receipt should not make physically unavailable goods appear ready for use.

Investigate interface or scanning errors before repeating transactions. Duplicate receipts can be harder to detect once putaway starts. If a correction is necessary, preserve the original transaction and approved adjustment trail.

Use the decision log template for consequential acceptance or disposition choices requiring durable rationale and authority.

Complete putaway and handover

Assign a valid location compatible with item status, handling and segregation requirements. Confirm the movement physically and in the system. Record any pallet split, relabeling or repacking through the approved traceability process.

Hand open inspections, supplier questions, claims and inventory adjustments to named owners. The warehouse shift handover checklist helps preserve unresolved receiving state across shifts.

Close the receipt only when every discrepancy is either resolved or transferred into a controlled open record with a review point.

Capture receiving information responsibly

Receiving conversations may contain driver, employee, supplier and commercial information. Capture only when authorized and necessary, with clear notice, agreement where required, controlled access and approved retention.

For an authorized receiving handover with visible, consented capture, Kuno can help draft a structured discrepancy and action record for human review. It does not count goods, inspect condition or decide acceptance. Explore Kuno

Verify every identifier, quantity, status and commitment against physical evidence and source systems before use.

Run the final QA checklist

Review receiving records as a process-control source, not just as proof that trucks were unloaded. Repeated shortages, label mismatches, late system receipts or damaged packaging can reveal issues in supplier preparation, transport, dock scheduling or internal handling. Analyze patterns with stable definitions and sufficient context. Do not assign supplier fault merely because an exception was first observed at the dock.

Periodically compare physical goods, receipt transactions, discrepancy records and putaway movements. Look for partial receipts left open, quarantine stock in usable locations, units converted inconsistently and corrections without evidence. Sample both exception and apparently clean receipts; reviewing only problem cases can miss controls that are routinely bypassed but have not yet produced a visible loss.

Design the checklist around the real material flow. Place identity and condition checks before goods are split or moved, and make exception labels and quarantine locations easy to access. If receivers routinely complete all fields after putaway, determine whether workload, device design or dock layout prevents timely capture. Improve the system while retaining the requirement for contemporaneous evidence.

Define what “received,” “accepted,” “inspected,” “released” and “available” mean in the warehouse and enterprise systems. These states should not be used interchangeably. Train adjacent teams, including planning and production, to read them correctly so they do not pressure receivers to bypass a hold merely because an order shows as delivered.

For supplier follow-up, send a concise reviewed package containing the relevant order, item, quantity, observed condition and authorized evidence. Keep internal speculation out of the external notice. Record the recipient, time, requested response and next escalation point. If goods must be returned, preserve authorization, carrier reference and physical custody through the final movement.

Plan for interruptions and handoffs at busy docks. If one receiver starts an inspection and another completes it, retain both identities, the transfer time and the exact state of unloading, counting and system entry. Do not let a shift change convert an unverified quantity into an accepted receipt. Make incomplete work visibly different from completed work in both the physical staging area and the digital queue.

Periodically test exception readiness with realistic scenarios such as an unexpected item, unreadable lot, damaged pallet or system outage. The purpose is to confirm that people know the approved segregation, notification and temporary-record routes. Do not simulate unsafe conditions or move real status labels casually. Record lessons, assign improvements and verify that updated tools remain available at the dock.

Before closing the receipt, confirm:

• Shipment, order, carrier and site references are traceable.
• Physical identity and unit of measure match the record.
• Count method, limitations and source quantities are visible.
• Condition evidence describes exact scope and location.
• Discrepant goods are identified, segregated and status-controlled.
• System quantity and availability reflect verified physical state.
• Corrections preserve an approved transaction trail.
• Putaway location and movement are confirmed.
• Claims, inspections and decisions have owners and deadlines.
• Sensitive evidence has appropriate access and retention.

Turn an agreed receiving handover into a reviewable draft. Kuno supports authorized capture and action extraction; warehouse, inventory and quality owners remain responsible for checking goods, records and decisions. See Kuno