If you move road freight between the UK and France, two acronyms now define your compliance obligations at the Channel crossing: ICS2 and ELO. Both became mandatory in 2026. Both affect every loaded truck, every empty trailer, and every freight forwarder managing UK–France movements. And critically, one cannot work without the other.

This article explains exactly how ICS2 and ELO connect, why the Entry Summary Declaration (ENS) must be filed first, and what the end-to-end process looks like for operators on the ground.

What Is ICS2?

ICS2 — the EU’s Import Control System 2 — is the EU’s advance cargo information platform. It replaced the legacy ICS1 system and became fully mandatory for all transport modes, including road and rail, from 1 January 2026.

Its core function is the Entry Summary Declaration (ENS): a pre-arrival safety and security filing that provides EU customs authorities with advance information about goods entering or transiting EU territory. For goods moving from Great Britain to France, the carrier or their freight forwarder must submit the ENS to ICS2 before the goods reach the French border.

ICS2 is the EU’s advance cargo information and risk analysis platform, mandatory for non-Union goods entering the EU customs territory. Since 1 April 2025, ICS2 has been operational for goods entering the EU by truck, train, or as unaccompanied trailers on ships.  

When the ENS is accepted by ICS2, the system issues a Movement Reference Number (MRN). That MRN is your proof that the safety and security declaration has been received and processed. It is also the link that connects ICS2 to the ELO — and this is where the two systems become inseparable.

What Is the ELO?

The ELO — Enveloppe Logistique Obligatoire, or Obligatory Logistics Envelope — is a French customs instrument that is part of the Smart Border system governing UK–France freight movements.

Think of the ELO as a digital folder. It consolidates all declarative reference numbers and cargo information for a given crossing into a single, scannable barcode. Its purpose is to secure and streamline the processing of goods at the Smart Border.  

When a truck is loaded, the ELO must group all the EU-side formalities necessary for crossing the Smart Border. For goods moving in the UK-to-EU direction, this includes EU import declarations, transit declarations, export declarations, and the ENS filed via ICS2 along with its Movement Reference Number.  

The ELO became fully mandatory on 20 April 2026. For imports, economic operators including road transport operators are obliged to put at least one Entry Summary Declaration into the ELO when ICS2 rules apply.  

One important point: UK formalities — specifically the Goods Movement Reference (GMR) generated under the UK’s GVMS system — are not included in the ELO. Those remain a separate UK obligation. The ELO is purely an EU-side instrument.  

Why the ENS Must Come First

Here is where many operators misunderstand the relationship between the two systems: the ELO cannot be created without the ICS2 ENS MRN. The two are not parallel processes. They are sequential.

The practical sequence is straightforward, but it leaves little room for error. The operator must first secure the ICS2 safety and security filing, then make sure the relevant ENS MRN is available, and then create the ELO, which must include the ENS MRN reference.  

This means that if your ENS has not been filed — or has been rejected — no ELO barcode can be generated, and no compliant border crossing can take place. If the ENS is filed too late, the driver can arrive ready to board but still be stuck waiting for the MRN and ELO chain to complete.

The End-to-End Process: Step by Step

Here is the complete filing sequence every freight forwarder, exporter, and haulier operating on the UK–France corridor needs to follow:

Step 1 — File the ICS2 ENS Submit the Entry Summary Declaration to ICS2 ahead of the goods departing for the port. The ENS must contain accurate goods descriptions (no vague terms — ICS2 uses automated stop-word validation), correct 6-digit HS codes, valid EU or XI EORI numbers, and the correct transport mode code. For Channel Tunnel shuttle movements, the transport mode is coded as road (code 3), not rail, even though the truck travels on a train.

Step 2 — Receive your MRN Once ICS2 accepts the ENS, a Movement Reference Number is issued. This MRN is the essential link between the two systems. Without it, you cannot proceed to Step 3.

Step 3 — Create the ELO The ELO creator links the ICS2 ENS and the various customs declaration references — import, export, and transit declarations — to the haulier’s details through the Prodouane interface, generating a single, unique ELO barcode. The ELO creator is typically the freight forwarder or logistics operator — not the driver.

Step 4 — Share the barcode with the driver The driver receives the ELO barcode before departing for the port. This is their single reference document for the crossing — covering all EU-side declarations in one scannable code.

Step 5 — Present at the terminal At the ferry terminal or Channel Tunnel terminal, the ELO barcode is scanned and paired with the crossing. The Smart Border system then determines the vehicle’s routing, including whether it can continue or is directed to customs controls.  

The entire chain — ENS filed, MRN received, ELO created, barcode with driver — must be complete before the truck reaches the terminal. There is no opportunity to catch up at the border.

What Happens Without a Valid ELO?

The consequences of arriving at Calais, Dunkirk, or the Channel Tunnel terminal without a valid, closed ELO barcode are immediate and operational. Vehicles may be refused boarding by the ferry or shuttle operator, directed to secondary inspection, or face formal notification of non-compliance to customs authorities. In any of these scenarios, the cost — in delays, missed delivery windows, and customer impact — is entirely avoidable.

Who Creates the ELO?

French Customs specifies that any actor within the logistics chain with the capacity to centralise all the necessary information for the border crossing may create an ELO. This can change from crossing to crossing.  

In practice, the ELO is most commonly created by the freight forwarder or customs agent who also manages the ENS filing, since they already hold the MRN. Clear communication between all parties in the supply chain — exporter, forwarder, haulier, and driver — is essential to ensure the barcode reaches the driver before departure.

The Bottom Line

ICS2 and ELO are not two separate compliance tasks that can be managed independently. They are a single sequential workflow, and the ENS is the foundation. For operators managing the transition to mandatory ELO requirements, the ICS2 ENS MRN is the essential prerequisite for ELO barcode generation. Filing the ENS therefore directly supports the end-to-end Smart Border crossing workflow, from ENS submission through to driver check-in.  

If your ENS process is manual, inconsistent, or not yet in place, that is the single most urgent action to address. The ELO will not function without it — and from 20 April 2026, neither will your UK–France freight movements.

Government figures confirm the airport’s position as Britain’s most valuable trading port — and what it means for UK customs compliance.

Britain’s Busiest Trading Hub, by the Numbers

When government trade data released in April 2026 confirmed that Heathrow Airport processed £293 billion worth of goods in 2025, it crystallised something that customs professionals have long understood: air freight is not a niche channel for perishables and luxury goods. It is the arterial system of modern UK trade, and Heathrow is its beating heart.

The figures, drawn from HMRC’s official trade statistics, place Heathrow above every seaport in the country when ranked by value. More than a quarter of all UK trade by value — some £1 in every £4 of goods Britain imports or exports — passes through a single airport in west London. That is a remarkable concentration of economic activity, and it carries significant implications for logistics operators, importers, exporters, and the customs compliance community that supports them.

Imports, Exports, and the Value of Connectivity

Of the £293 billion total, approximately £166 billion represented goods arriving into the United Kingdom, while around £127 billion flowed outwards as exports. The import-to-export ratio reflects a familiar structural pattern in UK trade: Britain imports more by value than it exports, and the most time-sensitive, high-value goods overwhelmingly travel by air.

The composition of those flows is equally revealing. On the inbound side, pharmaceuticals and temperature-sensitive medicines move through Heathrow’s cold-chain infrastructure from North American and European hubs to hospitals and pharmacies across the country. High-value electronics — smartphones, semiconductors, precision components — arrive from Asian manufacturing centres in the bellyhold of passenger aircraft. Luxury fashion from Milan and Paris reaches Bond Street concessions within hours of departure. Fresh produce from Sub-Saharan Africa and South Asia fills supermarket shelves days after harvest.

The export picture tells its own story of British commercial ambition. Yorkshire food producers, premium spirits distillers, precision engineering firms, and biotech companies depend on Heathrow’s connectivity to reach markets in the Gulf, North America, and Asia-Pacific — markets where delivery speed is not merely a convenience but a commercial prerequisite. Gourmet food producers, for instance, rely on air freight to deliver products that retain freshness and quality upon arrival in markets as far afield as Singapore and Hong Kong.

A Non-EU Powerhouse: Trade Geography After Brexit

Perhaps the most strategically significant finding in the 2025 data concerns the geographic composition of Heathrow’s trade flows. More than 90 percent of the airport’s trade by value is with countries outside the European Union. This is not simply a reflection of Heathrow’s long-haul route network — it is a structural feature of post-Brexit UK trade that has significant consequences for customs declaration volumes and compliance requirements.

Trade with non-EU third countries requires full customs declarations on both import and export. Unlike movements with the EU under the Trade and Cooperation Agreement — which, while no longer tariff-free in all directions, benefits from a degree of regulatory familiarity — third-country trade demands careful classification, accurate origin determination, correct customs valuation, and timely submission of documentation to HMRC. With over £263 billion of Heathrow’s throughput originating from or destined for non-EU markets, the volume of customs compliance activity generated by a single airport is extraordinary.

Growth, Capacity, and the Case for Expansion

In volume terms, 2025 air cargo throughput at Heathrow reached 1.59 million tonnes, a year-on-year increase of approximately 0.8 percent. While modest in percentage terms, the absolute weight increase of some 12,600 tonnes reflects the sustained upward trajectory of UK air freight demand, particularly among domestic UK-origin shipments. The value figures represent a more substantial step up from the £215.6 billion recorded in 2024, underscoring the increasing premium nature of goods moving through the airport.

The average cargo value per flight stood at approximately £600,000. This figure is not simply a statistical curiosity: it illustrates why even minor delays at Heathrow carry disproportionate commercial consequences. When a single aircraft movement represents hundreds of thousands of pounds in perishable goods, pharmaceuticals, or electronics, clearance delays of hours — not days — translate directly into financial loss and supply chain disruption.

The airport is operating at or near capacity, and its operator has been explicit that expansion — including the long-discussed third runway, which received government endorsement — is critical to sustaining the UK’s position in global trade. A new 3.5-kilometre runway is part of a multi-billion-pound investment programme, and infrastructure upgrades are already under way. Cargo handlers at the airport have reported volume surges of 28 percent in early periods, with new warehouse facilities under development to accommodate further growth.

What Moves Through Heathrow — and Why It Matters for Customs

The goods moving through Heathrow span an enormous range of commodity categories, each presenting distinct customs classification, valuation, and compliance challenges. Pharmaceuticals — among the highest-value goods by weight in UK trade — arrive under strict cold-chain conditions and may require licences, preferential duty claims under free trade agreements, or specific procedure codes on the import declaration. Semiconductor components and advanced electronics attract precise tariff classification requirements, with classification errors capable of triggering duty reassessments or enforcement action.

On the export side, industrial machinery, electric machinery, and high-end food and beverage products are consistently among the most significant categories by weight and value. Each of these requires accurate commodity classification under the UK Trade Tariff, correct origin determination, and complete documentation aligned with the destination country’s import requirements. For businesses exporting to markets with which the UK maintains a free trade agreement — Japan, Australia, Canada, or Singapore — correct origin proofs are the difference between a significant duty saving and the full Most-Favoured-Nation rate.

Filing for Heathrow’s Trade Volumes — Accurately and at Scale

The scale of trade flowing through Heathrow underscores a point that every importer, exporter, freight forwarder, and customs agent operating in the UK’s air freight sector must keep in sharp focus: the compliance burden associated with this volume of third-country trade is substantial, and the cost of errors — whether through incorrect classification, inaccurate valuation, or misaligned safety and security data — is equally so.

Customs Declarations UK (CDUK) provides a structured, cloud-based solution for submitting import and export declarations via Compass – Community Network Services for Heathrow, as well as Entry Summary Declarations (ENS) for safety and security compliance. The platform guides users through plain-English workflows covering all the critical data fields — importer and exporter identities, commodity classification, customs valuation, Incoterms, country of origin, and applicable licence references — with real-time validation checks that identify errors before submission.

For businesses handling regular movements through Heathrow, CDUK’s template and clone functionality allows declaration data to be reused and adapted across repeat shipments, significantly reducing manual data entry time. Every accepted declaration generates a Movement Reference Number instantly, with the full submission set archived securely for the statutory six-year retention period — providing the audit-ready records that HMRC may request at any point. Safety and security ENS data can be aligned with customs declaration records to ensure consistency and prevent the border holds that commonly arise from mismatched datasets between carriers and declarants.

As Heathrow’s throughput continues to grow — and with expansion on the horizon that will add further capacity and route diversity — the case for technology-enabled, validated customs filing has never been stronger. Efficient clearance is not simply an administrative convenience; at £600,000 per flight, it is a direct commercial imperative.

One Airport. A Quarter of Britain’s Trade. An Enduring Compliance Obligation.

The 2025 Heathrow trade data is more than an impressive headline figure. It is a reminder of how deeply concentrated — and how commercially critical — UK air freight has become. A single airport handling £293 billion in goods annually, processing over 1.5 million tonnes of cargo, and serving as the gateway for more than 90 percent of that trade with countries outside the European Union, creates an unambiguous and ongoing demand for accurate, efficient, and fully documented customs compliance.

For the thousands of businesses that import or export through Heathrow every year — whether they are pharmaceutical multinationals bringing temperature-sensitive medicines into the UK, or small food producers shipping artisan products to international retailers — the mechanics of customs declarations are not a background administrative matter. They are operational infrastructure. Getting them right, first time, every time, is what keeps supply chains moving.

The European Commission’s Directorate-General for Taxation and Customs Union has published a further update to the list of stop words and phrases prohibited in Entry Summary Declaration (ENS) goods descriptions under the Import Control System 2 (ICS2). Nine new terms become enforceable on 4 May 2026, adding to the growing body of banned language already active since the system’s initial deployment. Carriers, freight forwarders, customs agents, and anyone filing ENS declarations must audit their commodity description templates and standard operating procedures before that date to avoid automatic rejection by the ICS2 Common Repository.

What Are ICS2 Stop Words and Why Do They Exist?

ICS2 is the EU’s advance cargo information and risk management system, requiring traders and carriers to lodge Entry Summary Declarations before goods arrive at an EU border crossing. A central objective of ICS2 is the improvement of ENS data quality — specifically, the accuracy and specificity of goods descriptions that customs authorities use for pre-arrival risk assessment and safety screening.

Stop words and phrases are terms that the European Commission has identified as too vague, generic, or ambiguous to serve any meaningful purpose in a goods description field. When a prohibited term appears in a submitted ENS declaration — whether as the sole description or embedded within a longer entry — the ICS2 Common Repository rejects or flags the filing. The underlying principle is straightforward: a goods description must enable a customs officer to understand, at a glance, what is actually being transported. Terms such as “Miscellaneous,” “Unknown,” or “Goods” provide no actionable intelligence and therefore have no place in a compliant ENS submission.

The stop word initiative is issued under reference TAXUD.A.3.003/TA from the Commission’s Risk Management and Security unit. It applies uniformly across all ICS2 participating countries and across all ENS filing types, with singular and plural forms treated interchangeably.

What Was Already in Force

Before examining the 4 May 2026 additions, it is helpful to understand the scale and scope of what has already been implemented. The initial list, introduced in Spring 2025, prohibited a wide range of generic goods description terms. These included broad category words such as “Accessories,” “Chemicals,” “Electronics,” “Equipment,” “Machinery,” “Materials,” “Parts,” “Products,” “Spare parts,” “Textiles,” “Vehicles,” and “Goods” itself. Also banned were terms describing shipment handling rather than cargo content — “Consolidated cargo,” “General cargo,” “Courier goods,” and “Said to Contain” — along with placeholder language such as “Unknown,” “Not available,” “N/A,” and “See invoice.”

A further update effective 2 February 2026 extended the list to include terms such as “Aid products,” “Comercial,” “Consumption,” “Ensemble,” “Fake,” “Headwear,” “Item,” “Miscellaneous,” “N/A,” “Oddments,” “Promotional,” and “Vegan,” among others. At the same time, restrictions were applied to party name and address fields, prohibiting placeholder entries such as “00200,” “NA,” “N/A,” “Name,” “Not available,” “Numbers,” “Please select,” “Private,” “Sir,” “Sr,” “To order,” “Unknown,” and “xxxx.”

The declaration for an empty movement differs in content from that of a loaded one, but the obligation to file in advance remains identical. Operators should not interpret the absence of cargo as an exemption from the pre-arrival declaration process.

The 4 May 2026 Update: What Is New

The additions taking effect on 4 May 2026 are concentrated in a specific category of shipping shorthand that has long been common practice in the freight industry but which the Commission has now formally prohibited in ENS goods description fields. All nine new terms relate to shipper-loaded container conventions and acknowledgements of limited cargo visibility at the time of filing. They are as follows.

“As loaded” and “As received” — both individually and in the combined form “As loaded / as received” — are phrases typically used when a carrier has not verified the contents of a container or consignment. They describe the carrier’s state of knowledge rather than the nature of the goods, and are now banned accordingly.

“Load and Count as per shipper”, “Loaded by shipper”, and “Shipper Load and Count” are variations of the same concept: responsibility for the load being attributed to the shipper, with the carrier disclaiming direct knowledge of the cargo. These phrases, often used for shipper-packed containers (SPCs) and full container loads (FCLs), may reflect operational reality but are not acceptable as goods descriptions in ENS filings.

“Shippers Load Stow and Count”, along with its common abbreviations “SLAC” and “SLSC”, completes the new set. These acronyms are well-established in container shipping documentation but have no descriptive value from a customs and security risk assessment perspective.

The common thread across all nine terms is that they describe how a consignment was loaded rather than what the consignment contains. Under ICS2, the goods description field must answer the latter question. From 4 May 2026, the Common Repository will treat any ENS submission containing these terms as non-compliant.

Understanding the Broader Principle

It is important to approach the stop word list not as an exhaustive register of banned vocabulary, but as an illustration of a broader compliance principle. The European Commission has been explicit that the list is not finite. Terms may be added over time as data quality analysis identifies new patterns of vague or evasive language entering the ICS2 system.

The guiding standard for any ENS goods description is specificity and accuracy. A compliant description should identify what the goods actually are — their nature, composition, or function — in plain, precise language. A shipment of inkjet printer cartridges should be described as such, not as “Electronic items” or “Office supplies.” A consignment of stainless steel industrial valves should be named specifically, not described as “Machine parts” or “Hardware.” Where a single ENS covers multiple commodity lines, each line should carry its own precise description rather than a catch-all entry covering the whole consignment.

This standard applies regardless of whether the specific term appears on the published stop word list. If a description would not allow a customs officer to form a clear picture of the cargo, it is likely to attract scrutiny even if no individual word has been formally prohibited.

Practical Impact on Filing Operations

For carriers and logistics operators, the 4 May 2026 changes have immediate operational implications. Any ENS filing template, customs management system, or booking-to-filing data pipeline that currently uses “SLAC,” “SLSC,” “As loaded,” “As received,” or any variant of “Shipper Load and Count” in the goods description field must be updated before that date.

The challenge is particularly acute for consolidation and groupage operators, where a single master ENS may cover dozens of shipment lines from different shippers, some of which may not have provided specific cargo descriptions at the time of booking. In these cases, the responsibility lies with the filing party to obtain adequate cargo descriptions from shippers or to apply best-available knowledge to generate compliant entries. Blanket use of carrier-loaded disclaimers is no longer an acceptable workaround.

Customs brokers and agents should also review the standard description text used in any system pre-population or auto-fill rules. A description that was previously tolerated — or that passed validation under earlier versions of the Common Repository rules — may now trigger a rejection if it contains one of the newly prohibited terms.

How to Write Compliant ICS2 Goods Descriptions

Writing an ICS2-compliant goods description does not require technical expertise, but it does require deliberate attention to specificity. The following guidance reflects the principles embedded in the Commission’s stop word initiative.

The description should identify the actual nature of the goods. For manufactured items, this typically means naming the product type, its primary material or composition where relevant, and its function or application. “Polypropylene injection moulding pellets” is compliant; “Plastic goods” is not. “Printed cotton T-shirts” is compliant; “Clothing” is not. “Lithium-ion battery cells for portable electronics” is compliant; “Batteries” or “Electronics” is not.

Where a consignment genuinely contains multiple product types, each should be declared on a separate commodity line with its own specific description. Consolidating them under a single vague line is the root cause of many stop word violations and should be avoided as a matter of routine practice rather than exceptional compliance effort.

Commercial invoice descriptions provide a useful starting point, but they should be verified. Some supplier invoices use abbreviated or internal product codes that would not be meaningful to a customs authority. The goods description in the ENS should be legible and informative to someone with no prior knowledge of the commercial relationship.

Filing ENS Declarations Through Customs Declarations UK

The Customs Declarations UK (CDUK) platform provides a structured, validated environment for filing ENS declarations that aligns directly with ICS2 data quality requirements. The platform’s interactive wizards guide users through each data element, including goods descriptions, with plain-English prompts that encourage the kind of specific, accurate entries the Common Repository expects.

For operators managing high volumes of ENS submissions, CDUK supports bulk data upload via CSV and Excel, enabling rapid population of declaration lines without repetitive manual entry. Goods description fields benefit from real-time validation that can flag inconsistencies and missing data before submission — reducing the risk of outright rejection by ICS2 and the administrative burden of re-filing corrected entries after the fact.

For businesses new to ICS2 obligations, the platform offers onboarding support and training resources to ensure teams understand not only how to use the system but also why compliance with data quality standards — including stop word avoidance — matters for seamless cross-border operations.

Conclusion

The European Commission’s 4 May 2026 stop word update is a targeted but significant step in the ongoing drive to improve ENS data quality under ICS2. The nine newly prohibited terms — covering “As loaded,” “As received,” shipper loading disclaimers, and the abbreviations SLAC and SLSC — reflect a clear policy direction: carrier-loaded shorthand has no place in the goods description field of a safety and security declaration. The field exists to describe cargo, not logistics conventions.

Compliance with ICS2 stop word rules is not merely a technical filing requirement. It reflects a commitment to the safety and security principles that underpin advance cargo information systems across the EU — and it is increasingly the baseline expectation for every business participating in cross-border trade.

A widely held assumption among road freight operators is that an unloaded trailer crossing an international border falls outside the scope of customs formalities. There is, after all, nothing to declare. Under France’s mandatory Obligatory Logistics Envelope (ELO) procedure, which came into force in April 2026, that assumption is incorrect — and the consequences of acting upon it are material.

This article sets out the regulatory position clearly, addresses the most common misconceptions, and provides a structured overview of the steps road freight operators must take to ensure compliance on every crossing into France, regardless of whether a trailer is loaded or empty.

Understanding the ELO Requirement

ELO — Obligatory Logistics Envelope — is a simplified customs procedure operating under the framework of the European Union’s Union Customs Code (UCC). It permits authorised operators to record goods movements in their own systems rather than submitting a full customs declaration at the border. In France, use of the ELO procedure has been mandated for road freight movements from April 2026, including those arriving from the United Kingdom via the Channel crossing.

Central to the ELO process is the ELO barcode: a unique movement identifier issued by French customs once the required pre-arrival safety and security declaration has been successfully submitted and accepted. This barcode must be in the possession of the driver before the vehicle departs for the French crossing point. It is not a document that can be obtained at the border, nor one that can be substituted with alternative paperwork at the point of entry.

In practical terms, the ELO barcode functions as customs clearance authorisation for that specific vehicle movement. Without it, the movement is non-compliant from the moment it enters French territory.

The Position on Empty Trailers: A Regulatory Clarification

The most persistent misconception in the road haulage sector concerns the applicability of ELO to empty trailer movements. Operators repositioning equipment, returning after a delivery, or deadheading to collect a load frequently assume that the absence of cargo removes any obligation to comply with customs pre-arrival procedures. Under the current ELO framework, this is not the case.

French customs requires an ELO barcode for the vehicle movement itself, not solely for the cargo it carries. The rationale is grounded in risk assessment: customs authorities require advance visibility of all cross-border vehicle movements in order to allocate resource, identify anomalies, and maintain the integrity of the border process. An empty trailer represents a vehicle crossing an EU external border and, as such, falls within the scope of the mandatory pre-arrival declaration requirement.

The declaration for an empty movement differs in content from that of a loaded one, but the obligation to file in advance remains identical. Operators should not interpret the absence of cargo as an exemption from the pre-arrival declaration process.

Why This Presents a Compliance Risk for UK Hauliers

The introduction of ELO as a mandatory requirement coincides with a broader set of UK customs tariff updates effective April 2026, creating a more complex compliance environment than many operators have previously encountered. UK hauliers have, in the main, developed robust processes for fully documented loaded movements — those supported by commercial invoices, commodity codes, and export declarations. Empty trailer runs, however, have historically required minimal documentation and have not been subject to the same procedural rigour.

It is precisely this gap that presents the most significant compliance risk in 2026. Operators who have not reviewed their internal despatch procedures to incorporate ELO barcode generation for all vehicle crossings — including empty movements — are exposed to delays, inspections, and potential penalties that are entirely avoidable.

Smaller haulage operators and owner-drivers, who may lack dedicated compliance functions, face a particular risk of non-awareness. The regulatory obligation applies uniformly, irrespective of fleet size or the frequency of crossings.

The ICS2 Entry Summary Declaration: The Mandatory First Step

Before a valid ELO barcode can be generated for any vehicle movement, an Entry Summary Declaration (ENS) must be submitted through the EU’s Import Control System 2 (ICS2). This is a pre-arrival safety and security filing that provides French and EU customs with the information necessary to conduct a risk assessment of the incoming movement. It is mandatory for all road freight entering the EU from the United Kingdom, and it must be completed before the vehicle departs — not at the port of embarkation and not at the point of entry into France.

The ENS submission is the foundational step in the ELO process. Once filed and accepted by customs, the ELO barcode is generated and made available to the operator. The sequence is fixed and cannot be reversed or circumvented:

Any break in this sequence — most commonly, a failure to file the ENS in advance or a filing error that results in rejection — means no ELO barcode is available. A driver arriving at the crossing without a valid barcode is not in a position to complete the process retrospectively at the border.

Data Requirements for an Empty Movement Declaration

A question frequently raised by operators is what information is required when filing an ENS for an empty trailer movement. The absence of goods does not reduce the data fields that must be completed; it changes only the nature of the content within those fields. The following information is required as a minimum:

• Vehicle and trailer registration numbers
• Carrier EORI (Economic Operators Registration and Identification) number
• Planned routing and expected date and time of crossing
• Declaration of empty status, using the applicable customs code for an unloaded movement
• Consignor and consignee information, where applicable to the movement type
• Country of departure and country of destination

Customs filing platforms such as CDUK are configured to guide operators through the correct data fields for empty movement declarations, ensuring that submissions are complete, accurate, and formatted in accordance with ICS2 system requirements.

Consequences of Non-Compliance

Road freight operators who proceed to the French crossing without a valid ELO barcode face a range of operational and regulatory consequences. These are not theoretical risks; they are the direct and foreseeable outcomes of a failure to comply with a mandatory pre-arrival filing obligation:

• Delay at the crossing point while the non-compliant status of the movement is investigated
• Direction of the vehicle to a secondary inspection facility for physical examination
• Formal notification of the non-compliance to the relevant customs authority
• Exposure to financial penalties under EU customs enforcement provisions
• Potential impact on Authorised Economic Operator (AEO) status, where applicable
• Reputational and commercial consequences where customer delivery commitments are not met

For operators running time-critical or return-load operations, a single avoidable delay at the French border carries costs that extend well beyond the immediate crossing. Compliance with the ELO requirement must be treated as an operational prerequisite, not an administrative afterthought.

Recommended Action for Transport Managers and Operators

Transport managers and logistics compliance leads should take the following steps immediately to ensure that all crossings — including empty trailer movements — are fully compliant with the ELO requirement from April 2026:

• Review all despatch and pre-departure checklists to incorporate ICS2 ENS filing as a mandatory step for every crossing, including empty runs
• Confirm that your customs filing agent or software provider is configured to handle empty movement declarations under ICS2 / ELO
• Ensure that drivers are briefed on the requirement to carry a valid ELO barcode and understand that this document must be obtained before departure
• Establish a clear escalation process for instances where barcode generation is delayed or the ENS is rejected
• Verify that your EORI number and carrier registration details are current and correctly recorded in your filing system

Operators who have not yet established an ICS2 ENS filing process are advised to engage with CDUK without delay. Filing your ENS through CDUK is the mandatory first step before any ELO barcode can be created, and it is the foundation upon which compliant road freight entry into France now rests.

Filing Your ICS2 ENS and Generating Your ELO Barcode with Customs Declarations UK

Customs Declarations UK (CDUK) provides road freight operators with a single, integrated workflow for both the ICS2 Entry Summary Declaration and the ELO barcode that depends on it. Once you have completed your ENS submission through the CDUK platform and received confirmation of acceptance from French and EU customs authorities, CDUK automatically generates the ELO barcode directly within the platform — eliminating the need to manage separate systems, chase third parties, or handle manual barcode retrieval. The process is guided by a structured, plain-English wizard that walks operators through the correct data fields for each movement type, including empty trailer runs, ensuring submissions are complete and formatted to ICS2 system requirements before they are transmitted. Real-time validation catches errors and omissions before filing, reducing the risk of rejection and the cascading compliance failure that follows when a driver departs without a valid barcode. For transport managers overseeing multiple crossings, CDUK’s declaration archive provides a full audit trail of every ENS submission and its corresponding ELO output, supporting compliance reviews and any regulatory enquiries that may arise. Operators who are not yet set up on CDUK are advised to register without delay: every crossing into France now begins with a filed ENS, and every ELO barcode begins with that filing being accepted.

What UK–EU RoRo operators must do now. From 20 April 2026, every truck crossing the French Smart Border with the United Kingdom — whether loaded or empty, in either direction — must present a single barcode known as the Obligatory Logistics Envelope (ELO). Operators who arrive without a valid, closed ELO risk being directed to the orange lane for physical customs checks.

What the ELO Is and Why France Has Introduced It

The Obligatory Logistics Envelope is a digital aggregation tool developed by the French Directorate General of Customs and Indirect Taxes (DGDDI) as part of the French Smart Border regime governing UK–EU freight movements. Its purpose is straightforward: to consolidate under a single reference all of the declarative formalities that apply to a given transport unit crossing the border between France and the United Kingdom. Rather than relying on individual document checks at multiple points, French Customs can scan one barcode and verify in real time that every required declaration is in place, correctly filed, and in good standing.

The ELO is accessed and created through a nominative account on douane.gouv.fr, the French Customs portal. It is available free of charge. Once created, the ELO is closed by the operator after all relevant declaration references have been entered; this triggers automated verification of the status of each declaration. The system then generates a PDF document bearing the ELO barcode, which the driver presents at the crossing infrastructure at the ticketing or “pairing” stage.

The Declarations That Must Go Into an ELO

When a truck is loaded, the ELO must group all the EU-side formalities necessary for crossing the Smart Border. For goods moving in the UK-to-EU direction, this includes EU import declarations, transit declarations, export declarations, and — of central importance to those operating in the UK customs space — the ENS filed via ICS2 along with its Movement Reference Number.

UK formalities — specifically the Goods Movement Reference (GMR) generated under the UK’s GVMS system — are not included in the ELO. Those remain a separate UK obligation. The ELO is purely an EU-side instrument.

Who Needs to Act and What Roles Are Involved

The question of who creates the ELO is deliberately flexible. French Customs specifies that any actor within the logistics chain with the capacity to centralise all the necessary information for the border crossing may create an ELO. This can change from crossing to crossing. In practice, the responsibility will typically fall to one of the following parties:

The ICS2 ENS: The Filing That Unlocks the ELO

For many UK-based and EU-based operators moving goods by road through French Channel ports, the ICS2 ENS MRN is the filing that connects the entire chain. The ENS must be submitted to the EU’s ICS2 system ahead of the goods being loaded, generating an MRN that confirms the safety and security data has been received and accepted by EU customs. That MRN is then entered into the ELO alongside the other relevant EU customs declaration references.

Practical Steps Before 20 April 2026

Operators approaching this deadline should work through a structured preparation checklist. The priority actions are as follows:

The ICS2 ENS Filing Capability That Unlocks ELO Compliance

The Customs Declarations UK platform provides a dedicated ICS2 ENS service that enables freight forwarders, hauliers, transport companies, customs agents, and exporters to prepare and submit ENS declarations to the EU’s ICS2 system through an intuitive, guided filing workflow. The platform generates the MRN on acceptance, providing the exact reference that must be carried into the ELO.

Through CDUK’s plain-English, wizard-based workflow, operators can enter all required data elements — consignor and consignee details, commodity descriptions, transport information, routing, and safety and security data — and submit directly to the ICS2 system. Real-time validation checks identify any missing or inconsistent data before submission, reducing the risk of rejections and the delays that follow. CDUK also archives all submission data for the statutory retention period, providing an audit-ready record for any subsequent compliance review.

Conclusion: A Convergence of EU Compliance Requirements

The ELO’s mandatory enforcement from 20 April 2026 represents the convergence of several EU compliance developments that have been developing across the post-Brexit period. ICS2 has been progressively rolling out across transport modes; the French Smart Border has been operating since Brexit; and the ELO itself has been available in voluntary form for nearly a year. What changes on 20 April is that all of these elements become simultaneously required and simultaneously verified at the point of crossing.

For operators who are already filing ICS2 ENS declarations accurately and in good time, and whose EU customs declaration obligations are being managed compliantly, the ELO adds a co-ordination step rather than a substantive new burden. For those who have not yet established compliant ICS2 ENS filing, the deadline is the prompt to act without further delay.

Introduction

The Import Control System 2 (ICS2) is the European Union’s advance cargo information platform, designed to strengthen safety and security screening for all goods entering EU territory. As a mandatory pre-arrival filing regime, ICS2 applies to carriers, freight forwarders, and declarants submitting Entry Summary Declarations (ENS) across sea, air, road, rail, and postal transport modes.

Once an ICS2 declaration has been successfully submitted and accepted by the relevant customs authority, certain fields are permanently locked. These non-amendable fields form the structural backbone of each declaration and cannot be modified after submission — regardless of the reason or urgency of the required change. If any of these fields contain an error or require updating, the only available remedy is to invalidate the original declaration and submit an entirely new one.

This guide provides a complete, declaration-type-by-declaration-type reference to all non-amendable fields across the seven ICS2 declaration types currently supported by the Customs Declarations UK platform: F10, F34, F40, F41, F45, F50, and F51. Understanding these fields before you file is the single most effective step you can take to avoid costly refiling, port delays, and compliance complications.

Why Non-Amendable Fields Matter

The ICS2 regime operates on the principle of advance cargo information integrity. Customs risk assessment systems — both in the EU and the UK — use submitted ENS data to perform pre-arrival risk analysis and safety screening. Once a declaration has been accepted and risk analysis initiated, the fields that define the movement’s fundamental identity cannot be changed without compromising that analysis.

The practical consequences of filing errors in non-amendable fields include:

• Delayed customs clearance while the invalidation and resubmission process is completed
• Port holds affecting cargo release and onward logistics schedules
• Potential regulatory scrutiny if frequent refilings suggest systemic data quality issues
• Additional broker or platform fees associated with reprocessing declarations
• Risk of non-compliance penalties if the required amendment window is missed

ICS2 Declaration Types: At a Glance

ICS2 uses a structured set of declaration type codes to differentiate between transport modes, operator types, and filing complexity. Each code carries its own set of mandatory data requirements, filing timelines, and — critically — non-amendable fields. The seven declaration types covered in this guide are:

Understanding Declaration Levels

ICS2 declarations are structured across a hierarchy of data levels, each capturing a distinct layer of the cargo movement. Non-amendable fields appear across all four levels, and understanding this structure is essential for accurate data entry before submission.

Non-Amendable Fields by Declaration Type

The tables below set out the non-amendable fields for each ICS2 declaration type. Fields are grouped by declaration level. Any field listed here cannot be corrected via an amendment — the entire declaration must be invalidated and a fresh ENS submitted if a change is required.

F10 — Maritime Full ENS

Full Entry Summary Declaration for maritime/sea transport. Used by shipping lines and maritime agents for all sea-borne cargo entering UK waters.

F34 — Air Simplified ENS (Express Couriers)

Simplified Entry Summary Declaration for air transport, used predominantly by express courier operators and postal services handling air cargo.

F40 — Road Transport ENS

Entry Summary Declaration for road transport movements. Used by hauliers, road freight operators, and logistics companies moving goods by truck or road vehicle.

F41 — Rail Transport ENS

Entry Summary Declaration for goods transported by rail. Applies to rail freight movements, including those transiting through the Channel Tunnel.

F45 — Postal ENS

Entry Summary Declaration for postal consignments. Used by postal operators and designated universal service providers handling international mail and parcels.

F50 — Maritime Simplified ENS (Transport Operator)

Simplified Entry Summary Declaration for maritime transport operators. This declaration type is submitted by carriers and shipping lines where a simplified filing regime applies.

F51 — Air Full ENS

Full Entry Summary Declaration for air transport. Used by airlines and air cargo operators for comprehensive pre-arrival safety and security data submissions.

Cross-Declaration Comparison: Non-Amendable Fields

The matrix below provides a at-a-glance comparison of non-amendable fields across all seven ICS2 declaration types. A tick (✓) indicates the field is non-amendable for that declaration type.

Field Reference: What Each Non-Amendable Field Means

The following section provides a brief explanation of each non-amendable field, to help declarants understand why these fields are structurally locked and what data they contain.

Specific Circumstance Indicator

Identifies the specific legal basis or circumstance under which the ENS is being lodged, such as a re-entry, a diversion, or a presentation notification scenario. This code defines the regulatory context of the entire declaration and cannot be altered post-submission.

Representative

Records whether the filing is being made by the operator in their own right or via a representative acting on their behalf. The representative status code is a fundamental element of the declaration’s legal identity.

Representative Identification Number

The EORI number or equivalent identifier of the representative lodging the declaration. As the filing party’s legal identity, this cannot be changed once the declaration is submitted.

Identification Number (Active Border Transport Means)

The unique identifier of the transport means actively crossing the border — such as the IMO number of a vessel or the registration of a vehicle. This field ties the declaration to a specific physical movement.

Mode of Transport (Active Border Transport Means)

Specifies the mode of transport crossing the customs frontier (e.g., sea, road, air, rail). As the fundamental identifier of the transport category determining the declaration type itself, this field is immutable.

Mode of Transport (Active Border Transport Means)

Specifies the mode of transport crossing the customs frontier (e.g., sea, road, air, rail). As the fundamental identifier of the transport category determining the declaration type itself, this field is immutable.

Conveyance Reference Number

The reference number assigned to the specific conveyance or journey — for example, a train number for rail movements. This uniquely identifies the physical transport event.

Re-entry Indicator

Flags whether the goods constitute a re-entry into the customs territory following a previous departure. This indicator affects risk assessment and cannot be amended retrospectively.

Customs Office of First Entry Reference Number

Identifies the customs office where the goods will first enter the customs territory. This field drives routing and risk analysis; changing it would invalidate the entire risk assessment.

Split Consignment Indicator

Indicates whether the consignment is being split across multiple declarations. This structural indicator affects how customs systems link related filings and cannot be changed post-submission.

Previous MRN

The Movement Reference Number of a preceding declaration to which this filing relates — for example, in split consignment or diversion scenarios. Altering this would break the audit trail linking declarations.

Declarant Identification Number

The EORI or identifier of the declarant responsible for lodging the ENS. As the legal owner of the filing, this cannot be amended.

Customs Office of First Entry Reference Number

Identifies the customs office where the goods will first enter the customs territory. This field drives routing and risk analysis; changing it would invalidate the entire risk assessment.

Carrier Identification Number

The EORI or identifier of the carrier responsible for the transport. This is a core structural element at master level and cannot be changed without invalidation.

Transport Document Number (Master Level)

The number of the master transport document — such as the master bill of lading or master airway bill — that identifies the entire consignment. This is a primary key in the declaration’s data structure.

Transport Document Number (House Level)

The number of the house transport document for individual shipments within a consolidated load. Like the master document number, this is a structural identifier that cannot be amended.

Goods Item Number

A sequential number identifying individual goods items within the declaration. Once assigned and submitted, this cannot be renumbered, as downstream risk systems reference items by this number.

What To Do When a Non-Amendable Field Contains an Error

Discovering an error in a non-amendable field after submission requires a specific course of action. The process must be completed promptly to avoid cargo delays, particularly where the vessel, aircraft, or road vehicle is in transit or approaching the port of first entry.

Best Practices for Avoiding Non-Amendable Field Errors

Given that errors in non-amendable fields require full invalidation and resubmission, prevention is significantly more efficient than correction. The following practices reduce the risk of non-amendable field errors before submission.

Filing ICS2 Declarations with Customs Declarations UK

Customs Declarations UK supports the full range of ICS2 declaration types, including F10, F34, F40, F41, F45, F50, and F51, for all transport modes. The platform is designed to make accurate ENS filing accessible to carriers, freight forwarders, express operators, and postal operators of all sizes, without requiring deep technical expertise in ICS2 data structures.

Key capabilities of the Customs Declarations UK platform for ICS2 include:

• Guided declaration wizards that walk users through every required field at each declaration level, with contextual help and validation prompts throughout
• Real-time pre-submission validation that catches data errors — including in non-amendable fields — before the declaration is transmitted to customs authorities
• Support for all seven ICS2 declaration types across sea, air, road, rail, and postal transport modes
• Reusable templates and cloning functionality to accelerate repeat filings on established lanes and routes
• Bulk upload via CSV or Excel for high-volume operators managing large numbers of ENS filings simultaneously
• Secure cloud-based archive of all submitted declarations, MRNs, and related documentation for the full statutory retention period
• Invalidation and resubmission workflow support, enabling operators to manage the refiling process efficiently when a non-amendable field error is identified

By combining structured data entry workflows with robust pre-transmission validation, Customs Declarations UK significantly reduces the likelihood of non-amendable field errors reaching the submission stage — helping operators maintain clean declaration records and avoid the operational disruption of invalidation and resubmission.

Conclusion

Understanding which fields cannot be amended after an ICS2 declaration has been accepted is one of the most operationally significant areas of knowledge for any ENS filer. Non-amendable fields span all four declaration levels — header, master, house, and goods item — and vary in number and composition across the seven declaration types.

The most consistent non-amendable fields across all declaration types are the Specific Circumstance Indicator, Representative details, Mode of Transport, Re-entry Indicator, Declarant Identification Number, Customs Office of First Entry Reference Number, and Carrier Identification Number. Additional fields — including transport document numbers, split consignment indicators, previous MRNs, and goods item numbers — apply to specific declaration types as set out in the tables above.

By ensuring that all non-amendable fields are accurately populated before submission — drawing on verified source documents, validated EORI numbers, and confirmed transport references — ICS2 filers can avoid the significant operational and compliance cost of invalidation and resubmission. The Customs Declarations UK platform supports this objective through guided workflows, real-time validation, and comprehensive declaration management tools across all supported ICS2 declaration types.

Based on the official notice issued by the French General Directorate of Customs and Indirect Taxes (DGDDI), 16 February 2026

Introduction

The French customs authority (Direction générale des douanes et droits indirects) has issued an updated operational notice addressing how Entry Summary Declarations (ENS) must be completed and submitted through ICS2 for goods crossing the Brexit Smart Border between the United Kingdom and France. This notice, dated 16 February 2026, applies to all operators crossing the Smart Border — regardless of which EU Member State they connect through — and carries significant practical implications for carriers, hauliers, freight forwarders, and logistics operators handling Ro-Ro and ferry movements.

The guidance arrives at a pivotal moment. ICS2 has been fully operational in France since 1 January 2026, marking the end of the French transition period. With the Obligatory Logistics Envelope (ELO) set to become mandatory in spring 2026, operators who have not yet aligned their ENS filing workflows with these updated requirements need to act without delay.

This guide translates the official French notice into a clear and practical reference, covering ENS completion rules, transport data fields, ELO integration, and how to use the Customs Declarations UK platform for compliant ICS2 submissions.

1. Background: ICS2 at the Brexit Smart Border

ICS2 (Import Control System 2) is the EU’s advance cargo information and risk analysis platform, mandatory for non-Union goods entering the EU customs territory (EUCT). Since 1 April 2025, ICS2 has been operational for goods entering the EUCT by truck, train, or as unaccompanied trailers on ships. France completed its ICS2 transition on 1 January 2026, at which point the system became fully effective for all cross-Channel movements.

The Brexit Smart Border, managed by the French SI Brexit system, processes the majority of UK-EU freight flows — principally trucks transported on Eurotunnel rail shuttles and ferry vessels operating between UK and French ports. While ICS2 is a pan-European system, the technical characteristics of the Smart Border require specific adaptations in how ENS declarations are structured and submitted, and these adaptations apply to every operator crossing this border, not only those connected via France.

2. ENS Filing Requirements: Transport Mode Codes

One of the most important — and frequently misunderstood — aspects of ENS filing at the Brexit Smart Border concerns the transport mode codes. The Smart Border is managed by the SI Brexit system, which does not support rail transport mode code 2. This creates a specific coding requirement that differs from what operators might expect for Eurotunnel shuttle movements.

The correct mode codes to use in the ENS are as follows:

• For trucks transported through the Channel Tunnel on a rail shuttle, operators must enter transport mode code 3 (road transport), not code 2 (rail). Although the active means of transport is technically a rail shuttle, the SI Brexit system cannot process code 2, and its use will cause processing failures.
• For trucks or unaccompanied trailers transported by ferry across Channel or North Sea routes, operators must enter transport mode code 1 (maritime transport).

This distinction is fundamental. Operators who have been filing with incorrect mode codes should review their processes immediately to ensure compliance with the updated requirements.

3. Active Means of Transport at the Border

The active means of transport is a mandatory data field in the F50 ENS dataset. How this field is completed depends on the mode of crossing.

For ferry crossings, the active means of transport must be identified using an IMO number — the internationally recognised ship identification number. Because ferries operate on frequent, regular rotations and operators must submit their ENS before presenting the transport unit at the ferry terminal, it is not always possible to know in advance which specific vessel will be used. French customs and DG TAXUD have acknowledged this practical constraint and confirmed a compliant workaround: operators must select an IMO number from the official list provided by French customs that corresponds to a vessel operating on the relevant route. The IMO entered does not need to match the exact ferry ultimately used — it serves solely to allow the ENS to be lodged in ICS2 and to trigger the risk analysis. Critically, once an IMO number has been entered, it must not be subsequently modified.

All ferry companies operating on the Brexit Smart Border routes have cooperated with this arrangement and have each provided at least one IMO number per route to assist operators with ICS2 compliance. The official list of IMO numbers by company and route is reproduced at the end of this guide.

For rail shuttle crossings through the Channel Tunnel, the active means of transport field is optional for the F50 dataset. Where it is provided, operators should enter the front number plate of the truck.

4. Passive Means of Transport at the Border

Regardless of whether the truck is loaded onto a ferry or a Channel Tunnel rail shuttle, the passive means of transport must always be declared in the ENS using the truck’s registration number plate. The specific plate to use varies by scenario:

For unaccompanied trailers on ferries (maritime F10 to F17 datasets), the back number plate of the trailer is used. For trucks on Ro-Ro vessels (road F50 dataset), the front number plate of the truck is required. For trucks on Channel Tunnel rail shuttles (road F50 dataset), the front number plate of the truck is again required.

This information is summarised in the official ENS completion table issued by French customs, reproduced in Annexe 2 of the original notice.

5. Unaccompanied Trailers (RNA): Specific Requirements

For unaccompanied trailers transported on ferries, the maritime ENS dataset rules apply in full. Operators must enter an IMO number from the official list corresponding to their route, in the same manner as for combined transport by ferry. The passive means of transport is identified by the trailer’s number plate.

6. ELO Integration: The Obligatory Logistics Envelope

The ELO (Enveloppe Logistique Obligatoire) is a digital document holder that consolidates all declarative reference numbers and cargo information for a given crossing into a single, scannable barcode. Its purpose is to secure and streamline the processing of goods at the Smart Border. ELO will become mandatory in spring 2026, but operators who have already migrated to ICS2 are required to use ELO at the Smart Border from the moment of that migration — they should not wait for mandatory enforcement.

The practical workflow is as follows. Once the ENS has been accepted in ICS2 and a Movement Reference Number (MRN) has been issued, that MRN must be integrated into the operator’s ELO. The ELO then generates a barcode that the truck driver presents at check-in with the ferry company. When the barcode is scanned at pairing, it triggers the processing of all declarations contained in the ELO, including the ENS, simultaneously.

This sequence has an important implication for timing. The ENS must be submitted to ICS2 — and the MRN obtained — before the driver arrives at the ferry terminal for check-in. Operators must therefore submit ENS declarations comfortably ahead of the minimum deadlines prescribed by EU legislation, leaving sufficient time to generate the ELO barcode. Late or last-minute ENS submissions risk disrupting the entire crossing process.

The SI Brexit system handles customs presentation of goods on behalf of operators and notifies ICS2 directly. It also transmits the routing decision — green lane or orange lane — directly to the truck driver based on the outcome of the risk analysis. As a result, operators crossing the Brexit Smart Border are not required to submit separate presentation formalities through the French ANTES system (FR-PNTS).

Operators should also note that shipments arriving directly from Northern Ireland are exempt from the ENS filing requirement entirely.

7. Official IMO Reference List by Route

The following IMO numbers have been officially confirmed by ferry companies for use in ICS2 ENS filings. Operators should select the IMO corresponding to their route. Once entered in the ENS, the IMO must not be changed.

8. Filing ICS2 ENS Declarations with Customs Declarations UK

For operators seeking a structured, validated, and efficient pathway for ICS2 ENS submissions, the Customs Declarations UK (CDUK) platform provides a fully integrated ICS2 solution designed to meet exactly these operational requirements.

CDUK supports all ENS dataset types relevant to the Brexit Smart Border, including the maritime F10 to F17 series for unaccompanied trailers and ferry movements, and the road F50 dataset for Ro-Ro combined transport through the Channel Tunnel. The platform’s step-by-step filing wizards guide operators through each mandatory data field in plain English — including transport mode code selection, IMO number entry for active means of transport, and vehicle registration plate fields for passive means of transport — reducing the risk of the field-level errors that are the most common cause of ENS rejections and border delays.

Within CDUK, operators can set up carrier and consignor profiles once and reuse them across multiple declarations, significantly reducing data entry time on high-frequency routes such as Dover–Calais or Dover–Dunkerque. For operations involving large volumes of Ro-Ro movements, bulk upload capability via CSV or Excel allows entire batches of ENS filings to be prepared and submitted efficiently, rather than declaration by declaration.

The platform performs real-time compliance validation before each submission reaches ICS2, catching issues such as missing IMO numbers, incorrect transport mode codes, or mismatched dataset fields before they cause a processing failure. On acceptance, each ENS is issued an MRN that operators can immediately integrate into their ELO, ensuring the barcode required for Smart Border crossing can be generated without delay. All submitted declarations are archived securely within CDUK for the statutory retention period, maintaining a complete audit trail for both regulatory and operational purposes.

For operators managing the transition to mandatory ELO requirements in spring 2026, CDUK provides the underlying declaration infrastructure needed to generate timely MRNs — the essential prerequisite for ELO barcode generation. Filing through CDUK therefore directly supports the end-to-end Smart Border crossing workflow, from ENS submission through to driver check-in.

To explore the CDUK ENS service and begin filing ICS2 declarations, visit the Customs Declarations UK platform at www.customs-declarations.uk.

9. Key Actions for Operators: A Practical Summary

The updated French customs guidance makes clear that several operational changes are required for all operators crossing the Brexit Smart Border. The following actions should be completed without delay.

Transport mode codes must be reviewed and corrected in all ENS templates. Code 2 (rail) is not permitted at the Brexit Smart Border. Channel Tunnel Eurotunnel movements require code 3 (road); ferry movements require code 1 (maritime).

IMO numbers from the official list must be incorporated into ENS filing workflows for all ferry routes. The correct IMO should be selected by route, entered in the active means of transport field, and must not be modified after entry.

Vehicle registration plates must be entered correctly in the passive means of transport field for all movements — trailer back plate for unaccompanied trailers on ferries, and truck front plate for combined transport by ferry or rail shuttle.

ENS submissions must be submitted well ahead of the minimum regulatory deadlines to allow MRN generation and ELO barcode creation before the driver reaches the ferry terminal.

ELO integration must be in place and operational for all operators already filing through ICS2, as it is required from the point of ICS2 migration and will become formally mandatory in spring 2026.

Operators moving goods directly from Northern Ireland do not need to file an ENS and should confirm this exemption applies to their specific flows.

Conclusion

The updated guidance from French customs represents an important operational clarification for every business running freight across the UK-EU Smart Border. With ICS2 now fully live in France, ELO approaching mandatory status, and the specific transport mode coding rules confirmed in detail, there is no remaining ambiguity about what is required. Operators who align their ENS filing processes with these requirements now — using validated platforms like Customs Declarations UK to manage submission accuracy, MRN generation, and declaration archiving — will be best positioned for compliant, efficient crossings as the Smart Border environment continues to develop throughout 2026.

The most pressing compliance deadline for traders operating across European Union borders arrives on February 3, 2026, when Import Control System 2 (ICS2) version 3 messaging becomes mandatory and version 2 is permanently decommissioned. This transition affects all Entry Summary Declaration (ENS) submissions for goods entering or transiting the EU, representing a fundamental shift in how safety and security data must be structured and transmitted. Economic operators who fail to implement version 3 messaging in time face significant operational disruption, potential border delays, and financial penalties.

Understanding the Version 3 Transition and Its Immediate Implications

The European Commission has been unequivocal in its guidance: any ENS declarations lodged using ICS2 version 2 prior to February 3, 2026 cannot be amended after that date using the legacy message format. Instead, these declarations must be invalidated and re-lodged using version 3 messaging standards. This creates a hard cutover point that requires traders, carriers, freight forwarders, and customs software providers to complete their technical implementations well before the deadline. The Commission has strongly urged all economic operators to implement version 3 capabilities as early as possible to avoid last-minute technical failures and the cascading delays that inevitably follow when entire supply chains attempt simultaneous system changes.

For businesses managing regular EU-bound shipments, this deadline demands proactive planning rather than reactive scrambling. The transition is not merely a technical update; it reflects the EU’s broader strategy to enhance pre-arrival risk assessment capabilities, improve data quality at the point of entry, and create more granular visibility over goods movements across member states. Version 3 messaging introduces refined data fields, stricter validation rules, and enhanced interoperability requirements that align with the full rollout of ICS2 Release 3 functionality. Customs Declarations UK platform is already compatible with ICS2 Version 3, and can support all types of ICS2 declarations.

GVMS Users: Immediate Action Required for Post-January 1 Movements

For traders and carriers using the Goods Vehicle Movement Service (GVMS) to manage roll-on/roll-off (RoRo) movements between Great Britain and the EU, the transition to ICS2 messaging carries immediate operational consequences. All movements submitted after December 31, 2025 must use the updated “Start a Goods Movement” menu option, selecting either “RoRo Unaccompanied [ICS2]” or “RoRo Accompanied [ICS2]” depending on the nature of the shipment. The legacy “RoRo (Accompanied / Unaccompanied)” option remains temporarily visible in the GVMS interface for technical reasons, but it must not be used for any movements initiated in 2026 or later. Selecting the wrong option will result in declarations being rejected by border systems, leading to vehicle holds and potential missed sailing slots.

GVMS users should update their internal standard operating procedures, driver instructions, and dispatch checklists to reflect the new menu selection requirements. Where GVMS access is delegated to third-party logistics providers or hauliers, clear communication is essential to ensure all parties understand the change and adopt the correct workflow immediately. The risk of accidental legacy submissions is highest during the first weeks of January, when operational muscle memory and automated processes may default to the old menu path. Establishing clear verification steps—such as requiring supervisors to review the first five movements of each new month—can prevent costly errors during this transitional period.

How Customs Declarations UK Supports ICS2 Version 3 Compliance

Customs Declarations UK has integrated full ICS2 version 3 messaging capabilities across its platform to ensure clients can file compliant Entry Summary Declarations for all movement types—whether goods are traveling from Great Britain to the European Union or moving between EU member states. The CDUK platform supports the complete spectrum of ENS filing scenarios.

The platform’s guided workflow automatically maps user-entered commercial data into the correct ICS2 version 3 message format, eliminating the need for declarants to manually interpret technical specifications or construct XML payloads. Real-time validation checks ensure that all mandatory data elements are captured, that value ranges conform to EU requirements, and that cross-field dependencies are satisfied before submission. This proactive error detection significantly reduces the risk of rejection at the point of transmission, allowing traders to resolve issues while goods are still in their control rather than discovering problems when vehicles are queued at the port.

Turning Compliance into Operational Advantage

The ICS2 version 3 mandate represents more than a regulatory obligation; it offers an opportunity to modernize customs filing workflows, eliminate inefficiencies, and establish a foundation for future EU trade requirements. Businesses that approach the transition strategically—by investing in capable platforms like Customs Declarations UK, training their teams thoroughly, and establishing robust data governance practices—will find themselves better positioned not only to meet the February 3 deadline but to handle subsequent regulatory changes with agility and confidence. Proactive compliance today reduces risk, protects cash flow, and ensures that cross-border supply chains continue to operate without disruption as European customs systems evolve.