The manual SI process on Evergreen
SI submission on Evergreen runs through ShipmentLink as the primary portal, with GreenX bookings flowing into ShipmentLink for SI capture, and DCSA SI API available via the ShipmentLink Developer Portal for direct integration.
- 01
Retrieve booking confirmation
Extract booking number, vessel and voyage, container allocation, port pair, and cut-off dates from ShipmentLink, GreenX (for spot bookings), or the email booking confirmation. Confirm the booking party or authorised agent holds a valid Evergreen customer account before proceeding. If the booking routes through IMT (Mediterranean mainline or the NAFR Morocco–Spain feeder), check whether the booking confirmation carries IMT party identifiers versus EGLV end-to-end.
- 02
Choose the correct SI channel
ShipmentLink web portal at shipmentlink.com and its mobile app are the primary channel. Direct DCSA SI API via the ShipmentLink Developer Portal is available for teams that have built against it. EDI IFTMIN via INTTRA (e2open) handles high-volume TMS-integrated flows. Country-office email is the manual fallback.
Pain pointEvergreen does not publish a single canonical list of country-office SI email addresses equivalent to COSCO's US port-specific addresses (lalb-si@cosco-usa.com, masterbill_sdc@coscon.com). Forwarders fall back to local Evergreen agency contact for email submission.
- 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. Whether ShipmentLink returns clear field-level error messages or generic rejections is not confirmed in public sources. The exact character limit for the cargo description field is also not documented 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 or 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. Evergreen's ICS2 Release 3 went live on 15 October 2024 after a national customs authority-approved delay from the 3 June 2024 general industry live date.
Pain pointFor F11 filings (Master BL with multiple House BLs), forwarders need to decide whether to let Evergreen file house-level data on their behalf or use F12/F13 self-filing to retain control. Whether Evergreen charges a carrier-side ENS surcharge equivalent to ONE's USD 35/BL ESD or Maersk's USD 50/house BL is not confirmed in public sources.
- 05
Validate cargo description for US-bound shipments
The US CBP 24-hour AMS rule applies via Evergreen Shipping Agency (America). 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, and notify-party addresses.
- 06
Reconcile Evergreen-family container prefixes
Evergreen bookings may produce containers with any of the following BIC prefixes: EMCU (EMC Taiwan), EGHU (Evergreen Marine HK), EGSU (Evergreen Marine Singapore), EITU (Evergreen Italy), HMCU (Evergreen Marine UK), UGMU (Greencompass Marine Panama), LTIU (Italia Marittima legacy Lloyd Triestino code), and IMTU (Italia Marittima). All route under EGLV for customs filing purposes. Do not attempt to file under a different SCAC based on the container prefix. GESU is NOT Evergreen — it belongs to GESeaCo container leasing.
Pain pointIMT's active post-consolidation NMFTA SCAC is not confirmed in public sources. Historically LTIU, but post-acquisition AMS and ICS2 filings may route under EGLV. Until operator confirmation, route under EGLV and keep IMT party identifiers visible to the reviewer.
- 07
Submit and track amendments
Submit through the chosen channel before the documentation cut-off, which is typically 1–3 days before sailing and varies by route and port. Post-cut-off amendments follow country-specific fee schedules that sit behind ShipmentLink login — there is no consolidated global amendment tariff published. USA, Germany, France, Italy (IMT), Spain, India, China, Taiwan, and Singapore each carry their own amendment fee structure accessible via portal login or country-office contact.
Where Evergreen SI errors happen
Common SI rejection and rework triggers on Evergreen, based on documented error patterns and the operational characteristics forwarders encounter at active origin ports.
HS code format or validity error
CommonSix-digit HS code is required. Submitting a 10-digit HTS code on EU lanes, using a deleted or renamed WCO code, or omitting HS codes on multi-commodity cargo triggers rejection. Remediation: validate HS codes against current WCO and EU TARIC data before submission and use the six-digit HS root.
Vague cargo description on US-bound SI
CommonFAK, 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
CommonMissing postal code, city, or EORI number on shipper or consignee triggers ICS2 ENS rejection, which cascades to No MRN / No Load at the 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 the terminal. Remediation: cross-check VGM against SI gross weight before submission and surface discrepancies to the reviewer.
IMT vs EGLV attribution confusion
OccasionalForwarder submits a Mediterranean-origin SI expecting EGLV end-to-end, but the booking routes through IMT with LTIU or IMTU container prefixes and potentially IMT party identifiers. TMS reconciliation errors follow. Remediation: confirm IMT routing at booking stage and carry IMT identifiers through SI, BL, and invoice reconciliation if confirmed. Post-consolidation SCAC behaviour is not confirmed in public sources.
Non-Evergreen container prefix attribution
OccasionalA GESU container encountered on an Evergreen booking is misattributed to Evergreen and submitted under EGLV. GESU belongs to GESeaCo (container leasing); actual Evergreen bookings carry EMCU, EGHU, EGSU, EITU, HMCU, UGMU, LTIU, or IMTU prefixes. Remediation: cross-check container prefix against confirmed Evergreen-family BIC codes and escalate unfamiliar prefixes to the local Evergreen office.
Amendment fee surprise by country
OccasionalForwarder submits a post-cut-off amendment expecting a standard rate and gets billed the local country-office fee. Because Evergreen does not publish a consolidated global amendment tariff, the fee may only become visible after submission. Remediation: pull the country-specific amendment fee from ShipmentLink before submission or route to the reviewer for approval; default to flagging 'country fee unconfirmed' rather than guessing.
How Expedion agents handle Evergreen SIs
Expedion agents run Evergreen SI submission end-to-end from booking data extraction through carrier acceptance, with channel selection, ICS2 validation, CBP compliance, and amendment routing handled automatically.
Default to ShipmentLink web portal for all bookings. Fall back to EDI IFTMIN via INTTRA (e2open) for high-volume forwarders with existing EDIFACT message flows. Use the direct DCSA SI API where the forwarder has built against the ShipmentLink Developer Portal. Route to country-office email only as manual fallback.
Enforce the six-digit HS code minimum, accurate cargo description, and complete EORI and party-address data for EU-bound cargo. Follow Evergreen's 15 October 2024 Release 3 go-live requirements and support F10, F12, and F13 filing types. 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. File via Evergreen Shipping Agency (America) under the AMS 24-hour rule.
Pull booking data from the forwarder's TMS, the ShipmentLink booking confirmation, or a GreenX spot booking; map it onto Evergreen's mandatory field set; and verify against source documents before submission.
Auto-map EMCU, EGHU, EGSU, EITU, HMCU, UGMU, LTIU, and IMTU container references to EGLV for customs filing purposes. Flag GESU containers as non-Evergreen (GESeaCo lease stock) for manual review.
Detect Mediterranean-origin bookings that may route through IMT and surface IMT party identifiers to the reviewer. Handle LTIU and IMTU container prefixes. Post-consolidation SCAC behaviour is not confirmed in public sources; the reviewer confirms it.
Route amendments through the same channel as the original SI. Prioritise pre-cut-off free amendments. Surface country-specific amendment fees where published; flag 'fee behind ShipmentLink login, reviewer to confirm' where the published figure is unavailable.
Monitor per-booking, per-port documentation cut-off and surface deadline warnings before the window closes. Handle port-specific cut-off windows rather than applying a universal default.
When an Evergreen booking sails on a CMA CGM, COSCO, or OOCL vessel under the Day 10 Product, SI submission still routes through Evergreen's channels (ShipmentLink, DCSA SI API, or INTTRA under EGLV), but agents surface the operating carrier to the reviewer so any operating-carrier-specific customs nuance can be flagged early.
Agent capability availability
*The behaviours above describe the Expedion agent spec for Evergreen. Confirm with your Expedion contact which capabilities are live in production today versus on the near-term build roadmap before relying on any specific item.*
Evergreen SI portal and fee details
Key details for ops teams submitting shipping instructions on Evergreen shipments.
| Detail | Value | Notes |
|---|---|---|
| Primary SI Portal | ShipmentLink (shipmentlink.com) | Evergreen's customer portal covering booking, SI, VGM, BL, tracking. Web + mobile app. |
| Direct API | DCSA SI API via ShipmentLink Developer Portal | shipmentlink.com/_ec/APIPORTAL_Home. Conformance listed alongside T&T v2.2, OVS 3.0, Booking 2.0 Beta, BL 3.0 Beta. |
| EDI channel | IFTMIN via INTTRA (e2open) | High-volume TMS-integrated flows. |
| Email fallback | Country-office email | No single canonical list published. Route via local Evergreen agency contact. |
| Who can submit | Booking party or authorised agent (shipper, forwarder, NVOCC) | Requires valid Evergreen customer account and the booking reference. |
| ICS2 Release 3 | Live from 15 October 2024 | Approved delayed go-live from the 3 June 2024 general industry live date. |
| ICS2 filing types | F10 / F12 / F13 supported | Per EU framework. F12/F13 require supplementary declarant EORI when buyer/seller omitted. |
| ICS2 carrier-side ENS surcharge | Not confirmed in public sources | Whether Evergreen publishes an equivalent to ONE's USD 35/BL ESD or Maersk's USD 50/house BL is not confirmed in public sources. |
| AMS (US-bound) | 24-hour rule via Evergreen Shipping Agency (America) | CBP auto-rejection of FAK / general / consolidated descriptions from 27 September 2025. |
| HS code minimum | Six digits | Per commodity line. 10-digit HTS on EU lanes or deleted WCO codes trigger rejection. |
| VGM | Must reconcile with SI gross weight | Mismatch triggers No VGM, No Gate-in holds at terminal. |
| Container prefixes (Evergreen-family) | EMCU, EGHU, EGSU, EITU, HMCU, UGMU, LTIU, IMTU | All route under EGLV for customs filing regardless of physical container prefix. |
| Non-Evergreen prefixes flagged | GESU (GESeaCo lease), GSLU (Gold Star Line / ZIM subsidiary) | Not to be filed under EGLV. Escalate to local Evergreen office. |
| SI cut-off | Typically 1–3 days before sailing | Route- and port-specific. Communicated on the booking confirmation. |
| Amendment fees (USA / Germany / France / Italy-IMT / Spain / India / China / Taiwan / Singapore) | Country-specific | Behind ShipmentLink login or via country-office contact. No consolidated global tariff published. |
| Late-SI / manual-submission fee | Not confirmed in public sources | Whether email submission attracts a manual processing surcharge is not confirmed in public sources. |
| IMT-routed Mediterranean cargo SCAC | Post-consolidation behaviour unconfirmed | Historically LTIU; post-acquisition AMS/ICS2 may route under EGLV. Not confirmed in public sources. |
TMS compatibility for Evergreen SI
Expedion agents submit Evergreen SIs from within your existing TMS. CargoWise users exchange data via the eAdaptor API (XML/SOAP) and submit through EDI IFTMIN via INTTRA or the ShipmentLink Developer Portal's DCSA SI API where built. Magaya Connect API handles forwarder-side data exchange. GoFreight operates browser-based against ShipmentLink. Logi-Sys routes through EDI via INTTRA. Forwarders without a TMS use ShipmentLink's web portal directly.
Full TMS compatibility details are on the Evergreen overview.
Related pages
Evergreen 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 · COSCO SI
Solutions: SI automation
Glossary: Shipping Instruction · HS Code · ICS2
Frequently asked questions
What channels does Evergreen accept for SI submission?
Four channels: the ShipmentLink web portal and mobile app (primary), direct DCSA SI API via the ShipmentLink Developer Portal (shipmentlink.com/_ec/APIPORTAL_Home), EDI IFTMIN via INTTRA (e2open), and country-office email as manual fallback. ShipmentLink is the default path for most forwarders. Evergreen does not publish a single canonical list of country-office SI email addresses, so email fallback routes through the local Evergreen agency contact.
Do I file the SI under EGLV or LTIU/IMTU when my Mediterranean booking routes through Italia Marittima?
File under EGLV unless the Evergreen country office instructs otherwise. IMT's active post-consolidation NMFTA SCAC is not confirmed in public sources — historically LTIU from the Lloyd Triestino era, but post-acquisition (31 January 2024, EMC via Evergreen Marine Asia for EUR 405 million) AMS and ICS2 filings may route under EGLV. LTIU and IMTU remain active as BIC container owner codes for physical containers; that is a separate identifier system from SCAC. Surface IMT party identifiers and LTIU/IMTU container prefixes to the reviewer if the booking carries them, and confirm routing with the local Evergreen office before overriding EGLV.
What ICS2 filing types does Evergreen support, and does Evergreen charge a carrier-side ENS surcharge like ONE's USD 35/BL ESD?
Evergreen supports F10 (complete straight BL), F12 (incomplete master BL), and F13 (incomplete straight BL with house-level data) under the EU ICS2 Release 3 framework. Release 3 ENS filing went live on 15 October 2024 after Evergreen received national customs authority approval for a delayed go-live from the 3 June 2024 general industry live date. F12 and F13 filings require supplementary declarant EORI numbers when buyer and seller details are omitted. Whether Evergreen charges a carrier-side ENS surcharge equivalent to ONE's USD 35/BL ESD or Maersk's USD 50/house BL ICS2 Manifest Submission Fee is not confirmed in public sources.
What are the Evergreen SI amendment fees by country, and why are they not published in a central tariff?
Amendment fees are country-specific and sit behind ShipmentLink login or require country-office contact. Evergreen does not publish a consolidated global amendment tariff equivalent to COSCO's USD 100 (USA / Far East / China / Australia) / USD 140 (Europe / ENS) / INR 5,000 (India) schedule. USA, Germany, France, Italy (IMT), Spain, India, China, Taiwan, and Singapore each carry their own amendment fee structure. Pre-cut-off amendments are typically free or cheaper than post-cut-off amendments, but the specific pre-vs-post delta by country is not confirmed in public sources. Expedion agents flag amendment fees as 'country fee unconfirmed' and route to reviewer approval rather than guessing the figure.
What is Evergreen's SI cut-off at Kaohsiung, Shanghai, and other major origin ports?
Evergreen's documentation cut-off is typically 1–3 days before vessel sailing and is route- and port-specific. The exact cut-off time is communicated on the booking confirmation rather than as a universal published deadline. The practical documentation cut-off at Kaohsiung, Shanghai, Ningbo, Shenzhen, Los Angeles, Long Beach, Rotterdam, Hamburg, and Trieste is not confirmed in public sources; Expedion agents monitor per-booking, per-port cut-off and surface deadline warnings rather than applying a global default.
My booking is on a CMA CGM, COSCO, or OOCL vessel under Ocean Alliance. Do I still submit the SI to Evergreen?
Yes. When an Evergreen booking sails on a CMA CGM, COSCO, or OOCL vessel under the Ocean Alliance Day 10 Product (launched April 2026, ~390 vessels across 41 weekly service loops and 520+ direct port pairs), the SI still routes through Evergreen's channels (ShipmentLink, DCSA SI API, or INTTRA under EGLV). Your BL and customs filings flow through Evergreen 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 early, but the primary SI submission path stays on Evergreen.
What happens if I submit a vague cargo description on a US-bound Evergreen SI?
CBP auto-rejects the manifest. Since 27 September 2025, CBP's ACE system automatically rejects manifests with FAK, general cargo, consolidated cargo, parts, or samples descriptions on cargo filed under the 24-hour AMS rule via Evergreen Shipping Agency (America). Descriptions must specify product name, materials, and technical specifications aligned with the six-digit HS code. Expedion agents validate cargo descriptions against CBP requirements before submission so US-bound SIs clear the ACE filter on the first pass.