A Section 301 exclusion removes the extra duty for a narrowly described product, for a limited time. When it expires, the full additional rate returns on the next entries, often with little fanfare, and importers who priced on the excluded rate feel it immediately. Tracking exclusions by product description, code, and expiry date, tied to your own SKU list, is the only reliable protection.
Exclusions are descriptions, not blanket codes
An exclusion usually covers a specific product description that may sit inside a broader tariff code alongside products that are not excluded. Two items sharing a code can have different duty treatment because one matches the exclusion wording and the other does not. That means SKU level mapping, with the exact description matched and documented, is the unit of work, not the code alone.
For more on this, see this related guide and our earlier explainer on the same theme.
Keep the evidence with the SKU: the exclusion notice, the description match reasoning, and any ruling or broker advice relied on. If an entry is questioned later, the file should show why the exclusion was claimed, in the language of the notice, without a scramble through old emails during an audit window.
Why expiry keeps surprising importers
Exclusions have been extended, modified, and allowed to lapse in batches, sometimes with announcements close to the expiry date itself. Teams that recorded excluded as a permanent attribute of a product, rather than a dated status, discover the change only when a duty bill or a margin report moves. By then the affected goods are already on the water at the old price math.
Retroactivity adds a second surprise. Extensions have at times applied retroactively, creating refund opportunities on entries made during a gap, which teams miss if they stopped tracking the exclusion at expiry. Tracking should continue past expiry for a window, watching for reinstatement and for refund deadlines on gap entries.
A tracking routine that fits a small team
Maintain one register: each exclusion you claim, its product description, the SKUs mapped to it, the current expiry date, and the owner. Review it monthly, and again whenever an extension notice publishes, updating dates and flagging SKUs whose mapping is arguable. Tie the register to purchase orders so a new order on an expiring exclusion triggers a pricing check before it ships.
Readers also found this companion piece from our archive useful.
Model the cliff in advance. For each exclusion expiring in the next two quarters, estimate the duty at the full rate on forecast volume, and decide early among repricing, resourcing, redesign, or accepting the margin hit. A decision made a quarter early is a strategy; the same decision made on the entry date is a surprise.
Coordinate broker, sourcing, and finance
Brokers apply what they are told at entry, sourcing commits prices months earlier, and finance sees the result last. The register only works if all three read the same dates: brokers instructed on which entries claim the exclusion and until when, sourcing quoting with the expiry in view, and finance accruing duty at the rate that will actually apply on arrival.
After any expiry or extension, reconcile a sample of entries against the register to confirm treatment matched the plan. Sampling catches the quiet errors, a broker default, a SKU mapped twice, that a register alone cannot, and it closes the loop between tracking and what was actually paid.
Frequently asked questions
Do Section 301 exclusions renew automatically?
No. Exclusions expire on their stated date unless an official notice extends them, and extensions can be partial or change the product description. Assume expiry happens and treat an extension as a change to verify, not a default.
Can I get a refund if an exclusion is extended retroactively?
Often yes for entries in the covered gap, through post summary correction or protest within the applicable deadlines. That is why tracking should continue after expiry: the refund window is time limited and easy to miss.
Does matching the tariff code guarantee the exclusion applies?
No. The product must match the exclusion specific description, which can be narrower than the code. Document the description match per SKU and get advice on arguable cases before claiming.
When should we reprice for an expiring exclusion?
As soon as forecast orders would arrive after the expiry date, which given shipping lead times can be months before the date itself. Work backwards from arrival, not from the calendar date printed in the notice.