India Platform
Which Indian rails can one agri-trade transaction use now?
Model
A platform is usable infrastructure, not a list of portals. For an agri-trade transaction, the relevant rails may include registration, customs, food import clearance, testing, certification, traceability, payments, logistics, and appeal.
FSSAI says its Food Import Clearance System integrates with Customs ICEGATE through the Single Window Interface for Facilitating Trade. Referred food articles can receive document scrutiny, inspection, sampling, and testing, followed by a no-objection certificate or non-conforming report. An importer can seek review of a rejection. This is evidence of a public clearance rail, not evidence of its speed or reliability for a chosen product.
Transaction Rails
| Rail | Public owner or entry | Question it must answer |
|---|---|---|
| Export/import identity | DGFT Foreign Trade Policy 2023 | Is an Importer-Exporter Code required, and who must hold it? |
| Food import clearance | FSSAI Imports | Which documents, inspection, sampling, testing, and review apply? |
| Agricultural export support | APEDA | Is the product scheduled, and must the exporter register? |
| Marine export support | MPEDA | Which seafood quality, registration, or market-access rail applies? |
| Product-specific support | Tea, coffee, spices, rubber, coconut, tobacco, and cashew bodies | Which statutory or promotional function applies to this commodity? |
Missing Proof
The current evidence does not establish national scores for digital
infrastructure, financial infrastructure, blockchain, DePIN, or energy. It
also does not establish interoperability across a full shipment. All five
scorecard dimensions remain unknown.
Practice
Put this to work
Trace one India transaction rail
For an importer, exporter, or systems designerCopy this prompt. Paste into Claude, ChatGPT, or any AI assistant. The page context is already loaded — send it and get analysis tailored to your role.
Trace the public rails for one India agri-trade transaction. Product and direction: [product, origin → destination] Port or state: [location] List each registration, data handoff, certificate, inspection, payment, logistics handoff, and appeal. For each, name the owner, input, output, system of record, stated time, observed time if available, failure mode, and manual fallback.
Checks
- Verify that every rail produces evidence accepted by the next actor.
- Record stated and observed time separately.
- Test the manual fallback before relying on interoperability.
Failure Modes
- A portal is counted as usable infrastructure without a completed handoff.
- The same evidence must be re-keyed or privately interpreted.
- A national rail is assumed to work identically at every port or state.
Context
- depends-on India — country decision hub.
- applies-to India Process — convert rails into an ordered compliance path.
- applies-to Data — retain product and evidence lineage across handoffs.
- uses Tight Five — connect platform rails to the other four country tests.
- contrasts-with New Zealand Platform — find the interoperability gap in a bilateral corridor.
Questions
Changes my mind: the named rail cannot produce evidence that the next counterparty accepts.
Next question: which handoff still depends on re-keying, private interpretation, or an unverified document?
- Which system is the source of truth?
- What happens when the handoff fails?