Trade Remedies

Section 301 Exclusions: Retroactivity, Expiration, and the Federal Register Trap

A USTR product exclusion from Section 301 tariffs doesn't apply automatically just because a product qualifies. It has to be actively claimed, with the correct Chapter 99 code, on the entry summary — and the only place that exclusion gets announced is a Federal Register notice most importers aren't systematically monitoring. An importer who never notices an applicable exclusion doesn't just miss a discount. They overpay duty on every affected entry until the window to claim it back closes.

---

Exclusions Are Opt-In, Not Automatic

Every USTR exclusion is assigned its own Chapter 99 subheading, and that code has to be reported on the entry summary alongside the base HTS code to actually claim the exemption. A product that qualifies for an exclusion but ships without the corresponding Chapter 99 code doesn't get the exempt treatment — it gets the full Section 301 rate, silently. Nothing about the entry itself signals that money was left on the table; the entry simply processes at the higher rate as if the exclusion didn't exist.

Exclusions are also narrow by design. They're typically granted at the 10-digit HTS code level or with a supplemental product description narrower than the full subheading, for a specific time period — usually about a year from the grant date. A product one digit or one word off the exclusion's actual scope doesn't qualify, even if it's functionally identical to the excluded product.

The Federal Register Is the Only Notice You Get

There's no dashboard that pings an importer when a relevant exclusion is granted, extended, or about to expire. Exclusions are announced through USTR Federal Register notices, and tracking them requires ongoing, active monitoring — not a one-time check when Section 301 tariffs were first evaluated for a product line. Since 2018, the exclusion landscape has gone through multiple rounds of grants, expirations, and lapses, with USTR at various points extending expired exclusions, letting them lapse entirely, and standing up new exclusion processes with different criteria. An exclusion that existed and mattered eighteen months ago may not exist today, and one that didn't exist eighteen months ago may exist now.

The Section 301 tariffs themselves have kept moving too — 2024–2025 statutory reviews pushed rates as high as 100% on targeted categories including EVs, lithium-ion batteries, and steel and aluminum derivatives, all layered on through additional Chapter 99 provisions. A product that wasn't worth chasing an exclusion for at a 7.5% rate is a very different calculation once the applicable rate has climbed.

Two Ways to Get This Wrong, and They're Not Symmetric

Missing an applicable exclusion means overpaying — real money, but a compliance-neutral mistake. The opposite error is worse: claiming an exclusion that has expired, or that doesn't actually match the product, is duty underpayment, and it counts as underpayment regardless of good faith. An importer who kept using an exclusion code past its expiration date because nobody flagged the lapse is now in exactly the exposure category prior disclosure exists to mitigate — the fix is available, but only if the importer catches it before CBP does.

The Retroactive Window, If You Catch It in Time

An unclaimed exclusion isn't necessarily gone forever the moment the entry is filed. Rate and amount of duty are explicitly protestable decisions under 19 U.S.C. §1514, and the same 180-day-from-liquidation window covered in Prior Disclosure vs. a CBP Protest applies here: an importer who realizes after the fact that an applicable exclusion wasn't claimed can potentially recover the overpayment through a protest, provided liquidation hasn't already become final outside that window.

That window is exactly the trap in the thesis here. The Federal Register notice that created the exclusion doesn't wait for an importer to notice it, and neither does the liquidation clock on the entries that should have claimed it. By the time a missed exclusion surfaces — often in a periodic internal review rather than in real time — some portion of the affected entries may already be outside the 180-day protest window, and that overpayment is no longer recoverable at all.

Why This Is a Software Problem, Not Just a Monitoring Problem

The gap here isn't legal complexity — it's that exclusion tracking requires continuously matching a live, changing Federal Register corpus against every affected product's 10-digit HTS code and current country of origin, for as long as Section 301 duties apply to that product. That's not a task most compliance teams can run manually at catalog scale without something falling through.

Kanon treats Chapter 99 as a mandatory second layer of every classification, evaluated after the base HTS code is determined: the current USTR exclusion corpus is checked against the product's 10-digit code and description, applicable exclusion codes are identified with their validity dates, and the full analysis — including which exclusions were checked and found inapplicable — is documented in the Classification Support Package. That's the difference between finding a missed exclusion inside the protest window and finding it after the window has already closed.

Frequently Asked Questions