New containers at Jebel Ali, a new vessel, and the origin stayed Pakistani
DRI seized more than 362 metric tonnes of dry dates in 13 containers at Nashik: shipped from Karachi, transshipped at Jebel Ali, and declared UAE-origin on import.
What happened
- DRI seized more than 362 metric tonnes of Pakistan-origin dry dates held in 13 containers, acting on specific intelligence.
- The containers were intercepted at CFS Ambad, Nashik, and had been imported by a Mumbai-based firm that the release does not name.
- The consignments arrived from Jebel Ali, UAE, with the import documents declaring the UAE as the country of origin.
- Preliminary investigation found the dates were shipped from Karachi Port to Jebel Ali in one set of containers on one vessel, then moved into another set of containers on a different vessel bound for India, through entities operated by Pakistani nationals.
- The instrument circumvented is DGFT Notification No. 06/2025-26 dated 2 May 2025, effective 2 May 2025, barring direct or indirect import or transit of all goods originating in or exported from Pakistan after the Pahalgam terror attack.
For Prelims
- Directorate of Revenue Intelligence: the agency under the Ministry of Finance that made this seizure of more than 362 metric tonnes of dry dates in 13 containers.
- Operation Deep Manifest: the standing DRI operation under which Pakistan-origin goods routed through third countries are identified, intercepted and seized; no start date and no count of earlier seizures is given.
- DGFT Notification No. 06/2025-26: dated 2 May 2025 and effective from 2 May 2025, the instrument imposing the complete prohibition on goods from Pakistan.
- Scope of the prohibition: direct or indirect import or transit of all goods originating in or exported from Pakistan - origin and place of export are separate limbs.
- Stated trigger: the release attributes the prohibition to the Pahalgam terror attack and to national security, and gives no date for the attack itself.
- The route: Karachi Port to Jebel Ali Port in one set of containers aboard one vessel, then a second set of containers aboard a different vessel to India.
- Place of seizure: CFS Ambad, Nashik, where the 13 containers were intercepted; the release uses the abbreviation CFS and does not expand or describe it.
- Declaration on import: the import documents named the UAE as the country of origin, which matched the port of shipment, Jebel Ali, but not the place the goods came from.
For UPSC: Use this where a trade restriction works as an instrument of security policy rather than of tariff policy: because the bar is written on origin, enforcement turns on documents and intelligence rather than on interdiction at a border. It is the cleanest current illustration of third-country routing attempted against a bilateral prohibition, and of why rules of origin, not duty rates, decide whether goods may enter at all. It fits questions on India-Pakistan economic relations after Pahalgam and on the customs enforcement chain.
What it is NOT: The prohibition's instrument is named - DGFT Notification No. 06/2025-26 of 2 May 2025 - but almost nothing after it is: the Mumbai importer is not identified, no arrest is recorded, no value is put on the 362 tonnes, no duty implication is quantified, and no penalty, confiscation or prosecution is stated, nor is any provision of the Customs Act cited as the basis of the seizure. The release never mentions a certificate of origin, only import documents declaring the UAE; it does not say how the specific intelligence was developed, whether the Jebel Ali entities face any action, or how many other consignments Operation Deep Manifest has caught.
For Mains
Syllabus: GS2.17 · GS3.1 · Linkage L2
Anchor
A prohibition on trade with a neighbour is not enforced at the border with that neighbour. It is enforced at CFS Ambad, Nashik, against paperwork that is true about the last port and false about the first - which is why rules of origin, not tariff lines, carry the security burden here.
Substantiation (data)
More than 362 metric tonnes in 13 containers, intercepted at CFS Ambad, Nashik, on specific intelligence. The cargo travelled from Karachi Port to Jebel Ali in one set of containers aboard one vessel, then into a second set of containers aboard a different vessel to India, arriving with import documents naming the UAE as the country of origin.
Exemplification
The transshipment is the whole mechanism. Nothing about the goods changed at Jebel Ali; only the containers, the vessel and the shipping documents did. Every paper generated after that point can be accurate about the voyage it describes while the one fact the prohibition depends on - where the dates were grown and packed - never appears on it.
Problematisation
The release names the prohibition but not the consequence. No provision of the Customs Act is cited for the seizure, no value is put on 362 tonnes, no importer is identified, no arrest is recorded, and no penalty, confiscation or prosecution is stated, so the account stops at interception and says nothing about adjudication.
Counterpoint
Against reading this only as an enforcement success: the containers had already travelled to CFS Ambad, Nashik, before they were stopped, and they were stopped on specific intelligence rather than by any routine test of origin. A control that depends on tip-offs scales with informants, not with trade volumes.
Position
The instrument is drafted well and the enforcement sits downstream of it. Because the notification reaches goods originating in as well as exported from Pakistan, and reaches indirect import and transit alike, transshipment cannot cure the defect in law; what the case exposes is that finding the defect in fact still rests on intelligence.
Deploys into: India-Pakistan economic relations after Pahalgam (GS2.17) · trade prohibitions and rules of origin as security instruments (GS3.1) · third-country routing, transshipment and misdeclaration · the DRI and the customs enforcement chain · why a document can be true in form and false in substance
Ministry of Finance · 2026-09-14 · PRID 2309982 · PIB source ↗