For freight forwarders moving ocean cargo into or through Europe, a Shipping Instruction is no longer only about preparing the information that eventually appears on a Bill of Lading.
Under Import Control System 2 (ICS2), some of the shipment data captured around that process can also determine what information is transmitted to the carrier for the Entry Summary Declaration (ENS).
That makes seemingly small details, such as whether the ICS2 Declarant EORI field is blank or populated, operationally important.
CargoWise has enhanced its Shipping Instruction functionality to support these ICS2 requirements, including carrier versus supplementary filing scenarios, transshipments, six-digit HS codes, CUS codes, and additional party information.
So, what should CargoWise users understand before transmitting a Shipping Instruction?
What is ICS2 and Why does it Matter to Freight Forwarders?
ICS2 is the European Union’s advance cargo information system for goods entering or transiting through the EU. Economic operators covered by the rules must provide safety and security information through an Entry Summary Declaration (ENS) before the goods arrive. The information is used by customs authorities for safety and security risk analysis.
Release 3 extended the system across maritime and inland waterways and subsequently road and rail. For maritime house-level filers such as freight forwarders, the deployment window ran from 4 December 2024 to 1 April 2025. CargoWise also identified 1 April 2025 as the point when house-level maritime filing became mandatory.
This distinction matters in 2026: CargoWise ICS2 Release 3 is not an upcoming change. It is part of the current compliance environment.
For forwarders, the challenge is therefore no longer simply preparing for ICS2. It is making sure shipment data, filing responsibilities, and CargoWise processes consistently support it.
What does the ICS2 Declarant EORI Field Mean in CargoWise?
One of the most important CargoWise Shipping Instruction changes is the ICS2 Declarant EORI field within Additional References.
The field helps establish how the house-level ICS2 information will be handled.
CargoWise documentation distinguishes two important scenarios.
If the ICS2 Declarant EORI field is blank, it signifies Carrier Filing. In this situation, CargoWise can send the relevant Direct Shipment or House Bill information to the carrier, including information such as the Actual Shipper, Actual Consignee, EORI, HS code, and House Bill number.
If an EORI is entered, it signifies Self or Supplementary Declarant Filing. CargoWise states that House Bill information will not be sent to the carrier in that scenario; instead, the Supplementary Declarant EORI is included, and the required partial ENS filing must be handled accordingly.
This means the field should not be treated as another optional reference that can be completed without understanding its purpose.
Its status communicates the intended ICS2 filing method.
Why does Leaving the ICS2 Declarant EORI Blank Matter?
This is where CargoWise users need to be particularly careful.
A blank field does not simply mean “information missing.”
In the applicable CargoWise Shipping Instruction workflow, it means Carrier Filing.
For example, suppose a freight forwarder is shipping cargo from Asia to the EU and the ocean carrier is responsible for lodging the relevant ICS2 information.
The forwarder leaves the ICS2 Declarant EORI field blank.
CargoWise can then provide the carrier with the required shipment and House Bill information for its filing scenario.
Now consider a different arrangement where another party will lodge a supplementary filing.
The relevant EORI is entered into the ICS2 Declarant EORI field. CargoWise then treats the transaction differently and does not send the HBL information to the carrier as though the carrier were completing that filing.
That is why CargoWise displays a warning asking users to verify the ICS2 filing method before transmitting the Shipping Instruction.
The field is effectively connected to a business decision: Who is responsible for supplying the required ICS2 dataset?
Does All ICS2 Information Appear on the Bill of Lading?
No, and this is an important distinction for operational teams.
The Shipping Instruction supports information used to prepare the carrier instruction and Bill of Lading, but ICS2 introduces additional compliance data that may be transmitted electronically without becoming printed Bill of Lading content.
This means a user should not judge ICS2 completeness simply by looking at the eventual document output.
For carrier filing scenarios involving House Bills, CargoWise guidance identifies data including the goods description, six-digit HS code, House Bill number, actual shipper, actual consignee, and relevant EORI information. Depending on the scenario, additional party information can also be required.
The operational lesson is straightforward:
What is printed and what is electronically transmitted for compliance purposes are not necessarily the same dataset.
How does CargoWise Handle EU Transshipments Under ICS2?
The requirements are not limited to cargo whose final destination is inside the EU.
Cargo can also come within the relevant ICS2 process when its routing involves a qualifying transshipment.
CargoWise therefore expanded the ICS2 Declarant EORI logic beyond scenarios where only the last international sea or inland-waterway leg is discharged in the applicable region.
The enhanced logic applies when any international Sea or inland waterway leg in the Consol routing has a Port of Discharge in the EU, Northern Ireland, Norway or Switzerland. This allows CargoWise to support ICS2 information for both imports and relevant transshipments.
This is operationally significant.
A shipment may have a final destination outside the EU but still pass through an EU port. Looking only at the final destination could therefore miss an ICS2-related data requirement.
Routing needs to be considered as part of the compliance process.
Why are Six-Digit HS Codes Important for ICS2?
ICS2 requires more precise cargo information than vague or incomplete descriptions.
CargoWise identifies the six-digit HS commodity code as one of the key ENS data requirements alongside accurate goods descriptions, party information, and EORI details.
To support this, CargoWise added validation to its Shipping Instruction process.
If the HS code used for ICS2 contains fewer or more than six digits, the system warns the user that the reported ICS2 HS code must be six digits.
This matters because compliance problems often begin upstream.
If classification data is incomplete when the shipment is created, the problem eventually reaches the Shipping Instruction and ENS process. Operations then has to correct the information when the filing deadline is much closer.
Good ICS2 compliance therefore depends as much on shipment data quality as it does on the actual declaration.
What are CUS Codes and How does CargoWise Support Them?
CargoWise also introduced a CUS Code(s) field to support additional ICS2 requirements involving relevant chemical products.
The field is available under Goods Details or Goods and Equipment Details and allows users to enter up to nine CUS codes per pack line. CargoWise also validates the values and directs users toward its Global Codes records when an invalid CUS code is detected.
CargoWise specifically identifies CUS codes as applicable to harmless and dangerous-goods chemicals where required.
For forwarding teams handling chemical cargo, this creates another reason why generic commodity information may no longer be enough.
The system can provide the fields and validations, but the business still needs accurate product and classification information upstream.
What Information should be Checked Before Sending a Shipping Instruction?
There is no single checklist that replaces determining the correct filing scenario, because the required dataset can differ according to shipment structure, filing arrangement, and carrier requirements.
However, CargoWise’s updated guidance shows the importance of checking areas such as the goods description, six-digit HS code, applicable CUS codes, House Bill number, actual shipper and consignee information, EORI numbers, and notify-party information where relevant. For a direct consol or straight Bill of Lading under carrier filing, CargoWise’s guidance also identifies the consignee/EORI and, where the consignee is “To Order,” notify-party/EORI information.
Most importantly, the team must know who is filing.
A perfectly formatted Shipping Instruction can still create problems if the filing responsibility has been misunderstood.
Why is ICS2 More than a CargoWise Field Configuration?
ICS2 can easily be treated as a software configuration task:
Add the EORI. Validate the HS code. Enter the CUS code. Send the Shipping Instruction.
But the underlying operational question is bigger.
The European Commission allows ENS information to be supplied through multiple filings where the carrier does not hold the complete dataset. In those arrangements, the parties need to agree on responsibilities and exchange information necessary to link the filings.
That means forwarders need processes around CargoWise that answer questions such as:
Who is responsible for the master-level filing?
Who holds the House Bill data?
Is the carrier filing the required information, or is a supplementary declarant involved?
Are seller, buyer, consignee, and consignor details available early enough?
Are EORI numbers correctly maintained?
Are six-digit HS codes available before Shipping Instructions are transmitted?
Does the routing include an EU or other applicable transshipment point?
This is where CargoWise configuration and operational workflow need to work together.
How can Elicit Technology Help with CargoWise ICS2 Configuration?
CargoWise already provides dedicated fields, validations, and Shipping Instruction functionality to support ICS2. But getting the system functionality right is only one part of compliance.
Your shipment data, master data, forwarding configuration, filing responsibilities, and operational workflow also need to align.
As a CargoWise Service Partner, Elicit Technology can help freight forwarders review their CargoWise setup for ICS2, including Shipping Instruction configuration, EORI data, House Bill workflows, HS and CUS code handling, user processes, validations, workflow controls, and testing.
The goal is not simply to populate another compliance field.
CargoWise ICS2 integration is to make sure the right information reaches the right filing party at the right stage of the shipment.
Conclusion: Make ICS2 Compliance Part of the Shipment Workflow
ICS2 Release 3 changed the amount and quality of advance cargo information required across maritime and other transport modes. Today, those requirements are part of day-to-day European import and transit operations. The European Commission warns that incomplete or inaccurate ENS data can result in rejected declarations, requests for additional information, and delays in entry processing.
For CargoWise users, one of the most important details can be surprisingly simple:
Blank ICS2 Declarant EORI = Carrier Filing.
Entered ICS2 Declarant EORI = Self/Supplementary Declarant Filing.
But getting that choice right depends on understanding the entire shipment and filing arrangement behind it.
If your team is unsure whether its CargoWise Shipping Instructions, EORI setup, House Bill data, or ICS2 workflow are configured correctly, book a call with us, and we can help review and optimize your CargoWise ICS2 process before data-quality issues become filing problems.
