The Digital Gateway: A London-to-Hamburg Shipment Under ICS2
ICS2 Release 3 introduces mandatory Entry Summary Declaration (ENS) requirements for road freight entering the EU. This London to Hamburg case study explains how multiple filing, 6-digit HS codes, and pre-arrival submission rules impact UK exporters and EU freight forwarders.
ICS2 (Import Control System 2) has changed EU border compliance from “reporting” into pre-arrival permissioning. If your safety & security data is incomplete, late, or too vague, your truck can be delayed—or stopped—before it even enters the EU.
Import Control System 2 (ICS2)
This case study follows a real-world pattern: precision automotive components leaving London (GB) and travelling by accompanied road freight to Hamburg (DE), with the first EU entry point in France (Calais/Dunkerque or Eurotunnel).
Scenario Setup: Who Files What and Where the Risk Happens
Shipment profile
- Origin: London, United Kingdom (non-EU)
- Destination: Hamburg, Germany (EU)
- First EU entry: France (Calais/Dunkerque or Eurotunnel)
- Mode: Road (accompanied freight)
- Goal: Pass ICS2 safety & security controls without delay at the EU “front door”
The two critical operators
- Carrier (Master filer): Responsible for the master-level ENS dataset for the transport movement.
- Freight forwarder / house filer (Supplementary declarant): Supplies the detailed item-level dataset (house level) when the carrier does not hold the commercial detail.
Key point: although Hamburg is the destination, the compliance “moment of truth” is France, because the ENS risk assessment is tied to the first point of entry into the EU customs territory.
ICS1 vs ICS2: What Actually Became Stricter
The biggest operational shock is that “good enough” data under ICS1 is often not acceptable under ICS2 Release 3 for road/rail.
The practical differences that trigger rejections
- Commodity codes: Moving from “sometimes acceptable at 4 digits” to requiring better precision, commonly treated as 6-digit HS at minimum for risk analysis workflows.
- Goods descriptions: “Parts” and other generic descriptions are not acceptable; authorities require a plain language description precise enough to identify the goods, and note that general terms cannot be accepted.
- Data requirements for a Customs Goods Manifest
- Timing: For road, ENS must be lodged no later than 1 hour before arrival at the EU entry point.
- Multi-party data: ICS2 is designed for supply-chain filing models (including multiple filing), forcing parties to coordinate data earlier.
Step-by-Step: The “Digital Handshake” Using Multiple Filing
When the carrier doesn’t have buyer/seller identifiers, itemised descriptions, or HS detail, ICS2 allows Multiple Filing—but only if both parties coordinate correctly.
Step 1: Carrier submits the Master ENS dataset
The carrier lodges the master ENS data for the movement and includes the house filer’s EORI (the forwarder/supplementary declarant) so customs knows another dataset is coming.
Step 2: Forwarder submits the House ENS dataset
The forwarder files the detailed commercial dataset (item-level), including accurate goods descriptions and HS detail needed for risk assessment.
Step 3: ICS2 links both filings into one ENS
ICS2 merges the two filings using a unique linking key. The Commission’s guidance explains the linking key is composed of:
- Carrier EORI
- Master transport document reference
- Supplementary declarant (house filer) EORI
If the key doesn’t match (wrong document reference, wrong EORI, late house filing), the ENS remains incomplete—and the shipment is exposed at the border.
The “Description Trap”: Why “Auto Parts” Gets You Rejected
One of the most common causes of disruption is a goods description that fails the “identify the goods” standard.
UK government guidance (reflecting EU data rules) explicitly notes that general terms like “consolidated”, “general cargo”, “parts”, “freight of all kinds” are not precise enough and cannot be accepted, and that a non-exhaustive list of unacceptable terms is published by the Commission.
Description checklist that passes scrutiny
- No bulking: Avoid grouping unlike items under one generic line
- Use trade language: What is it, what is it for, and (where useful) material/type
- Avoid generic nouns: “parts”, “samples”, “goods”, “equipment”, “machinery” on their own
Before (high risk): “Auto parts”, “Machine components”, “Samples”
After (lower risk): “Front brake pads for passenger cars”, “Aluminium radiator valves”, “Gearbox assemblies for cars”
(These “after” examples align with the level of specificity carriers and forwarders are being asked to provide in practice.)
What Happens at Calais/Eurotunnel: Two Outcomes
Outcome A: Cleared and moving
- ENS lodged on time (≥1 hour before arrival for road)
- Master + house filings linked successfully (matching linking key)
- Goods descriptions precise; HS detail consistent with description
Result: truck proceeds through the French border process and onward to Hamburg.
Outcome B: Held, delayed, or refused progression
- Late ENS / incomplete dataset / missing house filing
- Generic descriptions triggering validation/risk flags
- Data mismatch between documents and filings
Result: increased likelihood of intervention, disruption, and cost escalation.
The Compliance Clock: Dates You Must Build Around
ICS2 Release 3 for road/rail has had a deployment window (April → September 2025) used by member states to phase operators in.
Separately, the Commission notes a major messaging change: the new version (v3) of ICS2 messages applies from 3 February 2026, with decommissioning of the previous version (v2).
What that means operationally
- Treat 1 September 2025 as the “hard edge” for road/rail go-live expectations (even where enforcement approaches may vary by route and member state).
- Ensure your intermediaries/platforms are ready for the 3 February 2026 message version change.
Practical Implementation Checklist for UK Traders and Forwarders
1) Map your first-EU-entry routes
If you’re entering via France, treat French border readiness as your gating risk (data must be complete before the truck reaches the coast).
2) Fix the data at source
Update commercial invoice templates to consistently capture:
- itemised descriptions (non-generic)
- HS at least to 6 digits (where requested)
- full party details needed by your carrier/forwarder
3) Agree the “multiple filing” operating model
Document who provides:
- the master transport reference
- the carrier EORI
- the house filer EORI
…and how quickly the house dataset will be sent, so the filings link correctly.
4) Time discipline
Build a rule into your dispatch SOP: ENS must be lodged ≥1 hour before road arrival at EU entry.
5) Platform readiness
Confirm whether you’ll file via system-to-system or via portal and that your provider supports the required ICS2 message version changes by Feb 2026.
FAQ
Does ICS2 apply if my goods are going to Germany but enter the EU via France?
Yes. Safety & security risk analysis is tied to the first point of entry into the EU customs territory, so the key controls are applied at the entry member state.
Can the carrier file everything alone?
Sometimes, yes—if they have all house-level detail. Otherwise, multiple filing allows a house filer (often the forwarder) to submit the missing dataset.
What’s the most common reason filings fail?
Late submission and poor goods descriptions. Authorities require descriptions precise enough to identify the goods; general terms like “parts” are not acceptable.
What’s the key technical mechanism in multiple filing?
The unique linking key (carrier EORI + master transport document reference + house filer EORI) is used to merge partial filings into a complete ENS.
What date should we treat as a hard technical milestone?
3 February 2026 is a published milestone for the start of the new version (v3) of ICS2 messages and decommissioning of prior message versions.
Comments