The manual SI process on COSCO
SI submission on COSCO runs through SynCon Hub as the primary e-commerce platform, with COP (cop.lines.coscoshipping.com) as the API-enabled alternative for teams that have built against its open API.
- 01
Retrieve booking confirmation
Extract booking number, vessel/voyage, container allocation, port pair, and cut-off dates from SynCon Hub, COP portal, or email confirmation. Confirm the booking party or authorised agent has a valid COSCO customer account before proceeding.
Pain pointSI submission requires a COSCO customer account tied to the booking party. Third-party 3PLs submitting on behalf of the booking party need both the account and the booking reference — attempting to file without a valid account linkage returns a generic authorisation error without naming the missing credential.
- 02
Choose the correct SI channel
SynCon Hub (primary web portal at synconhub.coscoshipping.com). COP portal (cop.lines.coscoshipping.com) for teams using its open API. EDI IFTMIN via INTTRA for high-volume TMS-integrated flows. Port-specific email as fallback (US examples: lalb-si@cosco-usa.com for Los Angeles/Long Beach; masterbill_sdc@coscon.com for other US ports).
Pain pointCOSCO publishes channel coverage per region but does not publish a single canonical list of email addresses for non-US ports, so forwarders often fall back to their local COSCO office contact for email submission outside the US.
- 03
Complete mandatory SI fields
Populate: full shipper, consignee, notify party, and forwarder blocks (company name, street address, city, postal code, country); container and seal numbers; package count and type; gross weight (must reconcile with VGM); cargo description (specific, not generic); six-digit HS code per commodity line; and document type.
Pain pointSubmitting a 10-digit HTS code on EU-bound lanes or using a deleted or renamed WCO code triggers rejection. COSCO's portal-level field validation behaviour is not documented in public sources; whether SynCon Hub returns clear field-level error messages or generic rejections is not confirmed in public sources.
- 04
Populate ICS2 data for EU-bound cargo
For EU-bound shipments, include ICS2-required fields: EORI numbers for shipper and consignee, accurate cargo description (not FAK / general cargo), complete party addresses with postal codes, and six-digit HS code. ICS2 data must be at the house BL level for F12/F13 multi-filings. COSCO's ICS2 implementation follows the October 2024 industry-wide go-live with 'No MRN / No Load' enforcement on incomplete filings.
Pain pointFor F11 filings (Master BL with multiple House BLs), forwarders need to decide whether to let COSCO file house-level data on their behalf or use F12/F13 self-filing to retain control. COSCO does not publish a standardised per-filing fee for carrier-side ENS equivalent to ONE's USD 35/BL ESD surcharge; late-SI or manual-submission processing fees for COSCO were not confirmed in public sources.
- 05
Validate cargo description for US-bound shipments
US CBP 24-hour AMS rule applies. Since 27 September 2025, CBP automatically rejects manifests with 'FAK', 'general cargo', or 'consolidated cargo' descriptions. Include explicit HS-code-aligned descriptions and complete shipper/consignee/notify-party addresses.
Pain pointA description that cleared under pre-September 2025 practice may now trigger CBP auto-rejection. Forwarders reusing older description templates without refresh are the common source of new rejections on US-bound COSCO SIs.
- 06
Reconcile legacy and leased container prefixes
COSCO bookings frequently produce containers with BIC prefixes other than COSU: CCLU, CSLU, CBHU, COCU (legacy from the February 2016 China Shipping merger) and CICU (COSCO Container Industries leased equipment). All of these route under COSU for SI, BL, and customs-filing purposes. Do not attempt to file under a different SCAC based on the container prefix.
Pain pointTMS systems that auto-derive SCAC from BIC prefix lookup will try to file a CCLU- or CICU-prefixed container under a legacy or leasing-company code. This produces a customs filing mismatch and a reconciliation exception that has to be manually corrected downstream.
- 07
Submit and track amendments
Submit through the chosen channel before the documentation cut-off (typically 1-3 days before sailing; some services use a 17:00 eve-of-sailing cut-off). Post-cut-off amendments follow the published regional fee schedule: USD 100/BL (USA, Far East, China, Australia); USD 140/BL (Europe, ENS trades); INR 5,000/BL (India). Other regions (Germany, France, Italy, Spain, Singapore, China domestic) have regional tariffs but require portal login or local office contact.
Pain pointApplying the USA USD 100 rate to a Europe-bound amendment is a common reconciliation error. The Europe/ENS rate is USD 140/BL and the India rate is INR 5,000/BL — regional variance must be priced before submission, not after.
Where COSCO SI errors happen
The most common COSCO SI rejection and rework triggers, drawn from industry-wide SI patterns and COSCO-specific operational characteristics.
HS code format or validity
CommonSix-digit HS code required. Submitting 10-digit HTS codes on EU lanes, using deleted or renamed WCO codes, or omitting HS codes on multi-commodity cargo triggers rejection. Remediation: validate HS codes against current WCO and EU TARIC data before submission; use the six-digit HS root, not 8- or 10-digit destination-specific codes.
Vague cargo description on US-bound SI
Common'FAK', 'general cargo', or 'consolidated cargo' descriptions are auto-rejected by CBP since 27 September 2025. Remediation: populate a specific, HS-code-aligned description for every US-bound SI and validate before submission.
Incomplete party addresses on EU lanes
OccasionalMissing postal code, city, or EORI number on shipper or consignee triggers ICS2 ENS rejection, which cascades to 'No MRN / No Load' at load port. Remediation: verify EORI numbers for both shipper and consignee and populate complete addresses with postal codes before submission.
VGM / gross weight discrepancy
CommonSI gross weight does not reconcile with the VGM declaration. Mismatch triggers rejection and 'No VGM, No Gate-in' holds at terminal. Remediation: cross-check VGM against SI gross weight before submission; surface discrepancies to the reviewer for correction.
Legacy or leased container prefix confusion
CommonForwarders encountering CCLU, CSLU, CBHU, COCU, or CICU containers on COSCO bookings attempt to route documentation under a non-COSU SCAC based on BIC prefix lookup, causing TMS reconciliation errors and potential customs filing mismatches. Remediation: map all legacy-merger and leased-equipment container prefixes to COSU for SI, BL, and customs purposes.
ICS2 'No MRN / No Load' block
OccasionalIncomplete ICS2 filings fail to generate a valid MRN. Container is denied loading at the load port. Remediation: verify MRN generation status post-submission and re-file incomplete data before the load deadline.
Amendment fee surprise by region
OccasionalForwarder submits a post-cut-off amendment on a Europe-bound SI expecting the USA USD 100 rate and gets billed USD 140 (Europe/ENS). Remediation: pre-calculate regional amendment fee from COSCO's published tariff (USD 100 / USD 140 / INR 5,000) and route for forwarder approval before submission.
How Expedion agents handle COSCO SIs
Expedion agents automate the end-to-end COSCO SI workflow from booking data extraction to carrier acceptance, defaulting to digital channels and enforcing field-level validation before submission.
Default to SynCon Hub for all bookings. Fall back to EDI IFTMIN via INTTRA for high-volume forwarders with existing EDIFACT message flows. Use the COP portal for teams that have built against its open API. Route to port-specific email only as manual fallback.
Enforce six-digit HS code minimum, accurate cargo description, and complete EORI and party-address data for EU-bound cargo. Verify MRN generation status post-submission to catch 'No MRN / No Load' blocks before they cascade into missed loadings.
Validate cargo descriptions against CBP requirements for US-bound shipments. No FAK, general cargo, or consolidated cargo descriptions since 27 September 2025; replace with explicit HS-code-aligned product descriptions before submission.
Pull booking data from the forwarder's TMS or booking confirmation email, map it onto COSCO's mandatory field set, and verify against source documents before submission. Never accept pre-populated portal data as a default without cross-check.
Auto-map CCLU, CSLU, CBHU, COCU, and CICU container references to COSU for SI, BL, and invoice reconciliation without attempting separate legacy-carrier handling.
Route amendments through the same channel as the original SI. Prioritise pre-cut-off free amendments. Surface regional amendment fees (USD 100 USA/Far East/China/Australia; USD 140 Europe/ENS; INR 5,000 India) to the reviewer before post-cut-off submission.
Monitor per-booking, per-port documentation cut-off and surface deadline warnings before the window closes. Handle the 17:00 eve-of-sailing cut-off used on certain COSCO services as a distinct window from the 1-3-day default.
When a COSCO booking is on a CMA CGM, OOCL, or Evergreen vessel under the Day 10 Product, SI submission still routes through COSCO's channels (SynCon Hub / COP / INTTRA under COSU) but agents surface the operating carrier to the reviewer so any operating-carrier-specific customs nuance can be flagged early.
COSCO SI portal and fee details
Key details for ops teams submitting shipping instructions on COSCO bookings.
| Detail | Value | Notes |
|---|---|---|
| Primary SI Portal | SynCon Hub (synconhub.coscoshipping.com) | COSCO's e-commerce platform for booking, SI, and document management. |
| Alternative Portal | COP (cop.lines.coscoshipping.com) | Customer operations platform. Offers open API access. |
| EDI Channel | IFTMIN via INTTRA | Established EDI relationship for SI, booking, and tracking flows. |
| Email fallback (US LA/LB) | lalb-si@cosco-usa.com | Los Angeles / Long Beach SI submissions. |
| Email fallback (other US ports) | masterbill_sdc@coscon.com | US ports outside LA/LB. |
| Who can submit | Booking party or authorised agent (shipper, forwarder, NVOCC) | Valid COSCO customer account and booking reference required. |
| ICS2 ENS (EU-bound) | EORI + six-digit HS + complete party addresses | F12 and F13 multi-filing supported for house-level data. |
| ICS2 enforcement | No MRN / No Load | Incomplete filings deny loading at the load port. |
| AMS (US-bound) | CBP 24-hour rule | Auto-rejection of FAK / general cargo / consolidated cargo descriptions from 27 September 2025. |
| HS code minimum | Six digits | Use the WCO six-digit root; 8- or 10-digit destination codes rejected on EU lanes. |
| VGM | Must reconcile with SI gross weight | Mismatch triggers 'No VGM, No Gate-in' hold at terminal. |
| Legacy container prefixes | CCLU, CSLU, CBHU, COCU (2016 merger), CICU (leased) | All route under COSU — not separate SCACs. |
| SI cut-off | Typically 1-3 days before sailing | Route- and port-specific. Some services use 17:00 on eve of sailing. |
| Amendment (USA / Far East / China / Australia) | USD 100/BL | COSCO USA tariff (document dated 21 August 2025). |
| Amendment (Europe / ENS trades) | USD 140/BL | COSCO Europe tariff. |
| Amendment (India) | INR 5,000/BL | COSCO India local charges, effective 1 February 2025. |
| Amendment (Germany / France / Italy / Spain / Singapore / China domestic) | Published in regional tariffs | Portal login or local office contact required. |
| Late-SI / manual-submission fee | Not confirmed in public sources | No consolidated schedule equivalent to Hapag-Lloyd's EUR 100 manual SI fee. |
TMS compatibility for COSCO SI
Expedion agents submit COSCO SIs from within your existing TMS. For CargoWise users, agents exchange data via the eAdaptor API and route submissions through EDI IFTMIN via INTTRA or authenticated SynCon Hub sessions. For Magaya, Logi-Sys, and other TMS with INTTRA connectivity, agents use the established EDI path. For GoFreight and forwarders running browser-only workflows, agents drive SynCon Hub directly. 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 · Bill of lading · Documentation · Tracking & visibility
SI across carriers: Maersk SI · MSC SI · CMA CGM SI · Hapag-Lloyd SI · ONE SI · Evergreen SI
Ocean Alliance context: OOCL — COSCO subsidiary with separate IT systems, SCAC (OOLU), and customer portal (MyOOCL).
Solutions: SI automation
Glossary: Shipping Instruction · HS Code · ICS2
Frequently asked questions
What channels does COSCO accept for SI submission?
COSCO accepts SIs through four channels: SynCon Hub (synconhub.coscoshipping.com) as the primary web portal; COP (cop.lines.coscoshipping.com) as the customer operations platform with open API access; EDI IFTMIN via INTTRA for high-volume automated flows; and port-specific email as fallback (US examples: lalb-si@cosco-usa.com for Los Angeles/Long Beach; masterbill_sdc@coscon.com for other US ports). The actual preference order forwarders follow in practice is not confirmed in public sources. Expedion agents default to SynCon Hub and fall back to EDI via INTTRA for integrated flows.
Do I submit SIs under COSU, COAU, or something else when my containers have CCLU/CSLU/CBHU/COCU/CICU prefixes?
Route everything under COSU. CCLU, CSLU, CBHU, and COCU are CSCL-legacy container prefixes carried over from the February 2016 COSCO–China Shipping merger; CICU is a COSCO Container Industries leased-equipment prefix. All five are BIC-registered container prefixes, not SCAC codes: they identify equipment, not the booking carrier. COAU is the confirmed Americas/Asia SCAC; whether it still appears on active bookings is not confirmed in public sources. Map all five container prefixes to COSU for SI, BL, customs, and TMS reconciliation, regardless of the physical container's BIC code.
What ICS2 filing types does COSCO support, and is there a carrier-side ENS surcharge like ONE's USD 35/BL ESD?
COSCO's ICS2 implementation follows the October 2024 industry-wide go-live. EU-bound cargo requires EORI numbers for shipper and consignee, six-digit HS codes, accurate cargo descriptions (not FAK / general cargo), and complete party addresses with postal codes. F12 and F13 multi-filings are supported for house-level data. 'No MRN / No Load' enforcement applies — containers without a valid Movement Reference Number are denied loading. COSCO does not publish a standardised carrier-side ENS surcharge equivalent to ONE's USD 35/BL ESD. A consolidated late-SI or manual-submission processing fee schedule for COSCO is not confirmed in public sources.
What are the COSCO SI amendment fees, and do they differ between pre-cut-off and post-cut-off?
Published amendment fees by region are: USD 100/BL (USA, Far East, China, Australia); USD 140/BL (Europe, ENS trades); INR 5,000/BL (India, effective 1 February 2025). Germany, France, Italy, Spain, Singapore, and China-domestic have regional tariffs but require portal login or local office contact. Whether there is a consistent fee difference between pre-cut-off and post-cut-off amendments is not confirmed in public sources; the published tariffs apply to amendments after the documentation cut-off. The COSCO USA tariff document is dated 21 August 2025 and the India local charges document is effective 1 February 2025.
What is COSCO's SI cut-off at Shanghai, Ningbo, and other major China origin ports?
COSCO publishes route- and port-specific SI cut-offs, typically 1-3 days before vessel sailing; some services use a 17:00 eve-of-sailing cut-off. Port-specific cut-off times for Shanghai, Ningbo, Shenzhen, and Qingdao are not confirmed in public sources and vary by service string. The practical cut-off window at individual China origin ports is not confirmed in public sources. Expedion agents extract the cut-off from the booking confirmation per booking rather than applying a global rule.
My booking is on a CMA CGM or Evergreen vessel under Ocean Alliance. Do I still submit the SI to COSCO?
Yes. Ocean Alliance vessel sharing means the physical vessel may be operated by COSCO, CMA CGM, OOCL, or Evergreen depending on service string rotation, but SI submission and BL issuance remain with the booking carrier. A COSCO booking's SI goes to COSCO (SynCon Hub, COP portal, or EDI via INTTRA under COSU) regardless of which alliance member operates the vessel. Expedion agents surface the operating carrier to the reviewer so any operating-carrier-specific customs nuance can be flagged, but the SI routing does not change.
What happens if I submit a vague cargo description on a US-bound COSCO SI?
Since 27 September 2025, US CBP's ACE system automatically rejects manifests with vague cargo descriptions such as 'FAK', 'general cargo', 'consolidated cargo', 'parts', or 'samples'. A vague description on a US-bound COSCO SI will fail the 24-hour AMS rule, trigger a CBP rejection, and block loading. Descriptions must specify product name, materials, and — where applicable — technical specifications. Expedion agents validate every US-bound cargo description against CBP's specificity requirements before submission and flag any that would fail the post-September 2025 rule for reviewer correction.