The new data layer
for EU customs.
The EU Customs Data Hub is the central data environment established by the new Union Customs Code. It is designed to progressively change how customs information is provided, processed, analysed and reused across the European Union.
Data Hub CENTRAL DATA ENVIRONMENT
The Data Hub is established by Regulation (EU) 2026/2108 under the new Union Customs Code.
The legislation provides for progressive implementation rather than immediate replacement of existing systems.
The architecture moves towards information being provided and processed through a shared EU customs data environment.
Different categories of operators enter the new environment at different stages between 2028 and 2034.
From multiple customs systems
towards a shared data environment.
The Data Hub changes the architecture behind EU customs. Instead of treating every customs process as an isolated exchange of information, the new model is designed around data that can be provided, processed and reused within a common EU environment.
Procedure-centred systems
Customs information currently moves through a landscape of specialised national and EU systems serving different processes.
Data-centred architecture
The new framework establishes a common EU customs data environment through which information can support multiple customs purposes and processes.
Data Hub
Provide the information.
Use the data across customs processes.
The Data Hub is designed around customs data rather than a sequence of isolated electronic declarations. Economic operators provide the information required for customs purposes, while the common environment supports its processing and use by customs authorities.
CONCEPTUAL FLOW — IMPLEMENTATION IS PHASEDoperator Provides the information required for customs purposes.
Data Hub Receives and processes customs information in the common environment.
authorities Use relevant information for customs supervision, decisions and controls.
functions Supports broader analysis, risk management and customs cooperation.
Think in terms of data,
not just declarations.
This is one of the most important conceptual changes in the new customs architecture. The objective is not simply to reproduce today’s declarations inside a larger IT system, but to organise customs processes around the information required by customs.
“submit once and forget”.
Information still has to be accurate, complete and available when required under the applicable customs rules.
Different customs processes can still require different data, events or updates.
The important change is the ability to use relevant information within a more connected customs data environment.
The new Union Customs Code establishes the EU Customs Data Hub as the central customs data environment and provides the legal basis for the progressive transition to this model.
One data environment.
Different roles.
The Data Hub is not designed for one type of user. Economic operators, customs representatives, national customs authorities and EU-level customs functions interact with the environment for different purposes and with different responsibilities.
ROLE → DATA → CUSTOMS FUNCTIONMakes the data required for the relevant customs purposes available in accordance with the applicable rules and implementation arrangements.
A customs representative can perform customs-related actions for the represented person within the applicable form and scope of representation.
National customs authorities use relevant customs information for supervision, controls, decisions and the performance of customs tasks within their competence.
The new architecture strengthens the ability to use customs information at Union level for common risk management, analysis and cooperation.
A shared environment does not make every actor responsible for the same thing.
The move to a common data environment does not remove the concept of customs representation. Where a representative acts for another person, the legal basis, type and scope of that representation remain relevant.
Understand customs representationThe Data Hub changes the customs data architecture. It should not be read as eliminating the legal distinctions between economic operators, representatives and customs authorities.
OFFICIAL EU LAW Regulation (EU) 2026/2108 ↗
The Data Hub is the environment.
Access is another layer.
A central customs data environment does not mean that every user will work through the same screen. Identity, authorisation, representation and technical integration determine how an actor can interact with customs services.
The customs environment must identify the person or organisation interacting with the relevant service.
Interaction may take place through user-facing services or through technical connections, depending on the customs function and implementation arrangements.
The common customs data environment provides the central infrastructure through which the relevant information and customs functions are progressively organised.
Human access and system access
are not the same thing.
Businesses should distinguish between a person using a customs service and business software exchanging information electronically. Both can be part of a digital customs environment, but their technical requirements are different.
A person authenticates and uses the relevant customs service according to the access arrangements available for that function.
Business or customs software may interact electronically with customs services where the applicable technical specifications and interfaces provide for that connection.
Do not design your integration
around assumptions.
The legal architecture and the final technical implementation are different layers. Businesses and software providers should rely on published technical specifications for the relevant service and implementation phase.
The legal framework establishes the EU Customs Data Hub.
The transition is phased rather than an immediate replacement of the current customs environment.
Do not assume that every customs interaction will use one identical user interface.
Technical integration should be assessed against the specifications published for the relevant service.
The Data Hub has a legal basis, but implementation is progressive. Technical access should therefore be assessed against the official specifications applicable to each service and rollout phase.
LEGAL BASIS Regulation (EU) 2026/2108 ↗
The Data Hub will not
arrive all at once.
The new Union Customs Code establishes a phased transition. The Data Hub becomes operational first for specific e-commerce flows, then opens more broadly on a voluntary basis before becoming the standard environment for customs data.
New Union Customs Code
The new legal framework establishes the EU Customs Data Hub and the governance framework for its development.
First required functionalities operational
The Data Hub functionalities required for the first e-commerce implementation phase must be operational no later than 1 June 2028.
First operational use
The first mandatory Data Hub use begins for the distance-sales environment covered by the new rules, including the relevant importers and IOSS-related flows specified by the Regulation.
Voluntary use expands
Other importers, exporters and holders of the transit procedure may begin using the Data Hub capabilities for the relevant customs procedures instead of relying only on the existing declaration model.
Data Hub fully operational
The functionalities of the EU Customs Data Hub provided for by the new Union Customs Code must be fully operational by this date.
Data Hub becomes the standard route
Importers, exporters and holders of the transit procedure must provide or make available the information required for the relevant customs procedure using the EU Customs Data Hub.
Prepare for the architecture.
Do not pretend the migration is complete.
Existing customs systems and procedures remain relevant during the transition and are progressively phased out.
For the wider operator population, Data Hub use becomes possible before it becomes mandatory.
This is when the Data Hub architecture becomes the standard route for the relevant customs information.
Data Hub
These milestones are based on the transitional provisions of the new Union Customs Code. They are not projections by Customs Explorer.
OFFICIAL EU LAW Regulation (EU) 2026/2108 — Article 285 ↗
What happens to NCTS,
AES, ICS2 and the other systems?
The Data Hub is a structural change, not an overnight switch. Existing national and EU customs systems continue to support customs operations during the transition while the new environment is progressively implemented.
The Data Hub should not be understood as simply another acronym in the list.
NCTS, AES, ICS2 and PoUS are associated with particular customs functions. The Data Hub represents a broader architectural layer: a common environment for customs information and services.
Data Hub
Customs Explorer treats the Data Hub as a progressive migration programme. System-specific operational instructions remain relevant until the corresponding transition is legally and technically applicable.
OFFICIAL EU LAW Regulation (EU) 2026/2108 ↗
The legal direction is clear.
Many implementation details are not.
The Regulation establishes the Data Hub and its transition timetable. But legislation does not by itself define every interface, message, access route or migration detail that businesses will eventually need.
The new Union customs framework establishes the Data Hub as the central EU customs data environment.
The legal framework provides for progressive implementation rather than a single immediate migration date.
Technical capabilities must be delivered progressively to support the implementation stages defined by the legal framework.
Businesses should not assume that all customs interactions will take place through one identical portal or screen.
Do not assume a universal API or one technical integration model for every customs function until applicable specifications are published.
Detailed migration arrangements must be assessed for the relevant customs process rather than inferred from the overall Data Hub timetable.
not our confidence.
Established by adopted law or sufficiently definitive official documentation.
Part of the official implementation direction but still dependent on future delivery or rollout.
The available official material does not yet support a sufficiently precise operational answer.
The important updates will be technical, not just legislative.
As implementation progresses, the questions that matter to businesses move from “what is the Data Hub?” to “how do we actually connect, submit, authorise and migrate?”.
How users and organisations access the relevant Data Hub services.
How representation relationships and user rights are implemented.
Technical specifications for software and automated data exchange.
The structures, data elements and rules required for each customs function.
When and how current operational environments move to the new model.
What traders, representatives and software providers need to change.
Data Hub Observatory
A dedicated Customs Explorer area will track the transition from legislation to operational implementation: milestones, technical specifications, access models, system migration and official updates.
Customs Explorer updates implementation status only when supported by EU legislation, European Commission material or other authoritative customs documentation. Unpublished technical assumptions are not presented as confirmed requirements.
PRIMARY LEGAL SOURCE Regulation (EU) 2026/2108 ↗
EU Customs Data Hub:
practical questions.
The Data Hub is already part of the EU customs legal framework, but implementation is progressive. These answers distinguish the adopted framework from technical arrangements that still depend on future implementation.
01 Is the EU Customs Data Hub operational today?
Not as the fully operational customs environment described by the new framework. The EU Customs Data Hub has been established in Union law, but its implementation follows a phased timetable.
02 When will businesses start using the Data Hub?
The transition is staged. The first operational phase is linked to the new e-commerce customs environment in 2028. Wider voluntary use follows from 1 March 2031, while the broader mandatory phase begins from 1 March 2034 for the operators and procedures covered by the Regulation.
See the implementation roadmap03 Will NCTS, AES, ICS2 and other customs systems disappear?
Do not treat the Data Hub timetable as an automatic shutdown calendar for every existing customs system. Current systems remain operationally relevant during the transition, and migration must be assessed for the specific customs function and implementation phase.
Understand the system transition04 Is the Data Hub simply one new EU customs portal?
No. It is better understood as a common EU customs data environment rather than simply as one website replacing every existing customs interface. The way individual users, businesses and software systems interact with that environment depends on the relevant service and technical implementation.
05 Will businesses need new customs software?
Businesses should not assume a specific software requirement before the relevant technical specifications are available. Existing customs software, interfaces and internal processes may need to evolve as Data Hub services are implemented, but the practical impact depends on the customs functions used by each business.
06 What should businesses do now?
Continue complying with the customs systems and procedures applicable today, while following official implementation developments relevant to your operations. Businesses with significant customs activity should also identify where customs data originates internally and which software, representatives and processes depend on it.
Verify the framework
at source.
Customs Explorer uses primary EU material for legal status, implementation milestones and future updates to this page.
Primary legal text establishing the new Union customs framework and the EU Customs Data Hub.
European Commission information on the reform and the development of the future EU customs environment.
Explore the wider customs transformation.
The Data Hub is one part of a wider reform of EU customs legislation, systems and operational processes.
EU Customs Systems
Understand the digital systems already supporting transit, export, entry, Union status and other customs processes.
EU Customs Reform
See how the new customs framework changes governance, processes, data and the future operating model.
Data Hub Observatory
Follow technical specifications, implementation milestones, migration developments and official Data Hub updates.
Legal framework in force · phased implementation · technical details monitored as official specifications develop.