Supplier or Material Change: When Must You Recheck an HTS Code?
Recheck an HTS code when a change touches a fact the code rests on, not every time a supplier changes. A new supplier making an identical part keeps the code, but usually changes the country of origin and with it the duty layers. A material swap changes the code when the part is classified by material (steel to aluminum moves 7326 to 7616) and often leaves it alone when the part is classified by function. For a manufacturer re-sourcing 200 parts a quarter, sorting each change into code, origin or duty decides which ones need a classification review.
In this post
- Does changing suppliers change the HTS code?
- Does a material change require HTS reclassification?
- Does a new country of origin change the HTS code or only the duty?
- Which product changes trigger an HTS recheck?
- Is a binding ruling still valid after the product changes?
- What if entries were already filed with the old code?
- How do you catch changes before the next entry?
- Putting change-triggered rechecks into your PLM and supplier flow
- References
This post is about rechecks triggered by your own changes: a new supplier, a new material, an engineering change order (ECO), a new plant. It is not the calendar review, which is in our annual HTS classification review checklist, it is not about keeping supplier certificates current, which is in keeping BOM origin data current, and it is not about choosing materials at the design stage, which is in our material composition tariff guide. Our HTS classification guide covers how GRI 1 to 6 decide the code in the first place. Every HTS number and note below was read in HTS 2026 Revision 23, released November 10, 2026, on November 19, 2026 [1] [18].
Does changing suppliers change the HTS code?
Changing suppliers does not change the HTS code when the new part is identical, because the code describes the goods, not who makes them. GRI 1 says classification "shall be determined according to the terms of the headings and any relative section or chapter notes" [2], and 19 CFR 152.11 says merchandise is classified under the HTS as interpreted by rulings and court decisions [3]. Neither the supplier's name nor its country is a term in the headings that cover a manufacturer's parts.
What a supplier change does move, almost every time, is everything around the code:
- Country of origin. A new supplier in Vietnam instead of China changes the origin, unless the work there is too minor to count (next sections).
- Duty layers. Origin decides which rate column and which Chapter 99 lines apply.
- Customs value. A new price, new assists or new terms change the value declared on each entry.
- The word "identical". A new supplier often meets the drawing with a different alloy grade, coating, resin or subcomponent. Those are the changes that move codes.
So the first question for a re-sourced part is not "did the supplier change" but "did any fact the code rests on change". A part number staying the same proves nothing; the spec sheet does.
Does a material change require HTS reclassification?
A material change requires reclassification when the part is classified by its material, and usually not when it is classified by its function. The HTS builds that split into its notes, which makes it the fastest way to triage a stack of ECOs.
Base metal and plastic articles that are not parts of a specific machine or vehicle sit in material chapters: 7326 for "other articles of iron or steel", 7616 for "other articles of aluminum", 3926 for other articles of plastics, 4016 for other articles of vulcanized rubber [1]. Swap the material and the heading changes with it. Parts of vehicles and machines are pulled into function headings instead, such as 8708 for motor vehicle parts or the machine headings under Section XVI Note 2 [4] [5]. There, a material swap usually leaves the code alone, though not always: Section XVII Note 2 sends several kinds of goods back to their material, even when they are made for a vehicle [4]:
"The expressions "parts" and "parts and accessories" do not apply to the following articles, whether or not they are identifiable as for the goods of this section: (a) Joints, washers or the like of any material (classified according to their constituent material or in heading 8484) or other articles of vulcanized rubber other than hard rubber (heading 4016); (b) Parts of general use, as defined in note 2 to section XV, of base metal (section XV) or similar goods of plastics (chapter 39)" (HTS Section XVII, Note 2)
| The change | Classified by | Old code (general rate) | New code (general rate) | Code moves? |
|---|---|---|---|---|
| Bracket, steel to aluminum, not a vehicle part | Material | 7326.90.86 (2.9%) | 7616.99.51 (2.5%) | Yes |
| Vehicle part of 8708, steel to aluminum | Function | 8708.99.81 (2.5%) | 8708.99.81 (2.5%) | Usually no; Section 232 treatment can change |
| Vehicle seal, rubber to plastic | Material (Section XVII Note 2(a)) | 4016.93.10 (2.5%) | 3926.90.45 (3.5%) | Yes |
| Bare board gets mounted components (beyond connectors) | Function | 8534.00.00 (Free) | A parts or apparatus heading (for example 8473.30.11, printed circuit assemblies for computers of heading 8471, Free) | Yes |
The last row comes from Chapter 85 Note 8: "printed circuits" in heading 8534 do "not cover circuits combined with elements other than those obtained during the printing process" [6]. A board revision that adds mounted components, other than non-printed connecting elements, takes the board out of 8534. Rates are the general column only, before any Chapter 99 line.
Bottom line: For a compliance team facing a quarter's worth of ECOs on 14,000 part numbers, sort them by how each part is classified first. Material-led parts (Chapters 39, 40, 73, 76) need a review on any material swap. Function-led parts need one only when the function, the components or a note's exception changes.
A function-led part that keeps its code can still change its duty. In Revision 23, U.S. note 16 to subchapter III of Chapter 99 lists Section 232 articles by HTS provision on lists titled by metal (steel, aluminum, copper), and outside Chapters 72, 73, 74 and 76 a listed provision is covered only where the listed metal is at least 15 percent of the article's weight [8]. A steel to aluminum swap can therefore change which list applies, or take a part out of coverage; check the lists in force on the entry date. Our Section 232 steel and aluminum guide covers those annexes.
Does a new country of origin change the HTS code or only the duty?
A new country of origin changes only the duty, not the HTS code. CBP's marking regulation defines origin as "the country of manufacture, production, or growth", and work done in a second country makes it the origin only if it effects a "substantial transformation" (19 CFR 134.1(b)); for a good of a USMCA country, the part 102 rules decide origin under that part [7]. Our guide to country of origin determination rules walks through that test.
Chapter 99 is where code and origin meet. The Section 301 note for heading 9903.88.01 reads: "The products of China that are subject to an additional 25 percent ad valorem rate of duty under heading 9903.88.01 are products of China that are classified in the subheadings enumerated in U.S. note 20(b)" [8]. A Section 301 line needs both facts: the right subheading and the right origin. Change either one and the line can switch on or off.
That is why a re-sourcing project needs two checks, not one:
- Origin check. Does the new supplier's process make its country the origin, or does the origin stay with an earlier stage (for example Chinese components assembled in Vietnam with minor work)?
- Layer check. With the code unchanged and the origin settled, which Chapter 99 lines apply on the entry date? See Section 232 vs Section 301 for how the two programs stack.
Which product changes trigger an HTS recheck?
A change triggers an HTS recheck when it touches one of the facts the code was decided on; everything else triggers an origin or duty check instead. The table maps the common changes in a manufacturer's year to the three layers a change can touch.
| Change in your company | HTS code | Country of origin | Duty layers | Binding ruling coverage |
|---|---|---|---|---|
| New supplier, identical part, same country | No | No | Value may change | Stays, if the part is identical |
| New supplier, identical part, new country | No | Yes | Yes (rate column, Chapter 99) | Stays for classification; origin is a separate question |
| Material swap on a material-led part | Yes | Maybe | Yes | Lost for the new part |
| Material swap on a function-led part | Usually no | Maybe | Maybe (Section 232) | Lost if the ruling describes the material |
| Component added or removed in an assembly | Maybe (GRI 3(b), Section XVI notes) | Maybe | Maybe | Lost if the description changes |
| New function or feature (an ECO) | Maybe | No | Maybe | Lost if the description changes |
| Production moved to a new plant | No | Yes, if the plant is in another country | Yes, if origin changes | Origin is a separate question |
| Packaging, color, tolerance only | Rarely | No | No | Usually stays |
Bottom line: For a manufacturer re-sourcing 200 parts a quarter, most supplier switches need an origin and duty check, not a classification review. The classification reviews go to material swaps on material-led parts and to ECOs that change an assembly's components or function.
Quotable insight: Every HTS code rests on a short list of deciding facts: the material of a material-led part, the function and components of an assembly, the features a subheading names. Write those facts down next to the code when you decide it. A supplier switch or ECO then needs a classification review only if it touches one of them, which turns "recheck everything that changed" into "recheck what the code depends on".
When I built the GRI engine behind GingerControl's classification, this was the design question that mattered most: the reasoning for a code is only useful later if it names the facts the code depends on, in words an engineer's change form can be compared against. A code with no recorded reasons has to be reclassified from scratch every time anything changes.
A deciding facts record needs only five fields per code. Kept next to the code in the item master, it is what a change form is checked against:
| Field | What to record | The change that reopens it |
|---|---|---|
| Classifying basis | Classified by material or by function, and the GRI or note that decided it | Any change, if the basis was a close call |
| Material | Material and grade, with the share for mixed parts | A material or grade swap on a material-led part |
| Function and components | What the part does, and the components that decided the heading | An ECO that adds, removes or replaces a component or function |
| Named features | The features the chosen subheading names (size, power, use) | A spec change to one of those features |
| Ruling relied on | The ruling number and the description it covers | Any change to what that description says |
Origin is kept in its own record, because a new supplier can change it without touching a single field above.
Is a binding ruling still valid after the product changes?
A binding ruling does not cover a part whose material or design has changed, because a classification ruling applies only to identical articles. 19 CFR 177.9(b)(2) says each classification ruling "will be applied only with respect to transactions involving articles identical to the sample submitted with the ruling request or to articles whose description is identical to the description set forth in the ruling letter" [9]. Section 177.9(b)(1) adds that each ruling assumes the facts given were "accurate and complete in every material respect" [9].
Three consequences for a manufacturer:
- The part number does not carry the ruling. A ruling for a steel housing does not follow the aluminum housing that replaced it under the same number.
- The description is the boundary. Read the ruling's description of the product, not only its conclusion, against the new spec.
- A new version needs its own basis. Classify it from its facts, cite similar CROSS rulings as reasoning, or request a new binding ruling where the duty at stake justifies the wait.
What if entries were already filed with the old code?
The change does not make entries of the old version wrong, because goods are classified in the condition in which they are imported [17]; only entries of the changed version can be wrong, and each is corrected by where it stands: a post summary correction while it is unliquidated and inside the window, a protest if it is liquidated with duty overpaid, and a prior disclosure if duty was underpaid and the entry is liquidated or past the window. That makes the date you pick the most important number in the file. Use the entry date of the first shipment that carried the changed part, not the date engineering approved the ECO: parts in the pipeline often keep arriving in the old version for weeks.
Once you have the list of affected entries, the route depends on where each entry stands:
| Where the entry stands | Usual route | Rule |
|---|---|---|
| Unliquidated, within the window | Post summary correction by your broker, within 300 days of entry or up to 15 days before scheduled liquidation, whichever is earlier | 91 FR 41053 [10] |
| Liquidated, duty overpaid | Protest within 180 days of liquidation | 19 U.S.C. 1514(c)(3) [11] |
| Duty underpaid, liquidated or past the correction window | Prior disclosure, before CBP opens a formal investigation | 19 CFR 162.74 [12] |
An entry not liquidated within one year from the date of entry is deemed liquidated by operation of law unless liquidation is extended or suspended (19 CFR 159.11) [13], and the PSC window closes at 300 days or 15 days before scheduled liquidation, whichever is earlier, so a change found ten months or more after the first changed entry leaves the earliest entries outside the correction window. Where the correct code carries a lower rate, the overpaid entries follow the same table. GingerControl identifies and documents the opportunity; your licensed broker or counsel files.
The exposure on underpaid entries is set by statute. A negligent violation of 19 U.S.C. 1592 carries a civil penalty of up to the lesser of the domestic value of the goods or "two times the lawful duties, taxes, and fees of which the United States is or may be deprived" [14]. With a valid prior disclosure of a negligent violation, the penalty falls to interest on the unpaid duty, provided the duty is tendered [14]. The United States has five years from the date of a negligent 1592 violation to bring suit, or five years from discovery where the violation arises from fraud (19 U.S.C. 1621) [15]. The importer's baseline duty is reasonable care: under 19 U.S.C. 1484 the importer of record, "using reasonable care", files "the declared value, classification and rate of duty" [16]. Our guides to reasonable care and prior disclosure under 19 CFR 162.74 cover each step; which route fits a given set of entries is a decision for your broker or customs counsel.
How do you catch changes before the next entry?
You catch changes before the next entry by putting the trigger where the change is made: in the PLM when engineering releases an ECO, and in the ERP or supplier master when procurement adds a vendor or a new origin. A calendar review finds a stale code months later; a trigger finds it before the PO ships.
- Change releasedECO approved in the PLM, new vendor or origin set up in the ERP or supplier master
- Compare against the deciding factsDoes the change touch the material, function, components or ruling description behind the code?
- Sort into code, origin or dutyCode: classification review. Origin: origin check. Duty: recompute the Chapter 99 layers for the entry date
- Approve and recordA named person approves the result; the reasoning and the effective date are kept with the part
- Update before the first changed lotThe new code, origin and duty reach the ERP and the broker before the shipment is entered
Most of the effort is in the second step, and a two-person team cannot do it by hand for every change in a 14,000-part catalog. This is the work GingerOS is built for. GingerOS, the AI-native system that runs your trade compliance, watches new rules and changes in your ERP, PLM and supplier records and alerts you when one affects you; it asks for missing product facts before it suggests an HTS code, records the reasoning for your approval, and writes approved results back to your ERP with an audit trail. Connections are set up for each client, read-only, with no master data migration. For BOMs, it weighs which component gives a product its essential character, which is the part of an assembly a component swap most often disturbs; our post on BOM classification governance explains that link.
GingerControl's Classification Researcher follows the reasoning a licensed customs broker uses: GRI analysis, Section and Chapter Note review, and CROSS ruling research. Its classifications are for general reference, educational, and planning purposes; before a code goes on an entry, your licensed customs broker reviews it. GingerControl is not a customs broker, does not file entries, and does not give legal advice.
Putting change-triggered rechecks into your PLM and supplier flow
If supplier switches and ECOs reach compliance only after the entry, the fix is a trigger at the source, not a bigger annual review. GingerOS, the AI-native system that runs your trade compliance, watches your PLM, ERP and supplier records for that trigger: it alerts you when a change affects a part and records the reasoning behind each code for your approval. It starts with Prototype Week: one call, then a clickable prototype of your own flow in three days. See GingerOS run on your own change orders
References
- U.S. International Trade Commission, Harmonized Tariff Schedule of the United States, 2026 Revision 23
Data cited: Headings 7326, 7616, 3926 and 4016 and their text; general rates of 7326.90.86 (2.9%), 7616.99.51 (2.5%), 3926.90.45 (3.5%), 4016.93.10 (2.5%), 8708.99.81 (2.5%), 8534.00.00 (Free), 8473.30.11 (Free)
Source: Chapter 39, Chapter 40, Chapter 73, Chapter 76, Chapter 84, Chapter 85, Chapter 87, HTS Revision 23
Published: Revision 23 (2026); read November 19, 2026 - U.S. International Trade Commission, HTS 2026 Revision 23, General Rules of Interpretation
Data cited: GRI 1 text, classification determined by the terms of the headings and any relative section or chapter notes
Source: General Rules of Interpretation, HTS Revision 23
Published: Revision 23 (2026); read November 19, 2026 - Code of Federal Regulations, 19 CFR 152.11
Data cited: merchandise classified in accordance with the HTS as interpreted by administrative and judicial rulings
Source: 19 CFR 152.11, eCFR
Published: eCFR current through November 17, 2026; read November 19, 2026 - U.S. International Trade Commission, HTS 2026 Revision 23, Section XVII Notes (Chapter 86)
Data cited: Note 2(a) and 2(b), articles excluded from "parts" and "parts and accessories" of Section XVII; Note 3, principal use
Source: Chapter 86 with Section XVII notes, HTS Revision 23
Published: Revision 23 (2026); read November 19, 2026 - U.S. International Trade Commission, HTS 2026 Revision 23, Section XVI Notes (Chapter 84)
Data cited: Note 2, rules for classifying parts of machines
Source: Chapter 84 with Section XVI notes, HTS Revision 23
Published: Revision 23 (2026); read November 19, 2026 - U.S. International Trade Commission, HTS 2026 Revision 23, Chapter 85 Notes
Data cited: Note 8, scope of "printed circuits" in heading 8534
Source: Chapter 85, HTS Revision 23
Published: Revision 23 (2026); read November 19, 2026 - Code of Federal Regulations, 19 CFR 134.1
Data cited: definition of country of origin; substantial transformation; part 102 rules for NAFTA or USMCA goods
Source: 19 CFR 134.1, eCFR
Published: eCFR current through November 17, 2026; read November 19, 2026 - U.S. International Trade Commission, HTS 2026 Revision 23, Chapter 99, Subchapter III, U.S. Notes 16(c) and 20(a)
Data cited: U.S. note 20(a), products of China classified in the subheadings of note 20(b) subject to the additional 25 percent duty of heading 9903.88.01; U.S. note 16(c), Section 232 lists by metal and the 15 percent metal weight condition outside Chapters 72, 73, 74 and 76
Source: Chapter 99, HTS Revision 23
Published: Revision 23 (2026); read November 19, 2026 - Code of Federal Regulations, 19 CFR 177.9
Data cited: 177.9(b)(1), rulings assume the information furnished is accurate and complete in every material respect; 177.9(b)(2), classification rulings apply only to identical articles
Source: 19 CFR 177.9, eCFR
Published: eCFR current through November 17, 2026; read November 19, 2026 - Federal Register, Modification and Clarification of the National Customs Automation Program Test Regarding Post-Summary Corrections, 91 FR 41053
Data cited: a PSC must be transmitted within 300 days of the date of entry or up to 15 days prior to the scheduled liquidation date, whichever is earlier
Source: 91 FR 41053, Federal Register
Published: July 6, 2026; read November 19, 2026 - United States Code, 19 U.S.C. 1514
Data cited: 1514(c)(3), protest filed within 180 days after the date of liquidation or reliquidation
Source: 19 U.S.C. 1514, govinfo
Published: U.S. Code, 2024 edition; read November 19, 2026 - Code of Federal Regulations, 19 CFR 162.74
Data cited: prior disclosure made before, or without knowledge of, the commencement of a formal investigation, with a tender of the actual loss of duties
Source: 19 CFR 162.74, eCFR
Published: eCFR current through November 17, 2026; read November 19, 2026 - Code of Federal Regulations, 19 CFR 159.11
Data cited: an entry not liquidated within one year from the date of entry is deemed liquidated by operation of law
Source: 19 CFR 159.11, eCFR
Published: eCFR current through November 17, 2026; read November 19, 2026 - United States Code, 19 U.S.C. 1592
Data cited: 1592(c)(3), maximum penalty for negligence; 1592(c)(4)(B), prior disclosure of negligence limited to interest on the unpaid duties when tendered
Source: 19 U.S.C. 1592, govinfo
Published: U.S. Code, 2024 edition; read November 19, 2026 - United States Code, 19 U.S.C. 1621
Data cited: five-year limit for actions under section 1592, from the date of the alleged violation, or from discovery where the violation arises from fraud
Source: 19 U.S.C. 1621, govinfo
Published: U.S. Code, 2024 edition; read November 19, 2026 - United States Code, 19 U.S.C. 1484
Data cited: 1484(a)(1), importer of record, using reasonable care, files the declared value, classification and rate of duty
Source: 19 U.S.C. 1484, govinfo
Published: U.S. Code, 2024 edition; read November 19, 2026 - Supreme Court of the United States, United States v. Citroen, 223 U.S. 407 (1912)
Data cited: classification is ascertained from the imported article in the condition in which it is imported; an article does not become dutiable under a description because it was made to be imported at a lower rate
Source: 223 U.S. 407, Library of Congress
Published: 1912; read November 19, 2026 - U.S. International Trade Commission, HTS release list
Data cited: 2026 Revision 23 released November 10, 2026; the 2025 edition ended at Revision 32
Source: HTS releases, USITC
Published: read November 19, 2026
Questions people ask
Do HTS codes change based on country of origin when a part moves from China to Vietnam?
No. GRI 1 sets the code by the terms of the headings and the section and chapter notes, and for brackets, housings and harnesses none of those terms turn on origin. The move changes the duty: the rate column and Chapter 99 lines such as Section 301. If 200 parts a quarter leave China, recheck origin and duty, not codes. GingerOS shows each affected part's new duty and next step, which a lookup by code alone does not show.
Can an HS code be changed when we switch suppliers but the part is identical?
If the part is truly identical, the code stays, because classification follows the goods, not the seller. The risk is the word identical: a re-sourced bracket often meets the drawing with a different alloy grade, coating or resin. If procurement moves 200 parts a quarter, compare each new spec sheet with the facts the code rests on. GingerOS records the reasoning behind each code, so there is something to compare against; a bare code field gives you nothing.
Engineering just released an ECO on an imported part: when is HTS reclassification required?
When the ECO changes a fact the current code rests on: the material of a part classified by material, a function or component that moves an assembly to another heading, a feature a subheading names, or what a ruling describes. Tolerance, color or packaging changes rarely move it. If engineering releases 40 ECOs a month across 14,000 parts, a yearly review finds them months late; GingerOS watches changes in your PLM and alerts you when one affects a part.
Engineering wants to swap a steel bracket to aluminum or change a resin grade: does the material change move the HTS code?
Often, when the part is classified by material. A steel bracket under 7326.90.86 (2.9% in HTS 2026 Revision 23) becomes an aluminum one under 7616.99.51 (2.5%); with 3,000 Chapter 73 parts, each swap is a code review. A new resin grade in a plastic article usually stays in 3926, whose subheadings sort by article, not polymer. GingerOS asks for missing material facts before it suggests a code; a lookup on the old description returns the steel heading.
We redesigned a steel bracket in aluminum: can we legally change its HS classification for lower duties?
Yes, when the product changes and the new code describes the goods as imported. The Supreme Court held in United States v. Citroen (1912) that an article is not dutiable under a description it does not meet just because it was made to be imported at a lower rate. If engineering moves 30 steel brackets from 7326 (2.9%) to aluminum under 7616 (2.5%), GingerOS records the reasoning; a code edited in the ERP carries none. GingerControl identifies and documents the opportunity; your licensed broker or counsel files.
We re-sourced a part to a new supplier: can you rely on the HTS code on its invoice?
No, not on its own. Under 19 U.S.C. 1484 you, as importer of record, must use reasonable care to declare the classification, and a supplier's code may come from its own country's tariff schedule rather than the U.S. HTS. For 200 re-sourced parts a quarter, treat each supplier code as a hint. GingerOS asks for missing product facts before it suggests an HTS code and records the reasoning for your approval, which an invoice code never carries.
Engineering switched our ruled steel housing to aluminum: is the CBP binding ruling still valid?
Not for the changed part. Under 19 CFR 177.9(b)(2), a classification ruling applies only to articles identical to the sample or to the description in the ruling. A ruling that describes a steel housing does not cover its aluminum replacement. If 40 of your 14,000 parts rest on rulings, keep each ruling number with its part; GingerOS watches changes in your PLM and alerts you when one affects a part, which a part-number check misses.
Which entries are wrong if we find a material change after entries were filed with the old code?
Only the changed part's entries, since goods are classified in the condition in which they are imported. Date it by the first changed entry, not the ECO. A post summary correction can be filed within 300 days of entry or up to 15 days before scheduled liquidation, whichever is earlier. At 60 entries a month, GingerOS checks each entry's HTS code, origin and value; a part-number search also pulls old-version entries. GingerControl identifies and documents the opportunity; your licensed broker or counsel files.
We run 14,000 active part numbers: how often do HTS codes change, and how often should we recheck them?
Many times a year: the 2026 HTS reached Revision 23 on November 10, 2026, and the 2025 edition ran to Revision 32. For 14,000 part numbers the faster clock is internal: supplier switches, ECOs and new plants. Recheck on each of those events and keep the annual review as the sweep. GingerOS watches your ERP, PLM and supplier records for those events; an annual review finds an internal change only when it runs, often months late.
Our ECOs and supplier switches reach compliance late: what HS code change notification catches them, not just tariff updates?
A tariff alert that watches the schedule and new notices catches outside changes only. Catching your own needs a trigger where changes happen: the PLM for ECOs, the ERP or supplier master for new vendors and origins. For a two-person team covering 14,000 part numbers, that trigger is the practical way to see each change. GingerOS watches ERP, PLM and supplier records, alerts you when a change affects a part, and records each code's reasoning for approval.
Classifying SKUs one ruling at a time?
Hand this to GingerOS.
Pick a 30-minute slot on the next page with Chen Cui, our CEO. Bring one notice or one SKU list (an ERP export, a spreadsheet or an email will do) and see what GingerOS does with it.
Reviewed by Michael Weick, LCB / CCS




