Customs Explorer
⌕

Customs Explorer

Parcel data requirements

E-COMMERCE CUSTOMS DATA

Parcel Data
Requirements.

The information behind every cross-border parcel matters.

Understand the product, transaction, shipment and operator information used in EU customs processes for international e-commerce parcels — and why incomplete or inconsistent data can create problems before goods reach their destination.

Data requirements differ between customs declarations, entry summary declarations and other regulatory processes. The applicable dataset depends on the operation and legal framework.

PARCEL DATA RECORD
ILLUSTRATIVE
CROSS-BORDER SHIPMENT Structured parcel information From commercial data to customs processes
01
Goods description What is being shipped?
02
Commodity classification How are the goods classified?
03
Value and currency What transaction information applies?
04
Origin and parties Where are the goods from, and who is involved?
05
Transport information How is the parcel being moved?
Customs declarations
Safety & security data
E-commerce shipments
EU customs requirements
PARCEL INFORMATION FRAMEWORK

Essential data behind
cross-border parcels.

Reliable parcel information begins with accurate commercial and logistics records. These data may support customs declarations, safety and security filings, regulatory checks and shipment processing.

01 GOODS DATA

Goods description

The description should identify what the goods actually are. Generic descriptions can make classification, risk assessment and customs verification more difficult.

PRODUCT NAME MATERIAL / TYPE QUANTITY
DATA QUALITY EXAMPLE

“Cotton T-shirts” is more informative than “clothing” or “gift”.

02 CLASSIFICATION

Commodity code

Commodity classification connects the product to the applicable tariff structure and relevant customs measures. The required code length depends on the declaration and regulatory context.

HS CN TARIC
IMPORTANT DISTINCTION

HS, CN and TARIC codes are related but do not represent identical levels of classification.

03 TRANSACTION DATA

Value and currency

Transaction information helps establish the value relevant to customs processes. The commercial price and the customs value are not necessarily the same.

PRICE CURRENCY VALUATION DATA
COMMON CONTROL

Check whether transport costs, adjustments or other valuation elements must be considered.

04 ORIGIN DATA

Country of origin

The origin of the goods may affect customs measures, trade policy requirements and eligibility for preferential treatment. Origin must not be confused with the country of dispatch.

NON-PREFERENTIAL ORIGIN PREFERENTIAL ORIGIN
KEY DISTINCTION

Goods shipped from one country may have originated in another country.

05 PARTIES & IDENTIFIERS

Sender, recipient and operators

Customs and transport processes may require information about the consignor, consignee, importer, declarant and other relevant operators, depending on the filing.

NAMES & ADDRESSES EORI WHERE APPLICABLE
COMMON MISUNDERSTANDING

The buyer, consignee, importer and declarant are not necessarily the same person.

06 LOGISTICS DATA

Shipment and transport details

Shipment references, package information, weights and transport details support parcel identification, logistics handling and applicable customs filings.

TRACKING / REFERENCES PACKAGES WEIGHT
PRACTICAL CONTROL

Ensure that shipment references can be matched to the corresponding commercial and customs records.

UNDERSTANDING THE DATA

Commercial information is not the complete customs dataset.

A seller’s product and order records provide a starting point, but customs declarations may require additional information, legal determinations and procedure-specific data elements.

A

Commercial source data

Product catalogue, sales transaction, invoice, seller and customer information.

B

Customs declaration data

Classification, valuation, procedure, origin, customs parties and applicable document references.

C

Transport and safety data

Shipment and transport information required for the relevant logistics and safety filings.

Scope of this guide: These are important categories of parcel information, not a universal mandatory field list. Exact requirements must be checked against the applicable EU customs data rules, electronic system specifications and national implementation arrangements.

FROM ORDER TO CUSTOMS

How parcel data
moves across the supply chain.

Cross-border e-commerce depends on information exchanged between commercial, logistics and customs participants. Understanding who provides, transforms and submits data helps identify gaps before they affect the shipment.

01 SOURCE

Seller & product records

The seller’s systems provide product descriptions, order values, quantities, customer information and other commercial data.

PRODUCT + ORDER DATA
02 EXCHANGE

Marketplace & platforms

Where involved, marketplaces or integration platforms may collect, validate and transmit transaction information to logistics partners.

STRUCTURED DATA EXCHANGE
03 LOGISTICS

Carrier & logistics operator

The transport operator manages shipment references, routing, package details and other information needed for transport and applicable filings.

SHIPMENT + TRANSPORT DATA
04 DECLARATION

Declarant & customs representative

The relevant declarant, or a representative acting under the applicable arrangements, prepares and submits the customs declaration using the required data.

CUSTOMS DECLARATION
05 AUTHORITY

Customs systems & authorities

The competent systems receive and process submitted information. Customs authorities may carry out validation, risk analysis and controls.

PROCESSING + CONTROLS

Illustrative information flow only. Actual operations may involve fewer or additional participants, parallel filings and different submission sequences.

ROLES & RESPONSIBILITIES

Data provider, filer and legally responsible party are not always the same.

The practical source of information and the legal obligations associated with a filing must be assessed separately.

Data provider

Supplies commercial, product or logistics information. This may include the seller, marketplace or another party holding relevant records.

Filing or transmitting party

Sends information through the relevant electronic channel. Its responsibilities depend on the type of filing and applicable legal arrangements.

Legally responsible party

Bears obligations arising under the applicable customs rules. Responsibility cannot be determined solely from who supplied the data or operated the software.

CUSTOMS DECLARATION

Goods declaration

Supports the placement of goods under a customs procedure. It contains the data required for the relevant procedure, including classification, valuation and other applicable declaration particulars.

PROCEDURE-BASED DATA REQUIREMENTS
SAFETY & SECURITY

Entry summary declaration (ENS)

Provides advance information for safety and security risk analysis when required. Under ICS2, filing obligations and possible multiple filing arrangements depend on the transport operation and applicable rules.

ADVANCE RISK-ASSESSMENT DATA
Important compliance distinction

An ENS and a customs declaration serve different legal purposes. One does not automatically replace the other. A marketplace’s involvement or a carrier’s transmission of data does not, by itself, establish who is the declarant or who bears the relevant customs obligations.

DATA QUALITY & VALIDATION

Better parcel data.
Fewer avoidable problems.

Incomplete or inconsistent information can trigger system rejections, requests for clarification or additional controls. Effective validation starts before data is transmitted to a carrier, intermediary or customs system.

01 DESCRIPTION

Vague product descriptions

Labels such as “goods”, “accessories” or “samples” may not adequately identify the contents of a parcel for the relevant customs or safety filing.

AVOID “Clothing”
MORE SPECIFIC “Men’s cotton T-shirts”
VALIDATION CHECK

Describe the actual product, including relevant characteristics.

02 CLASSIFICATION

Incorrect commodity codes

A code may be incomplete, outdated or unsuitable for the actual product. Different filings may require different levels of classification detail.

RISK Unverified product code
CONTROL Classification review
VALIDATION CHECK

Verify the classification and required code format for the filing.

03 VALUATION

Value and currency inconsistencies

Differences between order records, invoices and transmitted shipment data can create questions about the declared transaction information.

RISK Conflicting amounts
CONTROL Reconciled records
VALIDATION CHECK

Reconcile values and currencies; assess customs valuation separately.

04 PARTY DATA

Missing or inconsistent party details

Names, addresses, roles or identifiers may be incomplete, incorrectly mapped or inconsistent across commercial and logistics systems.

RISK Incomplete party record
CONTROL Validated party data
VALIDATION CHECK

Check the parties and identifiers required for the specific filing.

05 LOGISTICS

Shipment reference mismatches

Tracking identifiers, package counts, weights or transport references may not match the information exchanged between the seller and logistics partners.

RISK Disconnected records
CONTROL Traceable references
VALIDATION CHECK

Match shipment references, package details and associated records.

06 SYSTEM EXCHANGE

Data mapping and transmission errors

Information can be lost, transformed incorrectly or rejected when data moves between e-commerce, logistics and customs software systems.

RISK Incorrect field mapping
CONTROL Schema and response checks
VALIDATION CHECK

Validate data formats, mandatory fields and submission responses.

PRE-SUBMISSION CONTROL

A practical four-stage validation process

A structured review can reduce avoidable errors. It should be adapted to the actual filing and the operator’s systems.

QUALITY WORKFLOW
01

Collect

Gather the relevant product, transaction and shipment data.

02

Validate

Check completeness, formats, classification and consistency.

03

Transmit

Send the appropriate dataset through the designated channel.

04

Monitor

Review acknowledgements, errors and any required follow-up.

Validation is not the same as customs acceptance.

Passing an internal quality check or a technical schema validation does not establish that a declaration is legally correct or that customs has released the goods. Formal acceptance, control and release depend on the applicable customs procedure and system responses.

EU CUSTOMS LEGAL FRAMEWORK

Understanding the rules
behind parcel data.

EU customs data requirements are established through the Union Customs Code and its implementing framework. The information required for an e-commerce parcel depends on the declaration type, the customs procedure and the applicable safety and security obligations.

LEGAL FOUNDATION

Three core EU customs regulations

These instruments establish the principal legal framework for customs declarations, data requirements and the operation of customs procedures in the European Union.

01 BASIC REGULATION

Union Customs Code

Regulation (EU) No 952/2013

Establishes the general legal framework for customs procedures, declarations, obligations and customs supervision within the Union.

Read regulation
02 DELEGATED ACT

UCC Delegated Regulation

Regulation (EU) 2015/2446

Supplements the UCC, including rules and data requirements relevant to customs declarations. Annex B contains important declaration data provisions.

Read regulation
03 IMPLEMENTING ACT

UCC Implementing Regulation

Regulation (EU) 2015/2447

Establishes detailed implementation rules for the UCC. Annex B provides formats and codes for relevant customs data requirements.

Read regulation
DECLARATION TYPES

Different filings. Different purposes.

The same parcel may be associated with different customs and safety filings. Their legal purpose, data requirements and responsible parties must not be confused.

H7 REDUCED DATASET

Low-value consignment declaration

The H7 dataset is designed for eligible low-value consignments, subject to the conditions and exclusions established by EU customs legislation.

Key considerations
  • Generally linked to consignments with an intrinsic value not exceeding EUR 150.
  • Specific eligibility conditions and exclusions apply.
  • Not every parcel valued below EUR 150 qualifies.
  • VAT arrangements, including IOSS where applicable, require separate assessment.
SIMPLIFIED DATA REQUIREMENTS — NOT A UNIVERSAL EXEMPTION
H1 STANDARD DATASET

Standard import declaration

The H1 dataset is used for standard declarations for release for free circulation and end-use under the relevant EU customs data framework.

Key considerations
  • Supports the relevant customs procedure and legal requirements.
  • May require a broader set of declaration particulars.
  • Classification, valuation and origin remain central.
  • Supporting documents and authorisations depend on the operation.
PROCEDURE-SPECIFIC IMPORT DECLARATION DATA
ENS SAFETY & SECURITY

Entry summary declaration — ICS2

An entry summary declaration provides advance information for safety and security risk analysis before goods enter the customs territory of the Union.

Key considerations
  • Applies under the relevant entry and transport rules.
  • Contains data intended for advance risk assessment.
  • Filing obligations can involve different transport participants.
  • Multiple filing arrangements may apply in relevant circumstances.
NOT A SUBSTITUTE FOR A CUSTOMS IMPORT DECLARATION

Important: The EUR 150 threshold is relevant to the eligibility rules for the H7 declaration dataset; it must not be interpreted as a general exemption from import VAT or from customs formalities. Applicable legislation and any subsequent amendments must always be checked for the date of the operation.

TECHNICAL DATA FRAMEWORK

Why Annex B matters

EU customs data requirements are organised into defined datasets and data elements. Annex B is a central reference for identifying the particulars associated with different declarations.

01

Data requirements

Identify the information required for the relevant declaration or notification under the applicable rules.

02

Formats and codes

Apply the prescribed formats, code lists and technical requirements to the relevant data elements.

03

System implementation

Check the applicable electronic system specifications, deployment status and national implementation arrangements.

OFFICIAL EU SOURCES

Consult the applicable legal and technical framework

Use consolidated legal texts and official European Commission guidance when assessing current requirements.

PRACTICAL REFERENCE

Parcel data requirements:
frequently asked questions.

Practical answers to common questions about customs information, low-value parcels, electronic declarations and data responsibilities in EU e-commerce.

What information is needed for an international parcel?

Relevant information commonly includes a precise goods description, quantity, value, currency, origin, sender and recipient details, and shipment references. Commodity codes and additional declaration particulars may also be required. The exact dataset depends on the customs or transport filing concerned.

Is a commercial invoice enough for customs clearance?

Not necessarily. A commercial invoice provides important transaction information, but the relevant customs declaration may require additional data, supporting documents, identifiers or authorisations. An invoice does not replace a customs declaration.

What is the difference between H7 and H1?

H7 identifies a reduced customs declaration dataset for eligible low-value consignments under the applicable conditions. H1 identifies the standard dataset for release for free circulation and end-use. The appropriate declaration depends on the goods, their value, the procedure and current legislation.

Does a parcel below EUR 150 always qualify for H7?

No. Value is only one eligibility factor. Specific exclusions and conditions apply, including restrictions relating to certain categories of goods. The rules in force on the declaration date must be checked, particularly where legislative changes affect low-value consignments.

Are ICS2 and customs import declarations the same?

No. ICS2 supports the collection and processing of advance safety and security information, including entry summary declarations. A customs import declaration serves a different legal purpose, relating to the placement of goods under the relevant customs procedure.

Who is responsible for submitting parcel customs data?

Responsibility depends on the filing. The declarant and any customs representative have obligations under the applicable customs rules. ENS obligations follow a separate legal framework. Sellers, marketplaces and logistics providers may supply or transmit information without necessarily being the legally responsible declarant.

Can incomplete parcel data delay customs processing?

Yes. Missing, inconsistent or incorrectly formatted information can lead to technical rejections, requests for clarification or additional checks. Internal validation can help identify avoidable problems, although it cannot guarantee customs acceptance or release.

Where can I find the official EU data requirements?

Start with the Union Customs Code, the UCC Delegated Regulation and the UCC Implementing Regulation, particularly their relevant Annex B provisions. Also consult the European Commission’s customs guidance and the technical specifications of the electronic system concerned.

CUSTOMS EXPLORER

Understand the data.
Improve the process.

Explore the EU customs framework behind e-commerce shipments, electronic declarations and international parcel processing.