Contact

Language Preferences

Get more precise information about services and resources by setting your language.

  • English
  • Dutch (Nederlands)
  • French (Français)
  • German (Deutsch)
  • Italian (Italiano)
  • Finnish (Suomeksi)
  • Swedish (Svenska)
  • Polish (Polski)
  • Spanish (Español)

Language Preferences

Our website is available in different languages. Would you prefer to switch language?

Continue in English

ICS2 – the EU Customs Pre-Arrival Security and Safety Program

ICS2 version 3 became mandatory across all transport modes on the 3rd of February 2026. For freight operators, road carriers, and manufacturers shipping into the EU, two further compliance deadlines arrive before the end of June.

Chris+Stennett+Logistics+Marketing+transparent+headshot

Chris Stennett

  • 11 May, 2026
  • 8 min read
ICS2 – the EU Customs Pre-Arrival Security and Safety Program

Contents:

     

    The Three-Phase Rollout and Where We Now Stand

    ICS2 has been rolling out in phases since 2021, progressively expanding the scope of operators required to file an Entry Summary Declaration (ENS). The third and final phase is now complete, with ICS2 mandatory across all transport modes as of the 3rd of February 2026.

    Five EU member states – Croatia, Latvia, Poland, Romania, and Slovakia – are due to complete the final road transport rollout on the 1st of June 2026. After that date, ICS1 will be fully decommissioned across all modes and all member states.

     

    What Changed When Version 3 Went Mandatory

    Any operator still using version 2 messaging formats after the 3rd of February – or the 1st of June in applicable countries – will have their filings rejected by the ICS2 Common Repository. This is the central EU platform that receives and processes all ENS data.

    In practice, version 3 introduces stricter data requirements across all ENS fields:

    • Goods description fields must be specific and meaningful. Most broad commodity labels are insufficient and will be rejected.
    • Consignee and consignor details must be completed to v3 standards.
    • Routing and transport data must reflect actual shipment information, not template-filled or approximated values.

    The consequences of non-compliance are administrative at first instance, but they carry direct commercial weight.

    Customs authorities can reject an ENS filing outright, which stops the shipment at the border. They can also impose administrative sanctions on operators with a pattern of incomplete or non-compliant submissions.

    For manufacturers with time-sensitive supply chains, a border hold is not a compliance problem in isolation. It is a production and financial problem.

     

    The Stop Words Update Coming on the 4th of May 2026

    Alongside the version 3 transition, the European Commission has published an updated stop words list that comes into force on the 4th of May 2026. Stop words are goods description terms that ICS2 identifies as too vague to serve any meaningful purpose in a customs risk assessment.

    When a prohibited term appears in an ENS goods description field, the ICS2 Common Repository rejects or flags the filing. This applies whether the term is the sole description or embedded within a longer entry.

    For example, generic descriptions such as ‘machine parts’, ‘clothing’, ‘electronics’, ‘goods’, ‘general cargo’, and ‘parts’ are already rejected. The May 2026 update adds a further nine terms to the prohibited list.

    Therefore, every operator must audit their goods description templates, standard operating procedures, and automated filing workflows before the 4th of May.

    For manufacturers with high-volume, recurring shipments, a single prohibited term used across hundreds of ENS filings becomes a systematic failure the moment the new list takes effect. The full updated list is published in the European Commission’s CIRCABC library.

     

    The June 2026 Road Transport Deadline

    The final milestone in the ICS2 rollout affects five specific EU member states. Croatia, Latvia, Poland, Romania, and Slovakia have been operating under a temporary derogation that allowed continued use of ICS1 for road transport. That ends on the 1st of June 2026, after which ICS1 will be fully decommissioned for road mode in those countries.

    For manufacturers and logistics providers with road freight corridors into Central and Eastern Europe, this deadline creates a hard transition point. Component manufacturers supplying automotive and industrial assembly lines are among those most directly in scope.

    Any carrier, freight forwarder, or haulage operator moving goods into those five markets after the 1st of June 2026 must file ENS under ICS2 version 3. There is no interim option and no further derogation.

    This group carries the highest risk from delayed preparation. Road transport operators in these markets may have had less exposure to the earlier ICS2 phases, which focused on air and express freight. Some will not yet have updated their systems or contracted with a compliant filing provider. The window to close that gap is now fewer than six weeks.

     

    ICS2 Multiple Filing and What It Means for Complex Supply Chains

    ICS2 version 3 introduces a structural change for operators with multi-party supply chains: multiple filing. Rather than requiring one party to hold the complete dataset, it allows the carrier, the freight forwarder, and the trader to each contribute partial ENS data to a single declaration.

    This capability is anticipated to extend to all transport modes in H2 2026, subject to confirmation from the European Commission.

    For supply chains where cargo information is split across several operators – or where multiple freight brokers each hold part of the shipment record – multiple filing removes a significant data collection bottleneck. In road and rail freight, where handoffs between parties are frequent, that bottleneck has historically caused filing delays and incomplete submissions.

    However, it creates a new compliance discipline. Each contributing party is accountable for the accuracy and completeness of its own data. The combined ENS must still meet the full ICS2 data standard before the goods arrive.

    In practice, multiple filing is not a simplification. It is a redistribution of filing responsibility.

    Operators who understand this early can design their data workflows accordingly. Those who treat it as a reduction in compliance obligations will find that an ENS is still rejected if any contributing party’s data is incomplete or includes prohibited terms.

     

    What This Means for Your Business

    For manufacturers and traders shipping goods into the EU by road — particularly into Poland, Croatia, Latvia, Romania, and Slovakia — the next few weeks represent the last window to audit and remediate ENS data quality before the June deadline. A non-compliant ENS after the 1st of June 2026 does not result in a warning. It results in a stopped shipment.

    The stop words update on the 4th of May creates a parallel risk for any operator using templated goods descriptions in their filing workflows. If those templates have not been reviewed against the updated list, filings that passed validation in April may be rejected in May – without the operator understanding why.

    Together, these two deadlines mean that the compliance burden falls not only on carriers and customs agents but on the manufacturers and traders whose shipment data sits at the origin of every ENS. If the goods description is wrong, or the party data is incomplete, the commercial consequence falls on the business that owns the cargo – not just the filer.

     

    A Practical Pre-June Checklist for Operators:

    1. Audit all goods description templates against the ICS2 stop words list before the 4th of May 2026. Any prohibited term embedded in a recurring description will trigger automatic rejection once the updated list takes effect.
    2. Confirm your filing system or customs agent is using ICS2 version 3 messaging formats. Version 2 was permanently decommissioned on the 3rd of February 2026, so any system still referencing it is non-compliant.
    3. Verify that consignee and consignor details in your ENS filings meet the version 3 data standard. Incomplete party data is one of the most common rejection triggers under the new standard.
    4. If you ship by road into Croatia, Latvia, Poland, Romania, or Slovakia, confirm that your carrier or filing provider is ICS2 v3 compliant before the 1st of June 2026. After that date, ICS1 filings for road mode will be rejected in all five countries.
    5. Review all automated filing workflows for template-filled or default description values. Systems that auto-populate goods descriptions from product codes or historical entries are a common source of stop word violations.
    6. If your supply chain involves multiple parties or freight brokers, begin mapping which party holds which ENS data. The anticipated multiple filing rollout in H2 2026 will require each contributing party to own and validate their portion of the record.

     

    How Customs Support Group Can Help You with ICS2

    Customs Support Group provides practical support across every stage of ICS2 compliance:

    • ENS data quality review and goods description audit against the current and updated stop words list
    • ICS2 v3 filing capability across road, rail, maritime, and air modes
    • Operator readiness assessment for the June 2026 road deadline in Croatia, Latvia, Poland, Romania, and Slovakia
    • Data workflow design for multiple filing arrangements in complex, multi-party supply chains
    • Ongoing compliance monitoring and ENS filing management for manufacturers and logistics providers

    Speak to our team to find out where your current ENS data sits against the ICS2 version 3 standard.