What Is an OS&D Report? Purpose, Key Fields, and Common Terms

OS&D Report A report documenting overages, shortages, and damages identified during freight receipt. The OS&D report is the formal record created at the receiving dock when the physical condition or quantity of inbound freight differs from the shipping documents.

In practice an OS&D report ties together three common exceptions: overages (more items than expected), shortages (fewer items than expected), and damages (items or packaging that arrived compromised). Warehouses and 3PLs use OS&D reports to initiate carrier claims, notify suppliers or merchants, and update inventory records in the warehouse management system (WMS).

Why The OS&D Report Matters

An accurate OS&D report preserves legal and commercial rights, accelerates claims, and prevents inventory inaccuracies. Carriers typically require written notification (often with photographs and supporting documents) before a claims window closes. Merchants need timely OS&D information to adjust purchase orders, reallocate stock, or trigger expedited replenishment.

Typical Fields Found On An OS&D Report

• Shipment identifiers: Bill of lading number, shipment reference, carrier, and booking numbers used to link the report to the transport documentation.
• Receiving details: Date/time, receiving dock, receiving clerk name, and condition of the trailer or container on arrival.
• Item-level information: SKU or GTIN, description, quantity expected, quantity received, and unit of measure.
• Damage description: Nature of damage (crushed, wet, punctured), severity, and location on the pallet or carton.
• Evidence: Photographs, weight discrepancies, pallet count, and signatures from carrier or driver when available.
• Action taken: Quarantine status, disposition (accept, reject, partial accept), and whether a claim was initiated.

How OS&D Reporting Interfaces With Systems And Processes

Most modern warehouses capture OS&D data directly in the WMS or a receiving app at the dock. That entry updates inventory holdings and triggers workflows: a quarantine tag, a quality control inspection, a supplier notification, or initiation of a carrier claim. Where electronic data interchange (EDI) or an advanced ship notice (ASN) is available, receiving personnel compare expected counts to scanned receipts to flag discrepancies quickly.

Who Uses The OS&D Report And When

• Warehouse operations: Use the report to correct inventory and direct follow-up actions (putaway, QC, return to shipper).
• Merchants and buyers: Rely on OS&D reports to adjust payable invoices, reconcile orders, and open supplier disputes.
• Carriers: Require documentation to investigate freight integrity and adjudicate claims.
• Customer service/fulfillment teams: Use OS&D information to manage customer expectations and reroute stock to meet demand.

Common Pitfalls And How To Avoid Them

Common mistakes include delayed reporting, poor photographic evidence, and incomplete linkage to shipping documents. Best practice is to capture OS&D details immediately at the dock, include time-stamped photos of damage and shipping labels, and ensure the OS&D report references the bill of lading and PO number. Consistent templates and training reduce disputes and speed claim resolution.

Practical Example

During a morning reception, a pallet of packaged consumer electronics is unloaded. The packing list shows 50 cartons; the WMS scan reveals 47 cartons. Two cartons show water stains and crushed corners. The receiving clerk creates an OS&D report that records the BOL number, lists the SKU and expected/received quantities, attaches three photos (wide shot of pallet, close-up of water stain, photo of label), and marks the goods as quarantined. The report is sent to the merchant and the carrier; inventory is adjusted to show 47 units available pending inspection and claim disposition.

In short, the OS&D Report is the formal record warehouses use to document overages, shortages, and damages at receipt; it links evidence, inventory adjustments, and claims actions so operations, merchants, and carriers can resolve exceptions efficiently.