Every Bill of Entry, Shipping Bill and manifest names the customs station it is filed at with a six-character code: INNSA1, INDEL4, INTKD6. Get the code wrong and ICEGATE rejects the document or, worse, routes it to the wrong customs house. This article explains how the codes are built and how to keep a list of them current.
Anatomy of a code
A customs location code has three parts:
| Part | Length | Example | Meaning |
|---|---|---|---|
| Country | 2 | IN | Always IN for Indian customs stations |
| Location | 3 | NSA | The place, usually matching the UN/LOCODE or IATA code |
| Type | 1 | 1 | What kind of station it is |
The type suffix is the part people miss. The same three letters can appear with different suffixes for different stations in the same city:
| Suffix | Type | Example |
|---|---|---|
| 1 | Sea port | INMAA1 Chennai sea port |
| 2 | Rail | INAMD2 Ahmedabad rail |
| 4 | Air cargo | INMAA4 Chennai air cargo complex |
| 5 | Foreign post office | INAMD5 Ahmedabad FPO |
| 6 | Inland container depot or container freight station | INTKD6 Tughlakabad ICD |
| B | Land customs station | INAGTB Agartala land border |
So Chennai has at least INMAA1 (sea) and INMAA4 (air), and they are not interchangeable: a sea consignment filed under INMAA4 goes nowhere.
Why a CFS shares its parent port's code
Container freight stations attached to a sea port are not separate customs stations for filing. A Bill of Entry for a container that will be cleared at a CFS at Nhava Sheva is filed under INNSA1, the port code, and the CFS is named separately in the document. Many of the ICD and CFS codes ending in 6 are standalone inland depots with their own customs jurisdiction, which is why they get their own code.
EDI and non-EDI stations
Most stations run the Indian Customs EDI System (ICES) and accept documents electronically through ICEGATE. A smaller number, mostly minor ports and land customs stations, still process documents manually. Filing software needs to know which is which: an electronic filing to a non-EDI station cannot be processed, and some incentive schemes are only claimable at EDI stations. ICEGATE's list carries this status, and EximFetch serves it as two datasets: customs EDI locations and customs non-EDI locations.
How many are there
ICEGATE's own list, as fetched on 16 November 2026, holds 589 customs locations:
| Type | Count |
|---|---|
| ICD and CFS (suffix 6) | 414 |
| Sea ports (1) | 65 |
| Land customs stations (B) | 62 |
| Air cargo (4) | 33 |
| Foreign post offices (5) | 9 |
| Rail (2) | 6 |
The list changes a few times a year: new ICDs are notified, stations are closed or merged. A master table copied from a PDF in 2022 is already missing dozens of entries. When EximFetch compared its older port-locations dataset against the live ICEGATE list, 382 of the 589 official codes were missing from the older list, almost all of them ICDs and CFSs.
Keeping your master list current
- Pull from ICEGATE, not from a blog. The authoritative list is ICEGATE's. EximFetch fetches it daily and serves it at
/icegate-locationswith the type decoded. - Store the full six characters and validate the suffix against the mode of transport.
- Sync by change, not by reload. Every record carries
fetchedAt; ask forupdatedSince=<your last sync>and you get only what changed. - Show the name, not just the code in your user interface. Operators recognise "ICD Tughlakabad" faster than INTKD6.
curl "https://api.eximfetch.com/icegate-locations?locationCode=INMAA" \
-H "Authorization: Bearer $EXIMFETCH_API_KEY"
That request returns every Chennai station with its type, which is usually the question an operator is really asking.
Published 17 November 2026, updated 17 November 2026.