SEZ Online had run for over a decade as the digital filing system for thousands of SEZ units, administered by NSDL under the Department of Commerce. In 2024, units were migrated onto ICEGATE, the customs backbone administered by CBIC under the Ministry of Finance. The first month's data showed gold imports overstated by USD 5 billion. A shipment that needed three uploads on SEZ Online now needs thirty. By March 2025 the Commerce Ministry issued a partial rollback "till further orders." What does it mean when a platform consolidation creates more friction than the system it replaced?
The question assumes that ICEGATE was extended to Special Economic Zones (SEZs) because the existing system was inadequate. That assumption is wrong. The NSDL SEZ Online system had been functioning for over a decade. It handled Bills of Entry, Shipping Bills, DTA sale filings, duty payments, and customs query routing for thousands of SEZ units across the country. It was not a paper-based workaround waiting to be digitised. It was a fully electronic platform, administered under contract by NSDL (now NDML), with its own filing protocols, digital signature infrastructure, and integration with SEZ Customs offices. The decision to migrate SEZ units onto ICEGATE was not driven by the inadequacy of SEZ Online. It was driven by the institutional need to consolidate trade data onto a single customs backbone, and that distinction explains nearly everything that followed.
SEZ policy sits under the Department of Commerce. Customs administration, including ICEGATE, sits under CBIC in the Ministry of Finance. SEZ Online was Commerce's system. ICEGATE is Finance's system. For years they ran in parallel, each independently reporting trade data to the Directorate General of Commercial Intelligence and Statistics. Two separate digital platforms, administered by two separate ministries, were independently reporting overlapping trade data with no automatic deduplication.
During the 2024 migration, imports into SEZs and subsequent clearances from SEZs into the DTA began to be counted twice. Gold imports for November 2024, initially reported at USD 14.8 billion, were revised to USD 9.84 billion; a USD 5 billion correction for a single month. A platform migration intended to improve data integrity had yielded the single largest data distortion in India's recent trade statistics.
By March 2025, barely five weeks after the "final" cutoff, the Commerce Ministry issued a partial rollback. DTA supply transactions (excluding FTWZ and Chapter 71 goods), exports through merchant exporters, and zone-to-zone transfers were permitted back on SEZ Online "till further orders." Development Commissioners were further empowered to allow exceptions for "specific transactions wherein unique challenges are being faced." The phrase "till further orders" in government communication is significant: it means no new deadline has been set, which in practice means the older system continues indefinitely for those categories.
Against this institutional history, the specific operational frictions reported by SEZ units are not isolated complaints; they are symptoms of a general-purpose customs platform being applied to a domain it was not designed for.
*The documentation multiplier.* On SEZ Online, a shipment of ten items requiring three mandatory documents each needed three consolidated uploads. On ICEGATE, the same shipment requires thirty individual uploads, each generating a separate Invoice Reference Number and Document Reference Number under the e-Sanchit framework. For a pharmaceutical SEZ unit distributing clinical trial medications to hospitals, where the goods are finished products stored at controlled temperatures and shipped in parts against individual patient orders, this is not a marginal increase in paperwork. It is a structural impediment to same-day dispatch. Scrap vehicles at manufacturing SEZs face the same bottleneck: materials that should clear in hours are held up because the documentation architecture treats each item as an independent import event.
*The Z Type dependency.* ICEGATE requires every T Type Bill of Entry (DTA sale) to reference the original Z Type BOE (import into SEZ). This creates a hard system dependency that SEZ Online never imposed. The implications cascade. Multiple Z Type BOEs cannot be referenced under a single T Type filing, so a shipment containing goods imported under several consignments must be broken into multiple filings. Goods procured domestically and later removed to DTA have no Z Type BOE to reference at all, and ICEGATE offers no pathway for this scenario. Most critically, goods imported before the ICEGATE rollout have no digital footprint on the new platform. The Department of Commerce acknowledged this explicitly: T Type BOEs "cannot be filed unless there is a corresponding Z Type B/E, such details being mandatory." The system demands a reference that does not exist for goods imported under the previous system, creating a retrospective compliance impossibility.
*The query routing inversion.* On SEZ Online, customs queries were routed to the SEZ unit that filed the BOE and held all relevant documentation. On ICEGATE, the query is routed to the DTA importer (the IEC holder), not the SEZ unit. The SEZ unit, which manages storage, distribution, and compliance, cannot see or respond to the query. The system sends the compliance question to the party least equipped to answer it, while the party most equipped has no visibility into the fact that the question exists.
*The PGA duplication.* For goods requiring Participating Government Agency clearance, such as pharmaceuticals needing a No Objection Certificate from the Assistant Drug Controller (ADC), ICEGATE requires PGA clearance at the T Type (DTA sale) stage even when the same clearance was obtained at the Z Type (import) stage. The ADC's NOC, obtained manually at the first port of arrival with quantities debited from the import licence, is not recognised by ICEGATE as having been performed. The SEZ Online system, understanding that these goods had already undergone PGA scrutiny, did not require a second clearance. ICEGATE, treating every BOE as an independent customs event, does. This is not enhanced compliance; it is the architectural consequence of a platform that does not distinguish between a first import and an internal movement of already-cleared goods.
*The vendor registration shortfall.* For scrap disposal from SEZ to DTA, the buyer is often a small recycler or waste dealer with no ICEGATE registration, no customs broker, and no capacity to navigate electronic filing systems. Under SEZ Online, this was manageable because the SEZ unit drove the filing process. Under ICEGATE, the DTA buyer's registration and participation become system prerequisites. The shortfall is not merely inconvenient; it makes certain routine transactions technically impossible to complete on the platform.
The NSDL dimension adds another layer. With ICEGATE absorbing the core filing functions that were SEZ Online's primary revenue source, NSDL's transaction-based income from SEZ operations declined to the point where, by the Department of Commerce's own assessment, it had become unremunerative to manage operations. A committee chaired by the Development Commissioner, Cochin SEZ, recommended revised service charges, which were implemented from January 2026. This is a quiet but telling detail: the migration did not just disrupt SEZ units' operations; it destabilised the commercial model of the platform operator that had been running the system those units depended on. SEZ Online continues to operate for the modules not yet absorbed by ICEGATE, but its long-term viability as a platform is now structurally uncertain.
The incentive architecture that accompanied the migration is also instructive. Units were informed that only those filing on ICEGATE would be eligible for benefits under the Remission of Duties and Taxes on Exported Products (RoDTEP) scheme. Units continuing on SEZ Online would not receive RoDTEP credit. This created a coercive dynamic: migrate to a system that may not support your transaction types, or forfeit export incentives you are otherwise entitled to. When a platform migration is incentivised through the withdrawal of unrelated benefits, it signals that the platform's own functionality is insufficient to motivate adoption.