Section 232 Derivative Inclusion List: Exposure Monitoring

GingerControl shows how to monitor the Section 232 derivative inclusion list against your HTS item master so no part surprises you at liquidation.

Chen Cui
Chen Cui16 min read

Co-Founder of GingerControl, Building scalable AI and automated workflows for trade compliance teams.

Connect with me on LinkedIn! I want to help you :)

What is the Section 232 derivative inclusion list, and why do teams find out too late?

The Section 232 derivative inclusion list is the growing set of Harmonized Tariff Schedule (HTS) codes that the government treats as steel or aluminum "derivative" articles, meaning finished and semi-finished parts that carry the metals tariff even though they are not raw steel or aluminum. Teams find out too late because the list expands by HTS code through a formal inclusion process, and unless someone is monitoring that process against your own item master, the first signal that a part became covered is often the duty CBP assesses at liquidation.

How do you monitor Section 232 derivative-inclusion changes against your own parts?

You subscribe your actual HTS item master to the derivative-list and proclamation feeds, so a change to a code you import triggers an alert on the effective date rather than a surprise months later. GingerControl does this with Compliance Radar, which matches Federal Register, CSMS, and White House actions to your records and delivers a one-click reclassify, so 232 derivative exposure surfaces before the entry posts, not at liquidation.

Section 232 derivative coverage has expanded repeatedly across 2025 and 2026, and the mechanism that expands it, plus the melt-and-pour and smelt-and-cast content declarations CBP now requires, is exactly what a monitoring program has to watch. For a manufacturer importing 300 to 3,000 steel-content and aluminum-content SKUs, a single missed inclusion can convert a duty-free part into one carrying the standard 25% derivative rate on its full customs value, and the gap is only discovered when the entry liquidates.

Last updated: July 2026

Why the Section 232 derivative list is a monitoring problem, not a rate problem

Most Section 232 content, including our own earlier explainers, answers the question "what is the rate?" That is the wrong question for a program owner. The rate is published. The hard part is the mapping: the government describes the goods it now covers in tariff-schedule language ("derivative articles of steel provided for in the applicable subheadings"), and it never describes your parts. The translation from "the list changed" to "these 41 part numbers in my catalog are now dutiable" is left entirely to you, and it is a manual forensic project every time the list moves.

That mapping problem has three properties that make it dangerous:

  • The list expands on a schedule you do not control. Coverage grew through a formal inclusions process in 2025 and through presidential proclamations in 2026. A part that was outside scope last quarter can be inside scope this quarter.
  • The duty base moved to full value. For entries on or after April 6, 2026, the April 2026 proclamation shifted the derivative duty from the declared metal-content value to the full customs value of the article, per CBP guidance in CSMS #68253075. A part you already imported is now more expensive to get wrong.
  • The error surfaces at liquidation. If a part is covered and you did not apply the Chapter 99 heading, CBP can catch it when the entry liquidates, and the exposure is back duties, interest, liquidated damages, and the prior-disclosure conversation that follows.

Quotable insight: Section 232 derivative exposure is not a rate-lookup problem, it is a mapping-and-timing problem. The rate is public; what is not public is which of your part numbers a derivative-list change just captured, and on what effective date. A team that monitors published rates but not the inclusion process against its own item master will still learn that a part became dutiable the same way it always has: from the bill at liquidation, months after the entries posted.

GingerControl is a trade compliance AI platform that helps importers, exporters, and customs brokers classify products, simulate tariff costs, and track policy changes. The point of a derivative-inclusion monitoring program is to turn that third capability, tracking policy changes, into a closed loop tied to your specific HTS codes.

How the Section 232 derivative list actually expands

You cannot monitor a process you do not understand. Here is the mechanism, drawn from the controlling BIS and CBP sources, and why each step is a signal your program should be watching.

1. The inclusions process (2025). The Bureau of Industry and Security (BIS) established a formal process for adding derivative steel and aluminum articles to Section 232, adopted in the Federal Register notice on the inclusions process (docket BIS-2025-0023). U.S. producers of steel or aluminum articles, or their industry associations, could submit requests during two-week windows three times a year (opening around May, September, and January). BIS then posted requests for a two-week public comment period and ran a roughly 60-day review.

2. The two criteria. BIS assessed each request on two questions: first, "whether the described product at the eight- or ten-digit HTSUS classification is a derivative steel or aluminum article," and second, whether imports of that article "have increased in a manner that threatens to impair the national security." If both were satisfied, the code was added and the tariff took effect shortly after publication.

3. The first round. The first inclusions round added more than 400 HTSUS subheadings to the derivative lists, effective in August 2025, with implementation delivered through CBP CSMS guidance messages. That single round is the clearest illustration of the risk: hundreds of codes moved into scope at once.

4. The 2026 restructuring. The April 2026 proclamation, effective April 6, 2026, restructured the regime, shifted the derivative duty to full customs value, and superseded the periodic public inclusions window, while leaving Commerce and the U.S. Trade Representative authority to expand derivative coverage going forward. A June 1, 2026 proclamation then expanded coverage again, effective June 8, 2026 through December 31, 2027, and introduced reduced-rate tiers for certain equipment, with implementation guidance in CBP CSMS #68855869.

The practical takeaway: the derivative list no longer expands only through a predictable quarterly window. It can move by proclamation, on a rolling basis, with a short runway to the effective date. That is precisely the pattern that defeats a spreadsheet and a quarterly review.

Bottom line: For a compliance manager and sourcing lead at a manufacturer running steel-content and aluminum-content inputs across hundreds of SKUs, the derivative list is a moving target that changes by both scheduled process and rolling proclamation. The only reliable defense is a standing monitor keyed to your own HTS codes, because the government describes the goods it covers, never your part numbers.

The item-master mapping: melt, pour, smelt, and cast

The second half of a derivative-inclusion program is the data on your side. Section 232 derivative compliance is not just "is this code covered." Once a part is in scope, CBP requires you to declare the metal's origin at a granular level, and the declaration is where item-master quality becomes a liability.

For steel and steel derivatives, importers must report the country of melt and pour, the country where the raw steel was first melted and cast into its initial solid form. For aluminum and aluminum derivatives, importers must report the country of smelt and cast. These are reported through the Automated Commercial Environment (ACE), and, per CBP's Section 232 FAQs, the ability to declare aluminum smelt-and-cast origin as "unknown" was closed in June 2025, with a 200% duty consequence for aluminum or aluminum-derivative articles whose smelt-and-cast country cannot be reported.

That means a derivative-inclusion monitoring program has to reconcile two datasets on every alert:

Program input What it answers Where it lives
The derivative inclusion list (Chapter 99 headings) Which HTS codes now carry the metals tariff Federal Register, proclamations, CBP CSMS
Your HTS item master Which of your parts sit on those codes Your ERP / item master / classification records
Melt-and-pour / smelt-and-cast data Whether you can declare metal origin, and at what rate Mill test certificates, supplier data, ACE filings
The effective date When the exposure starts The proclamation or CSMS message

If any one of those four is missing or stale when the list changes, the program fails silently, and the failure resurfaces at liquidation.

Building the derivative-inclusion exposure-monitoring program

Here is the program, in the order you would stand it up. Each step maps to a capability you either build, staff, or subscribe.

Step 1: Baseline your metals-exposed item master. Identify every SKU whose HTS code sits in, or adjacent to, the steel and aluminum derivative scope (Chapters 72, 73, 74, 76, and the Chapter 84, 85, and 87 headings that pull in metal-intensive equipment). This is a classification-governance exercise: you need a defensible HTS code on each part before you can monitor it. GingerControl's HTS Classification Researcher follows GRI logic and asks clarifying questions before assigning a classification, producing audit-ready reports grounded in Section Notes, Chapter Notes, and relevant CROSS rulings, which is the research foundation your licensed broker reviews and confirms.

Step 2: Subscribe those codes to the change feeds. This is the heart of the program. Instead of reading the Federal Register and every CSMS message and hand-matching them to your catalog, you point a monitor at the sources and let it match. GingerControl's Compliance Radar personalizes impact alerts to your Classifier and Sandbox records across five sources, CSMS, Federal Register, White House, CBP Rulings, and USTR, so only the notices that touch your codes surface, and it can auto-reclassify or recalculate on the effective date so a June-8 change does not sit unread until August.

Step 3: Model the hit the moment a part is flagged. When a part is newly covered, you need the dollar impact before the entries pile up. GingerControl's Product Sandbox runs an N x M tariff matrix, every product against every source country, with the full duty stack per cell (base, Section 232, Section 301, Chapter 99), so you can quantify what the new derivative rate does to landed cost and compare sourcing alternatives on the same canvas.

Step 4: Route each newly covered part to a mitigation decision. A flagged part is a decision, not just a data point. The options, drawback on the added duty, a Foreign-Trade Zone, resourcing to a partner-country origin, or confirming a reduced-rate tier applies, are yours and your broker's to make. The program's job is to make sure the decision gets made on the effective date, with the numbers attached, instead of after liquidation.

Step 5: Keep the audit trail. Every alert, every reclassification, and every sourcing choice should be timestamped. Product Sandbox's Selection History is built as a CF 28-ready audit trail under 19 CFR 163.4 (five-year retention), so when CBP asks how you knew a part was covered and when, you can show the record.

A worked example: the rack that became a steel derivative

Consider a mid-sized equipment manufacturer importing storage racks and assemblies. In the June 2026 expansion, steel racks were among the products newly pulled into derivative scope. Under the pre-2026 methodology, even a covered derivative was taxed on its declared metal content. Under the current rule, the standard 25% derivative rate applies to the full customs value of the article.

Walk the two paths:

  • Without monitoring: The importer keeps filing the racks the way it always has. The parts are now covered but no Chapter 99 heading is applied. Entries post through the summer. At liquidation, CBP applies the derivative rate on full value, plus interest, and the importer is now writing a prior disclosure and reconciling a duty accrual it never booked.
  • With monitoring: On June 8, the effective date, the alert fires because the racks' HTS code is on the importer's monitored list. The team recalculates landed cost in the Sandbox that day, confirms the correct Chapter 99 heading and melt-and-pour declaration with its broker, and either applies the duty correctly going forward or resources the part. No liquidation surprise.

The difference between the two paths is not knowledge of the rate. Both importers could have looked up 25%. The difference is whether anything was watching the derivative list against their own parts on the day it changed.

Frequently asked questions

How does GingerControl monitor Section 232 derivative-inclusion changes for my specific HTS codes?

GingerControl's Compliance Radar matches Federal Register, CSMS, White House, CBP Rulings, and USTR actions to your actual Classifier and Sandbox records, so a change to a steel or aluminum derivative code you import triggers a personalized alert rather than a raw feed you have to triage. For a compliance manager monitoring hundreds of metals-exposed SKUs, Radar can auto-reclassify or recalculate on the effective date, which is what keeps a newly covered part from surfacing at liquidation. Compliance Radar is currently in private beta.

What is a Section 232 derivative product, and how do I know if my part is one?

A Section 232 derivative product is a downstream steel or aluminum article, such as a fastener, rack, or metal-intensive component, that carries the metals tariff even though it is not raw steel or aluminum, identified by HTS code on the derivative inclusion list. GingerControl's HTS Classification Researcher assigns a defensible HTS code to each part using GRI reasoning and CROSS ruling research, producing the audit-ready classification your licensed broker confirms, which is the prerequisite for knowing whether a code sits in derivative scope.

How is the duty on a Section 232 derivative calculated, on the full value or the metal content?

For entries on or after April 6, 2026, the derivative duty applies to the full customs value of the article, a shift from the earlier methodology that taxed only the declared metal content, per the April 2026 proclamation and CBP CSMS guidance. GingerControl's Product Sandbox models this full-value calculation per cell alongside base duty, Section 301, and Chapter 99, so a compliance team can see the real landed-cost impact of a derivative inclusion before the entries post.

What happens if I miss a Section 232 derivative inclusion and only find out at liquidation?

If a part was covered and you did not apply the correct Chapter 99 heading, CBP can assess the back duty at liquidation along with interest, and you may face liquidated damages and a prior-disclosure process. GingerControl's Compliance Radar is designed to prevent exactly this by alerting on the effective date, and Product Sandbox's Selection History gives you the CF 28-ready audit trail (19 CFR 163.4) that documents when you knew a part was in scope.

How often does the Section 232 derivative list change, and can I rely on a quarterly review?

The list expanded through scheduled inclusion windows in 2025 and through presidential proclamations in April and June 2026, so it moves on both a periodic and a rolling basis, sometimes with only days between announcement and effective date. GingerControl's Compliance Radar replaces the quarterly manual review with continuous five-source monitoring keyed to your HTS codes, so a rolling proclamation does not sit unread between reviews.

Does GingerControl declare my melt-and-pour or smelt-and-cast origin to CBP?

No. GingerControl is decision-support software, not a customs broker, and it does not file entries or make declarations to CBP. GingerControl's tools surface which of your parts a derivative-list change captured and model the duty impact, and your team or your licensed broker files the melt-and-pour and smelt-and-cast declarations through ACE and makes the final entry.

Can GingerControl help me decide whether to pursue drawback or an FTZ on a newly covered part?

GingerControl's Product Sandbox quantifies the duty impact of a newly covered derivative and compares sourcing alternatives side by side, which is the analysis a mitigation decision starts from, and its Selection History preserves the reasoning. The drawback or FTZ decision itself is yours and your broker's or counsel's to make; GingerControl provides the exposure numbers and the audit trail that support it, not the legal determination.

Watch the derivative list against your own HTS codes

A Section 232 derivative-inclusion program comes down to one discipline: never let the derivative list change without something checking it against your item master on the effective date. The rate is the easy part. The mapping and the timing are what cost you at liquidation.

Watch the 232 derivative lists against your own HTS codes, not the whole Federal Register. GingerControl's Compliance Radar matches Federal Register, CSMS, and White House actions to your actual records and delivers a one-click reclassify on the effective date, and Product Sandbox models the exposure the moment a part is flagged. Set up monitoring for your codes →

GingerControl is not just a tool. We work with importers and trade compliance teams on process consulting, digital transformation strategy, and end-to-end custom system development, starting with a free 30-minute compliance audit. Talk to our team →

GingerControl is an HTS Classification Researcher. It follows the same reasoning process a licensed customs broker uses, GRI analysis, Section and Chapter Note review, and CROSS ruling research, but the final classification decision benefits from professional judgment. GingerControl produces audit-ready documentation that supports the classification decision; it does not provide legal advice or replace licensed customs expertise, and its analysis is decision support for the importer or their licensed broker or counsel, not customs business. Classifying specific goods beyond the six-digit level for importation, and importer-of-record registration via Form 5106, constitute customs business requiring a licensed broker under CBP rulings HQ H290535 and HQ H350722.

References

[REF 1] Bureau of Industry and Security (Federal Register): Adoption and Procedures of the Section 232 Steel and Aluminum Tariff Inclusions Process Data cited: the formal inclusions process, eligibility, two-week submission windows, public comment period, roughly 60-day review, and the two derivative-inclusion criteria (docket BIS-2025-0023) Source: Adoption and Procedures of the Section 232 Steel and Aluminum Tariff Inclusions Process Published: August 19, 2025

[REF 2] The White House / Federal Register: Strengthening Actions Taken To Adjust Imports of Aluminum, Steel, and Copper Into the United States Data cited: April 2026 restructuring, effective April 6, 2026; shift of the derivative duty to full customs value; supersession of the periodic public inclusions window with continued Commerce/USTR authority to expand coverage Source: Strengthening Actions Taken To Adjust Imports of Aluminum, Steel, and Copper Published: April 2026

[REF 3] U.S. Customs and Border Protection: Section 232 Tariffs on Steel and Aluminum Frequently Asked Questions Data cited: melt-and-pour and smelt-and-cast reporting through ACE; closure of the "unknown" smelt-and-cast option with a 200% duty consequence for aluminum; Chapter 99 derivative reporting; CSMS implementation references (including CSMS #68253075) Source: Section 232 Tariffs on Steel and Aluminum FAQs Published: updated 2026

[REF 4] The White House: June 2026 Section 232 proclamation on aluminum, steel, and copper Data cited: June 1, 2026 proclamation effective June 8, 2026 through December 31, 2027; expanded derivative coverage (e.g., steel racks); reduced-rate tiers for certain equipment; lowered U.S.-content threshold; CBP CSMS #68855869 implementation guidance Source: Strengthening Actions Taken To Adjust Imports of Aluminum, Steel, and Copper Published: June 2026

Chen Cui

Written by

Chen Cui

Co-Founder of GingerControl

Building scalable AI and automated workflows for trade compliance teams.

LinkedIn Profile

You may also like these

Related Post

We use cookies to understand how visitors interact with our site. No personal data is shared with advertisers.