A container arrives at the Port of Long Beach with a bolt seal numbered BTS-4471. The bill of lading says BTS-4471. The carrier’s electronic logging system says BTS-4471. Everything matches \u2014 until the warehouse team breaks the seal and finds the load is 14 cartons short of what the packing list claims.<\/p>
Nobody can say where the shortage happened. The seal was intact at origin. It was intact at the terminal gate. It was intact when the trucker picked it up. But the cargo inside was not.<\/p>
This scenario plays out every week at ports, rail ramps, and distribution centers across North America. Verisk CargoNet recorded $304.6 million in cargo theft losses in Q2 2026 alone, with an average shipment value of $564,009. Business email compromise remained the primary attack vector, letting criminals redirect shipments without touching a single seal. The problem is not that seals fail. The problem is that a seal number recorded in a free-text field tells you nothing about who handled the container, when, or what happened between handoffs.<\/p>
A high-security bolt seal deters entry and makes tampering visible. But a seal number typed into a shipping document is only a label unless your operation treats it as part of a structured chain-of-custody event system.<\/p>
A container seal number sitting in a free-text field on a bill of lading or TMS screen looks like a security control. In practice, it is often just a label \u2014 easy to mistype, overwrite, or copy forward without verification. When a discrepancy surfaces, the number cannot answer the questions that matter:<\/p>
ISO 17712 establishes the physical requirements for high-security mechanical seals \u2014 tensile strength, shear resistance, bend tests. Those specifications ensure the seal resists casual removal and exposes physical interference. But physical strength does not produce an unbroken custody record. That record comes from a sequence of verified events captured at every transfer point.<\/p>
The difference matters in a worsening theft environment. Verisk CargoNet reports that compromise-based schemes \u2014 business email fraud, shipment misdirection, identity deception \u2014 persisted at steady levels even as physical trailer thefts declined in California and Texas. Criminals no longer need to cut a seal. They redirect the shipment before a seal is ever applied, or they exploit gaps in the handoff record where nobody verified the seal against the system.<\/p>
A transportation management system or seal management platform should not treat the seal number as a single editable attribute. It should create an append-only event whenever the seal’s state changes. Five event types cover the normal seal lifecycle at any transfer point:<\/p>
1. Applied<\/strong> \u2014 The container is closed and a specific seal is attached. The event records the shipment ID, seal number, seal type (ISO 17712 classification), timestamp, facility or geolocation, and the person who applied it. A photo of the installed seal with the container number visible provides supporting evidence.<\/p> 2. Verified<\/strong> \u2014 A carrier, terminal operator, warehouse team, or consignee confirms the seal number and physical condition without changing the seal. This is the event that should fire at every gate-in, gate-out, driver handoff, and cross-dock transfer. The verifier scans or reads the number, compares it to the last applied or replaced event, and logs a pass or mismatch.<\/p> 3. Broken<\/strong> \u2014 An authorized party removes the seal and records the reason. Customs inspections, agricultural inspections, and emergency load adjustments all fall here. The event must capture who authorized the break, the reason code, and the condition of the removed seal.<\/p> 4. Replaced<\/strong> \u2014 A new seal follows an authorized opening, with an explicit link to the old seal number. The replacement event creates the bridge that keeps the custody chain unbroken across an authorized intervention. Without this event, a customs inspection looks like a tampering incident.<\/p> 5. Exception<\/strong> \u2014 The seal is missing, damaged, unreadable, mismatched, or otherwise suspect. This is the event that should stop the workflow, not just generate a warning.<\/p> Every event should capture the shipment and equipment IDs, seal number and type, timestamp, geolocation or facility, actor identity and role, seal condition, and supporting photo. Application and replacement events should record whether the seal is ISO 17712 compliant. Break and exception events need structured reason codes, notes, authorization, and the next required action.<\/p> This structure preserves history. A corrected typo does not erase the original entry. A replacement does not make the prior seal disappear. When a shortage surfaces at delivery, the event log shows exactly where the seal was last verified intact \u2014 and where the gap begins.<\/p> Different transfer points carry different risk profiles and require different seal types. A port terminal handling international containers needs ISO 17712 High Security seals. A cross-dock moving domestic pallets may rely on indicative seals. The table below maps all eight seal categories to their primary transfer-point roles:<\/p> The principle is layered security. A bolt seal protects the container door. A plastic seal on the pallet inside protects the inner load. An RFID seal at the gate automates verification. If only the bolt seal is intact but the pallet seal is broken, the event log narrows the interference window to the segment between the last pallet-seal verification and the discovery. That precision is what makes a chain-of-custody program actionable \u2014 not just evidence after the fact, but a diagnostic tool that tells you where to investigate.<\/p> The most dangerous design in a seal management system is a warning that users can ignore while the shipment continues moving. A seal mismatch at a terminal gate should not produce a pop-up that a clerk dismisses with a click. It should place the container on security hold and block the next milestone \u2014 whether that is gate-out, customs release, or delivery confirmation.<\/p> Here is how the stop points should work at each transfer point:<\/p> At the terminal gate:<\/strong> The observed seal must match the last valid applied or replaced event. If the numbers diverge, the container does not leave the gate until the discrepancy is researched and resolved. The TMS opens an exception task, notifies the designated security owner, and requests evidence from the current custodian.<\/p> Before a customs release step:<\/strong> The system confirms that every authorized inspection and resealing event is complete. If a customs break was logged but no replacement seal event followed, the release is blocked until the replacement is verified.<\/p> At delivery:<\/strong> The consignee verifies both the number and the physical condition before breaking the seal. A mismatch triggers a joint inspection, not a signature and a shrug.<\/p> This is not bureaucracy for its own sake. Allowing movement first and investigating later destroys location certainty and weakens any insurance claim. The event log is only as strong as the workflow that enforces it. If a mismatch can be overridden without a second authorization, the chain of custody has a hole that organized theft rings will find.<\/p> A Contguard security analysis published in August 2026 flagged a growing vulnerability: standalone GPS tracking has become a primary vector for organized theft. Criminals deploy low-cost signal relay boxes that broadcast fake location pings to a shipper’s TMS while the physical trailer is diverted to a dark warehouse. The dashboard shows the truck on schedule. The cargo is already gone.<\/p> Modern security frameworks now use multi-sensor anomaly scoring \u2014 cross-referencing GPS pings with internal light sensors, accelerometers, door-latch state, and temperature thresholds. If a trailer’s GPS says 65 MPH but the accelerometer detects zero motion, the system flags a 99% anomaly score and locks down the container.<\/p> Physical seals play a critical role in this architecture. A bolt seal or cable seal provides the tamper-evident layer that digital sensors cannot. If a GPS spoofer hides the diversion but the seal is broken on arrival, the physical evidence forces an investigation that the digital trail would not have triggered. RFID seals add another dimension \u2014 an automated read at the gate that compares the seal ID to the shipment record without human intervention, closing the gap that free-text entry leaves open.<\/p> The combination is what works. GPS for location. Multi-sensor fusion for anomaly detection. Physical seals for tamper evidence. RFID seals for automated verification. Chain-of-custody events for accountability. No single layer is sufficient. Each layer covers the blind spot of the next.<\/p> Transforming a free-text seal number into a structured event system does not require a complete TMS replacement. A phased rollout keeps operations running while building the custody record:<\/p> Step 1: Map your transfer points.<\/strong> List every location where a container changes hands \u2014 origin warehouse, port gate-in, terminal yard, rail ramp, cross-dock, destination DC. Each point is a verification station.<\/p> Step 2: Define the five event types in your system.<\/strong> If your TMS supports custom fields and status workflows, model the events as sequential status changes with mandatory fields for actor, timestamp, and photo. If your TMS cannot enforce a hold on mismatched seals, add a lightweight middleware layer between your gate processes and the TMS.<\/p> Step 3: Assign roles and authorization.<\/strong> Define who can apply, verify, break, replace, and override. High-risk overrides \u2014 such as releasing a container with a mismatched seal \u2014 should require approval by a second person. Every override event logs who requested it, who approved it, and which blocked milestone was released.<\/p> Step 4: Add photo evidence with context.<\/strong> A seal photo stored in a shared folder is barely better than free text. The photo must belong to the event and show the legible seal number, closure hardware, and container number where practical. The system should reject an application or replacement event when the photographed number and entered number conflict.<\/p> Step 5: Start with one lane, measure, expand.<\/strong> Pick one shipping lane with three to five transfer points. Run the event system for two weeks. Measure verification rate (percentage of handoffs where a verified event was logged), mismatch rate, and average time to resolve exceptions. Target 95%+ verification rate before expanding to additional lanes.<\/p> What is the difference between a seal number and a chain-of-custody event?<\/strong> A seal number is an identifier. A chain-of-custody event is a structured record that captures who handled the seal, when, where, and what happened. A number sitting in a free-text field is just a label. An event log creates an auditable history that can trace a discrepancy to a specific point in the journey.<\/p> Do I need a new TMS to implement seal event tracking?<\/strong> Not necessarily. If your current TMS supports custom fields and status workflows, you can model the five event types as sequential status changes with mandatory fields for actor, timestamp, and photo. If your TMS cannot enforce a hold on mismatched seals, consider adding a lightweight middleware layer that sits between your gate processes and the TMS.<\/p> How do RFID seals improve chain-of-custody at transfer points?<\/strong> RFID seals automate the verification event. Instead of a gate clerk manually reading a number and typing it into a system, a fixed reader at the gate captures the seal ID as the container passes and logs a verified event with a timestamp. This eliminates transcription errors and creates a read rate that exceeds 99.5% at a well-tuned installation. The RFID read does not replace the physical inspection \u2014 it makes the verification event faster and more reliable.<\/p> What happens if customs breaks my seal during inspection?<\/strong> Your program should handle this as a two-event sequence: a Broken event (authorized, with reason code and customs reference) followed by a Replaced event (new seal number, applied by the customs officer or facility representative, linked to the old number). The replacement event keeps the custody chain unbroken across the authorized intervention.<\/p> Which seal type should I use at each transfer point?<\/strong> Use ISO 17712 High Security bolt seals for international containerized freight at origin and port gate-in. Use cable seals or metal strap seals for rail and drum applications. Use plastic indicative seals for pallet-level and carton-level evidence at cross-docks. Use padlock seals for reusable internal custody transfers. Use RFID seals where throughput demands automated gate scanning. The right seal depends on the risk tier of the transfer point, not on a one-size-fits-all standard.<\/p> Can a seal chain-of-custody program stop business email compromise?<\/strong> Not directly. BEC attacks redirect shipments before a physical seal is applied, exploiting gaps in communication and identity verification rather than physical security. But a chain-of-custody program that requires a verified seal application event before a shipment can advance to the pickup milestone creates a control point. If the seal application event does not match the authorized shipper and facility, the system can flag the shipment for investigation before it leaves the dock.<\/p> How does this work with C-TPAT and ISO 17712 compliance?<\/strong> C-TPAT requires importers to maintain seal integrity throughout the supply chain, including verification at each transfer point. ISO 17712 defines the physical standards for the seals. A chain-of-custody event system provides the operational evidence that C-TPAT auditors look for \u2014 not just that high-security seals were used, but that they were verified at each handoff, that exceptions were documented, and that broken seals were replaced with a traceable link to the original.<\/p> A seal program that only records a number on a bill of lading is a program that cannot answer the most important question when something goes wrong: where did the gap happen? The answer comes from treating every seal interaction as a structured event \u2014 applied, verified, broken, replaced, exception \u2014 captured at every transfer point from origin to delivery.<\/p> Start with one lane. Map the transfer points. Define the five event types. Build the mismatch stops. Add photo evidence. Then expand. The goal is not more data. The goal is a custody record that can narrow a $564,000 shortage to a specific gate, a specific timestamp, and a specific handler \u2014 before the cargo disappears entirely.<\/p> Explore our bolt seal and container lock seal collections for ISO 17712 High Security options suited to port and terminal operations. Check out our guide on building a multi-layer seal strategy for deeper coverage on combining seal types across your supply chain. Subscribe to our newsletter for quarterly updates on cargo security best practices and chain-of-custody standards.<\/p> Contact our team to learn more about implementing a structured seal event system across your transfer points.<\/p> Written by:<\/strong> Kocents Engineering Team Updated:<\/strong> August 2026 Reviewed by:<\/strong> Kocents Quality Assurance<\/p> Kocents is an ISO 17712-certified security seal manufacturer specializing in bolt seals, cable seals, plastic seals, RFID seals, padlock seals, meter seals, metal strap seals, and container lock seals for global logistics and supply chain security.<\/em><\/p> Standards & References:<\/strong> ISO 17712:2013 (High Security Seal Classification), C-TPAT Minimum Security Criteria for Container Sealing, AEO Supply Chain Security Guidelines, TAPA FSR Physical Security Requirements.<\/p> container seal chain of custody, seal verification, ISO 17712 seal, cargo theft prevention, port terminal security, C-TPAT seal compliance, tamper evident seal, RFID container seal, supply chain security, seal number tracking, bolt seal, cable seal, plastic seal, padlock seal, metal strap seal, meter seal, container lock seal<\/p>","protected":false},"excerpt":{"rendered":" Learn how to build a container seal chain-of-custody program at ports, terminals, and DCs. Track 5 seal events, prevent cargo theft, and meet C-TPAT compliance in 2026.<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[253],"tags":[701,703,774,842,858,859,860,263,600,616,624,691],"class_list":["post-4453","post","type-post","status-publish","format-standard","hentry","category-application-cases","tag-tamper-evident-seal-cc","tag-cargo-theft-prevention-cc","tag-rfid-container-seal","tag-seal-verification","tag-chain-of-custody","tag-port-security","tag-terminal-security","tag-supply-chain-security","tag-c-tpat","tag-container-seal","tag-bolt-seal","tag-iso-17712"],"_links":{"self":[{"href":"https:\/\/www.woseal.com\/es\/wp-json\/wp\/v2\/posts\/4453","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.woseal.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.woseal.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.woseal.com\/es\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.woseal.com\/es\/wp-json\/wp\/v2\/comments?post=4453"}],"version-history":[{"count":1,"href":"https:\/\/www.woseal.com\/es\/wp-json\/wp\/v2\/posts\/4453\/revisions"}],"predecessor-version":[{"id":4454,"href":"https:\/\/www.woseal.com\/es\/wp-json\/wp\/v2\/posts\/4453\/revisions\/4454"}],"wp:attachment":[{"href":"https:\/\/www.woseal.com\/es\/wp-json\/wp\/v2\/media?parent=4453"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.woseal.com\/es\/wp-json\/wp\/v2\/categories?post=4453"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.woseal.com\/es\/wp-json\/wp\/v2\/tags?post=4453"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Mapping Seal Types to Transfer Point Security Tiers<\/h2>
Seal Type<\/th> ISO 17712 Class<\/th> Primary Transfer Point Role<\/th> Best Fit Scenario<\/th><\/tr><\/thead> Sello de perno<\/strong><\/td> High Security (H)<\/td> Origin seal, ocean container gate-in\/gate-out<\/td> International containerized freight, C-TPAT shipments<\/td><\/tr> Container Lock Seal<\/strong><\/td> High Security (H)<\/td> Terminal yard, high-value container storage<\/td> Extended yard dwell, high-risk lanes<\/td><\/tr> Junta del cable<\/strong><\/td> Security (S)<\/td> Rail ramp, valve and access point sealing<\/td> Railcars, drum closures, multi-leg transit<\/td><\/tr> Sello RFID<\/strong><\/td> Varies (H\/S\/I)<\/td> Automated gate scanning, dock-door verification<\/td> High-throughput ports, RFID-equipped DCs<\/td><\/tr> Sello de candado<\/strong><\/td> Indicative (I)<\/td> Reusable container closures, internal yard moves<\/td> Short-loop transfers, internal custody handoffs<\/td><\/tr> Precinto met\u00e1lico<\/strong><\/td> Security (S)<\/td> Railcar seals, drum and valve sealing<\/td> Rail transfer points, chemical drums<\/td><\/tr> Sello de pl\u00e1stico<\/strong><\/td> Indicative (I)<\/td> Pallet-level sealing, carton-level tamper evidence<\/td> Cross-dock pallet moves, e-commerce parcels<\/td><\/tr> Sello del contador<\/strong><\/td> Indicative (I)<\/td> Utility interface points at facility perimeters<\/td> Port facility utilities, reefer plug stations<\/td><\/tr><\/tbody><\/table><\/figure> Building Mismatch Stops Into Your Workflow<\/h2>
Why Physical Seals Still Matter in a GPS-Spoofing World<\/h2>
Implementing the Program: A Five-Step Rollout<\/h2>
FAQ<\/h2>
Building a Seal Program That Tells You Where the Gap Is<\/h2>