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.
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.
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.
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.
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.
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.
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.
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.
Three different systems of responsibility
Commercial systems
Maintain orders, invoices, product records and shipment information. These systems supply data but do not themselves create a legally accepted customs declaration.
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.
Customs authorities
Operate the relevant customs systems, accept declarations, carry out controls and authorise release in accordance with the applicable customs rules.
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.
Article 6 of Regulation (EU) No 952/2013 establishes the general principle of electronic data-processing techniques for exchanges and storage of information required under customs legislation. Articles 15, 18–19, 158, 162 and 170 remain relevant to information accuracy, representation and the lodging of customs declarations.
Annex B of Delegated Regulation (EU) 2015/2446 and Implementing Regulation (EU) 2015/2447 provides the applicable data requirements and formats, subject to the relevant provisions, amendments and transitional arrangements.
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.
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.
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.
Reduced dataset where the current legal conditions and exclusions permit its use.
Standard declaration dataset where applicable to release for free circulation.
Unclear eligibility, missing evidence, restrictions or other non-standard cases.
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.
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.
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.
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.
Three decisions the software must keep separate
Deterministic checks can evaluate formats, mandatory fields, consistency and documented eligibility criteria.
Classification, valuation, origin, restrictions and representation may require evidence and qualified human assessment.
Acceptance, verification and release are governed by customs legislation and the competent authority’s decisions.
Regulation (EU) No 952/2013: Article 6 on electronic exchanges; Article 15 on information responsibilities; Articles 18–19 on customs representation; Article 158 on customs declarations; Article 162 on their contents; Article 170 on lodging; Article 172 on acceptance; Articles 173–174 on amendment and invalidation; Article 188 on verification; and Article 194 on release.
Delegated Regulation (EU) 2015/2446, including Article 143a and Annex B, and Implementing Regulation (EU) 2015/2447 provide supplementary rules relevant to declaration datasets and their electronic implementation. The consolidated versions and applicable dates must be checked for the transaction concerned.
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.
Customs Integration Engine
What can be integrated?
Different platforms contribute different elements to a customs declaration. None should be assumed to contain every legally required field.
Marketplace APIs
Marketplace integrations may expose order lines, product identifiers, transaction amounts, customer details and fulfilment information, subject to permissions and API availability.
ERP & Product Master Data
ERP systems can supply commercial invoices, supplier information, product descriptions, valuation components and maintained customs attributes where those records exist.
Warehouse & Carrier Systems
Logistics platforms can contribute package references, transport identifiers, weights, routing information and shipment events.
Requirements before connecting to customs
The actual prerequisites must be established for the target country, procedure, operator and technical integration channel.
EORI and any additional national registration conditions.
Identification does not automatically grant system access.Who lodges the declaration and under which legal capacity.
Incorrect allocation of declarant or representative responsibility.Certificates, authentication methods, security controls and onboarding.
An otherwise complete application may be unable to connect.Supported formats, schemas, code lists, versions and validation rules.
EU data compatibility does not guarantee national message acceptance.Availability of test systems, sample messages and conformance requirements.
Integration cannot be reliably validated without suitable testing access.Specification changes, outages, message errors and support arrangements.
Ongoing maintenance costs and potential service interruption.EU rules. National electronic interfaces.
The UCC and its delegated and implementing rules establish the legal basis and relevant data requirements for customs declarations.
Import declaration submission generally depends on the competent Member State’s electronic systems and published technical arrangements.
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.
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.
Article 6 of Regulation (EU) No 952/2013 addresses electronic data exchanges. Articles 9 and 15 concern registration and information responsibilities; Articles 18–19 govern customs representation; and Articles 158 and 170 concern customs declarations and their lodging.
The relevant Annex B provisions of Delegated Regulation (EU) 2015/2446 and Implementing Regulation (EU) 2015/2447 provide data requirements and formats. Actual message transmission also depends on the applicable system specifications and access conditions.
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.
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.
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.
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.
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.
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.
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.
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.
Wrong declaration data, duty treatment or restriction assessment.
Validated classification records, evidence and review of uncertain cases.
Inappropriate reduced dataset or declaration rejection.
Versioned eligibility rules, exclusions and escalation.
Incorrect import VAT processing or mismatched transaction records.
Controlled IOSS data handling and VAT eligibility checks.
Duplicate transmission or a missing declaration record.
Reconciliation before retry, message correlation and audit logs.
Goods may be dispatched before the relevant customs release.
Separate legal status states and release-dependent workflow rules.
Failed submissions or incorrectly formatted messages.
Schema versioning, conformance testing and controlled deployment.
What a defensible audit trail should record.
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.
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.
Regulation (EU) No 952/2013: Article 15 on information responsibilities; Articles 18–19 on customs representation; Article 51 on keeping documents and information; Article 170 on lodging customs declarations; Articles 172–174 on acceptance, amendment and invalidation; and Articles 188 and 194 on verification and release.
Regulation (EU) 2016/679 (GDPR): Articles 5, 6, 25 and 32 are relevant to principles of processing, lawful bases, data protection by design and security of personal-data processing, where the GDPR applies.
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 regulatory foundation
of digital customs.
Primary EU legislative instruments governing electronic customs procedures, declarations, representation, recordkeeping and data protection.
Union Customs Code — electronic exchanges, customs representation, declarations, acceptance, verification and release.
ARTICLES 6, 15, 18–19, 51, 158, 170–174, 188, 194Supplementary UCC rules, including conditions for reduced declaration datasets and customs data requirements.
ARTICLE 143a · ANNEX BImplementing rules and relevant formats, codes and data requirements for electronic customs procedures.
ANNEX B · IMPLEMENTING PROVISIONSPersonal-data processing principles, legal bases, data protection by design and security obligations where applicable.
ARTICLES 5, 6, 25, 32Regulatory note: EU customs legislation should be consulted in its consolidated, applicable version. National technical specifications, customs system access conditions and transitional arrangements may affect implementation.
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