Latest Insights
HS Code Disputes in Bangladesh: Why Classification Strategy Matters
Two defensible readings of the same product can sit several percentage points apart.
Classification reads as a technical formality until the differential reaches a landed-cost model. The code drives the duty rate, the VAT base and the import policy treatment — and when it is questioned, it shapes the dispute that follows.
A classification is a position, not a fact
Tariff schedules are written in general terms and products are specific, so most classification work is an argument from product facts to a heading. Two competent people can reach different headings honestly.
That is why the reasoning matters as much as the result. A code without a documented rationale is a number somebody typed.
Where disputes actually start
Rarely in the law. Usually in an invoice description written for a supplier’s convenience, a catalogue that describes a product family rather than the item shipped, or an entry history that is inconsistent across consignments.
Consistency is itself a position. Where the same product has been entered under different headings, the weakest entry tends to set the terms of the discussion.
The cost is rarely one consignment
A classification question, once raised, looks backwards. Because the same product is imported repeatedly, the exposure is a pattern across a period rather than a single assessment — which is what turns a technical disagreement into a balance-sheet item.
Advance rulings, and when they help
Where a product is genuinely borderline and the volume justifies it, seeking certainty in advance converts an open exposure into a known one. It is most useful before a pattern of entries has been established, and least useful as a response to a query that has already been raised.
Building a position that survives audit
- Start from the product as it physically is: composition, function, stage of processing, how it is presented.
- Read the heading against the section and chapter notes, not the heading alone.
- Write the rationale down at the time, not after a query arrives.
- Keep entries consistent, and where a position changes, record why.
