eCoO 2.0: India's Certificates of Origin Went Fully Electronic

eCoO 2.0's operational shape matters more than its branding. Applications are filed online against the IEC, with multi-user access so an exporter can authorise several users under one IEC, and signing by digital signature token or Aadhaar-based e-sign. Certificates issue electronically from the chosen agency and are verifiable online against the DGFT platform — which is the quiet significance of the reform for everyone downstream: a partner customs authority, a bank checking documents under a credit, or a buyer's compliance team can test a certificate against the issuing record rather than against a rubber stamp's plausibility.

For document assembly, the electronic original changes handling in three small ways worth encoding in SOPs: the certificate's data must match the shipment documents at issue time (the HS drift problem reaches CoOs through whatever code and description the application carries); corrections are a formal in-lieu application, not a counter visit, so error costs are calendar costs; and the ₹200 fee prices each attestation event, which rewards getting the document set right once.

The preferential lane is where the reform carries legal weight. An FTA certificate is the foundation of a tariff claim examined at the destination — and, in India's own import direction, tested under CAROTAR 2020's origin-information framework. An electronically issued, centrally verifiable certificate strengthens exactly the thing origin verification probes: whether the certificate is genuine, what criterion it declares, and whether its particulars match the entry. The discipline the platform cannot supply is the exporter's: the origin criterion declared on the application (wholly obtained, value content, tariff-shift) must be the one the production facts support, because the certificate now preserves the declaration in a form that is easy to retrieve and compare years later.

The back-to-back CoO formalises a lane that previously ran on improvisation: Indian traders re-exporting foreign-origin goods needed origin paper they could not honestly obtain as "Indian origin." Para 2.93(f)'s design is conservative by construction — the certificate names its own evidence and the true country of origin on its face — which makes the supporting file (supplier's CoO, invoices, transport documents) part of the certificate's meaning rather than a drawer's contents.

A Certificate of Origin is now a database row with a legal face — issued against declared facts, fee-stamped, verifiable, and correctable only by formal application. For the shipment file, that means the CoO joins the set of documents whose data must be reconciled before issuance against the invoice, packing list and Shipping Bill, per the discipline in the pre-LEO reconciliation note. TradeWatch includes CoO-data consistency and criterion-declaration checks in its readiness packets, cited to the governing notices. Kanan Labs prepares a readiness packet. It does not file Shipping Bills or CoO applications and holds no customs credentials — your licensed CHA files, and certificates issue from the authorised agencies.