How to Correct an Incorrect Container or Seal Number on Shipping Documents
A single incorrect character in a container or seal number can create a mismatch across the bill of lading, cargo manifest, customs declaration and terminal system. The issue is rarely solved by merely editing a file: cargo may be stopped at gate-in or gate-out, a B/L or manifest amendment may be required, customs data may need to be amended, and documentation charges or delivery delays may arise. The correct approach is to establish the physical source of truth, distinguish a clerical error from an actual container swap or seal replacement, and then correct every affected record in the proper sequence and at the correct shipment stage.
QUICK FACTS
Check physical photos, EIR/gate records, booking, Shipping Instructions, B/L, manifest and customs data to establish the correct number.
If the actual seal differs from the documents, treat it as a supply-chain security event until a valid seal replacement record is available.
The carrier/forwarder corrects the B/L and manifest; the customs declarant amends the declaration; the depot or terminal corrects its EIR or gate data.
If the container number in the customs declaration is inaccurate when cargo passes the customs supervision area, use the dedicated procedure. For exports, submit Form 31/BKCT/GSQL with carrier confirmation and complete the supplementary declaration within five working days.
Within a controlled area, follow instructions from Customs, the terminal/depot or carrier and retain a complete audit trail.
Customs consequences, if any, depend on the timing, nature and actual impact of the error.
SCOPE
This article applies to FCL export and import shipments by sea where container and seal data are exchanged among the cargo owner, forwarder, ocean carrier, terminal/depot and Customs. It covers errors appearing on Shipping Instructions, draft or final Bills of Lading, manifests, Arrival Notices, Delivery Orders, EIR/gate records and customs declarations.
It does not replace special procedures for customs seals, quarantine seals, dangerous goods, investigations, theft or suspected unauthorized interference. Such cases require direct coordination with the competent authority and, where relevant, insurers and surveyors.
KEY TERMS
| Term | Meaning | Role in correction |
|---|---|---|
| Container Number | The unique equipment identification, generally comprising the owner code, equipment identifier, serial number and check digit. | Links the physical unit to the booking, B/L, manifest, customs and terminal records. |
| Seal Number | The number on the seal affixed to the container door after stuffing or after an authorized inspection/resealing event. | Supports cargo integrity and chain of custody; a mismatch may be clerical or may indicate that the seal was replaced. |
| Shipping Instruction – SI | Data submitted by the shipper/forwarder for preparation of the transport document. | Often feeds the draft B/L and manifest; it should be corrected before the documentation cutoff whenever possible. |
| Bill of Lading – B/L | A transport document issued by the carrier or NVOCC. | Only the issuer should amend it; a locally edited PDF is not an official amendment. |
| Cargo Manifest | Cargo data filed by the carrier or its agent with Customs. | If the B/L data have already been manifested, a B/L correction may also require a manifest amendment. |
| EIR / Gate Record | Equipment interchange receipt or system record of the container passing a depot or terminal gate. | Important operational evidence of the actual container and the time of handover. |
| Customs Amendment | Correction or supplementation of customs declaration data together with supporting documents. | Handled according to the clearance stage and the functions supported by the customs system. |
HOW THE ERROR PROPAGATES
1. One wrong entry can spread across several systems
Container and seal details are commonly entered during stuffing or SI submission and then reused for the draft B/L, final B/L, manifest, customs declaration, Arrival Notice, Delivery Order and terminal records. Correcting only one document therefore does not prove that the shipment data have been fully corrected. Identify both the issuing party and every downstream system that received the data.
2. Classify the root cause
- Typing error: the physical container and seal never changed, but one or more records contain an incorrect character.
- Legitimate operational change: a damaged container was swapped, an empty unit was replaced at the depot, or a seal was replaced following inspection, security control or terminal handling. Evidence must show the old and new numbers and the reason.
- Unexplained irregularity: the seal is missing, broken or different, or the physical container does not match the records and no valid report exists. Do not treat this as a routine documentation typo.
3. Confirm the physical source of truth
Use clear photos of the container identification and seal, EIR/gate records, stuffing records, inspection or resealing reports, booking data and terminal/carrier confirmation. Only after the correct number is established should amendment requests be sent.
DECISION TABLE BY SCENARIO
| Scenario | Primary owner | Required action | Supporting evidence | Delay risk |
|---|---|---|---|---|
| Error in SI or draft B/L before cutoff | Shipper/forwarder and carrier | Resubmit the SI or request an online amendment; review the revised draft. | Container/seal photos, stuffing record, booking. | The error may flow into the manifest. |
| Error in final B/L before manifest lock | B/L issuer | Request B/L amendment and confirm whether a manifest amendment is also required. | Before/after instruction, reason and proof of the correct number. | Amendment charges or document release delay. |
| Error after manifest filing or vessel departure | Carrier/NVOCC/manifesting agent | Request B/L and manifest amendment under carrier and destination procedures; monitor approvals and fees. | Formal request, B/L, SI, EIR and photos. | Destination mismatch, delayed D/O or gate-out. |
| Error found before customs declaration registration | Customs declarant | Correct the declaration software and recheck against the B/L, manifest and EIR before final transmission. | Finalized document set. | A formal customs amendment will otherwise be required. |
| Error found after registration but before clearance | Customs declarant and Customs | Amend under the current Article 20 procedure. For a paper declaration or a field not supported by the System, submit two originals of Form 03/KBS/GSQL with supporting documents. | Corrected B/L/manifest, EIR, carrier confirmation and photos. | Processing delay and possible administrative handling depending on timing and nature. |
| The container number in the customs declaration is inaccurate when cargo passes the customs supervision area | Customs declarant and supervising Customs officer at the border gate | Imports: present the import cargo delivery/receipt document. Exports: submit the Export Container Number List, Form 31/BKCT/GSQL, with a carrier-issued document confirming the container-number change. Customs verifies and updates the correct number in the System; the declarant then files a supplementary declaration at the office of registration within five working days after the cargo passes the supervision area. | Delivery/receipt document or EIR; Form 31 for exports; carrier confirmation of the container-number change; B/L and related records. | Gate hold, delivery delay or missing the five-working-day amendment deadline. This specific procedure concerns container-number discrepancies, not an unexplained seal-number mismatch. |
| Error found after clearance | Customs declarant | Submit a post-clearance amendment based on the 60-day rule and the post-clearance audit status; retain the complete audit trail. | Before/after records, reason and proof. | Post-clearance review and possible administrative consequences. |
| Seal replaced after inspection | Authority or operator conducting the opening/resealing | Record old and new seal numbers, reason, time, place and witnesses; update affected systems. | Inspection/resealing report and before/after photos. | Shortage dispute or integrity concern. |
| Unexplained broken, missing or different seal | Customs/terminal/depot/carrier and insurer where relevant | Stop delivery, preserve the condition, make an incident report and arrange inspection or tally as instructed. | Photos, CCTV/gate records, EIR and site report. | Security, cargo claim and custody liability. |
DOCUMENTS AND DATA TO CHECK
| Document/data | Issuer or preparer | Use | Fields to match |
|---|---|---|---|
| Physical container and seal photos | Stuffing location, driver, terminal or consignee | Establish the source of truth | Container no., seal no., time and location |
| EIR/gate record | Depot/terminal | Evidence of equipment handover or gate movement | Container no., condition, timestamp, location |
| Booking confirmation | Carrier/forwarder | Shipment and equipment reference | Booking no., vessel/voyage, container type |
| SI and draft B/L | Shipper/forwarder; carrier prepares draft | Pre-issuance correction | Container no., seal no., packages, gross weight |
| Final B/L and manifest confirmation | Carrier/NVOCC/agent | Transport document and manifest correction | B/L no., container/seal, vessel/voyage and ports |
| Customs declaration, cargo delivery/receipt document and container list | Customs declarant; carrier/terminal for supporting records | Supplementary declaration, customs-supervision-area handling or explanation | Container no., B/L, date cargo passed the supervision area; Form 31/BKCT/GSQL and carrier confirmation for exports where applicable |
| Container swap or resealing report | Depot, terminal, carrier or inspection authority | Proof of a legitimate physical change | Old/new numbers, reason, time and confirmation |
| Email/amendment request | Cargo owner/forwarder | Create an audit trail | Before/after data, cause, requester and timestamp |
RECOMMENDED WORKFLOW
Do not transmit the declaration, approve the draft, issue the document or dispatch the truck for gate-out until the correct number is confirmed.
Check photographs, EIR, gate records, stuffing records and inspection reports. Preserve the condition if the seal is irregular.
List each affected document, old data, correct data, reason, evidence and the person approving the correction.
The carrier/NVOCC corrects the B/L and manifest; the depot/terminal corrects EIR or gate data; the customs declarant submits the customs amendment. Never substitute a self-edited file for an official reissue.
Before channeling results, after channeling but before clearance, and after clearance are distinct stages. Check whether the System supports the field. For a paper declaration or an unsupported field, prepare two originals of Form 03/KBS/GSQL and supporting evidence under the current rules.
Dedicated customs-supervision-area procedure: Where an inaccurate container number is discovered in the customs declaration at the customs supervision area: for imports, present the cargo delivery/receipt document; for exports, submit Form 31/BKCT/GSQL together with the carrier-issued confirmation of the container-number change. After the supervising Customs officer verifies and updates the correct number in the System, file the supplementary declaration at the customs office of registration within five working days after the cargo passes the supervision area. Do not use this route to regularize an unexplained seal mismatch.
Compare at least the B/L, manifest, customs declaration, Arrival Notice/D/O and terminal data. For a replacement seal, confirm that the old/new seal record is retained and distributed.
Retain emails, revised documents, reports, photographs, amendment charges and completion timestamps for claims, audit and root-cause review.
COMMON RISKS AND ERRORS
| Error | Cause | Impact | Control |
|---|---|---|---|
| Amending the B/L without checking manifest status | Assuming automatic synchronization | Destination Customs or terminal still receives old data | Obtain written confirmation that both B/L and manifest data are updated. |
| Editing the B/L or EIR PDF locally | Attempt to save time | Unofficial document and fraud-control risk | Use only a document reissued by the authorized issuer. |
| Opening cargo despite a seal mismatch | Treating it as a simple typo | Loss of integrity evidence and difficult cargo claim | Preserve the condition and make an incident report. |
| Failing to record the old seal when resealing | Incomplete report | Broken chain of custody | Record old/new seal, reason, time, place and confirmation. |
| Customs amendment without source evidence | Only stating “typing error” | Insufficient basis for acceptance | Provide corrected B/L/manifest, EIR, photos and carrier/depot confirmation. |
| Waiting until D/O or gate-out | No pre-alert/document audit | Charges, storage and delivery delay | Check container/seal at stuffing, draft B/L, pre-alert and pre-declaration stages. |
| Using Form 03/KBS/GSQL instead of the dedicated customs-supervision-area file | Failing to distinguish the general amendment route from the special procedure for a container-number discrepancy at the gate | Rework, gate delay or missing the five-working-day supplementary-declaration deadline | For exports, use Form 31/BKCT/GSQL with carrier confirmation; for imports, present the cargo delivery/receipt document; then amend within the required period. |
LEGAL BASIS AND OFFICIAL SOURCES
The sources below support the duty to declare accurately, the amendment framework and the operational need to keep seal data consistent. For a specific shipment, always check the version in force, local Customs instructions, carrier procedures and terminal conditions.
| Source | Status/date | Relevance |
|---|---|---|
| Customs Law No. 54/2014/QH13 and Law No. 90/2025/QH15 | Read as part of the current legal framework | Accurate declaration principle and the statutory framework for amendments. |
| Decree 08/2015/ND-CP and Decree 167/2025/ND-CP | Decree 167/2025 effective 15 August 2025 | Current customs procedure, control and supervision framework. |
| Circular 38/2015/TT-BTC, Circular 39/2018/TT-BTC and Circular 121/2025/TT-BTC | Circular 121/2025 effective 1 February 2026 | Current Article 20 amendment procedure, including unsupported system fields and the specific customs-supervision-area process for an inaccurate container number: Form 31/BKCT/GSQL for exports and a five-working-day supplementary-declaration period. |
| Circular 50/2018/TT-BTC | In force; effective 5 June 2018 (status checked through 20 July 2026) | Data fields and forms for vessel and cargo manifest reporting. |
| Decree 169/2026/ND-CP | Effective 1 July 2026 | Administrative penalties in customs; not every data error is handled identically. |
| Maersk – Container seal numbers; Hapag-Lloyd – Shipping Instructions; ONE – Global Container Security Seal Standards | Operational policies may change | Carrier guidance on accurate seal reporting and amendment channels. |
FAQ
Should a one-character container error on the Invoice or Packing List be corrected?
Yes, where the document contains a container number. Even if it does not control terminal data, inconsistency can create issues during document review, claims or internal audit. The issuer should release a controlled revision.
The B/L seal number is wrong, but the physical seal is intact. What should be done?
Photograph the actual seal, compare the stuffing record and EIR, and request an amendment from the B/L issuer. Confirm whether the manifest has already been filed.
If the carrier swaps the container before sailing, must the customs declaration be amended?
It may need to be updated if the old number appears in the declaration or container list. Obtain the swap confirmation/new EIR, check the declaration status and follow the applicable amendment route.
Which seal number applies after inspection and resealing?
Records created after resealing should use the new seal number, while the file must retain both the old and new numbers and the resealing report. Never erase the old seal from the audit trail.
At the customs supervision gate, should Form 03 or Form 31 be used for a wrong container number?
They are not interchangeable. For an export container-number discrepancy identified when cargo passes the customs supervision area, submit Form 31/BKCT/GSQL with the carrier-issued confirmation of the container-number change. For imports, present the cargo delivery/receipt document. After Customs updates the correct number, file the supplementary declaration at the office of registration within five working days. Form 03/KBS/GSQL belongs to the general amendment route for paper declarations or fields not supported by the System.
Does amendment within 60 days guarantee no penalty?
No. The 60-day period identifies a post-clearance amendment case. Any administrative treatment depends on the circumstances, timing and applicable penalty rules.
Who pays the B/L or manifest amendment charge?
This depends on the carrier tariff, timing, service contract and cause of the error. Obtain a written charge notice; there is no universal fee for all carriers and ports.
IMPLEMENTATION SUPPORT
TGIMEX can review container and seal data across the booking, SI, B/L, manifest, customs declaration and terminal records; prepare a before-and-after matrix; coordinate amendment requests and assemble supporting evidence based on the actual shipment stage. Scope is confirmed only after review of the documents and does not replace a carrier or authority decision.
Tiếng Việt
中文 (中国)
NEED TO REVIEW IMPORT PROCEDURES OR A SHIPPING PLAN?
Send us the product name, shipping route, current dossier, or implementation request in advance so we can suggest a suitable approach that is practical, focused, and aligned with your shipment.
Import procedure for cream-filled wafers: HS code, tax, food safety, C/O and E2E workflow
Gate Valve Export Guide: Markets, HS, Origin, Documents and Process
Industrial Router Export Guide: Markets, HS, Licensing, Origin and E2E Workflow
Exporting Butterfly Valves from Vietnam: Markets, HS 8481, Origin, Pressure Compliance and Transport
Laser Cutting Machine Export Procedure: HS, Dual-Use Screening, Origin and Shipping
Blade server export procedure: markets, HS, origin, dual-use screening and logistics
Exporting Gateways from Vietnam: Markets, HS 8517.62.21, Origin and Compliance
Mini PC export procedure: markets, HS, origin, dual-use, FCC/IMDA/OFCA and logistics
Exporting Industrial PCs from Vietnam: Markets, HS, Origin, Compliance and Transport
SERVER RACK EXPORT GUIDE: MARKETS, HS, ORIGIN, COMPLIANCE AND SHIPPING
Exporting Tower Servers from Vietnam: Markets, HS, Origin and E2E Workflow
Exporting PoE Switches from Vietnam: Markets, HS, Origin, Compliance and Transport
Desktop PC export guide: markets, HS code, origin and shipping
Exporting Edge Servers from Vietnam: Markets, HS, Origin and E2E Workflow
Exporting Load Balancers from Vietnam: Markets, HS, Origin, Compliance and E2E Workflow