For companies shipping to Europe by road or rail, one of the most critical regulatory topics of 2025 was ICS2. The European Union's Import Control System 2 (ICS2), activated to strengthen customs security and risk analysis, made it mandatory as of April 1, 2025 for 'full Entry Summary Declaration (ENS)' data to be transmitted to the system before arrival in road and rail transport as well. It's particularly emphasized that this obligation can affect not only the carrier; but in some scenarios logistics providers, postal/express operators and even final recipients located in the EU.
September 1, 2025: Critical Threshold
The critical threshold here is September 1, 2025. According to information published by the European Commission, ICS2 became 'fully operational' for all transport modes in all member countries as of this date (including road and rail). So the 'transition period' logic ended; the system is now part of daily work.
The natural result of this is this: In a road shipment entering the EU from Turkey via Bulgaria, if the ENS data required for risk analysis at the border is not transmitted on time and in the correct format, the possibility of delay/process interruption in the process increases.
Data Discipline and Pre-Risk Analysis
The real change in the field is the reversal of the habit of 'collecting data after shipment'. ICS2's logic is to take data before entry and do risk analysis early. That's why operations where documents (commercial invoice, packing list, buyer/seller information, product description, etc.) change at the last minute can experience more friction. Especially in partial (LTL/LCL) or RoRo flows, the importance of data discipline increases; some national authorities also clearly schedule in their own publications that Release 3 is phased in and that the period between April 1, 2025–September 1, 2025 is the road/rail phase.
2026 v3 Message Cut-off Date
There's also an important date on the 'technical language' side: On the Commission's ICS2 page, there's an early transition recommendation to 'v3' version regarding practical guides and message standards to be applied after September 1, 2025; and you see that February 3, 2026 is indicated as a cut-off date for v3 messages. So as we enter 2026, not only 'is ENS data being given?' but also 'is it being given with the correct message version?' becomes the agenda.