Customs Explorer
⌕

Customs Explorer

IMPLEMENTATION OBSERVATORY
CONFIRMED IMPLEMENTATION IN PROGRESS

EU Customs Data Hub
Implementation Observatory

Track what is legally established, what is being built, which implementation milestones come next and which technical details are not yet specified.

LEGAL BASIS Regulation (EU) 2026/2108
CURRENT PHASE Foundation & implementation
NEXT MAJOR OPERATIONAL PHASE 2028 · E-commerce
LAST REVIEWED 5 October 2026
DATA HUB OBSERVATORY Implementation state
TRACKING
EU CUSTOMS DATA
HUB
IMPLEMENTATION
01 LEGAL Framework IN FORCE
02 IMPLEMENTATION Rules IN PROGRESS
03 TECHNICAL Specifications DEVELOPING
04 OPERATION Deployment 2028 → 2034
LAW Established
RULES Developing
TECH Developing
LIVE Phased
LAW SPECIFICATION IMPLEMENTATION OPERATION
CURRENT IMPLEMENTATION SNAPSHOT

Where does the Data Hub
actually stand today?

5 OCTOBER 2026 The legal architecture is established. Operational deployment is still ahead.

The Data Hub is now a confirmed part of the new Union Customs Code. The next stage is the development of the implementing framework, technical specifications and functionality required for phased deployment.

01
LEGAL FRAMEWORK EU Customs Data Hub established in EU law
REFERENCE Regulation (EU) 2026/2108
IN FORCE
02
DATA HUB FUNCTIONS Core legal functions defined
REFERENCE Union Customs Code · Article 38
CONFIRMED
03
TRANSITION 2028 / 2031 / 2034 migration stages fixed
REFERENCE Union Customs Code · Article 285
CONFIRMED
04
IMPLEMENTING RULES Detailed measures required for deployment
NEXT DEADLINES 2027 → 2029 → 2033
PLANNED
05
TECHNICAL INTERFACES Final operational integration model
DETAIL Follow implementing specifications
NOT YET SPECIFIED
NEXT VERIFIED LEGISLATIVE MILESTONE 1 July 2027
First implementation package required for the 2028 Data Hub phase.

The Commission must adopt the delegated and implementing acts necessary for the first mandatory Data Hub phase by 1 July 2027.

LEGAL BASIS Article 286
IN 30 SECONDS
01 Is the Data Hub confirmed?

Yes. It is established by the new Union Customs Code.

02 Is it the normal customs interface today?

No. Current systems and procedures remain operational during transition.

03 When does operational use begin?

The first mandatory phase begins with relevant e-commerce operations in 2028.

04 Are all technical details known?

No. Implementation and technical detail will continue to develop.

IMPLEMENTATION TRACKER

From legislation to
operational customs infrastructure.

The Data Hub is not a single launch event. Implementation moves through several layers: the legal framework, implementing measures, technical development, phased deployment and ultimately the transition from today’s customs systems.

The tracker separates what is already established from what still depends on future implementation.

01
LEGAL FOUNDATION

Union Customs Code establishes the Data Hub

The new customs framework gives the EU Customs Data Hub its legal basis, defines its role and establishes the direction of the future customs data environment.

PRIMARY EVIDENCE Regulation (EU) 2026/2108 New Union Customs Code
IN FORCE
02
IMPLEMENTING FRAMEWORK

Detailed rules move from law to implementation

Delegated and implementing acts are required to translate parts of the legal architecture into detailed operational rules for successive Data Hub phases.

VERIFIED MILESTONES 2027 · 2029 · 2033 Successive implementation packages
PLANNED
03
TECHNICAL SPECIFICATION

Interfaces, data exchanges and operational design

Businesses and software providers will ultimately need practical specifications covering how relevant customs data is supplied, accessed and exchanged through the future environment.

CURRENT OBSERVATORY VIEW Follow official specifications Do not infer future interfaces from today’s systems
NOT YET SPECIFIED
04
EARLY OPERATIONAL DEPLOYMENT

First Data Hub functionalities and e-commerce phase

The first operational stage is centred on the 2028 implementation window, including the first Data Hub functionalities and the relevant mandatory e-commerce use phase.

KEY DATES 1 June → 1 July 2028 First functionality → first mandatory phase
CONFIRMED
05
BROADER ACCESS

Data Hub use expands beyond the first phase

From March 2031, the legal timetable allows the Data Hub to enter a broader transition stage for other importers, exporters and transit procedure holders.

MILESTONE 1 March 2031 Voluntary broader use phase
CONFIRMED
06
FULL TRANSITION

Data Hub becomes the standard customs environment

The final transition window brings the Data Hub to full functionality and makes its use mandatory for the relevant import, export and transit processes covered by the new framework.

FINAL WINDOW February → March 2034 Full functionality → mandatory standard route
CONFIRMED
TRANSITION LOGIC

Existing systems do not disappear on day one.

The transition is designed as a progressive phase-out and phase-in process. Current customs systems remain operational while Data Hub functionality becomes available and the legal timetable moves toward broader mandatory use.

TODAY Existing customs systems NCTS · AES · ICS2 · PoUS · other environments
TRANSITION Parallel evolution Phase-out + Data Hub phase-in
2034 MODEL EU Customs Data Hub Standard data environment
CE
HOW TO READ THIS TRACKER A confirmed future date does not mean the technical solution is already fully specified.

Customs Explorer treats legal certainty and implementation certainty separately. A milestone can be fixed in legislation while interfaces, technical specifications or practical migration arrangements remain under development.

IN FORCE legally established
CONFIRMED future state/date established
PLANNED required future implementation
NOT YET SPECIFIED detail still open
MILESTONE WATCH

The dates that move the
Data Hub from law to operation.

Not every date in the reform means that businesses must change their customs processes. Some milestones concern legislation, others technical preparation, availability of Data Hub functionality or mandatory use.

OBSERVATORY RULE Track the event behind the date — not the date alone.
01 JUL 2027
IMPLEMENTING FRAMEWORK

First implementation package

CONFIRMED

First major legislative checkpoint for the measures needed to support the initial Data Hub implementation phase.

WHAT TO VERIFY

Which delegated and implementing measures have been adopted, what they define and whether they introduce concrete requirements for businesses or software providers.

LEGAL REFERENCE Article 286 Regulation (EU) 2026/2108
01 JUN 2028
DATA HUB AVAILABILITY

First Data Hub functionalities

CONFIRMED

The legal timetable requires the first Data Hub functionalities to become available before the first mandatory operational phase begins.

WHAT TO VERIFY

Which functions are actually available, who can access them, what data exchanges are supported and which technical specifications are operational.

IMPLEMENTATION First functionality Operational checkpoint
01 JUL 2028
FIRST MANDATORY PHASE

Relevant e-commerce operations enter the Data Hub

CONFIRMED

The first mandatory Data Hub phase is linked to the reform’s new e-commerce customs model.

WHAT TO VERIFY

Exact scope, affected actors, operational data requirements, interfaces and the practical relationship between customs obligations and e-commerce processes.

IMPACT Mandatory use begins Relevant e-commerce phase
01 MAR 2029
SECOND IMPLEMENTATION CHECKPOINT

Rules for broader Data Hub development

CONFIRMED

A further implementation checkpoint supports the transition toward broader Data Hub availability and the later stages of the customs-system migration.

WHAT TO VERIFY

New implementation measures, integration requirements, trader access arrangements and any confirmed changes affecting the 2031 transition phase.

LEGAL REFERENCE Article 286 Implementation package
01 MAR 2031
BROADER TRANSITION

Voluntary Data Hub use expands

CONFIRMED

The transition broadens beyond the initial e-commerce phase, allowing other relevant importers, exporters and transit procedure holders to use the Data Hub.

WHAT TO VERIFY

Eligibility, onboarding, available procedures, migration options and the practical consequences of choosing the Data Hub before mandatory use.

TRANSITION Voluntary use Wider trader population
31 JAN 2033
FINAL IMPLEMENTATION CHECKPOINT

Preparing the final migration

CONFIRMED

The final major legislative implementation checkpoint precedes the move toward full Data Hub functionality and broader mandatory use.

WHAT TO VERIFY

Final migration rules, remaining system phase-out arrangements, technical readiness and any operational conditions required before the 2034 model takes effect.

LEGAL REFERENCE Article 286 Final implementation package
01 FEB 2034
FULL FUNCTIONALITY

Data Hub reaches full functionality

CONFIRMED

The legal timetable reaches the point at which the Data Hub is expected to provide its full intended functionality.

WHAT TO VERIFY

Operational coverage, remaining legacy-system dependencies and confirmation that the environment is ready for the next mandatory transition step.

STATE Full functionality Data Hub environment
01 MAR 2034
STANDARD OPERATING MODEL

Mandatory Data Hub route for the wider customs model

CONFIRMED

The transition reaches the wider mandatory stage for the importers, exporters and transit procedure holders covered by the new framework.

WHAT TO VERIFY

Final scope of mandatory use, residual exceptions, operational continuity and the status of systems scheduled for phase-out.

END STATE Mandatory standard route Wider customs operations
READ THE TIMELINE CORRECTLY

Three dates can mean three very different things.

01 LEGAL DATE A rule or implementation measure must exist.
02 AVAILABILITY DATE Functionality becomes technically available.
03 MANDATORY DATE A defined group must use the new model.
OBSERVATORY UPDATE TRIGGERS

What would make this page change?

The Observatory should be updated when official evidence changes the known implementation state — not simply when commentary or speculation appears.

01 New delegated or implementing act

A new legal measure defines previously open operational detail.

02 Technical specification published

Interfaces, data requirements or access arrangements become officially documented.

03 Pilot or onboarding announced

Businesses or software providers can begin testing or connecting to the future environment.

04 Operational milestone reached

A planned Data Hub function or migration phase becomes genuinely operational.

05 Timeline formally changes

EU legislation or official implementation material modifies a previously established milestone.

PRIMARY TIMELINE SOURCE Regulation (EU) 2026/2108

Dates shown here should be read together with the applicable provisions, transitional rules and future implementing measures.

Verify on EUR-Lex
TECHNICAL READINESS

What is known — and what
still needs technical definition.

The legal framework describes what the EU Customs Data Hub must achieve. That does not mean every future interface, message, access method or migration mechanism is already technically defined.

OBSERVATORY PRINCIPLE Architecture can be confirmed before implementation detail is known.
AREA
WHAT IS ESTABLISHED
WHAT TO WATCH
STATUS
01
ACCESS LAYER Identity

Access to the future customs data environment must be linked to identifiable and authorised actors operating within the customs framework.

Final authentication mechanisms, identity workflows and the practical user journey for each category of actor.

NOT YET SPECIFIED
02
ACCESS LAYER Authorisation

The customs framework distinguishes between economic operators, representatives, authorities and other actors with different rights and responsibilities.

Role models, permissions, delegation mechanisms and how access rights will be managed operationally.

NOT YET SPECIFIED
03
CONNECTIVITY Access channels

The Data Hub is intended to support the provision, processing and reuse of customs information in a common EU-level data environment.

Which human-facing interfaces, system-to-system channels and integration options will be available for each operational use case.

NOT YET SPECIFIED
04
CONNECTIVITY APIs & integration

Business systems will need to interact with the customs data environment as implementation progresses and machine-to-machine exchanges become operational.

API specifications, protocols, authentication, endpoints, testing environments, versioning and integration requirements.

NOT YET SPECIFIED
05
DATA Data model

The reform establishes a shift toward customs information being supplied and reused as data rather than relying only on isolated declaration-centred exchanges.

Detailed datasets, data elements, validation rules, mappings and the relationship with existing EU customs data models and national implementations.

CONFIRMED Direction confirmed.
Detail developing.
06
BUSINESS ROLES Representation

Customs representation remains part of the legal customs framework and therefore has to be supported within the future operating model.

How mandates, direct and indirect representation, permissions and system access will work in the Data Hub environment.

NOT YET SPECIFIED
07
OPERATIONS Messages & statuses

Customs operations require communication of decisions, controls, releases, requests and other operational statuses between customs and relevant actors.

Future message structures, status models, notifications, acknowledgements and error-handling mechanisms.

NOT YET SPECIFIED
08
TRANSITION System migration

Migration is phased. Existing customs systems remain relevant while Data Hub functionality is introduced progressively toward the wider 2034 model.

Procedure-by-procedure migration schedules, phase-out sequencing, coexistence rules and national implementation arrangements.

CONFIRMED Transition confirmed.
Sequence developing.
TECHNICAL READINESS MAP

The destination is clearer than the interface.

This is normal for a long implementation programme. The legislation establishes the operating direction first; detailed technical rules then become progressively more concrete as each deployment phase approaches.

LEGAL ARCHITECTURE Established
Data Hub purpose, legal role and transition architecture
IMPLEMENTATION RULES Developing
Successive measures required through the implementation period
TECHNICAL DETAIL Still open
Interfaces, integration detail and practical operating specifications
DO NOT ASSUME

What businesses should not design around yet.

01

That today’s customs portals will simply be reproduced inside the Data Hub.

02

That existing message structures will remain unchanged.

03

That one future API or interface will serve every actor and customs process in the same way.

04

That a confirmed 2034 end-state defines every technical migration step between now and then.

FOR BUSINESSES Prepare your data before preparing for an interface.

Businesses can already map customs data sources, responsibilities, software dependencies and data-quality problems without guessing how the final Data Hub interface will work.

FOR SOFTWARE PROVIDERS Separate architecture planning from interface development.

The future direction can inform system architecture, but concrete integration should follow official technical specifications rather than assumed endpoints or formats.

FOR CUSTOMS PROFESSIONALS Watch roles and workflows as closely as technology.

Representation, responsibility, access rights and customs supervision may be as important operationally as the technical connection itself.

SYSTEM TRANSITION WATCH

What happens to today’s
EU customs systems?

NCTS, AES, ICS2, PoUS and other customs environments remain operationally relevant during the transition. The Data Hub introduces a new destination architecture, but migration is progressive rather than instantaneous.

IMPORTANT Do not interpret the Data Hub roadmap as a shutdown calendar for individual customs systems.
01 CURRENT LANDSCAPE
TRANSIT NCTS
EXPORT AES
SAFETY & SECURITY ICS2
UNION STATUS PoUS
+ Other customs environments
02 TRANSITION
PHASE-OUT Progressive
migration
Data Hub
phase-in
PHASE-IN

Coexistence and migration arrangements develop progressively as the implementation programme advances.

03 FUTURE MODEL
EU CUSTOMS DATA
HUB
Common data environment
FULL FUNCTIONALITY 1 February 2034
WIDER MANDATORY USE 1 March 2034
SYSTEM WATCH REGISTER

Follow migration evidence system by system.

The relevant question is not simply “when will this system disappear?” but which functions, procedures and data exchanges move — and when that movement becomes official.

SYSTEM
CURRENT ROLE
TRANSITION SIGNAL
WHAT TO WATCH
STATUS
01
TRANSIT NCTS

Operational environment supporting electronic customs transit procedures.

Data Hub migration

Transit is part of the wider transition architecture.

Procedure migration, message changes, trader connectivity, coexistence rules and confirmed phase-out arrangements.

NOT YET SPECIFIED
02
EXPORT AES

Electronic environment supporting export procedures and related exchanges.

Data Hub migration

Export processes fall within the broader future Data Hub model.

Export-data migration, process sequencing, interface changes and official transition arrangements.

NOT YET SPECIFIED
03
SAFETY & SECURITY ICS2

EU advance cargo information environment supporting safety and security risk analysis.

Data integration

Risk-related information becomes part of a more integrated EU customs data architecture.

Data reuse, integration with Union-level risk analysis, future interfaces and confirmed migration arrangements.

NOT YET SPECIFIED
04
UNION STATUS PoUS

Electronic environment supporting proof of Union status for relevant goods and documents.

Data Hub transition

Union-status information sits within the future customs-data landscape.

Future treatment of status evidence, data access, workflow integration and system migration.

NOT YET SPECIFIED
EVIDENCE THRESHOLD

What counts as a real migration signal?

Customs Explorer should only change a system’s transition status when the evidence becomes sufficiently concrete.

01 LEGAL Official measure

EU legislation or an implementing measure establishes a migration requirement.

02 PROGRAMME Work programme

An official programme identifies the relevant phase-out or phase-in step.

03 TECHNICAL Specification

Technical documentation defines how the new process will operate.

04 OPERATIONAL Deployment

Authorities confirm onboarding, migration or operational availability.

KEEP THESE TWO QUESTIONS SEPARATE

“Is the Data Hub confirmed?”
is not the same as
“When does NCTS disappear?”

QUESTION A Is the Data Hub part of the future customs architecture?
ANSWER YES · CONFIRMED
≠
QUESTION B Is the final migration date for every current customs system already known?
ANSWER NOT YET SPECIFIED
WHAT BUSINESSES SHOULD WATCH

Follow the process you use — not just the system name.

01 Procedure

Which customs procedure is affected by the migration?

02 Data

Which data must be supplied differently?

03 Connection

Does the trader, representative or software system need a new access route?

04 Timing

Is use optional, transitional or mandatory?

05 Legacy system

When does the current process actually cease to apply?

BUSINESS READINESS MONITOR

Prepare what is useful now.
Wait where the specification is still open.

Businesses do not need to redesign their customs systems today. They can, however, improve the foundations that will matter regardless of the final Data Hub interface.

WORKING PRINCIPLE Prepare the organisation. Do not build against assumptions.
01
PREPARE NOW Useful regardless of final technical design
02
WAIT FOR SPECIFICATION Do not implement an assumed solution
03
ACTION TRIGGER Official evidence that should start concrete work
AREA
PREPARE NOW
WAIT FOR SPECIFICATION
ACTION TRIGGER
01
FOUNDATION Customs data

Map where classification, origin, customs value, product, party and shipment data comes from.

START NOW

Final Data Hub datasets, validation rules, mappings and technical submission structures.

TRIGGER

Official data specifications or implementation documentation are published.

02
TECHNOLOGY Software & interfaces

Identify ERP, customs software, logistics platforms and other systems involved in customs-data flows.

MAP NOW

APIs, endpoints, protocols, authentication methods and final integration architecture.

TRIGGER

Technical specifications, testing environments or formal onboarding requirements become available.

03
ORGANISATION People & ownership

Define who owns customs data, who validates it and who is responsible when information must be corrected.

CLARIFY NOW

Detailed future operational roles created by specific Data Hub procedures or access models.

TRIGGER

Official workflow and actor requirements become sufficiently concrete for organisational implementation.

04
RESPONSIBILITY Representation

Document which customs activities are performed internally and which are delegated to representatives.

REVIEW NOW

Future Data Hub permissions, mandates, delegation workflows and technical access rights.

TRIGGER

Official access and representation rules define how delegated activity works in the new environment.

05
EARLY PHASE E-commerce

Businesses potentially affected by the 2028 phase should identify relevant sales flows, actors and customs-data dependencies early.

PRIORITY REVIEW

Detailed operational integration, final interfaces and any implementation detail not yet officially specified.

TRIGGER

Implementing measures and technical documentation define the practical requirements for the 2028 operational phase.

06
CONTROL Customs governance

Review internal customs controls, data-quality ownership, escalation routes and responsibility for compliance.

STRENGTHEN NOW

Any organisation-specific change that depends on future Data Hub procedures or technical requirements.

TRIGGER

Confirmed implementation rules materially change responsibilities, controls or operating procedures.

READINESS PRIORITY

Start with the parts that survive any technical design.

Clean customs data, clear responsibilities and a map of existing systems are useful whether the future connection is a portal, API, delegated interface or another officially defined mechanism.

NOW Data quality Classification · origin · value · parties
NEXT Process mapping Systems · people · representatives
WHEN SPECIFIED Technical implementation Interfaces · messages · migration
DECISION GATE

Should we implement something now?

QUESTION Is there an official requirement that applies to this business now?
YES Implement the confirmed requirement.

Use the applicable legislation, official specification and operational guidance.

NO Prepare foundations and continue monitoring.

Do not build a future process around assumptions that may change before implementation.

IMPLEMENTATION REFERENCE

Data Hub Observatory
frequently asked questions.

The Observatory separates the legal destination from the implementation detail still developing around the EU Customs Data Hub.

01 Is the EU Customs Data Hub still only a proposal?

No. The Data Hub forms part of the new Union Customs Code established by Regulation (EU) 2026/2108. The legal framework is in force, while operational implementation is phased over several years.

02 Does the Data Hub become fully operational in 2028?

No. The 2028 window concerns the first Data Hub functionalities and the first relevant mandatory e-commerce phase. Broader transition continues through 2031 and 2034.

03 Will NCTS, AES, ICS2 and PoUS all disappear at the same time?

The Data Hub roadmap should not be treated as a shutdown calendar for individual customs systems. Migration must be followed procedure by procedure and system by system as official implementation arrangements become available.

04 Are the future APIs and technical interfaces already known?

Not in sufficient detail to design a complete future integration around them. Businesses and software providers should distinguish the confirmed legal architecture from technical specifications that still need to be published or completed.

05 What should businesses prepare now?

Focus on customs-data quality, data ownership, current system dependencies, internal responsibilities, representation arrangements and the processes that may eventually need to migrate.

06 When should a business start technical implementation?

When an applicable requirement and sufficiently concrete official implementation material exist. Preparing data and processes early is useful; building technical solutions around assumed future interfaces is not.

CURRENT OBSERVATORY STATUS

What can be stated with confidence today?

LAST REVIEWED 5 October 2026
EU Customs Data Hub legal framework IN FORCE
Data Hub implementation programme CONFIRMED
First functionality in 2028 CONFIRMED
Broader transition in 2031 CONFIRMED
Full-functionality / wider 2034 model CONFIRMED
Final technical interfaces and integration detail NOT YET SPECIFIED
Individual legacy-system migration dates NOT YET SPECIFIED
HOW THE OBSERVATORY VERIFIES CHANGE

Evidence moves through four levels.

01 LAW Legal framework
02 RULES Implementation measures
03 TECHNICAL Specifications
04 LIVE Operational deployment
DATA HUB OBSERVATORY Living implementation reference · Last reviewed 5 October 2026

Status should change only when supported by new official evidence.

Verify primary law