Trade Remedies

When Three Overlays Hit One Product: The Stacking Problem

Parts 2 through 4 of this series covered Section 301, Section 232, and IEEPA one at a time, each with its own trigger: an origin test for Section 301, a Commerce national-security finding plus an upstream melt-and-pour or smelt-and-cast origin for Section 232, and a presidential emergency declaration plus a country-specific rate schedule for IEEPA. Treated separately, each is a distinct compliance question with its own answer. The problem is that CBP doesn't treat them separately — a single entry can owe all three at once, and none of the three authorities was written with the other two in mind.

Stacking isn't a special case that applies to a handful of unlucky products. It's the default outcome whenever a product's classification, origin, and upstream metal content each independently land inside one of these three regimes, and because the regimes don't cross-reference each other, clearing one gate says nothing about the other two — including on the exclusion side, where relief granted under one authority has no effect on duty owed under the other two.


Three Gates, Not One Compliance Check

The running example this series has used since Part 1 is a Chinese-origin steel product, and by Part 4 it was carrying up to five separately assessed Chapter 99 layers on a single entry: the MFN base rate, a Section 232 overlay, a Section 301 overlay, an IEEPA baseline overlay, and an IEEPA reciprocal overlay. That number isn't inflated for effect. Section 301 is triggered by the substantial-transformation origin test covered in Part 2. Section 232 is triggered by the product falling within a covered HTS subheading and carrying steel melted and poured, or aluminum smelted and cast, in a non-exempt origin — a test covered in Part 3 that runs on different facts than ordinary country of origin. IEEPA is triggered by a country-specific proclamation reaching the product's origin country, structured as the baseline rate, additional rate, and reciprocal tariff mechanics covered in Part 4.

None of those three tests asks about the other two. A product can be Chinese-origin under the Section 301 substantial-transformation standard, contain steel melted and poured in a non-exempt country under Section 232, and fall under an IEEPA country-specific proclamation for China — three independent findings that happen to point at the same entry. Getting one right, or wrong, has no bearing on the others.

The Layers Are Independent, Not Sequential

There's no priority rule where one authority pre-empts or absorbs another. Chapter 99 mechanically requires that when multiple provisions apply to the same product, each applicable code is separately reported on the entry summary and separately assessed — the codes sit side by side rather than resolving into a single combined rate. A Section 232 finding doesn't suspend the Section 301 analysis, and an active IEEPA proclamation doesn't make the Section 232 melt-and-pour question moot. Each authority runs its own test against the same product and reaches its own conclusion, and CBP expects all applicable conclusions reported on the same entry.

This is also why the order an importer works through the three regimes in doesn't change the outcome. Checking IEEPA first and Section 301 last produces the same total duty as the reverse, because nothing about any one layer's determination feeds into another's. What changes the outcome is missing one of the three checks entirely — and because the triggers are different (an origin test, an upstream metallurgical-origin test, a country-specific proclamation), a compliance process built around only one of them will systematically miss the other two on exactly the products where all three happen to apply.

Exclusions Don't Travel Between Layers

The independence cuts both ways on relief, not just on liability. A USTR exclusion granted against Section 301 duties applies only to the Section 301 duty — it has no effect on a Section 232 overlay or an IEEPA overlay assessed on the same product. A Commerce-granted Section 232 exclusion applies only to the Section 232 duty. IEEPA proclamations generally carry their own exception and exclusions process, separate from both USTR's Section 301 mechanism and Commerce's Section 232 mechanism. None of the three processes is aware of the other two, and none of them automatically extends relief across the boundary.

In practice that means an importer with a fully current USTR exclusion and a fully current Section 232 exclusion for the same product can still owe the full IEEPA rate on that entry, because nobody has separately checked IEEPA's exception process against that product and origin. Exclusion tracking has to be maintained per authority, not as a single "is this product excluded" flag — a product can be excluded from one or two layers and fully exposed on the third.

A Worked Example: The Same Product Through All Three Gates

Take a hypothetical Chinese-origin steel derivative article, entered value $10,000, with steel melted and poured in China and no applicable exclusion under any of the three authorities. The Section 232 overlay applies at the current general rate established by the 2025 reset — 50% of the covered steel content, or of the full entered value if that content can't be substantiated. The Section 301 overlay applies at whatever list rate covers that HTS subheading, and steel and aluminum derivatives were specifically targeted for increases in the 2024–2025 statutory review, with some rates reaching as high as 100%. The IEEPA baseline rate and any additional or reciprocal rate then apply on top of both, at whatever level the current China-specific proclamations set — a figure that, per Part 4, can change faster than either of the other two.

None of these figures are this product's actual duty; they're illustrative of the mechanism, not a real classification. The point is structural: three ad valorem rates, each computed against its own base under its own authority, added on top of the MFN rate and on top of each other rather than netted against each other. A product that would owe a modest single-digit MFN rate on its own can carry a total landed duty rate well above 100% once all three overlays are counted — and every one of those layers has to be separately substantiated on the entry, not just paid.

A Derivative Product Multiplies the Problem, It Doesn't Divide It

Part 3's Fox40 example — a shipment held over a minor aluminum key-ring component on an otherwise nonmetal product — illustrated how a Section 232 derivative listing can reach components nobody thinks of as a metal import. The stacking problem compounds that example rather than resolving it. If that same component were also of Chinese origin, the finished product wouldn't just owe the Section 232 content-based duty covered in Part 3; it would separately need a Section 301 origin analysis and a check against whatever IEEPA proclamations currently apply to Chinese-origin goods, each requiring its own documentation trail.

The unknown-origin default makes this worse, not better. If the smelt-and-cast country for that aluminum component is undocumented, Part 3's 200% Russia-rate default can apply on the Section 232 layer regardless of what the Section 301 and IEEPA layers separately require. A single missing data point on one layer doesn't get absorbed or offset by the other two being in order — it stands on its own, stacked with whatever the other two layers independently add.

Where This Leaves the Compliance Function

IEEPA: The Fastest-Moving Layer, and the Newest, the fourth post in this series, ended by asking what happens when a product gets hit by more than one of these overlays at once — this post is that answer: nothing nets out, nothing defers, and nothing is checked once and considered closed. A complete duty analysis on an affected product means running the Section 301 origin test, the Section 232 upstream-metal test, and the IEEPA country-proclamation check independently, on every entry, and separately verifying exclusion or exception status under each of the three authorities rather than assuming relief under one covers the others.

Part 6 of this series turns to the legal challenges now working through the courts against these authorities — including the question of whether IEEPA's use for tariffs will hold up at all, which would remove one of the three layers from the stack rather than just changing its rate.

Frequently Asked Questions

If a product has a valid Section 301 exclusion, does it also avoid Section 232 or IEEPA duty on the same entry?

No. A Section 301 exclusion only relieves the Section 301 duty. It has no effect on a Section 232 overlay or an IEEPA overlay assessed on the same product — each requires its own separate exclusion or exception under its own authority.

Does the order in which Section 301, Section 232, and IEEPA are evaluated change the total duty owed?

No. Each authority's Chapter 99 code is assessed independently against its own base, and the applicable rates are added together on the entry. Checking the three in a different order produces the same total, since none of the three determinations depends on the others.

If a product clears the Section 232 melt-and-pour or smelt-and-cast test, does it also avoid Section 301 or IEEPA?

No. Section 232's upstream-metal-origin test, Section 301's substantial-transformation origin test, and IEEPA's country-specific proclamations are three separate tests run on separate facts. A product can pass one and still be caught by either or both of the others.

How many Chapter 99 overlays can realistically apply to a single entry?

On the Chinese-origin steel example this series has followed since Part 1, up to five: the MFN base rate, a Section 232 overlay, a Section 301 overlay, an IEEPA baseline overlay, and an IEEPA reciprocal overlay — each assessed and reported separately on the same entry summary.

Primary Sources

Layer 1 base code. Layer 2 trade remedies. Every time.

Kanon evaluates Section 301, Section 232, and IEEPA independently against every classification — including exclusion and exception status under each authority — and documents every applicable stacked layer in the Classification Support Package.

Try Kanon free