Customs and Import Duties

Customs and import duties in international fulfillment affect not only costs but also delivery speed, customer satisfaction and complaint rates. Even small errors in tariff numbers, Total Shipment Value or country-of-origin declarations lead in practice to delays, additional charges or returns. Anyone shipping across borders therefore needs a stable process that connects purchasing, product data, shipping software, carriers and customer communication.

This guide covers the most important fundamentals, typical cost components and an actionable workflow for retailers, fulfillment teams and operations managers. The focus is on concrete day-to-day decisions: which data must be available before shipping, how duties are calculated, which documents are mandatory and how to reduce errors systematically.

Why customs processes are strategically important in fulfillment

International shipping may appear at first glance to be purely a shipping topic, but in reality it is an end-to-end process with a direct impact on conversion, margin and service level. When customs information is missing, shipments often end up in manual clearance. This extends transit time and increases support workload.

Important impacts in day-to-day operations:

• Higher delivery success rate through correct advance data
• Fewer follow-up charges and surprise costs for the recipient
• Lower return rate thanks to transparent duty communication
• More stable delivery times during peak periods
• Better predictability of contribution margins per target market

Impact of customs quality on KPIs

Fundamentals: Which charges arise on imports

On imports into a destination country, several cost items may be relevant depending on the type of goods and delivery terms. Companies must separate these items so that calculation and communication remain clear.

Typical cost components

Quick rule for teams

1. First secure goods classification and declaration data.
2. Then configure cost logic per destination country in the system.
3. Finally standardize customer communication on duties and transit times.

DDP vs. DAP at checkout

Mandatory data for reliable customs processing

Errors almost always originate in master data. Particularly critical are imprecise product descriptions, missing HS codes or inconsistent goods values between shop, ERP and shipping system.

This data must be complete before shipping

• Clear product designation without marketing fluff
• HS code per SKU with documented source
• Goods value per line item and total shipment value
• Country of origin per article
• Net weight and, if relevant, gross weight
• Number of units per line item
• EORI Information or comparable registration data, if required

Master data before go-live

• HS code per SKU verified
• Country of origin per SKU maintained
• Value logic aligned between shop and ERP
• Product texts standardized for customs purposes
• Plausibility check for weights active
• Test shipment to main destination countries completed
• Carrier invoices checked for discrepancies
• Support FAQ for import duties live

HS code, goods value and Incoterms – thinking them through together

In many projects, HS code, value declarations and Incoterms are handled separately. Operationally this does not work: all three factors together influence how quickly and correctly a shipment passes through customs clearance.

Practical logic for day-to-day operations

1. Product classification first: Without a valid tariff number, any cost estimate is uncertain.
2. Standardize value definition: Uniform rule on whether discounts, shipping or insurance are included.
3. Choose Incoterm consciously: The selected delivery term determines who bears duties and how transparent costs are for customers.
4. Version in the system: Document changes to HS code or value logic so that discrepancies remain auditable.

Introducing international customs processes

IOSS, OSS and local tax logic

For shipments into the EU or out of the EU, IOSS and OSS are important instruments for clean tax processing. At the same time, they do not replace the obligation to declare correctly. Many teams confuse tax registration with customs completeness. Both must be handled cleanly in parallel.

Recommendation for operations:

• Clearly separate responsibilities between tax, finance and operations
• Secure use of tax IDs technically in checkout and shipping data flow
• Check invoice and declaration data daily for consistency
• Document exception cases for thresholds and special goods as SOP

Most common causes of customs holds

Documents and communication along the supply chain

Even with technically correct data, delays occur when documents are incomplete or the recipient does not know which charges to expect. A professional process combines document creation and proactive communication.

Minimum set of documents (adjust per destination market)

Document release before shipping

Operational 30-day plan for error reduction

Teams achieve the greatest effects not through one-off actions but through a short iteration rhythm with clear metrics.

Week 1 to 4: recommended process

1. Week 1: Analyze data quality for top 100 SKUs and close gaps.
2. Week 2: Standardize checkout and email communication on duties.
3. Week 3: Evaluate test shipments to prioritized destination countries.
4. Week 4: Conduct KPI review with finance, support and operations.

Measurable targets after 30 days:

• Reduce share of manual customs clarifications
• Lower average transit time for international shipments
• Decrease support inquiries on import costs
• Narrow gap between calculated and actual duties

Related topics

• Cross-border shipping
• EU shipping vs. third country
• Incoterms explained
• Customs declaration
• IOSS and OSS for the EU

Last updated: July 7, 2026