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.

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.

The Import Control System 2 for road and rail freight reached a critical juncture on January 1, 2026, when the transition period officially ended and the European Union’s enhanced pre-arrival security regime moved into its final implementation phase. However, contrary to expectations of uniform enforcement across all member states, the practical reality is a fragmented compliance landscape characterized by country-specific derogations, divergent enforcement timelines, and technical migration requirements that demand careful operational planning. For UK carriers, hauliers, freight forwarders, and express operators moving goods into the EU, understanding which member states are enforcing ICS2 immediately and which have granted temporary relief until June 1, 2026 is now essential to avoid border delays, rejection of consignments, and compliance failures.

Starting Jan 1^st 2026, shipments without Entry Summary Declarations lodged in ICS2 now face compliance complications in member states that have begun enforcement. The guidance emphasized that the end of the transition period does not mean uniform application across the EU, and economic operators must verify enforcement status on a country-by-country basis. This fragmentation reflects the operational challenges member states face in connecting national customs systems to the EU’s centralized ICS2 infrastructure, training staff, and managing the volume of advance data flowing through the new system. While the regulatory obligation exists at the EU level, practical enforcement depends on national readiness, creating a two-tier compliance environment that will persist until mid-2026.

Understanding ICS2 and its strategic purpose

The Import Control System 2 is the European Union’s modernized platform for processing Entry Summary Declarations, which provide advance cargo information to customs and border authorities for safety and security risk analysis before goods arrive in the EU customs territory. ICS2 replaced the legacy ICS system with a more sophisticated data model designed to capture granular details about shipments, consignors, consignees, and goods descriptions earlier in the logistics chain. The system enables risk-based targeting of high-risk consignments while facilitating clearance of compliant cargo, supporting the EU’s dual objectives of secure borders and efficient trade facilitation.

ICS2 operates in a phased rollout aligned with different transport modes and shipment profiles. Release 1, launched in March 2023, covered postal and express consignments. Release 2, which became mandatory from March 1, 2024, extended to air cargo. Release 3, the subject of the January 1, 2026 deadline, applies to maritime, road, and rail freight. The complexity of Release 3 lies in the diversity of transport modes and business models it covers, from accompanied trailers crossing borders by road to unaccompanied containers moving via rail freight corridors. Each mode has distinct data requirements, filing timelines, and operational workflows, making implementation more challenging than earlier releases.

The Entry Summary Declaration under ICS2 must be lodged before goods are brought into the EU customs territory, with specific timeframes varying by transport mode. For road freight, the ENS is typically lodged before departure or at the moment the vehicle enters EU territory via a border crossing point. For rail freight, advance notice requirements depend on whether the service is scheduled or ad hoc. Maritime freight entering EU ports requires ENS filing sufficiently in advance to allow risk analysis before arrival. The system assigns a Master Reference Number to each ENS, which travels with the shipment and is referenced in subsequent customs declarations and transport documentation.

The fragmented enforcement landscape

Full ICS2 implementation is now required in Austria, Belgium, Cyprus, Czech Republic, Germany, Denmark, Luxembourg, Malta, Netherlands, Portugal, Sweden, and Slovenia. Bulgaria and Estonia made ICS2 mandatory from January 1, 2026, joining the group of member states enforcing the regime without derogation. These countries have completed the technical integration of their national customs systems with the EU’s Shared Trader Interface and Trader to Customs interface, trained operational staff, and activated enforcement protocols. Carriers and economic operators moving goods into these member states must lodge compliant ICS2 Entry Summary Declarations or risk refusal of entry, penalties, and disruption to onward transport.

Crucially, temporary derogations until June 1, 2026 apply in Spain, Finland, France, Greece, Hungary, Ireland, Italy, Lithuania, Northern Ireland, Croatia, Latvia, Poland, Romania, and Slovakia. These derogations permit continued use of legacy ENS filing methods or provide grace periods during which non-compliance will not result in immediate penalties. However, the scope and interpretation of these derogations vary. France, for example, confirmed that it began enforcing ICS2 ENS for road and rail freight from January 1, 2026 despite appearing on derogation lists, reflecting a policy decision to commence enforcement ahead of the formal June deadline. This creates confusion for operators who assumed French routes would remain under transitional arrangements until mid-year.

The practical implication of this fragmented landscape is that carriers must maintain parallel compliance strategies depending on destination member state. A haulier operating a route from the UK to Germany via France must ensure that ICS2 ENS filings are compliant for both France and Germany, even though other member states on alternative routes might still accept legacy filings. This multiplies administrative complexity and requires logistics planning systems to track enforcement status by destination and adjust filing workflows accordingly. For businesses operating trans-European networks, the lack of uniform enforcement creates operational friction and increases the risk of inadvertent non-compliance when staff apply incorrect assumptions about which member states are enforcing the new regime.

The critical February 3 deadline and ICS2 version 3 messaging

A separate but equally important compliance milestone arrives on February 3, 2026, when the mandatory transition to ICS2 version 3 messaging takes effect and version 2 is decommissioned. This technical migration affects all economic operators currently using ICS2, regardless of member state enforcement status. Economic operators who have been lodging ENS filings using version 2 messaging standards cannot amend those filings after the February 3 cutoff. Any changes to a version 2 filing after that date require invalidation of the original entry and re-lodging using version 3 message formats.

The distinction between version 2 and version 3 messaging relates to the technical schema and data structure used to transmit ENS information to the ICS2 system. Version 3 represents a refinement of data fields, validation rules, and response message formats developed through operational experience and stakeholder feedback during the initial rollout phases. The migration ensures that all economic operators are working with the same technical standard, improving system performance and reducing the risk of processing errors caused by inconsistent data formats. However, it also imposes a hard cutoff that requires software providers, customs brokers, and in-house filing systems to complete upgrades by the February deadline.

For businesses using commercial customs software or cloud-based platforms such as Customs Declarations UK, the responsibility for technical migration typically rests with the software provider, who updates the underlying message generation and validation engines. Users should verify that their platform has implemented ICS2 version 3 support and conduct test filings to confirm compatibility before the February 3 deadline. For businesses with in-house developed systems or direct API connections to the Shared Trader Interface, the technical migration workload is more substantial and requires internal development resources, testing, and coordination with IT teams.

The inability to amend version 2 filings after February 3 creates operational risk for shipments with long transit times or those subject to last-minute changes. If a consignment’s details change after the ENS has been lodged in version 2 and the deadline has passed, the only recourse is to invalidate the entire filing and submit a new version 3 ENS. This introduces delay, creates additional administrative work, and may trigger re-assessment of risk scores if the new filing is processed differently by the ICS2 risk analysis engine. Businesses should therefore prioritize migration to version 3 messaging well in advance of the deadline to minimize exposure to these scenarios.

Stop words compliance and goods descriptions

The European Commission also updated the ICS2 stop words list effective February 2, 2026, introducing additional terms that are prohibited in goods descriptions because they are too generic, ambiguous, or uninformative for risk analysis purposes. Stop words are terms such as “general cargo,” “samples,” “personal effects,” or “miscellaneous goods” that provide no meaningful information about the actual nature of the shipment. ICS2 validation rules automatically reject ENS filings that contain stop words, requiring re-submission with more specific descriptions.

The updated stop words list reflects operational experience from earlier ICS2 releases and incorporates feedback from customs authorities about descriptions that hinder effective risk assessment. Economic operators must review their standard goods descriptions and product catalogs to ensure compliance with the expanded list. Common pitfalls include using trade names without specifying the actual product category, using abbreviations that are not universally understood, or providing only generic functional descriptions without identifying the material composition or intended use. Best practice is to provide clear, specific descriptions that include material type, function, and sufficient detail for a customs officer to understand what is being imported without requiring supplementary documentation.

Stop word compliance is particularly challenging for mixed-load shipments, consolidated freight, and groupage services where a single trailer or container carries multiple consignments for different consignees. Each line item within the ENS must have a compliant description, and the consolidation layer must accurately reflect the relationship between master and house-level data. Freight forwarders and groupage operators often manage this complexity by implementing description libraries, automated validation checks, and staff training programs to ensure that customer-provided descriptions are enhanced or corrected before submission to ICS2.

Practical compliance strategies for multi-member state operations

Managing ICS2 compliance across a fragmented enforcement landscape requires systematic planning, real-time intelligence on member state enforcement status, and flexible operational workflows. Carriers and forwarders should establish a compliance matrix that tracks which member states are enforcing ICS2, which have derogations, and the specific requirements or grace periods applicable in each jurisdiction. This matrix should be updated regularly as member states communicate policy changes or as enforcement practices evolve during the derogation period. Relying on static assumptions about which countries are enforcing the regime creates risk, as evidenced by France’s decision to begin enforcement despite being listed for derogation.

Operational workflows should incorporate destination-specific checks that trigger appropriate filing actions based on the enforcement status of the destination member state. For routes into fully enforcing member states, ICS2 ENS filing is mandatory and should be prioritized in the booking and dispatch process. For routes into member states with derogations, businesses may choose to file ICS2 ENS proactively to ensure consistency and to prepare for the June 1 transition, or they may continue using legacy processes where permitted. The former approach reduces future disruption and builds operational capability, while the latter defers investment but concentrates migration risk into a compressed timeline as the June deadline approaches.

Communication with customers and supply chain partners is essential. Consignors in the UK or other third countries should be informed of ICS2 requirements and should provide accurate, detailed information about shipments early enough for compliant ENS filings to be prepared. This includes complete consignee details, precise goods descriptions without stop words, correct commodity classifications, and any other data elements required by ICS2. Late or incomplete data provision creates filing delays, increases the risk of rejection, and disrupts transport schedules. Clear communication about data requirements, lead times, and the consequences of non-compliance helps align expectations and reduces friction at the operational interface.

Staff training is equally important. Personnel responsible for preparing ENS filings, whether in-house logistics teams or third-party customs brokers, must understand ICS2 data requirements, stop words rules, version 3 messaging formats, and member state enforcement variations. Training programs should include practical exercises using real or representative shipment data, walkthroughs of validation error resolution, and guidance on handling common scenarios such as amendments, invalidations, and multi-leg journeys. Investing in training reduces error rates, shortens processing times, and builds institutional knowledge that supports long-term compliance.

How Customs Declarations UK supports ICS2 compliance

Navigating the technical and operational complexity of ICS2 requires a platform that integrates ENS filing with broader customs declaration workflows and provides real-time validation against current ICS2 rules. The Customs Declarations UK platform supports ICS2 Entry Summary Declarations through a guided, wizard-based interface that captures all required data elements for road, rail, and maritime freight. The platform incorporates stop words validation, version 3 messaging support, and destination-specific compliance checks that adapt filing requirements based on member state enforcement status. Users can clone existing declarations to accelerate repeat filings, import data from spreadsheets for bulk submissions, and validate entries in real time before transmission to the Shared Trader Interface.

The platform’s archive and retrieval capabilities ensure that businesses maintain complete records of all ENS filings for audit and compliance verification purposes. As member states transition from derogation to full enforcement over the coming months, the platform’s configuration can be updated centrally to reflect changing requirements without requiring individual users to modify their workflows. This centralized management of regulatory updates reduces the burden on businesses and ensures consistent application of current rules across all filings.

Conclusion

The end of the ICS2 transition period on January 1, 2026 marks a significant milestone in the EU’s safety and security regime, but the fragmented enforcement landscape and critical technical deadlines create a complex compliance environment that demands careful navigation. With twelve member states enforcing ICS2 immediately, fourteen applying temporary derogations until June 1, and a mandatory migration to version 3 messaging by February 3, economic operators must maintain situational awareness, flexible operational workflows, and robust technical systems to ensure uninterrupted cross-border trade. The convergence of these requirements in the first half of 2026 represents a period of heightened compliance risk, but also an opportunity for businesses that invest in accurate data management, proactive filing practices, and modern declaration platforms to differentiate themselves through operational excellence and reliability. As the derogation period winds down and uniform enforcement emerges across all member states, the businesses that have embedded ICS2 compliance into their standard operating procedures will be best positioned to maintain seamless EU market access.

Introduction

The EU Import Control System 2 (ICS2) represents a significant modernization of customs security processes across the European Union and the United Kingdom. At the heart of this system lies a critical requirement: accurate, specific, and meaningful descriptions of goods, parties, and addresses in customs declarations. Generic or vague terms—known as “stop words”—are systematically rejected by the system, leading to declaration failures, delays, and potential penalties.

This comprehensive guide explains what stop words are, why they matter, how to avoid them, and provides the complete official list of unacceptable terms for goods descriptions and party information. Whether you’re filing import declarations, export declarations, or safety and security (ENS) declarations through platforms like Customs Declarations UK, understanding and avoiding stop words is essential for smooth, compliant cross-border trade.

Why Stop Words Matter: The Risk-Analysis Foundation

The legal requirement for precise goods descriptions stems from customs administrations’ need to conduct effective risk analysis on all consignments entering or leaving the EU and UK. According to the European Commission’s guidance (Commission Delegated Regulation (EU) 2015/2446), descriptions must be “precise enough for Customs services to be able to identify the goods.”

A vague description prevents customs from:

• Identifying potential security threats
• Detecting prohibited or restricted goods
• Assessing duty and tax liabilities accurately
• Prioritizing inspections effectively

When descriptions are too generic, customs must resort to physical examinations of consignments to determine their true nature—causing unnecessary delays, increased costs, and supply chain disruptions for compliant traders.

Key principle: If a commodity code is not provided (common in safety and security declarations), the plain-language description becomes the primary risk-assessment tool. Generic terms like “consolidated cargo,” “general goods,” “parts,” or “freight of all kinds” are explicitly prohibited.

Legal Framework and Official Guidance

The requirement for acceptable goods descriptions is established in:

• Commission Delegated Regulation (EU) 2015/2446 (Annex B and Annex D)
• Data Element 18 05 000 000 (‘Description of goods’)
• Data Element 6/8 (goods description for certain procedures)

The regulation states: “General terms (i.e. ‘consolidated’, ‘general cargo’, ‘parts’ or ‘freight of all kinds’) cannot be accepted. A non-exhaustive list of such general terms and descriptions is published by the Commission.”

Important note: The list of stop words is dynamic and non-exhaustive. As everyday customs practice reveals new unacceptable terms, the Commission updates the list in coordination with Member States. This means declarants must stay vigilant and apply the underlying principle: be specific, be clear, be accurate.

Fundamental Principles for Acceptable Descriptions

For Goods Descriptions:

DO:

• Use specific product names: “Men’s cotton T-shirts” instead of “Clothing”
• Include materials: “Plastic kitchenware” instead of “Kitchen items”
• Specify types: “Lithium batteries” instead of “Batteries”
• Name actual products: “Apple iPhone 13” instead of “Electronics”
• Be precise about function: “Medical ventilator” instead of “Medical equipment”

DON’T:

• Use generic categories (e.g., “Goods,” “Products,” “Items,” “Materials”)
• Reference documents (“See invoice,” “As per manifest,” “AWB”)
• Use placeholders (“Various,” “Mixed,” “Misc,” “Consolidated”)
• Enter only numbers, file extensions, or special characters
• Use company names or brand names alone without product description

For Party Information (Consignor/Consignee/Notify Party):

DO:

• Provide actual company names and registered business names
• Include complete legal entity information
• Use real addresses with proper street names and numbers

DON’T:

• Use placeholders like “N/A,” “Unknown,” “Not available,” “Please select”
• Enter “Private,” “Private individual,” “xxxx,” or “2checkout”
• Leave fields blank or use generic terms

For Addresses and Cities:

DO:

• Provide actual city names and postal codes
• Include complete street addresses
• Use officially recognized place names

DON’T:

• Use “N/A,” “Unknown,” “Not available,” “Please select”
• Enter “Private,” “xxxx,” or “2checkout”
• Use placeholder or dummy addresses

Examples: Unacceptable vs. Acceptable Descriptions

Let’s look at practical examples drawn from the official EU Commission guidance:

Complete ICS2 Stop Words Reference Table

Below is the comprehensive official list of stop words that are unacceptable in customs declarations. This list is based on the European Commission’s published guidance (TAXUD b.1(2021)1688480) and is updated regularly.

Goods Description Stop Words

Acceptable Alternatives: How to Get It Right

The Commission’s guidance provides clear alternatives for each unacceptable term. Here are key examples:

Instead of Generic Terms, Use Specific Descriptions:

“Electronics” → Specify the actual items:

• Computer monitors
• Samsung Galaxy tablets
• Apple iPhone 13 Pro
• CD players
• Desktop printers
• LED televisions

“Chemicals” → Use ECICS database names or actual chemical names:

• Sodium hydroxide (CAS 1310-73-2)
• Acetone
• Hydrochloric acid
• Isopropyl alcohol

“Food” → Describe the actual food products:

• Packaged basmati rice
• Frozen chicken breasts
• Tomato pasta sauce
• Powdered whole eggs

“Parts” → Specify what parts and for what:

• Automobile brake pads
• Laptop replacement keyboards
• Industrial pump seals
• Aircraft engine components

“Textile goods” → Be specific about fabric and use:

• Cotton fabric in rolls (grey fabric, unbleached)
• Polyester curtains (ready-made)
• Cotton bed sheets (queen size)
• Men’s cotton T-shirts (HS 6109.10)

“Machinery” → Name the actual machines:

• CNC metal-working lathes
• Industrial sewing machines (lockstitch)
• Cigarette-making machines
• Offset printing presses

Üdvözlünk mindenkit, és üdvözöljük a Vámnyilatkozatok UK Kezdő lépések útmutatójának újabb videójában. Ma végigvezetjük azokon a lépéseken, amelyek szükségesek ahhoz, hogy beléphessen, és megkezdje az import/export, valamint a biztonsági és biztonsági nyilatkozatok benyújtását a Customs Declarations UK platformon.

Szerezze meg GB EORI-számát

A kezdéshez GB EORI-számmal kell rendelkeznie. Ha még nem rendelkezik ilyennel, kérjük, keresse fel a megadott linket (gov.uk) a jelentkezéshez. Biztonsági és védelmi nyilatkozatok benyújtásához győződjön meg arról, hogy szervezetként regisztrál, nem pedig magánszemélyként, mivel magánszemélyek nem nyújthatnak be ilyen típusú nyilatkozatokat.

Hozzáférés a HMRC szolgáltatásokhoz

Miután megvan az EORI-száma, van még néhány lépés:

• Itt iratkozzon fel a Vámnyilatkozat-szolgáltatásra (CDS), ha CDS-nyilatkozatok benyújtását tervezi.
• Ha még nem tette meg, regisztráljon itt, Nagy-Britanniában, hogy elkészíthesse az Entry Summary Declaration (ENS) nyilatkozatot.

Regisztráljon a Custom Declarations UK Platformon

A regisztrációk befejezése után:

• A megadott regisztrációs hivatkozás segítségével hozza létre fiókját a Customs Declarations UK platformon.
• Ellenőrizze, hogy a helyes GB EORI-számot (vagy XI EORI-számot, ha van) adta-e meg.
• Engedélyezze a szoftvernek, hogy nyilatkozatokat nyújtson be az Ön nevében, ha bejelentkezik az Ön EORI-számához kapcsolódó gov.uk fiókkal.
• Ha még nem tette meg, frissítse a fizetési módot.
• Állítson be értesítő e-maileket, és töltse fel vállalati logóját (opcionális).

Navigálás a platformon

A regisztráció után az irányítópult nulla deklarációt jeleníthet meg, ha még csak most kezdi. A bal felső sarokban található a főmenü:

• Profil:
  – Győződjön meg arról, hogy GB EORI-száma helyes – ez különösen fontos a Biztonsági és Biztonsági Nyilatkozatok esetében.
  – Opcionálisan adjon hozzáférést a Helpdesk-hez, ha szükséges.
• Engedélyezés a HMRC-vel:
  – Kattintson a hivatkozásra, hogy engedélyezze a szoftvert HMRC-fiókjával. Győződjön meg arról, hogy az EORI-számához kötött gov.uk hitelesítő adatokkal jelentkezik be.

Végső ellenőrzések és benyújtások

• Frissítse a fizetési módot: Győződjön meg arról, hogy fizetési adatai helyesek.
• Ellenőrizze az előfizetés részleteit: Győződjön meg arról, hogy rendelkezik a szükséges szolgáltatásokhoz megfelelő előfizetéssel.
• Értesítési e-mailek: A Beállítások alatt adja meg a CDS-értesítések és a fiókfolyam-frissítések e-mail címét.
• Embléma feltöltése (opcionális): Ha szeretné, adja hozzá cége márkajelzését.

Ha készen áll a beküldésre:

• A CDS-nyilatkozatokhoz kattintson a CDS opcióra a menüben.
• A Biztonsági és biztonsági (ENS) nyilatkozatokhoz válassza az ENS nyilatkozat lehetőséget, és kövesse az értesítés elindításához szükséges lépéseket.

Ez lefedi a Customs Declarations UK platform használatának kezdő lépéseit. Köszönjük, hogy megnézte, és reméljük, hogy ez az útmutató segít az importálási/exportálási, valamint a biztonsági és biztonsági nyilatkozatok zökkenőmentes elküldésében.

Hallo allemaal, en welkom bij een nieuwe video in de Customs Declarations UK Getting Started Guide. Vandaag leiden we je door de stappen die nodig zijn om aan boord te gaan en te beginnen met het indienen van import-/export- en veiligheids- en beveiligingsaangiften op het Customs Declarations UK-platform.

Verkrijg je GB EORI-nummer

Om te beginnen moet je een GB EORI-nummer hebben. Als je er nog geen hebt, ga dan naar de verstrekte link (gov.uk) om je aan te melden. Voor het indienen van veiligheids- en beveiligingsaangiften moet je je registreren als een organisatie in plaats van als een individu, aangezien individuen dit soort aangiften niet mogen indienen.

Toegang tot HMRC-services

Zodra je je EORI-nummer hebt, zijn er nog een paar stappen:

• Abonneer je hier op de Customs Declaration Service (CDS) als je van plan bent CDS-aangiften in te dienen.
• Registreer u om een ​​Entry Summary Declaration (ENS) hier in Groot-Brittannië te doen als u dat nog niet hebt gedaan.

Registreer u op het Customs Declarations UK-platform

Na het voltooien van deze registraties:

• Gebruik de verstrekte registratielink om uw account op het Customs Declarations UK-platform aan te maken.
• Controleer of u het juiste GB EORI-nummer (of XI EORI-nummer, indien van toepassing) hebt ingevoerd.
• Autoriseer de software om namens u aangiften in te dienen door in te loggen met het gov.uk-account dat is gekoppeld aan uw EORI-nummer.
• Werk uw betaalmethode bij als u dat nog niet hebt gedaan.
• Stel e-mailmeldingen in en upload uw bedrijfslogo (optioneel).

Navigeren op het platform

Nadat u zich hebt geregistreerd, kan uw dashboard nul aangiften weergeven als u net begint. In de linkerbovenhoek vindt u het hoofdmenu:

• Profiel:
  – Bevestig dat uw GB EORI-nummer correct is, met name belangrijk voor Safety & Security Declarations.
  – Geef indien nodig eventueel toegang tot de Helpdesk.

• Autoriseren met HMRC:
  – o Klik op de link om de software te autoriseren met uw HMRC-account. Zorg ervoor dat u inlogt met de gov.uk-referenties die gekoppeld zijn aan uw EORI-nummer.

Laatste controles en indieningen

• Betaalmethode bijwerken: zorg ervoor dat uw betalingsgegevens correct zijn.
• Abonnementsgegevens controleren: bevestig dat u de juiste abonnementen hebt voor de services die u nodig hebt.
• Meldings-e-mails: geef onder Instellingen e-mailadressen op voor CDS-meldingen en accountstreamupdates.
• Logo uploaden (optioneel): voeg indien gewenst de branding van uw bedrijf toe.

Wanneer u klaar bent om in te dienen:

• Klik voor CDS-aangiften op de CDS-optie in het menu.
• Selecteer voor Safety & Security (ENS) Declarations ENS Declaration en volg de stappen om uw melding te starten.

Dat omvat de basisprincipes van het aan de slag gaan met het Customs Declarations UK-platform. Bedankt voor het kijken en we hopen dat deze gids u helpt bij het soepel indienen van uw import-/export- en veiligheids- en beveiligingsaangiften.

Bună ziua tuturor și bun venit la un alt videoclip din Ghidul introductiv al declarațiilor vamale din Regatul Unit. Astăzi, vă vom ghida prin pașii necesari pentru a vă îmbarca și a începe să trimiteți declarații de import/export și siguranță și securitate pe platforma Declarații vamale din Regatul Unit.

Obțineți numărul dvs. GB EORI

Pentru a începe, trebuie să aveți un număr GB EORI. Dacă nu aveți deja unul, vă rugăm să accesați linkul furnizat (gov.uk) pentru a aplica. Pentru a trimite Declarații de siguranță și securitate, asigurați-vă că vă înregistrați ca organizație și nu ca persoană fizică, deoarece persoanelor fizice nu le este permis să trimită aceste tipuri de declarații.

Accesați serviciile HMRC

Odată ce aveți numărul dvs. EORI, mai sunt câțiva pași:

• Abonați-vă la Serviciul de Declarații Vamale (CDS) aici dacă intenționați să depuneți declarații CDS.
• Înregistrați-vă pentru a face o declarație sumară de intrare (ENS) aici, în Marea Britanie, dacă nu ați făcut-o deja.

Înregistrați-vă pe Platforma Declarații Vamale din Marea Britanie

După finalizarea acestor înregistrări:

• Utilizați linkul de înregistrare furnizat pentru a vă crea contul pe platforma Declarații Vamale din Regatul Unit.
• Verificați dacă ați introdus corect numărul GB EORI (sau numărul XI EORI, dacă este cazul).
• Autorizați software-ul să trimită declarații în numele dvs. conectându-vă cu contul gov.uk care este asociat cu numărul dvs. EORI.
• Actualizați metoda de plată dacă nu ați făcut-o deja.
• Configurați e-mailuri de notificare și încărcați sigla companiei dvs. (opțional).

Navigarea pe platformă

Odată înregistrat, tabloul de bord poate afișa zero declarații dacă tocmai ați început. În colțul din stânga sus, veți găsi meniul principal:

• Profil:
  – Confirmați că numărul dvs. GB EORI este corect – deosebit de important pentru Declarațiile de siguranță și securitate.
  – Opțional, acordați acces la Helpdesk, dacă este necesar.

• Autorizați cu HMRC:
  – Faceți clic pe link pentru a autoriza software-ul cu contul dvs. HMRC. Asigurați-vă că vă conectați cu acreditările gov.uk legate de numărul dvs. EORI.

Verificări finale și trimiteri

• Actualizați metoda de plată: asigurați-vă că detaliile de plată sunt corecte.
• Verificați detaliile abonamentului: Confirmați că aveți abonamentele potrivite pentru serviciile de care aveți nevoie.
• E-mailuri de notificare: în Setări, specificați adresele de e-mail pentru notificările CDS și actualizările fluxului de cont.
• Încărcați sigla (opțional): dacă doriți, adăugați brandingul companiei dvs.

Când sunteți gata să trimiteți:

• Pentru Declarații CDS, faceți clic pe opțiunea CDS din meniu.
• Pentru Declarații de siguranță și securitate (ENS), selectați Declarație ENS și urmați pașii pentru a începe notificarea.

Acesta acoperă elementele esențiale pentru începerea cu platforma Declarații Vamale din Regatul Unit. Vă mulțumim pentru vizionare și sperăm că acest ghid vă va ajuta să trimiteți fără probleme declarațiile de import/export și siguranță și securitate.