A federal court has struck down the Trump administration's "reciprocal" tariff framework, creating an immediate data integrity problem for any system caching HTS duty rates. If your application stored these elevated rates as authoritative, you're now serving outdated data to compliance workflows.
The ruling doesn't eliminate all tariff increases from the past two years — it specifically targets the reciprocal tariff mechanism. That distinction matters for your data pipeline.
The Data Problem
Reciprocal tariffs were layered on top of existing HTS rates as supplemental duties, often adding 10-50 percentage points to baseline rates. These weren't new HTS codes — they were rate modifications applied conditionally based on country of origin and the tariff treatment of U.S. goods in that country.
If your system ingested these as static rate updates rather than conditional overlays, you now have corrupted baseline data. The court's ruling is effective immediately, meaning any duty calculations running against cached reciprocal rates are returning incorrect values right now.
Which Records Are Affected
The industries still facing higher rates under surviving tariff programs include:
- Steel and aluminum (HTS Chapters 72-76): Section 232 duties of 25% on steel and 10% on aluminum remain intact
- Chinese-origin goods across multiple chapters: Section 301 duties (Lists 1-4) are unaffected by this ruling
- Solar panels and washing machines: Safeguard tariffs under Section 201 continue
- Automotive (HTS Chapter 87): Section 232 auto tariffs, where applicable, remain in force
The invalidated reciprocal tariffs primarily affected goods from the EU, Japan, South Korea, and other allied nations that were hit with matching duties based on their tariff treatment of American exports.
How TradeFacts.io Handles This Automatically
TradeFacts.io maintains separation between baseline HTS rates and supplemental duty programs at the data model level. When a tariff program is modified or invalidated, our pipeline updates the specific program layer without corrupting underlying rate data.
For this ruling, our team has already flagged all reciprocal tariff records as invalidated and reverted affected rate calculations to the appropriate baseline plus any surviving supplemental duties. API consumers pulling current rates are receiving corrected data as of 06:00 UTC today.
If you're querying historical rates for entry summaries filed during the reciprocal tariff period, use the effective_date parameter to retrieve rates as they existed at time of entry. Our versioned rate history preserves the full audit trail.
Subscribers on our webhook plan received automated alerts at 05:47 UTC with affected HTS subheading counts and diff summaries.
Need reliable HTS data that updates when the law does? Start a free 30-day trial and stop maintaining stale rate caches.