Customs Explorer
⌕

Customs Explorer

Customs declaration API

CUSTOMS EXPLORER / DIGITAL INTEGRATION

Customs
Declaration API.

Connecting customs declaration workflows with business software and authorised electronic submission channels.

Customs declaration integrations can support the preparation, validation, transmission and monitoring of declaration data. The technical connection depends on the relevant customs system, its supported interfaces and applicable access conditions.

Important: A customs declaration API is not a single, universally available EU interface. Integration options and submission requirements must be verified for each relevant customs system.

DECLARATION DATA FLOW CONCEPTUAL MODEL
BUSINESS DATA ERP / Logistics / Trade Records Goods, parties, documents and transactions
✦
INTEGRATION & DECLARATION SOFTWARE Declaration Processing Layer
DATA MAPPING VALIDATION MESSAGE CREATION ERROR HANDLING
SUPPORTED SUBMISSION CHANNEL Relevant Customs System Subject to authorised access and technical rules
Responses & Status Updates Acknowledgements, rejections, references and other system-specific outcomes
01
PREPARE Structure declaration data
02
VALIDATE Check data and business rules
03
EXCHANGE Use supported authorised channels
04
MONITOR Track responses and exceptions
DECLARATION WORKFLOW

From Business Data
to Customs Decisions.

A customs declaration integration connects business information with the software and electronic channels used to prepare, submit and monitor customs declarations.

The workflow depends on the customs procedure, the competent customs administration and the technical specifications of the relevant system. The stages below illustrate a common integration pattern, not a universal EU message sequence.

STAGE / 01

Collect Source Data

Retrieve relevant information from ERP, logistics, inventory and trade records, including goods, parties, values and supporting documents.

BUSINESS SYSTEMS
STAGE / 02

Map Declaration Fields

Transform source information into the data elements, structures and code values required by the applicable declaration system and procedure.

DATA TRANSFORMATION
STAGE / 03

Validate & Prepare

Check required fields, formats, relationships and known business rules. Resolve detected issues before transmission where possible.

PRE-SUBMISSION CHECKS
STAGE / 04

Submit Through a Supported Channel

Exchange the declaration message through an interface supported by the relevant system, subject to applicable access conditions.

AUTHORISED EXCHANGE
STAGE / 05

Process Responses

Interpret acknowledgements, errors, acceptance information, references and subsequent customs decisions as supported by the system.

STATUS & RECONCILIATION
TWO-WAY INFORMATION FLOW

Submission is only
one part of the process.

A declaration integration should be designed for two-way information exchange. Sending a message is not enough: subsequent responses must be interpreted and associated with the correct business transaction.

Depending on the system and procedure, responses may include validation failures, acceptance information, a declaration reference, control-related events, release information or other status changes.

Match every response

Link system messages to the originating declaration record.

Maintain a reliable status history

Record meaningful changes without treating every response as final.

Handle uncertain outcomes

Reconcile timeouts and missing responses before attempting resubmission.

MESSAGE EXCHANGE ILLUSTRATIVE
BUSINESS SIDE Declaration Software Data preparation & monitoring
DESTINATION Customs System Applicable electronic interface
01 Declaration submission
Outbound message
02 Technical acknowledgement / error
Where provided by the interface
03 Acceptance / reference information
Subject to validation and applicable rules
04 Further customs status / decision
Only where relevant and supported
UNDERSTANDING DECLARATION OUTCOMES

Not Every Successful Message
Means Customs Release.

Technical delivery, legal acceptance and release of goods are different events. Integration software must preserve those distinctions.

01
TECHNICAL EVENT

Message Received

The destination interface may confirm that a message has been received or processed at a technical level.

Does not necessarily mean: Declaration accepted
02
CUSTOMS EVENT

Declaration Accepted

Acceptance occurs under the applicable customs rules after the relevant requirements have been satisfied. An MRN may be communicated as part of the system’s processing.

Does not necessarily mean: Goods released
03
CUSTOMS DECISION

Goods Released

Release is a separate customs decision allowing the goods to be made available for the purposes of the procedure concerned, subject to the relevant rules.

Integration requirement: Recognise the relevant release outcome
DATA STRUCTURE & VALIDATION

Accurate Data.
Reliable Declarations.

A customs declaration is built from structured information about the goods, the parties, the customs procedure and the underlying commercial transaction.

Digital integration can collect and transform this information, but it cannot automatically guarantee that the underlying customs determinations are legally correct. Data requirements vary according to the declaration type, procedure, applicable legislation and destination system.

DATA DOMAIN / 01 01

Economic Operators & Parties

Information identifying the relevant parties and their roles in the customs operation.

  • Declarant and representative details
  • Relevant EORI identifiers
  • Consignor and consignee information
  • Other required party references
PARTY IDENTIFICATION
DATA DOMAIN / 02 02

Goods & Classification

Information describing the goods and supporting their identification under the relevant customs nomenclature.

  • Goods descriptions
  • Commodity classification codes
  • Net mass and other required quantities
  • Packages and item-level information
GOODS IDENTIFICATION
DATA DOMAIN / 03 03

Origin & Trade Measures

Information used to determine the applicable origin treatment and relevant trade measures.

  • Country of origin
  • Preferential origin claims, where relevant
  • Supporting origin evidence
  • Applicable measure-related references
ORIGIN & MEASURES
DATA DOMAIN / 04 04

Value & Commercial Data

Transaction information relevant to customs valuation and other declaration requirements.

  • Invoice and currency information
  • Relevant valuation elements
  • Delivery terms and transport costs
  • Adjustments, where applicable
CUSTOMS VALUATION
DATA DOMAIN / 05 05

Procedure & Documents

Information connecting the declaration to the intended customs procedure and relevant supporting evidence.

  • Requested and previous procedures
  • Supporting document references
  • Authorisations, where required
  • Previous document or movement references
PROCEDURAL DATA
VALIDATION FRAMEWORK

Three Layers.
Different Responsibilities.

Declaration software can apply several types of checks before submission. These checks are valuable, but they address different questions and should not be treated as equivalent.

Technical validation

Does the message meet the expected structure, format and interface specifications?

Business-rule validation

Are the values, code combinations and relationships consistent with the known rules of the system?

Substantive customs review

Are the declared classification, origin, value and procedure actually correct under the applicable law?

Key principle: Passing automated validation does not establish that a declaration is legally accurate or immune from subsequent customs controls.

DECLARATION QUALITY MODEL CONCEPTUAL
INPUT Structured Declaration Data Source records + mapped data elements
01
STRUCTURE Schema & Format Checks Required fields, data types, message structure
02
CONSISTENCY Code & Business Rules Known dependencies and validation conditions
03
LEGAL ACCURACY Customs Determinations Classification, origin, valuation and procedure
Automated checks support, but do not replace, appropriate customs expertise and controls.
DATA GOVERNANCE

Know Where Every
Data Element Comes From.

Reliable declaration integration requires more than field mapping. Organisations should identify which system owns each data element, who verifies its accuracy and how corrections are managed.

01 / OWNERSHIP

Define the Source of Truth

Establish the authoritative source for each field instead of relying on conflicting copies of data.

02 / COMPLETENESS

Identify Missing Information

Detect data that cannot be obtained from business systems and define how it must be supplied or reviewed.

03 / TRACEABILITY

Preserve Data Lineage

Record relevant source references, transformations, approvals and subsequent corrections.

04 / MAINTENANCE

Manage Changing Requirements

Review mappings when customs specifications, code lists or business processes change.

OFFICIAL REGULATORY CONTEXT Declaration data requirements and customs obligations

The applicable data requirements must be checked against the current Union Customs Code framework, its delegated and implementing provisions, and the specifications of the relevant system.

SECURE DECLARATION EXCHANGE

Secure the Connection.
Verify the Authority.

Electronic customs declaration systems require more than a technically valid message. Access, identity, representation and operational permissions must be addressed according to the applicable customs and system-specific requirements.

Authentication proves an identity to a system. Authorisation determines what that identity is permitted to do. Customs law separately governs the roles and responsibilities of the declarant and any customs representative.

CONTROL / 01 IDENTITY

Technical Authentication

The integration must use the authentication mechanism supported by the destination interface and comply with its security rules.

  • Approved credentials or certificates
  • Secure credential storage
  • Credential renewal and revocation
  • Environment-specific access controls
SYSTEM IDENTITY
CONTROL / 02 OPERATOR

EORI & Operator Identification

EORI provides an identification reference for economic operators in customs dealings. It must not be confused with technical credentials or access approval.

  • Relevant operator identifiers
  • Consistency of declared party roles
  • Registration requirements
  • System-specific onboarding
ECONOMIC OPERATOR IDENTITY
CONTROL / 03 AUTHORITY

Representation & Permissions

The declarant’s role and any direct or indirect representation must be established independently of the technical connection.

  • Direct or indirect representation
  • Evidence of empowerment to act
  • Applicable user permissions
  • Delegation and access governance
LEGAL & OPERATIONAL AUTHORITY
CONTROL / 04 TRACEABILITY

Audit & Message Integrity

Maintain records that support investigation, reconciliation and accountability throughout the declaration lifecycle.

  • Submission and response references
  • Time-stamped processing events
  • Controlled corrections and resubmissions
  • Appropriate log access and retention
EVIDENCE & CONTROL
ACCESS & LEGAL RESPONSIBILITY

API Access Is Not
Customs Representation.

A software application may be technically connected to a customs system without being entitled to submit declarations for every economic operator.

The right to act in a customs operation, the representation arrangement and the conditions for using an electronic submission channel must each be verified.

Technical access

Is the interface available, and has the connection been approved under the relevant technical rules?

Authority to act

Who is the declarant, who is the representative, and what authority supports the representation?

Responsibility for declarations

Which persons bear the relevant obligations under customs law, regardless of the software used?

Important: An EORI number does not automatically grant access to every customs system, and possessing API credentials does not itself establish customs representation authority.

DECLARATION ACCESS MODEL ILLUSTRATIVE
BUSINESS & LEGAL CONTEXT Economic Operator / Declarant Identity, declaration role and representation arrangements
TECHNICAL EXECUTION Declaration Software / Provider Message preparation, access controls, transmission and response handling
01
Authentication Identity verified by the system
02
System Authorisation Permitted functions and access scope
03
Customs Authority to Act Applicable legal role and representation
SUPPORTED ELECTRONIC CHANNEL Relevant Customs System Submission subject to applicable access and procedural requirements
The checks shown are conceptual and do not imply a universal three-step EU authentication protocol.
OPERATIONAL SAFEGUARDS

Protect the Entire
Declaration Lifecycle.

Security controls should cover preparation, transmission, response handling, corrections and the preservation of relevant records.

01 / TRANSPORT

Protect Data in Transit

Use the secure transport and cryptographic mechanisms specified for the relevant interface.

02 / ACCESS

Apply Least Privilege

Limit credentials and user permissions to the functions necessary for authorised operations.

03 / TRANSACTIONS

Prevent Uncontrolled Duplicates

Reconcile uncertain submissions before retrying. Duplicate handling must follow system-specific rules.

04 / RECORDS

Maintain Reliable Evidence

Preserve appropriate message references, responses, approvals and processing histories under applicable retention rules.

IMPLEMENTATION & OPERATIONAL RELIABILITY

Build for Real Operations.
Not Just Successful Tests.

Reliable declaration integration must handle incomplete data, rejected messages, uncertain transmission outcomes and evolving customs system requirements.

The most difficult problems often appear after the first successful submission. A production integration needs operational controls, exception handling, monitoring and a clear maintenance model.

CHALLENGE / 01 DATA

Incomplete Source Data

ERP and logistics systems may not contain every element required for a customs declaration or may store information in an unsuitable format.

BEST PRACTICE Identify missing data early and assign responsibility for completing and verifying each required element.
CHALLENGE / 02 RESPONSES

Rejected Declarations

A customs system may reject a declaration because of invalid data, incompatible code combinations or other applicable validation conditions.

BEST PRACTICE Preserve the original error response, identify the affected data and support controlled correction.
CHALLENGE / 03 DELIVERY

Timeouts & Unknown Outcomes

A communication timeout does not prove that the destination system failed to receive or process a submission.

BEST PRACTICE Reconcile the transaction using supported status or reference mechanisms before resubmitting.
CHALLENGE / 04 INTEGRITY

Duplicate Submissions

Automatic retries, user actions or disconnected systems can cause the same business transaction to be submitted more than once.

BEST PRACTICE Use internal transaction identifiers, controlled retry rules and duplicate checks appropriate to the interface.
CHALLENGE / 05 CHANGE

Changing Message Specifications

Customs systems may introduce updated schemas, code lists, validation rules or technical interface requirements.

BEST PRACTICE Track official specifications, version mappings and test changes before production deployment.
CHALLENGE / 06 DEPENDENCIES

Provider & Access Dependencies

Integration may depend on a software provider, national onboarding, authorised access arrangements or services outside the developer’s control.

BEST PRACTICE Confirm access conditions, contractual dependencies and recurring costs before committing to development.
EXCEPTION MANAGEMENT

A Missing Response
Is Not a Rejection.

When a submission produces no visible response, the integration must distinguish between a confirmed failure and an uncertain processing outcome.

Repeated transmission without checking the original transaction can introduce duplicate declarations or inconsistent business records.

Preserve transaction identity

Keep a stable internal reference linking requests, responses and the business operation.

Investigate before retrying

Use the reconciliation facilities actually supported by the destination system or provider.

Escalate unresolved outcomes

Route uncertain cases for manual review rather than assuming technical failure.

EXCEPTION RECOVERY CONCEPTUAL
SUBMISSION Declaration Message Sent Internal transaction reference retained
RESPONSE CHECK Has a definitive outcome been received?
YES Interpret the Outcome

Record acceptance, rejection or other applicable system status.

NO / UNKNOWN Reconcile First

Investigate using supported reference or status mechanisms.

CONTROLLED RESOLUTION Update, correct, retry or escalate

Select the appropriate action only after establishing the available transaction information.

Actual recovery mechanisms and permitted resubmission procedures vary by customs system.
PRACTICAL IMPLEMENTATION ROADMAP

Verify Feasibility
Before Writing the Integration.

A staged approach helps expose access restrictions, missing data, testing requirements and commercial dependencies before they become expensive development problems.

01
FEASIBILITY GATE

Verify the Target Interface

Identify the responsible customs system, supported connection method, access eligibility and required onboarding.

02
DATA READINESS

Audit the Available Data

Compare business records with required declaration data elements and establish ownership of missing fields.

03
ARCHITECTURE

Design Mapping & State Management

Define message transformation, transaction references, response handling and exception workflows.

04
TESTING

Validate Against Real Specifications

Use official or provider test facilities where available and complete any required conformance procedures.

05
CONTROLLED ROLLOUT

Introduce Production Gradually

Establish monitoring, operational responsibilities, manual fallback and recovery procedures.

06
ONGOING OPERATIONS

Maintain the Integration

Track system updates, credentials, incidents, provider commitments and recurring operational costs.

PROJECT FEASIBILITY CHECKPOINT

Before Development,
Answer These Questions.

A technically attractive integration may still be commercially or operationally unviable if access, testing or maintenance requirements cannot be met.

Is a suitable submission interface actually supported?
Can the intended operator or provider obtain access?
Are technical specifications and testing arrangements available?
Are development, onboarding and recurring costs acceptable?
Is there a workable plan for changes, incidents and support?
OFFICIAL SOURCES & FURTHER EXPLORATION

Understand the Rules.
Explore the Connections.

Customs declaration integration operates within a legal and technical framework. The Union Customs Code establishes core customs obligations, while the applicable electronic systems and their specifications determine how messages are exchanged.

Use official sources to verify legal requirements, applicable data elements and implementation conditions. The availability of an electronic customs system does not necessarily mean that an open or publicly accessible API exists.

01 / REGULATORY FRAMEWORK

Official EU Customs Resources

Primary legislation and European Commission information for understanding the customs declaration environment.

IMPORTANT TECHNICAL DISTINCTION

Electronic Customs System ≠ Public API

Customs authorities may provide electronic submission through national platforms, approved software channels or other controlled interfaces. Access arrangements, specifications, testing and eligibility must be established for the particular system and use case. There is no universal assumption that every EU customs declaration can be submitted through a single publicly available API.

CONTINUE EXPLORING CUSTOMS TECHNOLOGY

Connect the Systems.
Understand the Requirements.

Explore the wider Customs APIs section to understand integration models, technical dependencies and the boundaries of automated customs processes.