Seal Number Checklist

How this comes up in practice

A cargo claim dispute over temperature-sensitive freight came down to a single missing notation. The carrier had applied a seal at the shipper, written the number on the BOL header, and photographed the sealed trailer before departure. At the receiving facility, the receiver opened the trailer and found damage before anyone recorded the seal condition on arrival. The carrier's position was that the trailer had been properly sealed and maintained throughout transit; the receiver's position was that they had no record of what the seal looked like before they opened it. Both accounts were documented in writing. What was missing was the delivery-side seal record: the number confirmed and noted before the trailer was opened, with the receiver's initials. That comparison — seal at pickup against seal at delivery — would have established either an unbroken chain or a specific point of exception. Without the delivery notation, the dispute had two consistent but incompatible accounts and no document to settle them.

What seal records establish and where the chain breaks

A seal number's value in a freight transaction is proportional to the consistency with which it's recorded across custody points. A seal noted at the shipper, confirmed on the BOL, and compared at delivery creates a complete custody record for that container. Any break in that chain creates a dispute window — a period during transit where an exception could have occurred without documentation. For adjacent verification steps, compare this with Bill of Lading Red Flags, Cargo Theft Prevention Checklist, and GPS Tracking and Load Security Basics.

Seal records matter most in two situations: cargo claims, where the seal condition at delivery helps establish whether damage happened in transit or at the receiving facility; and theft incidents, where a seal on the BOL that doesn't match what arrived may indicate unauthorized access during transport. In both cases, the value of the seal record depends entirely on whether it was captured consistently.

The chain breaks at the delivery end when receivers open the trailer before recording the arriving seal number and its condition. If that notation isn't made before the trailer is opened, the opportunity to establish the arrival state is gone. A seal record at pickup without a corresponding record at delivery doesn't create the chain — it only establishes one end of it.

Recording seal numbers consistently through the transit chain

A seal number is only meaningful if it was recorded consistently at every custody point. The seal applied at the shipper needs to match what's on the BOL, what the driver confirms at pickup, and what the receiver records at delivery. A break in that chain — a different number, a missing notation, a seal that can't be located — is a documented exception that matters for cargo claims and transit disputes.

When in-transit tampering is disputed, the seal record is what the review turns on. A seal number recorded on the BOL and confirmed at delivery puts any exception in writing at the right time. Without that record, the question of when a discrepancy occurred becomes very difficult to answer.

Records to check at each custody point

Use the same identifiers across every record. Small differences can be clerical, but they should be resolved before pickup, dispatch, or payment.

If a detail is missing, ask for the missing record rather than filling the gap from memory, an old packet, or a search result.

What to document through the transit

Save records in their original format when possible. Use one folder named with the load number, lane, date, and parties involved.

If a dispute, identity concern, or theft concern appears later, the timeline is easier to reconstruct when emails, PDFs, screenshots, call notes, and lookup results are grouped together.

Questions to ask at pickup and delivery

Questions should be specific and tied to records. That keeps the conversation professional and avoids unsupported accusations.

If an answer changes the transaction, document the person, date, time, and channel used to confirm it.

Assumptions that reduce theft prevention

One detail checking out is not the same as authorization confirmed. A correct number, a recognized company name, or a well-formatted document can each appear in a transaction where the communicating party has no connection to the registered entity.

A warning sign is a reason to document and verify, not a finding. Record what prompted the concern and what check it led to — that record determines whether the situation can be addressed if it escalates.

When to escalate a theft concern

When the file still has gaps, slow the transaction enough to preserve the record and move the question to the right channel.

That may mean a direct call-back, a shipper or receiver confirmation, an internal escalation, an insurer or claims contact, or an official complaint or reporting resource where appropriate.

Source Notes

FAQ