IND imports ▲ 4.2%USA coffee 0901 ▲ 11.8%VNM exports ▲ 6.1%BRA 0901.11 ▲ 9.4%DEU machinery ▲ 2.7%Last refresh: 2026-08-01

The Importer Exporter Code, explained

A ten-digit identifier issued to Indian businesses that trade across the border. Without it, a consignment cannot be declared.

The Importer Exporter Code is the identifier that ties an Indian business to its customs filings. It is issued centrally, it is linked to the entity’s PAN, and it is required on both the bill of entry and the shipping bill. In practice it is the primary key of Indian trade.

Who needs one

Any commercial importer

A business bringing goods in for sale or use in production.

Any commercial exporter

A business sending goods out, whether manufacturer or merchant.

Service exporters claiming benefits

Where a scheme requires it, even without physical goods.

Not personal imports

Goods for personal use are handled differently and do not need one.

What it does, and does not, do

An IEC allows a business to file. It is not a licence for any particular product, it does not grant preferential duty, and it does not exempt anyone from product-specific regulation. Restricted and prohibited goods remain restricted and prohibited.

Why it matters when you read trade data

Because the code is entity-linked, Indian shipment records aggregate cleanly by company in a way that free-text name matching never quite achieves. Where a record set carries the identifier, a company’s whole trade history assembles without the entity-resolution guesswork that plagues other markets.

That is what makes an Indian company trade profile unusually reliable, and why separating manufacturers from merchant exporters is more tractable here than in most jurisdictions.

An IEC is not a licence

It lets you file. It does not authorise any particular product. Restricted and prohibited goods stay restricted and prohibited regardless of who holds a code.

How an entity identifier changes what data can do

Most trade data problems that look technical are really identity problems. A declaration records a company name as typed, and across thousands of filings by different agents over years, one business fragments into dozens of strings. Counting suppliers becomes counting spellings. Aggregating a company’s volume undercounts it. A concentrated market looks fragmented, and a strategy built on that looks reasonable and is wrong.

A stable identifier attached to the filing dissolves the problem. Where Indian records carry the code, a company’s whole history aggregates deterministically rather than probabilistically — no fuzzy matching, no judgement calls about whether two similar names are the same business, no risk of over-merging two genuinely different companies into one profile. That is why company-level analysis of Indian trade is more reliable than the same analysis in markets that publish names alone.

Name-only matching

  • Suffix variants fragment one company
  • Transliteration produces multiple spellings
  • Branch filings look like separate businesses
  • Over-merging is invisible in the output
  • Counts of counterparties are unreliable
VS

Identifier-linked records

  • One code, one entity, deterministically
  • Spelling variation is irrelevant
  • Branches roll up to the registered entity
  • No merge decisions to get wrong
  • Counterparty counts mean what they say

What the code does not do

It is worth separating the identifier from the permissions. Holding a code allows a business to file import and export declarations. It does not authorise any particular product, it confers no duty benefit, and it does not exempt anyone from product regulation. Restricted goods remain restricted, prohibited goods remain prohibited, and goods needing a separate agency approval still need it. A surprising number of first-time traders conflate the two and discover the difference at the port.

Practical implications for reading Indian records

Three things follow. First, a company’s Indian trade history can be assembled with confidence, which makes counterparty verification genuinely reliable rather than indicative. Second, manufacturers can be separated from merchant exporters by checking whether input imports and finished-goods exports sit under the same identifier. Third, changes over time — a new product chapter, a new origin, a stop in activity — are attributable to a specific business rather than to a name that may or may not be the same business it was last year.

Check both flows for one identifier

The most informative single query in Indian trade data is a company's import and export records side by side. Inputs in and finished goods out under related chapters is the clearest evidence of a real manufacturing operation that the record can offer.

Checking any of this against the record

Everything above is a framework, and a framework is only worth what it survives contact with. The useful discipline is to test each assumption against what consignments actually did, because customs data is one of the few commercial sources where the underlying event — goods crossing a border — physically happened and was documented under legal obligation at the time.

Two failure modes account for most wrong conclusions drawn from trade data, and both are easy to avoid once named. The first is reading the incomplete tail of a series as a decline — authorities publish on a lag and revise afterwards, so the last one or two periods will fill in after you look. The second is reading a value movement as a demand movement, when declared value can move because volume moved, because unit price moved, or because the product mix inside a tariff line changed.

What the record cannot answer

Customs data covers goods that crossed a border. It does not cover services, domestic trade, margin, contract terms or intent. Treat it as a dated, quantified observation to corroborate — not as a conclusion that arrives finished.

Turning the Importer Exporter Code, explained into a repeatable process

The difference between teams that get value out of trade data and teams that ran one interesting project is almost never analytical sophistication. It is whether the work became a routine. A saved query reviewed weekly, a short written note against each counterparty you assessed, and a standing habit of checking the period stamp before quoting a figure will out-perform an elaborate one-off study within a quarter, because markets move and a study does not.

The second habit worth building is writing down not just what you concluded but why and when. Records get revised, prices move, and counterparties change behaviour. Six months later nobody remembers whether a supplier was rejected on volume, on price band or on timing, and without that note the assessment simply gets repeated from scratch. A one-line rationale is what converts a list into institutional knowledge, and it costs seconds at the point where the thinking has already been done.

Finally, be explicit with colleagues about the confidence attached to any figure you circulate. A declared value from a complete period, controlled for origin and unit, is strong evidence. The same figure pulled from an incomplete recent period, averaged across a whole chapter, is barely evidence at all — and the two look identical once they are in a slide. Saying which one you have is what keeps trade data credible inside an organisation over time.

Frequently asked questions

Is an IEC required for every export?

For commercial import and export of goods, yes. Personal-use imports are handled differently, and some service transactions fall outside it entirely.

Does an IEC expire?

The code itself is intended to be permanent, but it is subject to periodic confirmation requirements. A lapse in that confirmation can suspend the ability to file, which is a problem discovered at the worst possible moment.

Can one business hold more than one IEC?

The code is tied to the entity's permanent account number, so one entity holds one code. Group companies each hold their own, which is why a group's trade has to be assembled across several identifiers rather than one.

Does the IEC appear in published trade data?

Where the record set includes it, company-level aggregation becomes deterministic rather than dependent on name matching. That is a material difference in the reliability of any counterparty analysis built on it.

How current is the trade data behind this?

Markets refresh on their customs authority's own release cycle — monthly for most, 45 to 60 days for a few. The most recent one or two periods are always still filling in, so exclude them when you are reading a trend rather than treating the gap as a decline.

Can I check this against my own product?

Yes. Give us the HS code or a product description and the market you care about, and we will return a sample of live customs records filed against it.

Keep reading

Related guides

The next questions this one usually raises are covered in Company names in trade data, The shipping bill, explained and Export documentation checklist. Each picks up where this article stops, and together they cover the sequence a consignment actually goes through — classification and duty before anything moves, documentation and payment while it moves, and verification of the counterparty before any of it is committed to. Reading them in that order is usually more useful than reading them by topic.