A cargo seal discrepancy at delivery is an exception, not a verdict. The number may have been copied incorrectly, a similar serial pattern may have caused confusion, or an authorized inspection may have led to resealing without an updated manifest. A broken, missing, replaced, or mismatched seal can also indicate a more serious event, but the physical observation alone does not establish what happened.
To handle cargo seal discrepancy delivery procedures documentation escalation effectively, stop routine receipt, preserve the load and seal as found. Compare the physical serial number with the seal log and shipping records, record the condition, and notify the responsible parties according to your written procedure. If loss or damage may be involved, follow your carrier, insurer, customs, and company instructions before opening or moving the cargo.
The objective is to connect the physical load to a defensible chain of custody. That starts with defining exactly what differs and separating a recording error from evidence that requires investigation. A consistent approach also helps receiving teams make faster, better-supported decisions. For broader context, review this guide to container seal exception handling before examining the discrepancy itself.
What Is a Cargo Seal Discrepancy and Why Does It Matter?
A cargo seal discrepancy is any difference between the seal expected from the shipment records and the seal observed at delivery. The exception may be administrative, physical, or both. A receiving team might find a wrong number, a missing seal, a broken seal, a replacement seal, or a seal that is present but damaged. Each condition should be recorded as an observation first, then investigated through the available shipping and custody records.
Which seal conditions count as discrepancies?
- Wrong seal: The number on the container does not match the number on the manifest, bill of lading, seal log, or other expected record. A manifest typographical error can create a seal-number discrepancy, so verify the source record before drawing conclusions.
- Missing seal: The closure point has no seal where one was expected. Record the absence and preserve the delivery context rather than assuming when or where it disappeared.
- Broken or damaged seal: The seal is visibly fractured, cut, deformed, loose, or otherwise unable to provide the expected physical indication of closure. A damaged seal is an exception even when its number appears correct.
- Replaced seal: A different numbered seal is attached than the one recorded at dispatch. This can follow a legitimate inspection or other authorized intervention. It can also reflect replacement after theft or pilferage, which is a possibility to investigate, not proof that either occurred. Customs inspection may result in resealing without an amended manifest, according to the same seal discrepancy guidance.
Similar-looking serial patterns can also create recording confusion, especially when characters are transcribed manually. Compare the physical number carefully with the original record, checking characters that are easy to mistake, before escalating the exception as a custody failure.
The serial number matters because it connects a physical control to the shipment history. A seal can help document cargo integrity during transit, while the number is recorded in shipping documents after the container is closed. That relationship gives the receiving team a traceable point of comparison: the number issued or expected, the number observed, and any authorized change between them.
Keep the distinction clear. A mismatch, break, or absence proves that the expected record and physical condition do not align. It does not, by itself, prove theft, pilferage, or cargo loss. For baseline guidance on arrival inspection, records, and container seal exception handling, use a documented process that preserves the facts for the next review.
How Do You Handle Cargo Seal Discrepancy Delivery Procedures, Documentation, and Escalation?
A seal mismatch is an exception at handoff, not automatic proof that cargo was stolen or tampered with. Treat the observation as a fact to preserve and investigate. The receiving team should keep the load controlled, compare the physical seal with the transport record. And escalate according to the shipment's security plan, carrier instructions, contract, and applicable authority requirements.
Discuss your security seal requirements with STiER
Use this immediate response sequence
- Pause routine receipt. Stop the normal unloading or acceptance workflow long enough to secure the container or trailer and prevent the discrepancy from being obscured. Do not cut a seal, open cargo, or move freight indiscriminately. If an authorized inspection is necessary, follow the responsible party's documented procedure and preserve the original condition as far as safety allows.
- Preserve the scene. Keep the doors, locking points, seal, surrounding hardware, and load in their observed state. Control access and note who is present. A different number can have an innocent explanation, such as a recording error or an authorized resealing after inspection, but it can also require investigation. Do not convert an observation into a conclusion before the records and chain of custody are reviewed. Possible causes include manifest typing errors, confusion between similar serial patterns, or an unrecorded replacement. Review common causes of seal number discrepancies.
- Compare records before taking action. Read the seal number from the physical seal and compare it character by character with the bill of lading. Manifest, shipping instructions, dispatch record, seal log, and any exception or inspection notice. Confirm the container or trailer ID, route, delivery location, and expected handoff. Ask the shipper or carrier whether a replacement seal was authorized and whether customs or another authority documented a resealing.
- Inspect using an authorized method. Where your procedure permits it, apply CBP's View, Verify, Twist, and Tug principles: view the seal and attachment. Verify the number, check for an uncompromised condition, and confirm that it is properly affixed. CBP describes this method as a way to confirm the correct number, condition, and attachment. Read the CBP VVTT seal-verification guidance. Do not manipulate a government-installed seal or perform an invasive inspection without authorization.
- Photograph and record condition. Capture clear images of the seal number, seal body, locking point, door hardware, container or trailer identification, and any visible damage. Record the date, time, location, people present, observed condition, documents checked, and whether unloading was paused. Retain the removed seal only when an authorized inspection or policy requires removal, and connect it to the incident record.
- Notify the responsible parties. Tell the receiving supervisor or security lead promptly. Based on the facts and policy, notify the shipper, carrier or shipping line, broker, importer, compliance lead, insurer, and relevant customs or foreign authority. Potential loss or damage should be reported to the insurer, whose instructions should be followed. CBP guidance says compromised seals or containers must be reported to CBP or the appropriate foreign authority. See CBP reporting guidance for compromised seals.
How Should You Document a Seal Discrepancy for Customs and Claims?
A useful discrepancy record separates what the team expected from what it actually observed. That distinction helps customs, the carrier, an insurer, and internal reviewers reconstruct the handoff without turning a mismatch into an unsupported conclusion about theft or cargo loss. Complete the record at the delivery point, while the condition of the seal, container, and documents can still be verified.
What should the receiving record contain?
- Expected and observed seal numbers: Copy the number from the bill of lading, manifest, seal log, advance notice, or other applicable record. Then record the number physically present, or state clearly that the seal was missing. Note transposed digits, unreadable markings, a broken body, cut wire, damaged bolt, or signs that a seal was replaced.
- Load identity and timing: Record the container or trailer ID, delivery date and exact time, facility or gate location, dock number if relevant, and the carrier, driver, vessel, or shipment reference. Include the names and roles of everyone present when the discrepancy was found.
- Condition evidence: Take clear photographs of the seal from multiple angles, its attachment point, the container or trailer doors, locking hardware, and any visible damage. Preserve the original files and record who took them. Do not alter the scene or open the load unless an authorized procedure permits inspection.
- Documents and custody: Attach or reference the delivery receipt, bill of lading, manifest, inspection notice, exception report, prior handoff records, and seal issuance entry. Build a simple chain-of-custody timeline showing who controlled the load, when each handoff occurred, and whether anyone documented a replacement or inspection.
- Inspection, replacement, and notification: Record who authorized any inspection, which seal was removed, where it was retained, the replacement number, why the replacement occurred, and who applied it. Log notifications to the receiving supervisor, security or compliance lead, carrier, shipper, broker, insurer, and relevant customs authority, including the time, contact, method, and response.
CBP recommends maintaining documentation showing compliance with the applicable seal standard, logging seals when received, conducting periodic inventory checks, and updating the seal log when seals are issued. Those controls make the delivery record easier to compare with the organization's inventory and issuance history. See the documented seal condition for claims for related insurance-record considerations.
When a customs authority has inspected and resealed a container, identify that authority and preserve the notification trail. CBP guidance describes notifying appropriate parties of the examined container and newly installed seal number, with notification documented by phone, fax, transport documents, or another agreed method. Its OSD log resource also provides a reference point for overage, shortage, and discrepancy documentation. Requirements vary by jurisdiction, contract, and company policy. So route the completed record through the responsible compliance or claims process rather than promising claim eligibility based on documentation alone.
Source references: CBP recommended seal procedures; CBP sealing policy; CBP OSD log resource.
When Should You Refuse Delivery or Accept It Under Protest?
A seal discrepancy does not produce one automatic receiving decision. The prudent response depends on what is actually observed, whether the cargo or container shows visible damage. What the contract and carrier instructions require, and whether customs or another authorized authority controls the next inspection. Treat the discrepancy as an exception requiring escalation, not as proof of theft or a basis for assigning liability.
Before choosing between refusal and acceptance, stop routine unloading if doing so is safe. Preserve the seal and container condition, and compare the physical number with the transport documents and seal log. If an authority has inspected and resealed the container, follow the applicable authority and carrier process. CBP guidance says compromised seals or containers should be reported to CBP or the appropriate foreign authority. And its sealing policy addresses notification, replacement seals, and protection of authority-installed seals. Sources: CBP Recommended Seal Procedures and CBP sealing policy.
"Accept under protest" should be a documented commercial and operational decision, not a verbal workaround. Confirm that the receiving record states the exception before signing, and identify who authorized acceptance and what follow-up remains open. Refusal can also create storage, demurrage, safety, or customs consequences, so check the governing agreement and carrier instructions first. Federal guidance distinguishes effective practices from universal commercial mandates; apply the requirements that govern your shipment, jurisdiction, and program. For U.S. shipments, retain the relevant seal and discrepancy records and use the applicable CBP OSD log resource where appropriate. The objective is a controlled decision supported by evidence, authorization, and a clear escalation path.
How Can a Serialized Seal Program Reduce Delivery Discrepancies?
A serialized seal program gives every seal a controlled identity before it reaches a loading dock. Instead of relying on a handwritten description such as "blue bolt seal," the shipper can issue a specific number. Record who received it, and connect that number to a container, trailer, shipment, and date. That traceability makes a delivery discrepancy easier to investigate without assuming that a mismatch proves theft or cargo loss.
Before transit, control starts with inventory. Log seals when they arrive, safeguard unused stock, and record each number issued and used. CBP guidance recommends maintaining a seal log, updating it when seals are issued, and conducting periodic inventory checks, including at least an annual inventory during an internal audit. See the CBP seal procedures and best practices for the relevant U.S. guidance. Written procedures should also define issuance, attachment, tracking, removal, destruction, and number records. CBSA identifies these controls for PIP members, while noting that its guidance applies to imported, exported, and in-transit cargo.
During transit, verification connects the record to the physical load. The person applying the seal should confirm the number against the shipping documents, record the container or trailer ID, and document the handoff. At receiving, trained staff can compare the expected number with the physical seal and check its condition and attachment. CBP's View, Verify, Twist, and Tug method is one example of a structured check. Training matters because similar-looking serial patterns and transcription errors can create confusion even when the cargo has not been disturbed.
After delivery, the exception history preserves context. Record the observed number, condition, time, location, people present, photos, inspection authority, and any replacement number. If an authority inspected and resealed the container, retain the removed seal and related notification or transport-document notation according to the applicable procedure. Certificates and conformity documentation should stay with the vendor and compliance records, so the organization can verify the seal standard when required. Accurate logs, verification processes, and certificates are recognized as useful components of a CTPAT-oriented control program. For background, review cargo seal serialization and tracking and CTPAT and ISO seal certification.
STiER offers serialized bolt and cable seals that can be customized with numbering, barcodes, logos, and text. Those options can align physical seals with internal shipment, lane, facility, or customer-control systems. Replacement control is equally important: a new seal should be issued from authorized stock, linked to the original exception record, and communicated to the responsible parties. That creates a defensible sequence from issuance through delivery.
Discuss your security seal requirements with STiER.
Frequently Asked Questions
What should you do first when a cargo seal does not match the records?
Pause routine receipt and preserve the scene. Record the container or trailer ID, observed seal number, condition, time, location, and people present. Compare the physical seal with the bill of lading, seal log, and delivery records, then notify your receiving supervisor and the responsible carrier or shipper. Do not assume the mismatch proves theft. A typographical error, similar-looking serial numbers, or an authorized resealing may also explain the discrepancy.
What are signs that a cargo seal may have been tampered with?
Look for a broken, cut, loose, damaged, or poorly attached seal, tool marks around the locking point. A different serial number, or a seal that does not match the shipping documents. Photograph the condition before moving or opening the load, and preserve removed seals when authorized. These observations identify an exception for investigation. They do not, by themselves, establish cargo loss or tampering.
What are the CTPAT requirements for cargo seals?
CTPAT seal controls generally include high-security seals meeting the applicable ISO 17712 requirements. A process to verify that seals are properly affixed and functioning, written control procedures, and accurate inventory and issue records. CTPAT guidance also emphasizes retaining documentation for review. Confirm the current requirements for your membership status and operation directly with U.S. Customs and Border Protection: CBP seal procedures.
What standard is required for high-security cargo seals?
ISO 17712 is the commonly referenced standard for high-security mechanical freight seals, including requirements related to testing and classification. The correct requirement can depend on the shipment, program, contract, and jurisdiction, so request current conformity documentation for the specific seal. Do not treat a generic product description or a seal number alone as proof of certification.
Ready to strengthen your seal discrepancy process?
A consistent response depends on clear procedures, accurate serialization, and documentation that supports review when a delivery exception occurs. STiER can help you evaluate the security seals, tracking controls, and compliance requirements that fit your operation.