The Office of the U.S. Trade Representative filed a Section 301 investigation on March 12 targeting 60 countries—including Canada, China, the European Union, and Mexico—for allegedly failing to enforce bans on goods made with forced labor. Trade compliance engineering teams managing HTS classification systems should prepare for potential tariff changes that could materialize within months.
The Federal Register filing identifies a specific competitive harm: U.S. exports must compete against products made with forced labor in markets where enforcement is lax, including goods previously denied entry to the U.S. and subsequently re-exported elsewhere. This creates what USTR calls an "artificial cost advantage" for firms in the 60 targeted economies.
Key Date: USTR has scheduled a public hearing for April 28 and opened a docket for comments. Organizations with data on forced-labor enforcement gaps or competitive impacts should consider submitting technical evidence before this deadline.
U.S. Trade Representative Jamieson Greer stated the administration intends to "move in a matter of months" rather than years, explicitly confirming that unresolved issues could result in new tariffs. For compliance teams, this compressed timeline means rate tables and duty calculations could require updates far sooner than typical Section 301 investigation cycles.
The forced-labor probe follows a parallel Section 301 investigation launched March 11 examining structural excess manufacturing capacity across multiple countries. Both investigations signal an aggressive expansion of tariff exposure beyond the existing global surcharge framework.
Rate Volatility Alert: The current 10% global surcharge—with potential increase to 15%—expires 150 days after implementation unless Congress extends it. Compliance systems must track both the Section 301 investigation timeline and the surcharge expiration window simultaneously to maintain duty calculation accuracy.
For trade compliance engineering teams, this investigation creates three immediate technical requirements. First, HTS rate caching logic must account for potential country-specific surcharges layered on top of existing duties. Second, classification workflows may need to flag products from the 60 targeted countries for enhanced documentation review. Third, API consumers should implement monitoring for Federal Register updates tied to this docket.
The Section 301 framework has already produced tariffs through similar investigations—USTR's Nicaragua probe resulted in implemented duties. Given Greer's stated intent to resolve issues quickly, teams relying on static rate tables risk serving outdated duty calculations to downstream systems.
The 60-country scope encompasses every major region of the global economy, meaning few supply chains will remain unaffected if tariffs materialize. Compliance teams should audit their HTS data sources now to ensure they can propagate rate changes programmatically when final determinations are published.
To ensure your classification and duty calculation systems stay current through this investigation cycle, contact TradeFacts.io at /contact.html for a free 30-day trial of our US HTS and Canadian Customs Tariff JSON API.