Knowing how to track serialized security seals takes more than buying seals with unique numbers. A reliable process connects each number to a specific shipment, responsible person, location or handoff, and final disposition. That creates a record your team can check when a seal is inspected, replaced, reported missing, or removed. The steps below give logistics and compliance teams a practical starting point.
Discuss serialized seal requirements with STiER
What does a serialized seal number tell your team?
A serialized seal carries a unique identifier that staff can record and compare during a shipment's movement. The number links a physical seal to a written or electronic record. When a worker checks a door, the recorded number can be compared with the number assigned to that shipment or documented at the previous handoff.
Serialization is an identification and recordkeeping tool. A number by itself does not show where a shipment is, prove that a door was never opened, or prevent every form of tampering. A seal's physical design, the way it is applied, the custody process, and the inspection routine all matter. Treat the number as one part of a cargo-security control, not as a substitute for a complete procedure.
For cargo moving through multiple facilities, a usable record answers a small set of questions: which seal was used, which shipment it belongs to, who applied it, when and where it was checked, whether the number matched, and what happened when the seal was removed. The U.S. Navy's User's Guide on Security Seals for Domestic Cargo provides guidance on types of seals used to secure and control cargo, doors, and equipment. The EFCOG Safeguards Seals Reference Guide discusses developing a seals program for a defined need and selecting and using seals. Your own process should account for the seal type, cargo, route, and customer or program requirements.
How should a team set up a seal-tracking process?
Start with a written procedure that follows the seal from receipt to closure. Decide who may receive, issue, apply, inspect, replace, and reconcile seals. Define where the official record lives and which fields are required. Then train staff to make the entry at the time of the action, rather than relying on memory at the end of a shift.
- Receive and control inventory. Record the seal type, identifier range or individual numbers, quantity received, receipt date, and the person accepting custody. Store unused seals so access is controlled and the team can identify missing stock. If the supplier provides documentation, retain it with purchasing and compliance records.
- Issue a seal to a job. Before use, connect its number to a shipment, container, trailer, or other defined asset. Record the employee or role taking custody and the time of issue. Do not assign one number to two active loads.
- Apply and verify. The authorized person applies the seal using the applicable work instruction, checks that it is engaged, and records the number exactly as shown. A second-person check can be useful where the operation's risk or procedure calls for one.
- Record every custody handoff. At each planned checkpoint, capture who checked the seal, when and where the check occurred, the observed number, and whether the seal appeared intact. Record a handoff when responsibility changes, not only when a vehicle arrives at its final destination.
- Close the record. At authorized opening or unloading, record the final check, removal or cut status, the person performing the action, and the disposition of the used seal. Reconcile the seal number against the shipment record and close the entry.
Keep the steps proportional to the operation. A small team might use a controlled form with a supervisor reviewing completed records. A larger network may use an approved system that captures the same details at each site. In either case, name the authoritative record and establish what staff should do when an electronic tool is unavailable.
Before rollout, walk through the procedure with the people who will use it. Ask a dispatcher, loader, driver, and receiving clerk to describe their part without prompting. If two roles think the other person records a handoff, the process has a gap. Run a short tabletop example: a seal is issued, applied, checked at an intermediate stop, and removed at destination. Identify who creates each entry and where the next person finds the expected number. Update the written steps where the example exposes unclear ownership.
Which information belongs in the tracking record?
Build the record around the questions a reviewer or receiving employee needs to answer. Avoid collecting fields that nobody uses, but do not leave gaps that make a number impossible to connect to a movement or action. A consistent record can be paper-based or digital; consistency and legibility matter more than the format.
| Record point | Information to capture | Why it helps |
|---|---|---|
| Inventory receipt | Seal type, serial number or range, quantity, date received, receiver, and any accompanying documentation | Establishes what entered controlled stock and who accepted it. |
| Issue and assignment | Seal number, shipment or asset reference, issue time, issuing person, and person taking custody | Connects one physical seal to one active movement or asset. |
| Application | Applied number, date and time, location, employee, and any required verification | Creates the starting point for later comparisons. |
| Inspection or handoff | Observed number, date and time, checkpoint or location, inspector, condition, and match result | Documents custody checks and identifies when a discrepancy was observed. |
| Exception | Expected and observed numbers, condition, discovery time and location, notification, and action taken | Preserves the facts needed to investigate and escalate a mismatch or damaged seal. |
| Removal and closure | Final number, removal time and location, responsible person, disposition, and record reviewer if required | Reconciles the seal and closes the shipment's tracking entry. |
For a digital system, consider whether the record keeps an edit history and identifies the user making a change. For a paper process, make corrections traceable: follow the organization's document-control rules rather than obscuring an original entry. Limit access to people with a business need, and retain records according to the applicable customer, company, and regulatory requirements. Do not assume that one retention period fits every shipment.
Set conventions for common data-entry details before different sites begin using the same log. Decide whether dates use a single format, how time zones are recorded on cross-border routes, whether a location means a facility name, gate, or checkpoint, and how identifiers with leading zeros are preserved. For example, if one record stores 004817 as 4817, a later comparison may appear to show a mismatch even when staff read the same physical seal. Test the form or software with actual identifier formats and confirm that searches return the full value.
It also helps to distinguish the seal's lifecycle status from the shipment's status. A seal can be in controlled stock, issued, applied, inspected, replaced, removed, or reconciled. A shipment may meanwhile be loaded, in transit, delayed, or delivered. Keeping these concepts separate lets a supervisor find unclosed seals without misreading the freight status. If a shipment is canceled before application, record that the assigned seal was returned to controlled stock or otherwise handled under policy; do not leave it looking active.
Where serialization options matter, specify the required identifier format and how the numbers will be supplied or applied. STiER offers serialized seal options and customization; buyers can describe expected volume and operational needs when requesting information through its security seal collection or its containers and shipping seals selection. Verify the details for the exact product and order instead of assuming every seal has the same marking or configuration.
How can teams choose a tracking method that fits the route?
Choose the method by asking how often staff will record a check, how many handoffs occur, what connectivity is available, and who must review the history. A simple method can work when the process is controlled and records are easy to retrieve. More complex routes may need a structured digital workflow. The comparison below is a planning aid, not a substitute for customer or program specifications.
| Method | Useful when | Controls to include | Watch for |
|---|---|---|---|
| Paper log or shipment form | Few handoffs, stable procedures, and records managed at a known site | Required fields, legible entries, controlled forms, review, and a filing process | Delayed entries, lost forms, difficult searches, and unclear corrections. |
| Spreadsheet or shared register | A team needs a searchable list and has a defined owner for access and updates | Unique shipment references, access permissions, backups, change controls, and reconciliation | Conflicting copies, accidental edits, duplicate numbers, and weak ownership. |
| Approved operational system | Multiple locations or teams need to record events in a common workflow | User identity, timestamps, required fields, exception flags, availability plan, and report access | Incomplete training, poor connectivity, or a system that does not match actual work. |
Whichever approach you use, define when a record must be entered. If the team records a handoff only after a route is complete, it may be difficult to establish who had custody when a mismatch first appeared. A prompt entry, even when a device is offline, should follow a controlled fallback and later reconciliation process.
For example, a two-stop delivery with a small team might use a numbered paper form carried with the dispatch packet. The driver records the departure check and the receiving employee records arrival, then the supervisor files the form against the shipment reference. A multi-terminal network might need users at each facility to enter inspections into a shared approved system. It can flag a missing checkpoint or an identifier used twice. Neither tool fixes a vague procedure: the team still needs an agreed event that triggers the entry, a responsible role, and a method to resolve incomplete records.
Test the chosen method under ordinary operating conditions, including a late arrival, a shift change, and a period without network access. Check how long it takes to enter an event, whether a worker can find the expected seal number quickly, and whether the process works on the equipment staff actually carry. If users create side lists because the official tool is slow or unavailable, determine why before those unofficial records become the practical source of truth.
How should staff inspect and reconcile a seal number?
At each designated check, compare the number physically visible on the seal with the expected number in the shipment record or authorized handoff information. Read the number carefully, including leading zeros or letters if the format includes them. Confirm the seal is attached where expected and look for visible damage or signs that the closure may have been disturbed. Record what was observed; do not mark a check as successful simply because a seal is present.
Use a consistent inspection sequence: confirm the shipment identity, locate the seal, read and compare the identifier, check condition, record the result, and communicate any exception through the established channel. If the seal cannot be read, do not guess at the missing characters. Follow the exception procedure and capture a clear description or image if your organization permits it and the record system supports it.
In a busy receiving bay, the order of checks matters. First verify the trailer or container reference against the delivery paperwork so a correct seal number is not accidentally entered on the wrong load. Then compare the expected number with the physical identifier, inspect the attachment and visible condition, and record the finding before the seal is removed. If two employees share the task, agree who reads and who records; have the recorder repeat the digits aloud so the reader can confirm them. This simple read-back can catch transposed digits without adding a complicated tool.
Depending on the asset and operating procedure, the relevant product may differ. Teams can review available bolt seals, cable seals, or plastic seals as starting points, then verify product specifications against their use case. A seal selection does not remove the need to identify the correct attachment point and document how staff will inspect it.
What should happen when a number does not match?
A mismatch, missing seal, unreadable identifier, or damaged seal is an exception. Staff should not quietly substitute another number or overwrite the expected value. The procedure should protect people and cargo first, then preserve the available facts and notify the designated supervisor, security contact, or compliance lead.
- Pause the routine handoff and follow the site's safety and escalation instructions.
- Record the shipment or asset reference, expected number, observed number or condition, time, location, and people present.
- Notify the authorized contact promptly and document when and how the notification was made.
- Follow the responsible organization's instructions on inspection, containment, replacement, and continued movement.
- If a replacement seal is authorized, record the old and new numbers, who approved the change, who applied the replacement, and the time and location.
- Review the event after immediate actions are complete and determine whether the record, training, inventory control, or handoff process needs correction.
Do not treat a replacement as a routine edit. Keeping both the original and replacement identifiers in the record helps explain what happened and preserves a sequence that can be reviewed. If a customer program or applicable requirement prescribes a specific response, follow that procedure.
Close the exception only when the required facts and approvals are captured. A useful review asks whether the mismatch arose from a reading or transcription error, a label or record assignment problem, a missed handoff, or a physical seal condition requiring further attention. Avoid assigning a cause before the responsible review is complete. Preserve supporting documents under the organization's rules, and make sure the shipment record points to the exception record so a later reviewer can follow the chain without searching through unrelated files.
Request help specifying serialized seals for your operation
How can procurement make serialized seals easier to track?
Procurement can reduce avoidable recordkeeping friction by giving the supplier a clear specification. Include the intended application, seal type under consideration, annual or order volume, required serial format, any marking or customization needs, and relevant compliance documentation requirements. Avoid sending sensitive shipment data when a general requirement is enough.
Ask how numbering is controlled, what information accompanies an order, whether the requested serialization or customization is available for the selected product, and how lead times and repeat orders will be handled. Confirm the exact product and its documentation rather than assuming one certification or feature applies to an entire category. For cargo applications, compare the relevant truck and trailer seals or 3PL and supply-chain security options with the operating procedure and applicable program.
When a high-security seal is specified, verify the documentation that applies to the particular product and use. STiER identifies ISO 17712:2013 high-security seal certification among its company credentials, but product-specific claims should be checked against the official product source. A quote request can state the shipment context, required volume, serialization needs, and documentation questions in one place.
Before placing an order, have operations and procurement review the same specification. Procurement can confirm the ordered identifier pattern and quantities; operations can check that the marking can be read at typical inspection distance and that the selected seal fits the application. Agree how unused, damaged, or canceled-order stock will be recorded. When repeat orders arrive, confirm the supplied numbering does not overlap with active or retained records unless the numbering scheme and controls explicitly handle that condition. This advance check prevents purchasing details from being separated from the tracking workflow that will use them.
What questions do teams ask about tracking serialized security seals?
Talk with STiER about serialized seal options
Does a serial number track a shipment's location?
No. A seal number identifies a particular seal in a tracking record. It does not provide live location data. Location information comes from the shipment's operational tracking process, while seal records document assignment, inspection, custody events, exceptions, and closure.
Can the same seal number be assigned to another shipment?
A team should not assign one number to two active shipments. After use, follow the organization's process for reconciling and disposing of the used seal and controlling records. Do not reuse a number unless the seal and numbering policy explicitly allows it and the record clearly prevents confusion.
What if a handoff record was missed?
Do not invent a time or observation. Follow the correction process, identify the missed entry, record when the gap was discovered, and notify the responsible reviewer if required. Record only what can be verified and preserve an audit trail of any correction.
Should every seal check include a photograph?
Not necessarily. A photo may help in a procedure that authorizes image capture, but it does not replace recording the identifier and check result. Set rules for image storage, access, privacy, and retention before making photos a routine requirement.
How can your team put a consistent process in place?
Map the seal's full lifecycle, assign responsibility at every handoff, standardize the required record fields, and test the exception process before relying on it in live operations. Then review completed records and refine steps that staff cannot follow consistently.
Contact STiER to discuss your serialized seal requirements
A well-run tracking process makes each seal number useful by connecting it to a clear, timely, and reviewable record from issue through final reconciliation.