- Identify the EU import scenario: destination Member State, product, origin, seller/importer arrangement, expected date, value, and declaration channel.
- Collect the physical product facts and separate variants or sets before opening the nomenclature.
- Start with a six-digit HS candidate, then use the current Combined Nomenclature to select the EU eight-digit branch. Read the legal notes and relevant explanatory material.
- Open TARIC and continue to the 10-digit code. Enter or review origin and date so applicable measures can be surfaced for the actual scenario.
- Check whether the result calls for additional TARIC or national codes, certificates, quotas, suspensions, anti-dumping identifiers, or other declaration data.
- Keep classification separate from origin evidence, customs value, preference, VAT/IOSS, and product-compliance checks. Each field needs its own source and owner.
- Save the HS6, CN8, TARIC10, additional codes, source URLs, lookup date, product facts, origin, and review status with the SKU.
- Use the CSV Catalog Checker for missing fields and a paid catalog review when many SKU rows need the same traceable process; verify the final declaration with the responsible party.
Guide
HS vs CN vs TARIC Codes for EU Ecommerce Imports
Move from the international six-digit HS subheading to the EU eight-digit Combined Nomenclature and 10-digit TARIC code while keeping origin, measures, and declaration fields separate.
Answer Summary
Preparation checklist
HS, CN, and TARIC are connected layers, not competing names for one code. The product facts and first six digits lead into EU-specific eight- and 10-digit detail.
CN is updated annually; TARIC integrates measures and is transmitted daily to EU national administrations. A saved code without source date can become stale even when the product is unchanged.
Classification, origin, customs value, preference, anti-dumping, quotas, suspensions, VAT/IOSS, and product controls should remain distinct fields in an ecommerce workflow.
Use this workflow
Required fields or decision table
Fields to prepare before the document draft
| Field or decision | What to prepare |
|---|---|
| HS chapter, heading, and subheading | Use the two-, four-, and six-digit international hierarchy as the starting point. Read section and chapter notes before selecting the HS subheading. |
| Eight-digit CN code | The Combined Nomenclature extends HS to eight digits and supplies EU tariff/statistical detail. Use the current annual edition and explanatory material. |
| 10-digit TARIC code | TARIC adds EU measure detail at digits nine and ten. Use the live TARIC database for the actual product, origin, and date. |
| Additional TARIC or national code | Some declarations need additional codes for anti-dumping, suspensions, end use, excise, VAT, or other measures. The 10-digit TARIC code does not guarantee that every declaration field is complete. |
| Country of origin and preference | Origin drives measures and possible preference, but ship-from country is not proof of origin. Keep non-preferential and preferential origin evidence separate. |
| Import date and customs procedure | Measures can change by date and procedure. Save the intended import date, declaration type, and relevant procedure instead of treating a lookup as permanent. |
| Product facts and variants | Material, composition, function, construction, processing, dimensions, included components, and packaging support the classification. Review variants separately when those facts differ. |
| Measure results | Store duty, quota, suspension, anti-dumping, licensing, and control results as dated outputs linked to the classification and origin, not as part of the product title. |
| Catalog and IOSS fields | Keep customs classification and import measures separate from VAT/IOSS identifiers and checkout-tax records. IOSS does not create or verify a TARIC code. |
Step-by-step preparation
How to prepare the draft
Ecommerce example
How this looks in a seller workflow
A seller imports a silicone kitchen utensil set from China into Germany. The supplier provides only a six-digit HS candidate. The seller records every utensil, material, value, set presentation, manufacturing origin, and expected import date before extending the code.
The reviewer selects a current CN8 candidate from the EU nomenclature, then checks TARIC for the 10-digit path and origin/date measures. The catalog stores the code layers and source dates separately. IOSS or marketplace VAT data remains in another field and is not used as evidence that the TARIC classification is correct.
- Supplier HS6: starting candidate only.
- CN8: EU classification and statistical layer.
- TARIC10: integrated EU measure layer.
- Additional codes: captured when the live result requires them.
- Origin, date, value, IOSS/VAT, and product controls: separate review fields.
Verification checklist
Verify the EU code layers and measures before declaration handoff
- The page uses the current annual CN edition.
- The live TARIC result was checked for the actual origin and date.
- The product facts support the six-, eight-, and 10-digit path.
- Any additional TARIC or national codes are recorded separately.
- Origin evidence is not copied from the dispatch address.
- Duty and commercial-policy measures are dated and linked to the result.
- IOSS/VAT fields are not used as classification evidence.
- Variant and set components have not been hidden under one generic product title.
- The final declaration path is verified with the responsible customs party.
Source-backed checks
What external guidance supports this workflow?
- European Commission: Combined NomenclatureOfficial explanation of the EU eight-digit CN, legal content, and annual updates.
- European Commission: TARICOfficial description of the integrated EU tariff and commercial-policy database.
- European Commission: CLASSSingle-access platform for CN explanatory notes, classification regulations, court rulings, committee conclusions, and TARIC information.
- EU BTI general informationExplains the eight-digit CN and ninth/tenth TARIC levels in the binding-tariff-information context.
Internal workflow links
Use the same catalog data in the next review step
- Classification CasesPaid workspace: keep product facts, candidates, risk review, and the source trail in one preparation record.
- Catalog ReviewPaid workspace: review repeated SKUs or platform CSV rows and use credits only when a listed processing action runs.
- Mapped Review ExportsPaid workspace: export reviewed catalog fields for TariffCatalog, Shopify, WooCommerce, or Amazon workflows.
- Compare PlansCompare one-time and monthly credit options for repeated catalog work.
- Official SourcesOpen the destination tariff, ruling, and government reference before filing.
- MethodologySee how candidates, source dates, and estimate-only boundaries are maintained.
- CorrectionsReport a source, wording, or workflow issue for editorial review.
Common mistakes
What to avoid
- Stopping at six digits for an EU import that requires the EU extension.
- Using an eight-digit CN code as if it contains every TARIC measure.
- Copying a US, UK, or supplier 10-digit extension into TARIC.
- Saving a TARIC result without origin, date, source, or additional-code context.
- Treating IOSS registration or VAT collection as proof of classification.
- Using dispatch country as manufacturing origin.
- Applying one code to materially different variants or mixed sets.
Editorial
Editorial review note
Written by the TariffCatalog Editorial Team for ecommerce document preparation workflows. The page is designed as a preparation checklist, not a filing outcome.
Maintained by Ryan Cole, with review focused on ecommerce catalog, document, and source-check workflow clarity.
Document requirements may be required differently by carrier, destination, shipment value, and product facts. Use the methodology, sources, and corrections pages to understand how the page is maintained.
Official source note
References to verify
Use official sources, carrier guidance, postal operator rules, and destination requirements to verify before filing or shipping.
USITC HTS
Use this official source when checking final classification, duty treatment, or customs requirements.
CBPUse this official source when checking final classification, duty treatment, or customs requirements.
EU TARICUse this official source when checking final classification, duty treatment, or customs requirements.
UK Trade TariffUse this official source when checking final classification, duty treatment, or customs requirements.
FAQ
Common questions
Is a CN code the same as an HS code?
CN builds on HS: the first six digits are the HS level and the EU adds two digits.
How many digits are in a CN code?
A CN code has eight digits.
How many digits are in a TARIC code?
The TARIC code uses 10 digits, and a declaration can also require additional TARIC or national codes.
Does TARIC replace the HS?
No. TARIC extends the HS/CN hierarchy and integrates EU measures.
Can I use a supplier’s 10-digit code in the EU?
Not without verification. National digits from another system are not automatically valid EU CN/TARIC extensions.
Does IOSS determine the TARIC code?
No. IOSS belongs to the VAT and low-value sales/import workflow; it does not classify the product.
How often do CN and TARIC change?
CN is updated annually, while TARIC measure data is maintained and transmitted to national administrations daily. Product records need source dates.
What fields should an ecommerce catalog keep?
Keep HS6, CN8, TARIC10, additional codes, origin, source/date, review status, customs value, preference, VAT/IOSS, and measure outputs in separate fields.
Disclaimer
TariffCatalog provides informational tools and preparation workflows only. Verify final classification, rates, document requirements, and filing treatment with official sources or licensed professionals.