Customs data is one of those terms that everyone uses and few define. Here is what it actually is, where the records come from, and why the coverage map has holes in it.
When goods cross a border, someone has to declare them. That declaration is a legal filing — not a marketing document — and it exists because a government wants to know what entered the country and what duty is owed.
A declaration typically records who shipped it, who received it, what the goods are classified as, how much they weigh, what they are worth, and how they travelled. That is the raw material everyone in this industry works from.
This distinction causes more confusion than anything else in the field:
The practical consequence: on declaration records, searching by product code works well. On bill-of-lading records it does not, and searching the goods description finds more. If a provider does not distinguish between the two, they are probably not close to the source data.
Coverage is decided by each country, and they do not agree. Broadly:
We set out which is which, market by market, on the country pages — including the markets we do not cover. A provider who claims uniform global coverage is either misinforming you or has never checked.
Because the importer fills in the code, not a central authority. The same product gets filed under different — sometimes outdated, sometimes simply wrong — headings by different companies.
This is not a defect of the data; it is a property of how the data is created. It means a search built on a single code will miss shipments that are genuinely there. Merging code-based and description-based searches is the only way to get close to complete.
There is a worked example in HS code 854140, where the same product is split across two codes by real importers.
Tell us the product and the market. We will reply with what the records actually contain for it — which markets have shipment detail, which have statistics only, and what a working list would look like. No charge, and no obligation.