What an ENS rejection actually is
The Import Control System 2 (ICS2) is the European Union's customs pre-arrival security programme for advance cargo information, and the Entry Summary Declaration (ENS) is the safety-and-security filing it runs on, lodged before goods are loaded for, or arrive in, the EU. ICS2 Release 3 has been live for vessel operators since 3 June 2024 and for house-level filers since 4 December 2024. An ENS rejection is the EU customs system declining that declaration, and the cargo cannot move until the problem is resolved. The rules and dates in this guide are current as of June 2026 and are drawn from the European Commission's ICS2 material.
Under those rules, EU customs authorities may reject incomplete ENS declarations, or issue risk mitigating referrals in the pre-loading or pre-arrival phase, requesting the declarant to provide the necessary data, for example where the data will not be accurate. A risk mitigating referral can require the declarant to provide additional information, to perform high-risk cargo and mail screening, or not to load the cargo. The referral must be answered before the risk assessment can resume.
Customs may also impose administrative sanctions for non-compliance with the data requirements. The European Commission does not set a single EU-wide amount for those sanctions; they are set by each member state. An EORI number identifies the economic operator to ICS2, and an ENS stalls without a valid EORI for the filing party.
As of 1 June 2026, all consignments entering the EU by any means of transport should have a valid ENS. The sections below take the common reasons an ENS is rejected or referred in turn, with the fix for each.
The common rejection reasons, and how to fix each
Most ENS rejections trace to five recurring problems, and each maps to a specific data point the declaration depends on: a precise goods description, a valid EORI number, a correct six-digit Harmonised System (HS code), consistent data across the master and house filings, and complete routing. What follows is the cross-carrier picture. For one carrier's filing channels, validation, and enforcement, see the carrier documentation and shipping instruction pages, which carry the per-carrier detail this guide does not restate. The first row bounces the most declarations, and the next section covers it in full.
| Rejection cause | What triggers it | How to fix it |
|---|---|---|
| Vague goods description or a stop word | A description too generic for risk analysis, such as 'general cargo', 'parts', or 'goods', or a term on the ICS2 stop-words list, which was updated effective 4 May 2026. | Describe what the goods actually are, specifically and per commodity line. The next section covers the 4 May 2026 update. |
| Missing or invalid EORI | The EORI number for the filing or consignee party is absent, malformed, or not registered, so the operator cannot be identified to ICS2. | Capture and validate the EORI for the EU-side party before filing, and confirm it is active in the EU system. |
| Missing or incorrect HS code | The six-digit Harmonised System (HS) code is absent, truncated, or does not match the written goods description. | Provide a valid six-digit HS code per line item, consistent with the description of the goods. |
| Data mismatch across filings | The carrier master filing and the forwarder or courier house filing carry different parties, weights, or descriptions, so the combined risk picture does not reconcile. | Reconcile the master and house data before submission. ICS2 allows single or multiple ENS filings, but the data across them must agree. |
| Incomplete or changed routing | The first EU office of entry or the onward EU countries are missing or wrong, or the routing changed after submission without an amendment. | Declare the full routing, including the first point of entry and onward EU legs, and amend the ENS whenever the routing changes. |
The 4 May 2026 stop-words update
Stop words are goods descriptions too vague to support customs risk analysis, and ICS2 rejects or flags an ENS that uses one. The European Commission maintains the list and publishes it in its CIRCABC library, under reference TAXUD.A.3.003/TA. An updated list took effect on 4 May 2026.
The 4 May 2026 update targets descriptions of how a consignment was loaded rather than what it contains. Examples include 'Shipper Load and Count' and 'Shippers Load Stow and Count' with their abbreviations SLAC and SLSC, along with 'Loaded by shipper', 'As loaded', and 'As received'. These describe a loading arrangement, not the goods inside, so they cannot serve risk assessment. They sit alongside long-standing banned generics such as 'general cargo', 'parts', 'goods', and 'consolidated cargo'.
The compliance principle holds across the whole list: state what the goods actually are, specifically and per commodity line, with a matching six-digit HS code, rather than how the box was packed or who packed it. Because the list is maintained and revised in CIRCABC, treat it as a living list and re-check the current version rather than relying on a fixed set of remembered terms.
Referrals, do-not-load, and what they cost you
A rejected or referred ENS has direct operational consequences. In the pre-loading phase, a risk mitigating referral can instruct that the cargo not be loaded until the referral is answered, and the risk assessment resumes only once it is. In the pre-arrival phase, a referral can require additional information or cargo screening before the goods are released. Either way, the shipment waits on the data.
Carriers enforce this at the booking and loading stage. Several ocean carriers apply a 'No MRN, No Load' rule: without a valid Movement Reference Number (MRN) confirming an accepted ENS, the container is not loaded and rolls to a later sailing. The filing types, the exact enforcement, and any carrier-side surcharge vary by carrier, and the per-carrier detail sits on the carrier documentation and shipping instruction pages rather than here.
Beyond the delay, customs may impose administrative sanctions for non-compliance with the ICS2 data requirements. The European Commission does not publish a single EU-wide penalty amount; sanctions are set by each member state, so any specific figure depends on the country of entry. The cost to plan around is the operational one: a held or rolled container, the demurrage and detention that follow, and the customer commitment that slips.
Where Expedion fits
Expedion is a managed AI workforce for freight forwarding operations. On the documentation desk, its agents execute the ENS and the shipping instruction on each carrier's own portal or API, applying that carrier's validation before filing, so the rejection triggers above (a vague description, a missing EORI, a truncated HS code, a master-house mismatch) are caught before the declaration is submitted rather than after it bounces. The agents run on top of your existing TMS through the TMS integration and the carrier documentation workflows, so there is no migration. This carrier-side capability is in supervised production with design partners, not general availability.
Agents check the goods description, the EORI, the six-digit HS code, and the party data against the booking before the declaration is submitted, so the common rejection triggers are caught inside the filing window.
Agents file the ENS and the shipping instruction on the carrier's portal or API using that carrier's validation rules, the same per-carrier behaviour documented on the carrier pages, rather than through one generic path.
When customs issues a referral or a rejection, agents surface it, assemble the requested data, respond on the carrier channel, and write the outcome back to your TMS, with human sign-off on anything outside cleared autonomy.
Frequently asked questions
Why was my ENS rejected?
An ENS is rejected or referred when its data cannot support EU customs risk analysis. The most common reasons are a vague goods description or a term on the ICS2 stop-words list, a missing or invalid EORI number, a missing or incorrect six-digit HS code, a data mismatch between the carrier master filing and the house filing, and incomplete or changed routing. Each has a direct fix: describe the goods specifically, validate the EORI and the HS code, reconcile the filings, and declare the full routing.
What is an ICS2 risk mitigating referral?
A risk mitigating referral is an instruction EU customs issues after risk analysis, asking the declarant to provide additional information, to perform high-risk cargo or mail screening, or not to load the cargo. The referral must be answered before the risk assessment can resume, so an unanswered referral holds the shipment. A referral differs from an outright rejection in that it is a request the declarant has to satisfy before the cargo can move.
What are ICS2 stop words, and what changed on 4 May 2026?
Stop words are goods descriptions too vague for customs risk analysis, such as general cargo, parts, or goods, and ICS2 rejects or flags an ENS that uses one. The European Commission maintains the list in its CIRCABC library and announced an update that took effect on 4 May 2026. The update adds terms that describe how a consignment was loaded rather than what it contains, such as Shipper Load and Count and its abbreviation SLAC. The list is not exhaustive, so the safe practice is to describe the actual goods per commodity line and re-check the current list.
Does Expedion file ENS for me?
Expedion's agents execute the ENS and the shipping instruction on each carrier's portal or API, apply that carrier's validation before filing, and handle referrals and rejections, then write the outcome back to your TMS. It is a carrier-side capability that runs on top of your existing TMS rather than replacing it, and your team holds sign-off on anything outside cleared autonomy.