GenuTrace Client Advisory: Is Your Cotton Supply Chain Ready for the Next Tariff Wave?
India’s New Forced Labor Import Ban Signals a Global Shift From Importer Enforcement to Sourcing-Country Enforcement
What Changed
On July 13, India’s Directorate General of Foreign Trade issued Notification No. 23/2026-27, banning imports of goods produced, wholly or in part, through forced labor, effective 30 days after gazette publication. The move is a direct response to a proposed 12.5 percent U.S. tariff under a USTR Section 301 investigation naming 60 economies, including Bangladesh, Cambodia, China, Indonesia, Pakistan, Sri Lanka, Thailand, Turkey, and Vietnam, for failing to prohibit or enforce bans on forced labor imports. Countries with comparable measures already in place, including the EU and Pakistan, were proposed for a lower 10 percent rate. India was not, and is now racing to close that gap.
This follows a wave of U.S. action in early June: CBP's updated Forced Labor Enforcement Operational Guidance (CBP Publication No. 5560-0526), Executive Order 14411 (“Strengthening Customs Enforcement”), and the USTR Section 301 findings themselves. India's law is the first legislative ripple from that wave. It won’t be the last.
The Enforcement Pressure Has Moved Up a Level
U.S. forced labor enforcement has historically targeted importers directly: detain the shipment, demand the documentation, exclude the goods if the paper trail fails. That still holds, and CBP’s updated guidance tightens it further. But Section 301 aims one level higher, at the sourcing country's own legal framework. It asks whether a government has built a system that makes forced labor imports illegal in the first place, not whether one importer's paperwork happens to be clean.
Bangladesh, Cambodia, Vietnam, and the rest of the Section 301 list should be expected to follow India's lead. Sourcing teams working across any of these geographies should expect new domestic legal frameworks to appear on a similar timeline, and should not mistake a new law for a solved compliance problem.
A Law Is Not a Test Result
India's notification empowers its government to prohibit specific goods after DGFT investigations. It does not test anything, and it does not trace anything. It raises the bar on paperwork and gives India a legal hook in trade negotiations, but it doesn't verify a single bale of cotton. Proving origin at the fiber level, in a shipment already loaded on a vessel, still requires scientific testing, chain-of-custody discipline, and a reference library built over years, not new legislation.
CBP's own updated guidance reflects this. It dedicates an entire appendix to isotopic testing, explicitly encouraging its use as part of due diligence because documentation alone is often not sufficient to demonstrate that a good wasn't produced, wholly or in part, with forced labor. Paper describes what a supply chain claims happened. It does not prove what a fiber's isotopic signature shows.
What Importers Must Have Ready
Bale-level cotton origin documentation
Full supply chain map from fiber to finished product
Transaction records at every tier: purchase orders, invoices, proof of payment, bills of lading
Identification of every entity involved, including sub-suppliers
Isotopic testing results where applicable
A documented due diligence system with supplier code of conduct, audits, and remediation protocols
Bottom line
A government can pass a forced labor law in a week. Proving origin cannot happen that fast. As more sourcing countries follow India's lead, the compliance paperwork bar will rise everywhere at once, but paperwork was never the thing that verified origin. If you claim it, can you prove it? That question now applies at the national level and the shipment level alike. If cotton is anywhere in your supply chain, the time to close that gap is now, not after a detention notice arrives.
GenuTrace provides isotope-based cotton origin verification built specifically for UFLPA compliance. Our testing is scientifically defensible, supply chain-ready, and designed to support your documentation package, not replace it.
Contact GenuTrace today: info@genutrace.com | www.genutrace.com
