A receiver finds one crushed pallet, two missing cartons and an extra skid that is not on the advance shipping notice. The driver wants a signature. Purchasing wants the material released. Finance wants to know who owns the loss. Customer service wants inventory now.
That is freight OS&D: over, short and damaged freight. It is not clerical cleanup. It is the point where physical inventory, carrier liability and customer availability collide. If the dock signs clean, mixes the exception into good stock or waits until tomorrow for photos, the company can lose both the product and the evidence needed to recover the money.
A disciplined OS&D workflow makes the receiving team fast without making them careless. Clean freight keeps moving. Exceptions get counted, isolated, documented and assigned before the trailer leaves. Easy Logistics can build that workflow inside a 3PL warehousing and fulfillment operation instead of leaving every dock to invent its own rules.
Freight OS&D starts as an inventory-control event
The first mistake is sending every discrepancy straight to “claims.” A formal claim may come later. The immediate job is to establish what arrived, what condition it was in and whether it can enter available inventory.
Use four operational codes:
- Over: more handling units or units arrived than the shipment record expected.
- Short: the trailer, pallet or carton count is below the expected quantity.
- Damaged: packaging or product condition creates a quality, safety or resale exception.
- Unknown: identity, ownership or disposition cannot be confirmed at receipt.
“Unknown” matters. A pallet with no matching purchase order is not free inventory. A crushed carton is not automatically scrap. A shortage is not proven theft. Each is a controlled exception until the evidence supports a disposition.
This is where the workflow separates from a general dock-to-stock improvement program. Dock-to-stock measures how quickly good inventory becomes usable. OS&D controls what must not become usable yet.
Run the first 15 minutes by exception code
The receiving team needs a short decision tree, not a 40-page SOP nobody opens while a driver is waiting.
- Count before breaking the load. Compare trailer position, pallet count, carton count and shipment identifiers with the bill of lading, purchase order and ASN.
- Stop only the exception. Move damaged or unidentified freight to a marked quarantine location. Release clean, matched units when policy allows.
- Record the delivery exception. Note observable facts on the delivery record before signing: quantities, handling-unit IDs and visible condition. Do not write a conclusion you cannot prove.
- Capture evidence. Photograph the trailer position, pallet from multiple angles, packaging, labels, seal if relevant and the product condition discovered during inspection.
- Assign an owner and clock. Create a case with a due time for carrier notice, supplier research, customer decision and financial reserve.
The wording matters. “Two cartons missing from pallet SSCC 000123…” is useful. “Driver stole product” is speculation and creates noise. Facts travel cleanly through operations, finance and carrier review.
The federal claim rules reinforce the distinction between a delivery notation and a claim. Under 49 CFR 370.3, a written cargo claim must identify the shipment, assert liability and demand a specified or determinable amount. A bad-order report, delivery-receipt notation or inspection report alone is not a sufficient claim.
Automate clean matches; send judgment calls to people
Automation should remove comparison work, not pretend a camera can decide commercial liability.
A practical logistics and API automation workflow pulls the expected purchase order, ASN, bill of lading and item master into one receiving record. A scan confirms the handling unit, compares expected and actual quantities, time-stamps the event and creates an exception only when the rules fail.
GS1 US explains that the Serial Shipping Container Code identifies an individual logistics unit and is commonly carried in a GS1-128 barcode on the logistics label. That identifier becomes the bridge between the physical pallet, ASN detail and evidence record. It is far stronger than a photo named “IMG_4832.jpg.”
Automate:
- expected-versus-received quantity comparisons;
- duplicate or unknown handling-unit alerts;
- required photo and document checklists;
- quarantine location assignment;
- notifications, aging clocks and status updates; and
- approved disposition transactions back to the WMS and ERP.
Humans still decide whether packaging damage threatens the product, whether an overage belongs to another consignee, whether partial product can be salvaged and who is financially responsible. That is exception work. Automating it blindly just makes bad inventory available faster.
Build the evidence packet before freight moves
An OS&D record should be usable by the warehouse manager, shipper, carrier and finance team without four separate email chains.
At minimum, retain the shipment ID, bill of lading, purchase order, ASN, carrier and trailer, appointment and arrival times, seal data when applicable, actual counts, exception code, photos, delivery receipt, product value, freight charges, inspection notes, disposition decision and every status update.
That packet aligns with the carrier-investigation requirements in 49 CFR 370.7, which calls for prompt, thorough investigation and identifies bills of lading, freight-charge evidence and invoices or certified value support as relevant claim documents.
The warehouse is building evidence, not deciding the legal outcome. The claim owner then follows the company’s freight-claim documentation process, contract terms and applicable law. That handoff should be explicit: case number, owner, claimed amount, filing date and next carrier-response deadline.
Price the exception, not just the damaged units
Illustrative example — run your own numbers.
A 3PL receives 600 inbound loads per month. Five percent create an OS&D case, or 30 cases. Each case requires 45 minutes of warehouse and office time at a blended loaded labor rate of $34 per hour. Ten cases also delay $1,200 of sellable inventory for an average of three days. Two weak evidence packets per month lead to $900 of unrecovered loss each.
- Direct exception labor: 30 × 0.75 × $34 = $765 per month.
- Inventory held in exception: 10 × $1,200 = $12,000 temporarily unavailable.
- Unrecovered losses: 2 × $900 = $1,800 per month.
The biggest number is rarely labor. It is the value trapped in quarantine, written off without proof or promised to customers while still physically questionable. Track case rate, hours to first decision, days in quarantine, value at risk, recovery percentage and repeat cause by supplier, lane and carrier.
Do not use inventory adjustments to make the dashboard look clean. Reconcile approved dispositions through the same transaction discipline used in a 3PL inventory-accuracy program. Otherwise the exception disappears from the report and reappears later as shrink.
Close each case and attack the repeat cause
A case is not closed because the pallet left quarantine. Close it only after the physical disposition, WMS transaction, ERP value, supplier or carrier recovery and customer impact agree.
For regulated motor-carrier claims, 49 CFR 370.9 requires a carrier to pay, decline or make a firm compromise offer within 120 days after receiving a written claim, or provide a written status and reason for delay at that point and every succeeding 60 days while it remains pending. Your workflow needs those follow-up dates. “Carrier notified” is not a closed-loop control.
Then aggregate the causes. Repeated shortages from one supplier may be an ASN or pack-verification failure. Repeated corner crush on one lane may point to packaging, pallet footprint or handling. Repeated unknown overages may reveal weak label controls. That is where better ASN receiving controls prevent future cases instead of merely processing them faster.
Here is the damaging admission: a formal OS&D workflow is overkill for a tiny operation receiving a few low-value, easily replaceable shipments each month. A short checklist and named owner may be enough. It also fails when receiving staff lack authority to stop or quarantine freight. Software cannot rescue a dock that is rewarded only for speed.
If OS&D cases are tying up inventory, weakening freight claims or creating arguments between the warehouse and finance, Easy Logistics can map the receiving controls, 3PL responsibilities and automation handoffs. Use the form below to request a freight OS&D workflow review or warehousing proposal.