# Section 232 Tariff Changes in 2026: Monitoring HTS Chapter 99 Updates Source: PageCrawl.io Blog URL: https://pagecrawl.io/blog/section-232-tariff-hts-2026-change-monitoring --- A new HTS Chapter 99 subheading for a steel derivative product gets added to the Section 232 scope in a Federal Register notice published on a Wednesday. CBP issues a CSMS message clarifying the effective date and the value-of-steel reporting requirement two days later. Your broker files entries Thursday and Friday using the old classification. By the time the change surfaces in your trade compliance review the following Monday, you have a stack of entries that need post-summary corrections, a duty underpayment to true up, and a conversation with CBP you would rather not have. Section 232 has stopped being a one-time action and become a moving target. Through 2025 and into 2026, the steel and aluminum programs have expanded repeatedly: new derivative products folded into scope, the aluminum rate stepped up, country-specific arrangements added and removed, and the auto and auto-parts actions layered on their own Chapter 99 provisions. Each expansion lands as a presidential proclamation, a Federal Register notice that lists the exact HTS Chapter 99 headings and the underlying Chapter 72, 73, and 76 codes, and then a CBP CSMS message that tells your broker how to actually file. Miss any one of those documents and your entries go in wrong. This guide covers what Section 232 actually changes in your HTS classification, which specific pages publish those changes first, how to set up automated monitoring for Chapter 99 updates and CSMS messages, and how to route alerts so your brokerage and compliance teams act before entries are filed against stale duty rates. ### How Section 232 Shows Up in Your Tariff Classification Section 232 of the Trade Expansion Act of 1962 lets the executive branch impose tariffs on imports that are judged to threaten national security. In practice for importers, it means an additional duty stacked on top of the normal HTS rate, and that additional duty is administered through Chapter 99 of the Harmonized Tariff Schedule. Chapter 99 is where temporary and special trade-program provisions live. A Section 232 entry does not just carry its normal Chapter 72 or 76 classification. It also carries a Chapter 99 subheading (the 9903.xx.xx range for these actions) that signals the additional duty, the rate, and any country exception. When the program expands, the change you have to track is almost always a change to Chapter 99: a new 9903 subheading, a revised rate on an existing one, or a new list of underlying codes that the subheading now covers. #### The four moving parts in 2026 - **Steel and steel derivatives.** The core steel action plus a growing annex of derivative products (fasteners, structural fabrications, and other downstream goods). Derivatives are the trap, because a product can be pulled into scope by being added to an annex without your underlying classification changing at all. - **Aluminum and aluminum derivatives.** The same structure as steel, with its own 9903 subheadings, its own derivative annex, and a rate that has stepped up over the program's life. - **Autos and auto parts.** A separate Section 232 action with its own Chapter 99 provisions and its own parts list, relevant to anyone importing vehicles or components. - **Country arrangements and exclusions.** Quota arrangements, tariff-rate quotas, and exclusion outcomes change which 9903 subheading and which rate applies based on country of origin. These shift more often than the base actions. Because the additional duty is keyed to Chapter 99 rather than your normal classification, the question "did my product's duty change" is really the question "did a 9903 subheading that touches my HTS codes get added, repriced, or re-scoped." That is a monitoring problem with a small, well-defined set of source pages. ### Where Section 232 Changes Are Published First Three layers publish the same change at different times and in different detail. You want all three, because each answers a different question. #### Presidential proclamations and the White House New Section 232 actions and major modifications begin as a presidential proclamation. These are the earliest signal and the broadest, but they are written in legal and policy language, not classification language. A proclamation tells you a derivative annex is being expanded. It rarely gives you the clean list of 9903 subheadings you can hand to your broker. #### Federal Register notices The Federal Register is where the action becomes operational and where the HTS Chapter 99 detail lives. Commerce and the relevant agencies publish notices that list the exact 9903 subheadings, the rates, the underlying Chapter 72, 73, and 76 codes covered, the effective dates, and any country carve-outs. This is the document your classification team needs. The Federal Register also publishes derivative-inclusion notices and exclusion determinations. You can build targeted Federal Register searches that return only notices matching your terms (for example "Section 232" combined with "aluminum" or a specific 9903 heading). The search results page has a stable URL you can monitor. For the broader pattern of watching regulatory publications, see our guide to [regulatory compliance monitoring](/blog/regulatory-compliance-monitoring). #### CBP CSMS messages The Cargo Systems Messaging Service is where Section 232 becomes a filing instruction. CSMS messages tell your broker the exact effective date and time, how to report the value of steel or aluminum content, which 9903 subheading to transmit, how stacking with other actions works, and how to handle in-transit merchandise. For a customs broker, the CSMS message is often more operationally important than the Federal Register notice, because it resolves the ambiguities that the notice leaves open. CSMS also publishes corrections and clarifications after the fact. A program can technically take effect on a Monday and have its filing mechanics clarified in a Wednesday CSMS message, and entries filed in between are at risk. #### The HTS itself The official Harmonized Tariff Schedule, maintained by the U.S. International Trade Commission, is updated to reflect these actions. Chapter 99 in the HTS is the authoritative current state of which subheadings exist and what they cover. Monitoring the Chapter 99 page (and the HTS change-record or revision log) confirms that a proclamation or notice has actually been implemented in the schedule your broker's software pulls from. ### What to Watch For in Each Source Not every change to these pages matters equally. Knowing the categories lets you tune alerts so the urgent ones reach a human fast and the routine ones do not create noise. #### New or expanded derivative annexes The single most common 2026 change. A derivative-inclusion notice adds downstream products to the steel or aluminum action. If any of your imported products fall into an added category, your landed cost jumps without your base classification changing. Watch derivative annex notices and the corresponding new 9903 subheadings closely. #### Rate changes on existing 9903 subheadings A subheading that already covers your goods gets a higher additional-duty rate. The aluminum program has done this. These are quiet changes (one number moving) with large cost consequences at volume. #### Country arrangement changes A country moves from a tariff-rate quota arrangement to the flat additional duty, or an arrangement expires. The 9903 subheading and rate that applies to your origin country changes even though nothing about the product changed. #### Exclusion grants, denials, and expirations If you rely on a product exclusion, its expiration restores the additional duty. Exclusion determinations and renewal windows have firm dates. Missing a renewal window restores full Section 232 duty on goods you had been importing duty-light. #### Effective-date and in-transit rules CSMS messages specify whether goods on the water before the effective date are covered. This determines whether entries you have already committed to are at the old or new rate. ### Manual Tracking Falls Apart Here Specifically Plenty of brokerage and compliance teams still track Section 232 by reading a couple of trade newsletters and checking the Federal Register when someone remembers. For a program that changes this often, across three publication layers with different timing, that approach breaks in predictable ways. #### The three-layer timing gap The proclamation, the Federal Register notice, and the CSMS message often arrive on different days. A team watching only one layer either reacts too early (before the operational detail exists) or too late (after entries are already filed). You need all three watched simultaneously, which no individual checking pages by hand sustains. #### Derivative annexes hide in long documents A derivative-inclusion notice can be dozens of pages, and the product that affects you might be one line in an annex table. A human skimming for "does this affect us" misses it. A change detector that flags the notice and an AI summary that surfaces the added HTS codes does not. #### No record of when you knew If CBP questions a duty calculation, "when did your company become aware of the change" is a real question. Manual checking leaves no timestamped record. Automated monitoring captures the page content and a screenshot at each check, which is exactly the kind of dated evidence an auditor or your own counsel wants to see. This is the same audit-trail logic behind [SEC 17a-4 web archive monitoring](/blog/sec-17a-4-web-archive-monitoring) and broader [compliance monitoring software](/blog/compliance-monitoring-software). #### Coverage stops when one person is out When Section 232 monitoring lives in one analyst's weekly routine, it pauses during vacations and turnover, which is exactly when an expansion you missed becomes a stack of post-entry corrections. ### Setting Up Automated Section 232 Monitoring PageCrawl watches web pages and alerts you when their content changes. Here is a concrete configuration for the Section 232 sources, building from the most operationally urgent outward. This builds on the general approach in our [tariff and trade policy monitoring guide](/blog/tariff-trade-policy-monitoring-import-duty-changes); this post narrows it to the Section 232 and Chapter 99 specifics. #### Step 1: Monitor CBP CSMS messages CSMS is the most time-sensitive layer because it drives filing. CBP lets you filter CSMS messages by category and search by keyword, and the filtered results page has a stable URL. 1. Build a CSMS search or category-filtered view for "Section 232" (and one each for "steel" and "aluminum" if you want finer routing). 2. Add the results page URL as a monitor in PageCrawl. 3. Set the tracking mode to text content so navigation and layout changes do not trigger false alerts. 4. Set check frequency to its most frequent setting your plan allows. CSMS messages affect same-day filing, so a 5 or 15 minute check is worth it on a paid plan. 5. Enable AI summaries with the focus set to "new Section 232 CSMS messages, effective dates, 9903 subheadings, value reporting requirements, in-transit provisions." #### Step 2: Monitor Federal Register search results The Federal Register gives you the classification detail. Create one or more saved searches targeting your products. 1. On federalregister.gov, search for "Section 232" combined with the metals relevant to you, or for a specific 9903 heading like "9903.81" (steel) or "9903.85" (aluminum). Add narrower searches for your underlying Chapter 72, 73, or 76 codes if your import mix is concentrated. 2. Copy the search results URL. 3. Add it as a monitor with text content mode and a daily or twice-daily check. 4. Set the AI focus to "new Section 232 notices, derivative product additions, duty rate changes, exclusion determinations, affected HTS codes." This is where you catch derivative annex expansions. Run a separate monitor per metal so alerts route cleanly to the right reviewer. #### Step 3: Monitor HTS Chapter 99 directly Monitoring the USITC HTS Chapter 99 page (and the HTS revision or change-record log) confirms that a change has actually landed in the authoritative schedule your broker's software relies on. 1. Add the Chapter 99 page (the 9903 range covering Section 232) as a monitor. 2. Use text content mode with a daily check. 3. Set AI focus to "added or modified 9903 subheadings, rate changes, changes to covered HTS codes." Note: the full Chapter 99 page can be large, so review the first two weeks of alerts and tighten the monitor to the specific 9903 section if you get noise from unrelated trade-program updates on the same page. #### Step 4: Monitor proclamations for early warning Add the White House presidential-actions page and the Commerce Section 232 program page as lower-frequency monitors (every 6 to 12 hours). These give you the earliest heads-up that something is coming, before the operational detail exists. Set the AI focus to "Section 232, steel, aluminum, derivative products, automobiles, tariff modification." #### A note on tracking specific codes For teams with a concentrated import mix, you can go a step further and track the duty rate cell itself on a page that displays it, rather than the whole notice. PageCrawl's element-level tracking lets you watch a specific value and alert only when that number changes. That is most useful once you know exactly which 9903 subheading governs your goods. ### Routing Alerts to the People Who File Detection is half the job. The workflow around it decides whether a caught change actually prevents a misfiled entry. #### Match the alert to the action Different Section 232 changes need different first responders: - **CSMS effective-date and filing changes** go to the brokerage operations team and any in-house entry writers immediately, because they affect entries being filed today. - **Derivative annex additions** go to classification and compliance, who decide whether your products are now in scope. - **Rate changes** go to finance and pricing, who remodel landed cost and margins. - **Exclusion expirations** go to whoever owns the exclusion renewal calendar, well before the expiration date. Use [Slack alerts](/blog/website-change-alerts-slack) to deliver each monitor's changes to a channel for the team that owns that response, so a CSMS filing change never sits unread in a shared inbox. #### Feed changes into brokerage and ERP systems For teams running a customs entry system or ERP, PageCrawl's [webhook output](/blog/webhook-automation-website-changes) sends structured data about each detected change to any endpoint. You can open a ticket in your compliance system the moment a derivative annex notice appears, flag affected SKUs against your product catalog, or log every change with its timestamp for the audit trail. #### Build a cross-reference workflow With [n8n](/blog/n8n-website-monitoring-automate-change-detection) or [Zapier](/blog/zapier-website-monitoring), you can take a Section 232 change alert, extract the affected 9903 subheading and underlying HTS codes, cross-reference them against the codes you actually import, and notify only the product owners whose goods are touched. That turns a broad regulatory alert into a targeted "your part is now in scope" message, which is the difference between an alert that gets acted on and one that gets ignored. This is the same alert-to-action pattern that works for adjacent compliance feeds like [government agency news monitoring](/blog/government-agency-news-monitoring) and [legislative tracking](/blog/legislative-tracking-monitor-bills-laws). ### A Practical Monitoring Plan by Role #### Customs brokers Brokers file for many importers and cannot afford to file against a stale 9903 subheading. Prioritize CSMS (5 to 15 minute checks), then the Federal Register notices, then Chapter 99 confirmation. Route CSMS changes straight to the desk that writes entries, and keep timestamped snapshots so you can show a client exactly when guidance changed. #### Importers of record You own the duty liability, so the audit trail matters most. Watch the Federal Register and Chapter 99 for the codes you import, watch CSMS for effective dates, and feed every change into your entry-review process with a logged timestamp. Keep an exclusion-expiration calendar fed by your exclusion-determination monitor. #### Manufacturers using steel and aluminum Even if you do not import directly, derivative annex expansions and rate increases flow into your input costs through your domestic suppliers. Monitor derivative-inclusion notices and rate changes, and route them to procurement and finance to remodel input costs before supplier price letters arrive. ### Choosing your PageCrawl plan PageCrawl's **Free plan** lets you monitor **6 pages** with **220 checks per month**, which is enough to validate the approach on your most critical pages. Most teams graduate to a paid plan once they see the value. | Plan | Price | Pages | Checks / month | Frequency | |------|-------|-------|----------------|-----------| | Free | $0 | 6 | 220 | every 60 min | | Standard | $8/mo or $80/yr | 100 | 15,000 | every 15 min | | Enterprise | $30/mo or $300/yr | 500 | 100,000 | every 5 min | | Ultimate | $99/mo or $999/yr | 1,000 | 100,000 | every 2 min | Annual billing saves two months across every paid tier. Enterprise and Ultimate scale up to 100x if you need thousands of pages or multi-team access. Compliance monitoring is the cheapest insurance you can buy. A single missed regulatory change can trigger fines in the tens or hundreds of thousands, not to mention the audit overhead of proving you did not see it coming. Enterprise at $300/year covers 500 regulatory pages with unlimited history and timestamped screenshots, which is usually exactly what an assessor wants to see. All plans include the **PageCrawl MCP Server**, so your compliance team can ask Claude to summarize every change to a specific regulation over the last quarter and pull the exact diff, turning your monitoring history into a queryable audit trail. AI assistants can create monitors through conversation on every plan, including Free, and paid plans add on-demand checks and monitor management. Standard at $80/year is enough to cover 100 pages across your primary regulatory bodies if your program is smaller. ### Getting Started Start with the three pages that actually prevent a misfiled entry: a CBP CSMS search filtered for "Section 232," a Federal Register search combining "Section 232" with the metal most relevant to your import mix, and the USITC HTS Chapter 99 page for the 9903 range that covers your goods. Set these up with text content mode, put the CSMS monitor on the most frequent check your plan allows, and configure AI summaries focused on effective dates, 9903 subheadings, and added HTS codes. Route the CSMS alerts to whoever writes your entries and the Federal Register alerts to classification. Run it for 30 days and watch which monitors produce useful signal versus noise. Tighten your Federal Register search terms and your Chapter 99 monitor scope based on what you see. Then expand: add proclamation monitors for early warning, add the auto and auto-parts provisions if they apply, and wire webhook or automation-platform workflows that cross-reference changes against the exact codes you import. PageCrawl's free tier includes 6 monitors, enough to cover the core CSMS, Federal Register, and Chapter 99 sources for a single metals program. As Section 232 keeps expanding through 2026, the teams that see each Chapter 99 change the day it publishes will keep filing clean entries while everyone else is processing corrections. --- Need more? The complete PageCrawl.io help center, with every article, is available as a single document at https://pagecrawl.io/llms-full.txt. Read it for context on anything this page does not cover.