Skip to main content

DGFT / FTP | 28 September 2026

Non-Preferential Rules of Origin: DGFT September 2026 Draft and Exporter Preparation

Finin2min Editorial Desk | Review: Ravi Sisodia

For Non-Preferential Rules of Origin, operational ownership matters as much as knowing the statutory provision. Origin compliance should distinguish preferential treaty rules from non-preferential origin. The September 2026 item is important because it signals a more formal framework, but businesses should not describe draft criteria as already binding.

Finin2min 2-Minute Summary

Practical workflow

Exporters can prepare by mapping bill of materials, manufacturing steps, supplier origin declarations, substantial transformation/value-add information and certificate workflows. Trade teams should identify products whose origin conclusion is sensitive to imported inputs.

Worked example

An Indian exporter assembles a product using major imported components. A non-preferential origin analysis should examine the proposed origin rule and actual transformation; simply shipping from India does not establish Indian origin.

Detailed practical analysis

Non-preferential rules of origin support ordinary country-of-origin certification and differ from preferential rules under an FTA. The September 2026 DGFT draft should therefore be read as a proposed framework unless and until finalised. Exporters can still use the consultation period to map current origin evidence. For manufactured goods using imported inputs, the existing non-preferential test looks beyond simple operations and requires sufficient manufacturing/processing in India under the governing FTP/HBP criteria. A bill of materials should identify domestic and imported inputs, HS codes, values and manufacturing steps. Operations such as repacking, simple assembly or labelling may not establish Indian origin by themselves. Exporters should retain supplier declarations and production records rather than rely solely on a commercial invoice stating “Made in India.” The Certificate of Origin platform data should reconcile with the shipping bill and invoice. If the draft changes application, verification or self-certification mechanics, gap-assess systems before the final rule so master data can be adapted quickly. Trade teams should also distinguish a buyer’s contractual origin requirement from the government certificate process. During a customs verification abroad, the ability to demonstrate actual manufacturing is more important than reproducing a certificate. A product-level origin dossier reduces the risk of repeated evidence requests for recurring exports.

Implementation and review notes

Origin compliance should be coordinated with procurement. Purchasing teams need supplier declarations that identify country of origin and manufacturing information for major inputs, while production records should show the transformation in India. A certificate team working only from invoice descriptions may not know that imported material dominates the product or that processing is merely simple assembly. For recurring products, build an origin bill of materials with version control and update it when suppliers or manufacturing processes change. The 2026 draft should be tracked to finalisation; if the final text changes documentary or digital-certificate requirements, update the COO SOP with the effective date. Exporters should avoid issuing customer declarations broader than the certificate actually supports. When a foreign buyer asks for “India origin” for procurement policy rather than customs preference, clarify which standard is being represented. Internal audit can sample certificates and trace them back to BOM, production and supplier evidence. This makes origin certification a manufacturing-data control rather than a last-step export document.

Final reviewer note

At closure, reconcile the first operating step around consultation-status label and BOM origin fields before reading the final reported number. Validate the legal treatment from DGFT Trade Notices - Trade Notice 27/2026-27; use DGFT Certificate of Origin platform for additional process detail. A case involving The deviation log is required to flag calling consultation final law should show how the team measured and resolved the difference. A case involving A recurring weakness is confusing preferential and non-preferential COO should show why the chosen treatment remains supportable. Keep unresolved matters on the issue register with a responsible owner and review date instead of clearing them only because a portal or form accepts submission.

Control points

Risk indicators

Primary / Official Sources