The manual documentation process on COSCO
COSCO shipments generate four document types beyond SI and BL — VGM, DG, advance manifest, and arrival notice — that ops teams must produce and submit on carrier-specific deadlines.
- 01
Calculate VGM
Determine verified gross mass using SOLAS Method 1 (weigh the packed container) or Method 2 (sum of cargo, packaging, dunnage, and tare). The declaration must include numerical weight, unit of measure, and declaring party details.
- 02
Submit VGM through preferred channel
Four channels: VERMAS EDI (standard SMDG VERMAS message, preferred for integrated TMS flows); E-SI forms through SynCon Hub or COP (alongside or before SI submission); INTTRA eVGM (via COSCO's established INTTRA integration); fax (legacy but still accepted). VGM must be submitted before the terminal VGM cut-off.
Pain pointVGM cut-offs are per-terminal and per-service, not global. Missing the cut-off triggers 'No VGM, No Gate-in' and the container is not loaded. COSCO does not publish a global VGM cut-off standard. A VGM submission fee or late-VGM fee by origin port is not confirmed in COSCO's published tariffs.
- 03
Flag DG at booking stage
Populate the DG flag during booking on SynCon Hub or the local booking channel. Enter IMO class, UN number, and per-container DG details. Whether SynCon Hub exposes a dedicated DG checkbox in the booking form or requires a separate submission is not confirmed in public sources.
- 04
Submit DG declaration under IMDG Amendment 42-24
Submit the DG declaration with UN number, IMDG class, packing group, and proper shipping name per the applicable IMDG Code amendment. Amendment 42-24 is mandatory from 1 January 2026. Key changes: carbon products fully regulated (no exemptions), sodium ion batteries added as Class 9, lithium battery test documentation required upstream. Misdeclaration triggers a COSCO-specific USD 20,000 'special handling cost' payable within 2 working days. This is a carrier-imposed charge, distinct from any regulatory fines from flag-state or port-state authorities.
Pain pointCOSCO does not publish a global DG approval SLA. The carrier's DG review turnaround at individual origin ports (24 hours / 48 hours / longer) and any restricted-commodities list beyond standard IMDG classifications are not confirmed in public sources. Initiate DG classification at booking stage, not documentation stage, to avoid late-stage approval surprises.
- 05
Prepare advance manifest data
For US-bound: AMS 24-hour rule. Manifest data filed 24 hours before cargo is loaded at the foreign port. ISF ('10+2') is filed by the importer on the same timeline. CBP's ACE system auto-rejects vague descriptions ('FAK', 'general cargo', 'parts', 'samples') since 27 September 2025. For Canada-bound: ACI filing window of 24–96 hours before arrival or loading (timeline depends on shipment type and voyage duration). For EU-bound: ICS2 F10/F12/F13 filing types with 'No MRN / No Load' enforcement. F12/F13 filings require supplementary declarant EORI numbers when buyer and seller details are omitted.
- 06
Handle ICS2 'No MRN / No Load'
Without a valid Movement Reference Number from EU Customs, COSCO will not load the cargo. Whether COSCO charges a carrier-side ENS surcharge (equivalent to ONE's USD 35/BL ESD) or a Manifest Submission Fee on house BLs (equivalent to Maersk's USD 50/house BL) is not confirmed in public sources.
- 07
Monitor arrival notice generation
COSCO issues two arrival notices for US-bound cargo: first arrival notice 5–7 days pre-arrival without IT number; second arrival notice 2 days pre-arrival with IT number. Delivery method (email, portal notification, EDI) and consistency across destination ports are not confirmed in public sources.
- 08
Generate pre-alert to consignee
Parse the arrival notice for vessel/voyage, ETA, container numbers, and outstanding charges. Generate a branded pre-alert for the consignee and initiate customs clearance preparation well ahead of the vessel arrival.
Where COSCO documentation errors happen
Common COSCO documentation rework and cost triggers, drawn from documented carrier workflows and known data gaps.
Missed VGM cut-off
CommonPer-terminal deadline passed; container denied loading under 'No VGM, No Gate-in'. Remediation: monitor per-terminal VGM cut-off from the booking confirmation and submit well before the window closes.
VGM / SI weight mismatch
CommonVGM declaration does not reconcile with the SI gross weight. Mismatch triggers rejection and a 'No VGM, No Gate-in' hold at terminal. Remediation: cross-check VGM against SI gross weight before submission.
DG approval delay
OccasionalNo published global SLA. Booking is at risk if DG classification review is not initiated early. Remediation: initiate DG classification at booking stage, not documentation stage. Escalate to the local COSCO office if the approval timeline threatens the loading window.
DG misdeclaration triggers USD 20,000 penalty
OccasionalIncorrect UN number, IMDG class, or proper shipping name discovered post-booking. COSCO invoices the USD 20,000 special handling cost, payable within 2 working days. This is in addition to any regulatory fines from flag-state or port-state authorities. Remediation: validate the DG declaration against IMDG Amendment 42-24 requirements before submission. For carbon products, sodium ion batteries, and lithium batteries, apply the amendment's upstream documentation requirements.
ICS2 incomplete filing
CommonMissing or generic cargo description, truncated HS code, or missing EORI numbers on EU-bound cargo. ENS rejected; 'No MRN / No Load' enforcement denies loading. Remediation: complete all ICS2 fields in the SI before submission; use F12/F13 self-filing where the forwarder files house-level data.
US CBP auto-rejection on vague descriptions
Common'FAK', 'general cargo', 'parts', or 'samples' on a US-bound manifest. CBP's ACE system auto-rejects these since 27 September 2025. Remediation: populate specific, HS-code-aligned cargo descriptions for every US-bound SI.
ACI late filing penalty
OccasionalCanada-bound ACI filed after the 24–96 hour window. CAD 750 late-filing penalty; CAD 8,000 for non-submission. Remediation: monitor the ACI window by shipment type and voyage duration; file at the earliest applicable cut-off.
Legacy container VGM mismatch
OccasionalVGM submitted for a CCLU, CSLU, CBHU, COCU, or CICU-prefixed container with the wrong carrier reference. VGM not matched to the COSCO booking in TMS reconciliation. Remediation: map all legacy-merger and leased-equipment container prefixes to COSU for VGM submission and matching.
How Expedion agents handle COSCO documentation
Expedion agents automate the end-to-end COSCO documentation workflow across VGM, DG, advance manifest, and arrival notice, routing through digital channels and validating data against regulatory and carrier-specific requirements.
Submit through VERMAS EDI, SynCon Hub or COP E-SI forms, or INTTRA eVGM. Reserve fax for genuine last-resort scenarios. Pull verified gross mass from the weighbridge certificate or shipper declaration and include the declaring party details.
Track per-terminal VGM deadlines from the booking confirmation. Surface missed-cut-off risk before the window closes so the ops team can escalate rather than discover a 'No VGM, No Gate-in' hold at terminal.
Automated cross-check between the declared VGM and SI gross weight to catch discrepancies before they trigger 'No VGM, No Gate-in' holds. Mismatches are surfaced to the reviewer with source-of-truth data pre-populated.
Pre-validate the DG declaration against IMDG Amendment 42-24 requirements: carbon products (no exemptions), sodium ion batteries (Class 9), lithium battery upstream test documentation. Flag the booking as DG and track approval status through the local COSCO office. Surface the USD 20,000 misdeclaration penalty at validation stage, not post-invoice.
Given the absence of a published global approval SLA, monitor DG turnaround per origin port and escalate if the approval timeline threatens the booking's loading window.
Handle AMS (US, COSU SCAC, 24-hour rule, CBP auto-rejection after 27 September 2025), ACI (Canada, 24–96 hour window, CAD 750 / CAD 8,000 penalties), and ICS2 (EU, F10/F12/F13 filing types, 'No MRN / No Load') filing requirements per booking destination.
Enforce six-digit HS code, accurate cargo description, and complete EORI and party-address data for EU-bound cargo. Monitor MRN generation post-filing. Flag 'No MRN / No Load' blocks before they cascade into missed loadings.
Monitor for first (5–7 day, no IT number) and second (2-day, with IT number) arrival notice generation on US-bound bookings. Reconcile against tracking vessel-arrival milestones. Issue consignee pre-alerts on the earlier event.
Map CCLU, CSLU, CBHU, COCU, and CICU container references to COSU for VGM submission, DG declaration, and manifest filing so downstream reconciliation does not break on BIC-to-SCAC auto-mapping.
COSCO documentation reference: fees and deadlines
Published fees and deadlines drawn from COSCO advisories and regulatory sources. Where a cell reads 'Not confirmed', the data point is not available in public sources.
| Item | Value | Geography | Source |
|---|---|---|---|
| VGM submission channels | SynCon Hub, EDI (VERMAS), INTTRA eVGM, fax | Global | COSCO VGM Q&A, SMDG VERMAS standard, INTTRA |
| VGM Manual Submission Fee | Not confirmed in published tariffs | Global | Not confirmed |
| VGM cut-off | Per-terminal, per-service; missed cut-off = container not loaded | Global | COSCO service schedules |
| DG submission | DG flag in booking + DG declaration with UN number, IMDG class, packing group, proper shipping name | Global | COSCO DG advisory |
| DG approval SLA | Not published | Global | Not confirmed |
| DG misdeclaration penalty | USD 20,000 (payable within 2 working days) | Global | COSCO DG safety advisory |
| IMDG enforcement | Amendment 42-24 from 1 January 2026 | Global | IMO / Hazcheck / West P&I |
| ICS2 filing types | F10 / F12 / F13 | EU | COSCO ICS2 implementation |
| ICS2 enforcement | No MRN / No Load | EU + Norway + Switzerland + NI | COSCO ICS2 implementation |
| ICS2 carrier-side ENS surcharge | Not confirmed in published tariffs | EU | Not confirmed; contrast with ONE USD 35/BL ESD |
| AMS deadline (US) | 24 hours before loading at foreign port | USA | CBP |
| CBP auto-rejection | From 27 September 2025; vague descriptions rejected | USA | CBP trade information notice |
| ACI deadline (Canada) | 24–96 hours before arrival (varies by shipment type) | Canada | CBSA |
| ACI penalties | CAD 750 late filing; CAD 8,000 non-submission | Canada | CBSA |
| Arrival notice (US-bound, first) | 5–7 days pre-arrival (no IT number) | US destinations | COSCO arrival notice process |
| Arrival notice (US-bound, second) | 2 days pre-arrival (with IT number) | US destinations | COSCO arrival notice process |
| eBL platform | GSBN (primary); IQAX interoperability; DCSA eBL v3.0 live since 11 June 2025 | Global | GSBN; see BL page for detail |
TMS compatibility for COSCO documentation
Expedion agents operate COSCO documentation workflows from within your existing TMS. For CargoWise users, agents exchange data via the eAdaptor API and route VGM, DG, and manifest submissions through EDI (including VERMAS) via INTTRA. For Magaya, agents use Magaya Connect with API calls into COSCO channels. For GoFreight, agents drive the COSCO portals through direct REST integration. For Logi-Sys, agents operate over EDI via INTTRA. Teams that have built against COP's open API get a native integration through that channel.
Full TMS compatibility details are on the COSCO overview page.
Related pages
COSCO carrier pages: Overview · Booking · Shipping instructions · Bill of lading · Tracking & visibility
Documentation across carriers: Maersk documentation · MSC documentation · CMA CGM documentation · Hapag-Lloyd documentation · ONE documentation · Evergreen documentation
Ocean Alliance context: OOCL — COSCO subsidiary with separate IT systems, SCAC (OOLU), and customer portal (MyOOCL).
Solutions: Documentation automation
Glossary: VGM · Dangerous Goods · ICS2
Frequently asked questions
What VGM submission channels does COSCO support?
Four channels: VERMAS EDI (standard SMDG VERMAS message, preferred for integrated TMS flows); E-SI forms through SynCon Hub or the COP portal (alongside or before SI submission); INTTRA eVGM via COSCO's established INTTRA integration; and fax (legacy, still accepted). VGM must be submitted before the terminal VGM cut-off, which is per-terminal and per-service, not global. Missing the cut-off triggers a 'No VGM, No Gate-in' hold and the container is not loaded.
Does COSCO charge a VGM submission fee or late VGM fee?
Not confirmed in public sources. COSCO's published tariffs do not contain a consolidated VGM submission fee or late-VGM fee schedule equivalent to the UK late-VGM charges documented for other carriers (for example, ONE's GBP 130/container late-VGM fee). Whether origin-port-specific VGM fees exist but are surfaced only on invoice is not confirmed in public sources. Expedion agents submit through digital channels (VERMAS EDI, SynCon Hub, INTTRA eVGM) to avoid any potential manual-processing surcharge and monitor per-terminal cut-offs to avoid late-submission exposure.
What is COSCO's DG misdeclaration penalty, and when is it payable?
COSCO's DG misdeclaration penalty is USD 20,000, invoiced as a 'special handling cost' and payable within 2 working days of invoice. This is a COSCO-specific carrier-imposed charge, distinct from any regulatory fines levied by flag-state or port-state authorities. The penalty applies to incorrect UN number, IMDG class, packing group, or proper shipping name discovered post-booking. Expedion agents pre-validate the DG declaration against IMDG Amendment 42-24 requirements before submission and surface the USD 20,000 exposure at validation stage rather than post-invoice.
What changes under IMDG Amendment 42-24 affect COSCO cargo?
IMDG Amendment 42-24 is mandatory from 1 January 2026 for COSCO cargo, following the IMO mandatory date. Three changes have the largest operational impact: carbon products are now fully regulated with no exemptions; sodium ion batteries are added as Class 9 dangerous goods; and lithium battery test documentation is required upstream at origin, not just at booking. Forwarders handling lithium batteries (UN 3480, UN 3481), sodium ion batteries, or carbon products should update their DG declaration templates, shipper collection checklists, and TMS classification rules before the 1 January 2026 enforcement date to avoid USD 20,000 misdeclaration exposure.
How does COSCO handle ICS2 advance manifest data?
COSCO's ICS2 implementation follows the industry-wide go-live. Three filing types apply: F10 (complete straight BL with buyer/seller data), F12 (incomplete master BL, carrier only, no house data), and F13 (incomplete straight BL). F12 and F13 filings require supplementary declarant EORI numbers when buyer and seller details are omitted. 'No MRN / No Load' enforcement applies: containers without a valid Movement Reference Number from EU Customs are denied loading. Whether COSCO's ENS deadline varies by service (beyond the standard 24 hours prior to loading) is not confirmed in public sources.
Does COSCO charge a carrier-side ENS surcharge like ONE's USD 35/BL ESD?
Neither a standardised COSCO carrier-side ENS surcharge equivalent to ONE's USD 35/BL Entry Summary Declaration Surcharge nor a Manifest Submission Fee on house BLs (equivalent to Maersk's USD 50/house BL) is confirmed in public sources. For EU-bound cargo, the operational focus is on complete ICS2 data (six-digit HS code, accurate cargo description, EORI numbers, complete party addresses) to avoid 'No MRN / No Load' blocks rather than a predictable per-BL surcharge.
What is COSCO's arrival notice timeline for US-bound cargo?
COSCO issues two arrival notices for US-bound cargo: the first arrival notice is published 5–7 days pre-arrival without an IT number; the second arrival notice is published 2 days pre-arrival with the IT number. The delivery method (email, portal notification, or EDI) and consistency across destination ports are not confirmed in public sources; no uniform delivery mechanism is confirmed. Expedion agents monitor for both notice events, reconcile against vessel-arrival tracking milestones, and issue consignee pre-alerts on the earlier signal.