Customs Explorer
⌕

Customs Explorer

E-commerce customs automation

CUSTOMS EXPLORER / E-COMMERCE CUSTOMS / AUTOMATION
DIGITAL CUSTOMS INTELLIGENCE

E-commerce
Customs Automation

Connecting commercial data, customs compliance and electronic declaration systems.

E-commerce customs automation transforms order, product and shipment information into structured customs data. It can support declaration preparation, validation, submission and status monitoring across high-volume parcel operations.

Effective automation depends on legally correct data, clearly assigned responsibilities and access to the appropriate customs interfaces. It cannot eliminate the declarant’s obligations or customs authorities’ powers of control.

DATA Extraction & mapping
RULES Validation & eligibility
STATUS Responses & exceptions
REFERENCE ARCHITECTURE EU CUSTOMS / DIGITAL OPERATIONS
01
Marketplace Orders and transaction data
02
ERP / Commerce Platform Products, values and parties
03
Logistics Systems Consignments and transport data
AUTOMATION LAYER
Customs Data Engine
DATA NORMALISATION RULE VALIDATION DECLARATION MAPPING EXCEPTION HANDLING
CUSTOMS INTERFACE National Customs Systems Authorised electronic submission channels
VALIDATION RESPONSES ACCEPTANCE / CONTROL / RELEASE
CONCEPTUAL FLOW — NOT A SINGLE EU-WIDE API
01 / SYSTEM ARCHITECTURE

One customs workflow.
Multiple connected systems.

E-commerce customs automation connects commercial, logistics and regulatory information. The objective is to transform fragmented source records into consistent declaration data while maintaining traceability throughout the customs process.

The architecture must distinguish internal business systems from legally recognised customs procedures and the electronic interfaces made available by competent customs authorities.

01 SOURCE
COMMERCIAL & LOGISTICS DATA

Data acquisition

Retrieve order, product, invoice and consignment information from marketplaces, ERP platforms, warehouse systems and transport providers. Source records must be associated with the correct shipment and underlying transaction.

ERP MARKETPLACE WMS CARRIER DATA
OUTPUT Structured source records
02 TRANSFORM
DATA NORMALISATION

Mapping and enrichment

Convert commercial fields into a consistent internal data model. Normalise currencies, quantities, units, party identifiers and product references. Enrich records with validated classification, origin and other required customs information where available.

FIELD MAPPING UNITS CURRENCIES MASTER DATA
OUTPUT Normalised customs dataset
03 VALIDATE
REGULATORY DECISION RULES

Eligibility and compliance checks

Evaluate the applicable customs procedure and declaration dataset, including H7 eligibility where relevant. Check mandatory data, intrinsic value, goods exclusions, VAT arrangements and potential restrictions. Records requiring judgment or missing evidence must be routed for review.

H7 / H1 VALUE CHECKS IOSS EXCEPTIONS
OUTPUT Validated or flagged records
04 PREPARE
DECLARATION GENERATION

Build the electronic declaration

Populate the required declaration data elements according to the applicable EU legal framework and national technical specifications. Apply message-format validation and preserve a link between submitted values and their source records.

ANNEX B MESSAGE SCHEMA DECLARANT TRACEABILITY
OUTPUT Declaration-ready message
05 CONNECT
CUSTOMS SYSTEM INTEGRATION

Transmit through an authorised interface

Submit the declaration through the relevant national customs channel where the operator has the necessary technical access and legal authority. Authentication, certificates, authorisations, message protocols and testing requirements vary between implementations.

NATIONAL SYSTEM AUTHENTICATION MESSAGE EXCHANGE
OUTPUT Submission and system responses
06 MONITOR
STATUS & EXCEPTION MANAGEMENT

Process responses and customs decisions

Interpret technical rejections, acceptance, requests for additional information, control events and release messages. Update operational systems without confusing technical transmission, legal acceptance and customs release.

REJECTIONS MRN CONTROLS RELEASE
OUTPUT Auditable customs status
01.1 / SYSTEM BOUNDARIES

Three different systems of responsibility

A

Commercial systems

Maintain orders, invoices, product records and shipment information. These systems supply data but do not themselves create a legally accepted customs declaration.

B

Automation software

Transforms, checks and prepares data. It can support authorised submission and monitoring, but cannot replace the legal responsibilities of the declarant or representative.

C

Customs authorities

Operate the relevant customs systems, accept declarations, carry out controls and authorise release in accordance with the applicable customs rules.

TECHNICAL REALITY

Integration is not simply an API connection.

A functioning customs integration may require national registration, operator identification, technical onboarding, security credentials, message certification or conformance testing. Requirements must be verified for the target Member State and procedure before development assumptions are finalised.

02 / DECLARATION EXECUTION

Automate the workflow.
Control every decision.

Automated declaration processing combines deterministic business rules, customs data requirements, technical validation and electronic message exchange.

The software can prepare and transmit declarations where the relevant access conditions are satisfied. It cannot independently establish legal eligibility from incomplete evidence or replace customs decisions.

AUTOMATED PROCESS
HUMAN REVIEW WHEN REQUIRED
CUSTOMS AUTHORITY
01
DATA READINESS AUTOMATABLE

Verify declaration data completeness

Before generating a customs message, the system checks whether mandatory information is available, correctly formatted and consistent with related order, product and consignment records.

PARTY IDENTIFIERS GOODS DATA VALUE & CURRENCY CONSIGNMENT DATA
Control boundary: A technically complete record is not necessarily legally accurate. Unsupported classifications, origin claims or values must not be treated as verified merely because fields are populated.
02
DECLARATION ROUTING RULES + REVIEW

Select the applicable declaration dataset

The engine evaluates the available legal and operational conditions to determine whether an H7 reduced dataset, an H1 standard dataset or another applicable declaration arrangement should be considered.

ROUTE A H7

Reduced dataset where the current legal conditions and exclusions permit its use.

ROUTE B H1

Standard declaration dataset where applicable to release for free circulation.

EXCEPTION Manual assessment

Unclear eligibility, missing evidence, restrictions or other non-standard cases.

Legal boundary: The H7 dataset is not a general replacement for H1. Dataset selection must follow the legislation applicable to the goods and the date of the declaration.
03
MESSAGE PREPARATION AUTOMATABLE

Generate and validate the customs message

Validated data is mapped into the required electronic declaration structure. The software applies the relevant message schema, code lists, conditional fields and national implementation requirements before transmission.

ANNEX B DATA CODE LISTS SCHEMA VALIDATION VERSION CONTROL
Technical boundary: EU-level data requirements and national message specifications are related but not identical. A generic data model may require a separate adapter for each target customs system.
04
ELECTRONIC SUBMISSION ACCESS DEPENDENT

Transmit through the authorised customs channel

Where technical and legal access has been established, the system submits the declaration through the relevant national customs interface, either directly or through an appropriately authorised intermediary.

AUTHENTICATION MESSAGE EXCHANGE TRANSMISSION LOG
Access boundary: EORI identification alone does not necessarily grant access to a national customs interface. Registration, representation authority, credentials and technical onboarding may also be required.
05
RESPONSE INTERPRETATION CUSTOMS DECISION

Distinguish technical and legal customs events

The software receives and interprets system responses. These may include technical rejection, legal acceptance, declaration identifiers, control notifications and release decisions, depending on the national system and procedure.

! Rejected Correct and resubmit where appropriate
✓ Accepted Declaration accepted; release not implied
? Control Information or examination may be required
→ Released Customs release decision recorded
MRN distinction: An import declaration MRN must not be confused with a reference assigned to an Entry Summary Declaration (ENS) under the safety and security framework. Their purposes and procedural contexts differ.
06
EXCEPTION RESOLUTION HUMAN OVERSIGHT

Escalate cases that cannot be safely automated

Exceptions are assigned to a competent operator for assessment. The system should preserve the original data, validation findings, submitted messages and customs responses so that corrective action can be justified and audited.

CLASSIFICATION DOUBTS VALUATION ISSUES RESTRICTED GOODS CUSTOMS HOLDS
Correction boundary: Amendment and invalidation of accepted customs declarations are governed by Articles 173 and 174 UCC. A software retry must not be treated as unrestricted permission to modify an accepted declaration.
02.1 / AUTOMATION GOVERNANCE

Three decisions the software must keep separate

SOFTWARE RULE Can this data pass a predefined validation?

Deterministic checks can evaluate formats, mandatory fields, consistency and documented eligibility criteria.

OPERATOR JUDGMENT Is the underlying customs information defensible?

Classification, valuation, origin, restrictions and representation may require evidence and qualified human assessment.

CUSTOMS AUTHORITY Can the goods be released?

Acceptance, verification and release are governed by customs legislation and the competent authority’s decisions.

03 / CONNECTED CUSTOMS SYSTEMS

Connecting commerce
to customs infrastructure.

Commercial platforms and customs authorities operate different information systems, data structures and security models. Successful integration requires more than transferring an order into a declaration.

A scalable architecture separates source-system connectors, customs validation logic and country-specific submission adapters.

03.1 / REFERENCE INTEGRATION MODEL LOGICAL ARCHITECTURE — NOT A LIVE CONNECTION
SOURCE SYSTEMS
01
Marketplaces Orders, items, transactions
02
ERP / E-commerce Invoices, products, parties
03
WMS / Carriers Shipments, packages, transport
CUSTOMS AUTOMATION LAYER
INTERNAL PROCESSING

Customs Integration Engine

DATA NORMALISATION
CLASSIFICATION / ORIGIN DATA
DECLARATION VALIDATION
MESSAGE GENERATION
EXCEPTION MANAGEMENT
CUSTOMS INTERFACES
EU
EU Data Requirements UCC / Annex B framework
MS
National Import Systems Member State specifications
↺
Customs Responses Acceptance, controls, release
03.2 / SOURCE CONNECTORS

What can be integrated?

Different platforms contribute different elements to a customs declaration. None should be assumed to contain every legally required field.

01 / COMMERCE

Marketplace APIs

Marketplace integrations may expose order lines, product identifiers, transaction amounts, customer details and fulfilment information, subject to permissions and API availability.

COMMON GAP Validated customs classification and origin
02 / BUSINESS

ERP & Product Master Data

ERP systems can supply commercial invoices, supplier information, product descriptions, valuation components and maintained customs attributes where those records exist.

COMMON GAP Data quality and regulatory maintenance
03 / LOGISTICS

Warehouse & Carrier Systems

Logistics platforms can contribute package references, transport identifiers, weights, routing information and shipment events.

COMMON GAP Legal transaction and customs valuation data
03.3 / CUSTOMS CONNECTIVITY

Requirements before connecting to customs

The actual prerequisites must be established for the target country, procedure, operator and technical integration channel.

REQUIREMENT WHAT MUST BE VERIFIED IMPLEMENTATION RISK
Operator identification

EORI and any additional national registration conditions.

Identification does not automatically grant system access.
Representation authority

Who lodges the declaration and under which legal capacity.

Incorrect allocation of declarant or representative responsibility.
Technical credentials

Certificates, authentication methods, security controls and onboarding.

An otherwise complete application may be unable to connect.
Message specifications

Supported formats, schemas, code lists, versions and validation rules.

EU data compatibility does not guarantee national message acceptance.
Testing environment

Availability of test systems, sample messages and conformance requirements.

Integration cannot be reliably validated without suitable testing access.
Operational maintenance

Specification changes, outages, message errors and support arrangements.

Ongoing maintenance costs and potential service interruption.
03.4 / MEMBER STATE IMPLEMENTATION

EU rules. National electronic interfaces.

01
Common EU legal framework

The UCC and its delegated and implementing rules establish the legal basis and relevant data requirements for customs declarations.

02
National technical implementation

Import declaration submission generally depends on the competent Member State’s electronic systems and published technical arrangements.

03
Separate EU-wide systems and functions

EU systems serving specific customs or safety and security functions should not be confused with a universal import declaration endpoint. For example, ICS2 concerns entry safety and security information, not the replacement of national import declarations.

ARCHITECTURAL PRINCIPLE

Design country-specific customs adapters only after confirming the availability of the relevant interface, its access conditions and its technical documentation. This verification should precede major software development expenditure.

04 / COMPLIANCE & OPERATIONAL RESILIENCE

Automation at scale.
Accountability at every step.

A customs automation platform must protect the integrity of declaration data, preserve evidence of processing decisions and prevent technical failures from becoming repeated compliance errors.

Security controls, customs compliance checks and operational safeguards address different risks. All three must be designed into the workflow rather than added after deployment.

01 / DATA INTEGRITY

Source-data reliability

Customs declarations must be based on sufficiently accurate and complete information. Automated extraction cannot establish the correctness of unsupported commercial values, commodity codes or origin statements.

RECOMMENDED CONTROLS Source-system identification Field-level validation Evidence and document references Controlled master-data updates
02 / ACCESS SECURITY

Identity and authorisation

Access to commercial records and customs submission functions should be restricted according to operational responsibilities. Technical credentials must not be confused with the legal authority to act as declarant or customs representative.

RECOMMENDED CONTROLS Role-based access control Strong authentication Credential protection and rotation Representation-authority checks
03 / AUDITABILITY

Declaration audit trail

Operators need to reconstruct the information and processing history behind a declaration. Audit records should distinguish original data, transformations, validation results, approvals, transmitted messages and customs responses.

RECOMMENDED CONTROLS Versioned declaration snapshots Timestamped processing events Operator and system attribution Protected change history
04 / EXCEPTION CONTROL

Failures and duplicate prevention

Network failures, timeouts and ambiguous responses can leave the submission status uncertain. Retrying a request without checking its outcome may create duplicate transmissions or inconsistent records.

RECOMMENDED CONTROLS Idempotency and duplicate detection Submission-state reconciliation Controlled retry policies Manual escalation of uncertain states
05 / DATA PROTECTION

Personal and commercial information

E-commerce customs processing may involve personal data, business identifiers, transaction values and commercially sensitive information. Access, storage, sharing and retention require appropriate legal and technical safeguards.

RECOMMENDED CONTROLS Data minimisation Encryption and secure transmission Defined retention policies Processor and controller assessment
06 / CONTINUITY

Operational resilience

Customs systems, marketplace APIs and integration services may become unavailable or change their specifications. A production platform needs controlled recovery procedures and visibility over unresolved declarations.

RECOMMENDED CONTROLS Availability monitoring Backups and recovery testing Message-version management Documented fallback procedures
04.1 / FAILURE SCENARIOS

Where automation can fail.

The most consequential failures are not necessarily software crashes. They are situations in which an apparently successful automated process produces an incorrect customs outcome or an unverified operational state.

FAILURE SCENARIO POTENTIAL CONSEQUENCE DESIGN SAFEGUARD
Incorrect product classification

Wrong declaration data, duty treatment or restriction assessment.

Validated classification records, evidence and review of uncertain cases.

Unsupported H7 selection

Inappropriate reduced dataset or declaration rejection.

Versioned eligibility rules, exclusions and escalation.

Incorrect IOSS handling

Incorrect import VAT processing or mismatched transaction records.

Controlled IOSS data handling and VAT eligibility checks.

Unknown submission outcome

Duplicate transmission or a missing declaration record.

Reconciliation before retry, message correlation and audit logs.

Acceptance treated as release

Goods may be dispatched before the relevant customs release.

Separate legal status states and release-dependent workflow rules.

Customs interface change

Failed submissions or incorrectly formatted messages.

Schema versioning, conformance testing and controlled deployment.

04.2 / EVIDENCE & TRACEABILITY

What a defensible audit trail should record.

01 Source Original records and documents
02 Transformation Mapped fields and rule versions
03 Validation Checks, warnings and approvals
04 Submission Exact message and transmission event
05 Customs response Identifiers, decisions and timestamps

Auditability is a design objective, not proof of compliance by itself. Records must be accurate, appropriately protected and retained according to the legal requirements applicable to the information and procedure concerned.

04.3 / LEGAL ACCOUNTABILITY

Software does not become the declarant.

Automation can perform operations on behalf of a business or customs intermediary, but the legal status of the declarant and any customs representative must be determined under the Union Customs Code.

Article 15(2) UCC addresses responsibility for the accuracy and completeness of information supplied to customs. Articles 18 and 19 govern representation, while Article 170 establishes rules concerning the lodging of customs declarations.

The design should therefore record the relevant legal actor, representation arrangement and authorisation before permitting an electronic submission.

05 / FREQUENTLY ASKED QUESTIONS

Customs automation.
Questions that matter.

Technical and regulatory answers to common questions about automated customs declarations, electronic integration, legal responsibility and operational controls.

01 Can customs declarations be fully automated?

Many processing stages can be automated, including data collection, mapping, validation, message preparation and electronic transmission. However, the extent of automation depends on the applicable customs procedure, the quality of available information, national system capabilities and the operator’s legal and technical authorisations.

Automation does not remove the need for customs compliance assessments or the powers of customs authorities to verify declarations and control goods.

02 Is there a single EU customs API for import declarations?

No single, universally accessible EU API provides a general submission channel for all national import declarations. The Union Customs Code establishes a common legal framework, while relevant import declaration systems and their technical interfaces operate within the applicable EU and Member State implementation arrangements.

EU-level systems such as ICS2 serve particular functions and should not be mistaken for a universal import declaration interface.

03 Can a Shopify, Amazon or other marketplace integration create a customs declaration?

Marketplace data can support the preparation of customs declarations, but commercial order information is not necessarily sufficient. Customs classification, origin, valuation, party identification and declaration-specific data may require additional sources and controls.

A declaration becomes part of the relevant customs procedure only through the legally applicable lodging and acceptance process.

04 Can software automatically choose between H7 and H1?

Software can apply documented eligibility rules to identify potential declaration routes. Nevertheless, the selected dataset must be legally appropriate for the goods and procedure. H7 is subject to specific conditions and exclusions under the relevant delegated rules.

Cases involving uncertain classification, restrictions, incomplete information or ambiguous eligibility should be escalated rather than automatically approved.

05 Does an EORI number provide direct access to customs systems?

Not necessarily. EORI identifies an economic operator for relevant customs purposes, but access to electronic submission channels may require separate registration, authentication, technical onboarding and appropriate authority to lodge declarations.

The specific requirements must be confirmed with the competent customs administration or authorised service provider.

06 Can a customs declaration be automatically resubmitted after a timeout?

A timeout does not prove that the original submission failed. The system should first reconcile the transmission state using available message identifiers, acknowledgements and customs responses.

Automated retries should follow the applicable interface specifications and must avoid creating duplicate or conflicting submissions.

07 Is an MRN confirmation equivalent to customs release?

No. Declaration identification, acceptance, verification and release are distinct concepts. Article 172 UCC addresses acceptance of customs declarations, while Article 194 governs release of goods.

An automated logistics workflow should rely on the relevant customs release status rather than treating an MRN alone as permission to release or dispatch goods.

08 Who is responsible when software submits an incorrect declaration?

Customs responsibilities depend on the legal status of the declarant, any customs representation arrangement and the relevant circumstances. Articles 15, 18, 19 and 170 UCC are particularly relevant.

The existence of automation does not itself transfer customs responsibility to the software. Separate contractual or other liabilities may also arise depending on the parties involved.

09 What records should an automated customs platform preserve?

A defensible audit trail should link source documents, declaration data, transformation rules, validation results, approvals, transmitted messages and customs responses.

Article 51 UCC addresses the keeping of documents and information. Retention, accessibility and personal-data protection requirements must be assessed under the applicable legislation.

THE CUSTOMS EXPLORER PERSPECTIVE

Faster declarations.
Stronger customs control.

The value of customs automation is not simply the number of declarations processed per hour. It is the ability to combine speed, traceability, regulatory accuracy and reliable operational decisions within a controlled digital system.

EXPLORE DIGITAL CUSTOMS