Customs Explorer
⌕

Customs Explorer

EU CUSTOMS DATA HUB
IN FORCE — LEGAL FRAMEWORK PHASED IMPLEMENTATION

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.

LEGAL BASIS Regulation (EU) 2026/2108
LAST REVIEWED 5 October 2026
JURISDICTION European Union
EU CUSTOMS DATA ENVIRONMENT Conceptual architecture
ECONOMIC OPERATORS Trade data Information required for customs purposes
CUSTOMS Authorities Controls, decisions and customs information
EU ENVIRONMENT Systems & services Connected customs functions
OTHER SOURCES Relevant data Information used for customs purposes
EU Customs
Data Hub
CENTRAL DATA ENVIRONMENT
A central EU environment — introduced progressively, not an overnight replacement.
IN 30 SECONDS What matters now
01 It now has a legal basis.

The Data Hub is established by Regulation (EU) 2026/2108 under the new Union Customs Code.

02 It is not fully operational today.

The legislation provides for progressive implementation rather than immediate replacement of existing systems.

03 It changes the data model.

The architecture moves towards information being provided and processed through a shared EU customs data environment.

04 Businesses should follow the rollout.

Different categories of operators enter the new environment at different stages between 2028 and 2034.

WHAT CHANGES

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.

01 CURRENT LANDSCAPE

Procedure-centred systems

Customs information currently moves through a landscape of specialised national and EU systems serving different processes.

TRADER Economic operator
TRANSIT NCTS
EXPORT AES
SAFETY ICS2
STATUS PoUS
Different processes can require different systems, messages and access routes.
02 DATA HUB MODEL

Data-centred architecture

The new framework establishes a common EU customs data environment through which information can support multiple customs purposes and processes.

BUSINESS Trade data
CUSTOMS Authority data
SOURCES Other relevant data
COMMON ENVIRONMENT EU Customs
Data Hub
01 Customs processes
02 Risk analysis
03 Controls
04 Cooperation
The architectural direction is greater reuse and connection of customs information.
THE STRUCTURAL SHIFT Four ideas behind the new model
01
FROM Repeated submissions
TOWARDS Greater data reuse
02
FROM Separated environments
TOWARDS Connected EU data
03
FROM Document-led exchanges
TOWARDS Data-led processing
04
FROM Fragmented analysis
TOWARDS EU-level analysis
HOW THE DATA MODEL WORKS

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 PHASED
EU CUSTOMS DATA FLOW
Data moving through the customs environment
01
PROVIDE Economic
operator
Provides the information required for customs purposes.
Trader Representative
02
PROCESS EU Customs
Data Hub
Receives and processes customs information in the common environment.
Data Services
03
USE Customs
authorities
Use relevant information for customs supervision, decisions and controls.
Supervision Controls
04
REUSE & ANALYSE EU customs
functions
Supports broader analysis, risk management and customs cooperation.
Risk Analysis Cooperation
THE KEY CONCEPT

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.

TODAY’S MENTAL MODEL
Declaration / message Information packaged around a specific customs process.
DATA HUB MODEL
Customs information Data organised so that it can support the relevant customs purposes.
DATA REUSE Reuse does not mean
“submit once and forget”.
01

Information still has to be accurate, complete and available when required under the applicable customs rules.

02

Different customs processes can still require different data, events or updates.

03

The important change is the ability to use relevant information within a more connected customs data environment.

LEGAL FRAMEWORK IN FORCE
WHY THIS MATTERS

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.

OFFICIAL EU LAW Regulation (EU) 2026/2108
WHO USES THE DATA HUB

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 FUNCTION
ACTOR ROLE IN THE DATA ENVIRONMENT MAIN FOCUS
01
BUSINESS Economic operator
Provides customs information

Makes the data required for the relevant customs purposes available in accordance with the applicable rules and implementation arrangements.

GOODS PARTIES VALUE ORIGIN MOVEMENT
02
REPRESENTATION Customs representative
Acts for another person where authorised

A customs representative can perform customs-related actions for the represented person within the applicable form and scope of representation.

AUTHORITY IDENTITY DATA ACTIONS
03
MEMBER STATE Customs authorities
Supervise and apply customs rules

National customs authorities use relevant customs information for supervision, controls, decisions and the performance of customs tasks within their competence.

SUPERVISION CONTROL DECISIONS ENFORCEMENT
04
EU LEVEL EU customs functions
Supports EU-wide customs coordination

The new architecture strengthens the ability to use customs information at Union level for common risk management, analysis and cooperation.

RISK ANALYSIS COOPERATION COORDINATION
DO NOT CONFUSE ACCESS WITH RESPONSIBILITY

A shared environment does not make every actor responsible for the same thing.

01 Who owns the customs obligation? Start with the person to whom the relevant customs obligation applies.
02 Who provides or acts on the data? This may be the operator itself or an authorised representative.
03 Who uses the information? Customs authorities and relevant EU customs functions use data within their legal competences.
CUSTOMS REPRESENTATION A practical point for businesses

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 representation
LEGAL CONTEXT Roles remain legally distinct

The 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
ACCESS & INTEGRATION

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.

IMPLEMENTATION PRINCIPLE Access arrangements evolve with the rollout
ACCESS STACK Conceptual model — not a representation of a single EU interface
01
WHO ARE YOU? Identity

The customs environment must identify the person or organisation interacting with the relevant service.

Economic operator Representative Authority
02
WHAT MAY YOU DO? Authorisation & representation

Identity alone does not determine what a user may do. The applicable rights, authorisations and any representation relationship remain relevant.

Rights Delegation Representation
03
HOW DO YOU CONNECT? Access channel

Interaction may take place through user-facing services or through technical connections, depending on the customs function and implementation arrangements.

Portal / service Software System connection
04
WHERE DOES THE DATA GO? EU Customs Data Hub

The common customs data environment provides the central infrastructure through which the relevant information and customs functions are progressively organised.

Data Services Customs functions
TWO ACCESS QUESTIONS

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.

HUMAN ACCESS
User-facing interaction

A person authenticates and uses the relevant customs service according to the access arrangements available for that function.

USER ACCESS SERVICE DATA ENVIRONMENT
SYSTEM ACCESS
Software-to-system interaction

Business or customs software may interact electronically with customs services where the applicable technical specifications and interfaces provide for that connection.

SOFTWARE INTERFACE DATA ENVIRONMENT
TECHNICAL SPECIFICATION

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.

CONFIRMED
Central EU customs data environment

The legal framework establishes the EU Customs Data Hub.

CONFIRMED
Progressive implementation

The transition is phased rather than an immediate replacement of the current customs environment.

NOT YET SPECIFIED
One universal trader interface

Do not assume that every customs interaction will use one identical user interface.

NOT YET SPECIFIED
Universal API model for every customs function

Technical integration should be assessed against the specifications published for the relevant service.

FOR BUSINESSES & SOFTWARE PROVIDERS Use a four-step check
01 Identify the customs function
02 Identify the actor
03 Check the access route
04 Use the published specification
IMPLEMENTATION STATUS Legal framework ≠ final technical interface

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
IMPLEMENTATION ROADMAP

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.

LEGAL TIMELINE 2028 → 2031 → 2034
SEPTEMBER 2026
IN FORCE

New Union Customs Code

The new legal framework establishes the EU Customs Data Hub and the governance framework for its development.

LEGAL FOUNDATION Data Hub established in Union law
BY 1 JUNE 2028
CONFIRMED

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.

PREPARATION Infrastructure for the first mandatory use case
FROM 1 JULY 2028
CONFIRMED

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.

FIRST PHASE E-commerce customs environment
FROM 1 MARCH 2031
CONFIRMED

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.

TRANSITION PERIOD Existing model + voluntary Data Hub use
BY 1 FEBRUARY 2034
CONFIRMED

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.

SYSTEM MILESTONE Full Data Hub functionality
FROM 1 MARCH 2034
CONFIRMED

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.

MANDATORY PHASE Data Hub becomes the normal customs data environment
WHAT THIS MEANS TODAY

Prepare for the architecture.
Do not pretend the migration is complete.

01 Current systems still matter

Existing customs systems and procedures remain relevant during the transition and are progressively phased out.

02 2031 is a transition point

For the wider operator population, Data Hub use becomes possible before it becomes mandatory.

03 2034 is the structural change

This is when the Data Hub architecture becomes the standard route for the relevant customs information.

TRANSITION MODEL Old and new environments coexist before migration completes.
CURRENT Existing customs systems
FUTURE EU Customs
Data Hub
SOURCE STATUS Dates fixed in EU law

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
CURRENT SYSTEMS & TRANSITION

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.

TRANSITION PRINCIPLE Current systems remain relevant until migration occurs.
01 CURRENT LANDSCAPE
02 TRANSITION
03 DATA HUB ARCHITECTURE
NCTS
TRANSIT Movement under transit
CURRENT SYSTEM
FUTURE DATA ENVIRONMENT Transit information Progressively handled through the Data Hub architecture.
AES
EXPORT Export processing
CURRENT SYSTEM
FUTURE DATA ENVIRONMENT Export information Incorporated into the common customs data architecture.
ICS2
SAFETY & SECURITY Pre-arrival information
CURRENT SYSTEM
FUTURE DATA ENVIRONMENT Entry and risk data Connected to the wider EU customs data environment.
PoUS
UNION STATUS Proof of Union status
CURRENT SYSTEM
FUTURE DATA ENVIRONMENT Status information Customs information becomes part of the evolving data architecture.
DO NOT READ THE ROADMAP AS A SHUTDOWN CALENDAR

A Data Hub milestone does not automatically mean that every existing system disappears on that date.

Migration depends on the customs process, the implementation phase and the relevant technical arrangements. Businesses should continue to follow the operational requirements of the systems that apply to them until the competent authorities specify the corresponding transition.

WORKING RULE Use the system required today. Prepare for the architecture required tomorrow.
SYSTEM VS ENVIRONMENT

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.

SPECIALISED SYSTEMS
TRANSIT NCTS
EXPORT AES
ENTRY ICS2
STATUS PoUS
Function-specific environments
COMMON EU ENVIRONMENT EU Customs
Data Hub
DATA SERVICES RISK COOPERATION
Shared customs data architecture
TRANSITION STATUS Phased implementation

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
IMPLEMENTATION OBSERVATORY

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.

CUSTOMS EXPLORER METHOD Separate confirmed requirements from implementation assumptions.
DATA HUB IMPLEMENTATION REGISTER Current knowledge state
LAST REVIEWED 5 October 2026
AREA STATUS WHAT WE CAN SAY TODAY
01
LEGAL ARCHITECTURE EU Customs Data Hub
CONFIRMED

The new Union customs framework establishes the Data Hub as the central EU customs data environment.

02
TRANSITION Phased rollout
CONFIRMED

The legal framework provides for progressive implementation rather than a single immediate migration date.

03
IMPLEMENTATION Technical rollout
PLANNED

Technical capabilities must be delivered progressively to support the implementation stages defined by the legal framework.

04
USER EXPERIENCE Final trader interface
NOT YET SPECIFIED

Businesses should not assume that all customs interactions will take place through one identical portal or screen.

05
SYSTEM INTEGRATION Interfaces & APIs
NOT YET SPECIFIED

Do not assume a universal API or one technical integration model for every customs function until applicable specifications are published.

06
MIGRATION System-by-system transition
NOT YET SPECIFIED

Detailed migration arrangements must be assessed for the relevant customs process rather than inferred from the overall Data Hub timetable.

HOW TO READ THIS PAGE Status describes the evidence,
not our confidence.
CONFIRMED

Established by adopted law or sufficiently definitive official documentation.

PLANNED

Part of the official implementation direction but still dependent on future delivery or rollout.

NOT YET SPECIFIED

The available official material does not yet support a sufficiently precise operational answer.

WHAT TO WATCH NEXT

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?”.

01 ACCESS Authentication & identity

How users and organisations access the relevant Data Hub services.

02 REPRESENTATION Delegation & permissions

How representation relationships and user rights are implemented.

03 INTEGRATION System-to-system exchange

Technical specifications for software and automated data exchange.

04 DATA Data requirements

The structures, data elements and rules required for each customs function.

05 MIGRATION Existing system transition

When and how current operational environments move to the new model.

06 OPERATIONS Business readiness

What traders, representatives and software providers need to change.

CUSTOMS EXPLORER

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.

LEGAL STATUS TECHNICAL SPECS MIGRATION OFFICIAL UPDATES
DEDICATED TRACKER Follow the Data Hub
as implementation develops.
Data Hub Observatory
VERIFICATION METHOD Primary sources first

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
FREQUENTLY ASKED QUESTIONS

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.

LEGAL FRAMEWORK: IN FORCE Implementation: phased
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 roadmap
03 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 transition
04 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.

TECHNICAL DETAIL: NOT YET SPECIFIED
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.

OFFICIAL SOURCES

Verify the framework
at source.

Customs Explorer uses primary EU material for legal status, implementation milestones and future updates to this page.

CUSTOMS EXPLORER VERIFICATION How this page is maintained
01 Check primary EU law
02 Check official implementation material
03 Separate confirmed facts from open details
04 Update the living record
CONTINUE FROM HERE

Explore the wider customs transformation.

The Data Hub is one part of a wider reform of EU customs legislation, systems and operational processes.

01
AVAILABLE NOW

EU Customs Systems

Understand the digital systems already supporting transit, export, entry, Union status and other customs processes.

02
COMING NEXT

EU Customs Reform

See how the new customs framework changes governance, processes, data and the future operating model.

PLANNED
03
IMPLEMENTATION TRACKER

Data Hub Observatory

Follow technical specifications, implementation milestones, migration developments and official Data Hub updates.

PLANNED
EU CUSTOMS DATA HUB Living reference page

Legal framework in force · phased implementation · technical details monitored as official specifications develop.

LAST REVIEWED 5 October 2026