- Confirm whether the sale is an EU distance sale of imported goods and identify the seller, marketplace, intermediary, carrier, and importer/declarant roles before treating it as an IOSS workflow.
- Check the current official EU VAT One Stop Shop guidance for scope and exclusions. Do not infer eligibility solely from a cart value or marketplace label.
- Create a clean catalog record with SKU, product description, material, function, origin, quantity, value, and a candidate HS code. The CSV Catalog Checker can flag missing origin and HS fields before label processing.
- Confirm the required IOSS data handoff with the actual registered party or carrier. Keep the identifier out of public product pages and customer-facing communications unless that controlled workflow directs otherwise.
- Use the Customs Description Quality Checker to make the declaration wording specific enough to identify what is moving, rather than copying a storefront title.
- Keep the IOSS/VAT decision separate from customs classification, customs value, import duty, and carrier handling. Use the Import Duty Calculator only as an estimate worksheet where its assumptions fit the route.
- Check the commercial invoice or carrier declaration data against the order, shipment label, and catalog record before dispatch; record the responsible party and the date of the operational instruction.
- For exceptions, changed rules, high-risk goods, or unclear responsibility, pause and obtain guidance from the registered IOSS party, carrier, intermediary, destination authority, or qualified adviser.
Guide
IOSS Customs Declaration Checklist for Ecommerce Sellers
Prepare IOSS-related ecommerce shipment data without confusing import VAT collection, customs declarations, HS codes, origin, or carrier handoff requirements.
Answer Summary
Preparation checklist
IOSS is designed to simplify declaration and payment of VAT for certain distance sales of low-value goods imported into the EU. It is not a universal shipping setting, customs classification answer, or substitute for a carrier declaration.
The ecommerce task is to keep order, catalog, origin, product-description, value, and HS candidate data accurate enough for the responsible IOSS and carrier workflow.
Eligibility, marketplace role, excise status, consignment value, IOSS number handling, destination, and carrier process can change the applicable path. Do not put an IOSS number in a public product page or treat it as a customer-facing field.
Use this workflow
Required fields or decision table
Fields to prepare before the document draft
| Field or decision | What to prepare |
|---|---|
| Order and consignment value | Record the actual goods value, currency, discounts, quantity, and consignment facts. Keep shipping and tax treatment visible rather than collapsing them into a product title or one opaque total. |
| Seller or deemed-supplier role | Identify whether the seller, marketplace, or another party is responsible for the IOSS workflow. Do not assume a marketplace always uses the seller’s IOSS arrangement. |
| IOSS registration handoff | Record the approved operational instruction from the registered seller, intermediary, marketplace, or carrier. Protect the identifier and do not expose it in invoices, storefront content, or customer communications unless the responsible process requires a controlled handoff. |
| Product description | Use specific product, material, function, and quantity wording. Carrier declarations need shipment facts, not marketing copy. |
| HS code candidate | Prepare a candidate based on product facts, then verify the destination requirement. IOSS does not decide the HS code or remove classification review. |
| Country of origin | Use the actual manufacturing/substantial-transformation origin, not the dispatch warehouse or marketplace country. |
| Destination and carrier channel | Record the EU destination, carrier/postal operator, label platform, importer/declarant arrangement, and current data-transmission instructions. |
| Exception check | Flag excise goods, value/consignment questions, returns, multiple shipments, unclear marketplace role, and changes to EU rules for a separate review. |
Step-by-step preparation
How to prepare the draft
Ecommerce example
How this looks in a seller workflow
A non-EU seller ships a low-value consumer accessory to a customer in Spain through a marketplace that may be the deemed supplier for the order. The seller does not assume its own IOSS record belongs on the label. It confirms the marketplace and carrier instructions, then prepares the SKU description, value, origin, and HS-code candidate from its catalog.
The seller keeps VAT/IOSS handling separate from the tariff and classification review. If the product changes material, origin, consignment structure, or marketplace arrangement, the seller sends the order through the exception check instead of copying a previous label workflow.
- Order record: seller, marketplace role, item value, destination, currency, and relevant discounts.
- Catalog record: exact product description, material/function, origin, candidate classification, and SKU.
- Shipping record: carrier channel, responsible data handoff, applicable controlled identifier process, and final review timestamp.
Verification checklist
Review the draft before it travels with the shipment
- The shipment is reviewed against current IOSS scope and exceptions rather than assumed eligible from value alone.
- Seller, marketplace, intermediary, carrier, importer, and declarant responsibilities are written down for the actual order.
- The IOSS identifier is handled only in the approved operational workflow and is not exposed in public or customer-facing content.
- Product description, origin, HS candidate, value, quantity, currency, and destination agree across order, catalog, and carrier data.
- The seller has checked whether the item or consignment creates an exception requiring a different customs/VAT route.
- The page is used as a preparation checklist, not as tax, customs, or legal advice.
Source-backed checks
What external guidance supports this workflow?
- European Commission: VAT One Stop ShopOfficial overview of IOSS and distance sales of low-value imported goods, including the EUR 150 scope statement and exclusions.
- European Commission: EU Customs Tariff (TARIC)Official reference for EU customs tariff and related measures; IOSS does not replace product classification review.
- European Commission: EORIOfficial EORI eligibility and registration information; which party needs an identifier depends on its customs role.
- Etsy international shipment informationPlatform example showing that labels may be prefilled but sellers remain responsible for reviewing customs descriptions, origin, values, and tariff data.
Internal workflow links
Use the same catalog data in the next review step
Common mistakes
What to avoid
- Treating IOSS as a substitute for a customs declaration, HS code, country-of-origin review, or accurate product description.
- Publishing or emailing an IOSS identifier outside the approved carrier, marketplace, or intermediary process.
- Assuming every marketplace order uses the seller’s own IOSS arrangement.
- Using ship-from warehouse country instead of actual origin.
- Ignoring consignment structure, product exceptions, or changed EU rules when copying a prior shipment workflow.
- Combining VAT, duty, carrier fees, and product value into a single untraceable field.
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
What is IOSS in a customs declaration?
IOSS is an EU VAT collection and declaration simplification for qualifying distance sales of imported low-value goods. Customs declaration data, product classification, origin, and carrier requirements still need to be handled separately.
Is an IOSS number mandatory?
Not for every shipment. The correct VAT/customs route depends on the transaction, value, goods, parties, destination, and current EU rules. Verify the applicable workflow before dispatch.
Does IOSS replace the HS code?
No. IOSS does not classify a product. Prepare and verify the HS/CN/TARIC data required for the destination and carrier workflow.
Where should an IOSS number be entered?
Use only the controlled handoff specified by the registered seller, marketplace, intermediary, or carrier. Do not expose the identifier in public content or ordinary customer communication.
Does every EU-bound order qualify for IOSS?
No. Scope and exceptions matter, including transaction and goods facts. A marketplace may also have a different role than the direct seller.
Do I need an EORI number for IOSS?
They are separate concepts. An EORI may be required for an economic operator carrying out certain EU customs activities; confirm which party is the relevant operator for the actual import workflow.
Disclaimer
TariffCatalog provides informational tools and preparation workflows only. Verify final classification, rates, document requirements, and filing treatment with official sources or licensed professionals.