China’s export surge in early 2026 — customs clearance challenges for EU importers
11 March 2026
Should you offer free returns in the EU?
12 March 2026
FLEX. Logistics
We provide logistics services to online retailers in Europe: Amazon FBA prep, processing FBA removal orders, forwarding to Fulfillment Centers - both FBA and Vendor shipments.
If your business ships goods into the European Union — whether by air, sea, road, or rail — ICS2 version 3 is not a distant regulatory update to file away for later. It went live on 3 February 2026, and with the previous version (v2) officially decommissioned, there is no fallback. For importers, freight forwarders, carriers, and e-commerce sellers moving inventory across EU borders, understanding exactly how ICS2 v3 works in practice is now a core operational requirement.
This article breaks down the full operational workflow under ICS2 v3, explains what changed compared to the previous version, and outlines the key monitoring points that logistics teams need to build into their day-to-day processes.
If you need a broader overview of what ICS2 Phase 3 means specifically for your e-commerce shipments, this guide covers the essentials for sellers before you dive into the operational detail below.
What ICS2 Actually Is — And Why v3 Matters
The Import Control System 2 (ICS2) is the EU's advance cargo information platform, designed to strengthen safety and security risk analysis across all goods entering or transiting through EU territory. The system is managed by the European Commission's Directorate-General for Taxation and Customs Union, and it operates on the basis of the Entry Summary Declaration (ENS) — a mandatory pre-arrival filing that must be submitted by Economic Operators (EOs) before goods physically arrive at the EU border.
ICS2 is not new — it has been rolled out in phases since 2021, initially covering express and postal operators, then air cargo, and finally sea, road, and rail. What version 3 brings is a consolidated, updated set of message formats and data requirements that apply across all transport modes. The v2 messages are now gone. If your IT systems or customs filing processes were still running on v2 formats, the February 2026 cutoff was a hard deadline — not a suggestion.
The scale of the system matters too. ICS2 doesn't just collect data; it feeds directly into EU-wide safety and security risk analysis. Every ENS filed triggers an automated assessment. The output of that assessment determines whether goods move smoothly or get flagged for intervention. Getting the workflow right isn't bureaucratic box-ticking — it directly affects your shipment timelines and your ability to meet customer delivery commitments.
The Core Ops Workflow Under ICS2 v3
Understanding ICS2 v3 means understanding the sequence of events from the moment a shipment is booked to the moment goods are presented at customs. The process has several distinct phases, and each one carries its own obligations.
ENS Filing: Who Files, When, and What
The Entry Summary Declaration is the foundation of the entire ICS2 process. Every shipment brought into or transiting through the EU must have a complete ENS submitted in the system prior to arrival. For air transport, a minimum dataset must also be filed before loading takes place — this is the pre-loading phase, and it's a step that catches some operators off guard if they haven't mapped their workflows carefully.
The timing of ENS submission depends on the mode of transport. For air cargo, the pre-loading data must be filed before the aircraft is loaded. For maritime shipments, the ENS must be submitted well before the vessel arrives at the first EU port of entry. For road transport — which is particularly relevant for e-commerce imports moving across EU land borders — the timeline is tighter and requires careful coordination between carriers and forwarders.
Who is actually responsible for filing the ENS depends on the contractual arrangements in place within the supply chain. Under ICS2, the system accommodates both single filing (where one party submits the complete ENS) and multiple filing (where different supply chain actors file different parts of the declaration). For e-commerce supply chains, which often involve manufacturers, consolidators, freight forwarders, and carriers spread across different countries, the multiple filing model is common — but it requires clear agreement upfront about who owns which data elements. For Amazon sellers specifically, getting ENS filings right is inseparable from the broader challenge of forwarding inventory to Amazon fulfillment centers in Germany on time and in compliance.
A complete ENS under v3 must contain all required data elements specific to the mode of transport and the business model being used. This is one of the key operational shifts in v3: the data requirements have been refined and in some cases expanded compared to v2, particularly for road transport, which was fully brought into scope in the later phases of ICS2 deployment.
Connecting to ICS2: STP vs. STI
Economic Operators have two main routes to interact with ICS2. The first is through the Shared Trader Portal (STP), a web-based interface provided by the EU that allows manual or semi-manual ENS submission. To use the STP, the submitting party must be registered in the Unified User Management and Digital Signatures system (UUM&DS) — this is the EU's central identity and access management layer for customs systems, and registration is a prerequisite that needs to be handled well before any shipments move.
The second route is direct system-to-system integration via the Shared Trader Interface (STI). This is the preferred approach for operators with significant filing volumes, as it allows ENS submissions to be automated through a company's own TMS or customs software. Before going live with STI, mandatory self-conformance testing must be completed and passed — this is non-negotiable, and testing for v3 message formats is separate from any previous v2 testing that may have been done.
Operators who are not in a position to develop their own IT connection — which is common for smaller importers and e-commerce sellers — can also work with an IT Service Provider (ITSP) who handles ENS submission on their behalf. This is a practical route for many businesses, but it doesn't reduce the obligation: the Economic Operator remains legally responsible for the accuracy and completeness of the ENS data.
Risk Analysis and What Happens After Filing
Once an ENS is submitted, the ICS2 system performs safety and security risk analysis on the declared data. This happens automatically, and the outcome determines what happens next. In most cases, the shipment proceeds without intervention. However, when the risk analysis flags a concern, the system issues what is called a risk mitigating referral.
Risk mitigating referrals can take several forms. The declarant may be asked to provide additional information or documentation. In air cargo scenarios, a referral may require high-risk cargo screening to be performed before loading. In more serious cases, a do-not-load instruction can be issued, preventing the shipment from departing until the matter is resolved.
This is a critical point for operations teams to understand: a referral must be answered and resolved before risk assessment can resume. This means that an unanswered or poorly handled referral creates a bottleneck that can hold up an entire shipment. Building a process for monitoring referral status — and responding to them promptly — is not optional for any operator filing ENS declarations at volume.
Arrival Notification and Goods Presentation
After the pre-arrival phase, the workflow continues at the point of physical arrival. The operator of a sea-going vessel or aircraft must lodge an arrival notification when the means of transport reaches the first EU customs office of entry. Goods must then be formally presented to customs upon arrival.
This final step closes the loop between the advance declaration and the physical goods. Customs authorities use the ENS data, the results of the pre-arrival risk analysis, and the arrival notification together to decide on any further controls. Incomplete or inaccurate ENS data at this stage can trigger delays, administrative sanctions, or rejection of the declaration — all of which add cost and complexity to an already time-sensitive process.
What Changed in v3 — The Key Differences to Know
Version 3 of ICS2 is primarily a technical and data-format update, but the operational implications are real. The most significant change is the decommissioning of v2 message structures, which means any system, workflow, or integration built around v2 formats needed to be fully updated before the February 2026 go-live.
For road and rail transport specifically, ICS2 v3 aligns with the transition away from the derogation period that was in place between September 2025 and the February 2026 cutoff. During that transitional window, specific guidance was published for operators submitting ENS for road and rail shipments while the system was still being fully deployed. That transitional period is now over.
Another update in v3 concerns the stop words list — a reference list used in processing ENS descriptions that was updated as of 2 February 2026. This affects how goods descriptions are validated in the system. Filing with outdated or non-compliant descriptions can cause validation errors that delay processing.
Monitoring ICS2: What Your Team Should Be Tracking Daily
For logistics teams that are now live on ICS2 v3, the operational focus shifts from implementation to monitoring. The system is not a set-and-forget process — it requires active oversight across several dimensions. Here are the four areas that should be on every ops team's daily radar:
Referral status — The most time-sensitive item on the list. Any ENS that generates a risk mitigating referral requires a response, and the clock starts immediately. Teams should have a clear escalation path in place: who receives the referral notification, who has the authority and information to respond, and what the target response time is. For air cargo in particular, pre-loading referrals can halt a shipment at origin if not handled quickly.
ENS rejection rates and validation errors — A high rate of rejected or incomplete declarations is a signal that either the data being supplied upstream is inaccurate, or that the system integration has a mapping issue. Both need to be caught early. Customs authorities have the power to impose administrative sanctions for non-compliance with data requirements, so a pattern of errors is not just an operational inconvenience — it carries regulatory and financial risk.
Multi-filing coordination — For operators using the multiple filing model, coordination monitoring is essential. When different parties are responsible for different parts of the ENS, there is a real risk that a declaration remains incomplete simply because one party hasn't filed their portion yet. Tracking completeness status across all expected parties — before the deadline — needs to be part of the daily operations rhythm.
System availability and business continuity — ICS2, like any large-scale government IT system, can experience downtime. The European Commission has published Business Continuity Planning (BCP) guidance specifically for ICS2, outlining the fallback procedures operators should follow when the system is unavailable. Having that guidance understood and accessible before an outage occurs is far better than trying to navigate it in the middle of a live operational crisis.
Getting ICS2 v3 Right in Practice
ICS2 v3 is now the operational standard for all goods entering the EU, without exception. The framework is complex enough that gaps in preparation — whether in data quality, IT connectivity, staff awareness, or monitoring processes — tend to show up quickly once real shipments are moving through the system.
For e-commerce sellers and importers who are focused on getting inventory into EU markets efficiently, the compliance burden is real but manageable with the right partners and processes in place. Staying on top of the ENS filing timeline, understanding who in your supply chain is responsible for each data element, and building active monitoring into your customs workflow are the three pillars of a clean ICS2 operation.
At FLEX. Logistics, customs clearance is a core part of the service offering for online retailers importing goods into the EU. Whether your shipments arrive by air into one of our warehouse locations in Germany, Poland, or France, or move cross-border by road, FLEX. works with experienced customs agents to ensure your ENS filings are accurate, timely, and compliant with ICS2 v3 requirements. If you're navigating the new framework and want a logistics partner who understands both the operational and regulatory side of EU imports, get in touch with FLEX. Logistics today.
