USTR amends four China 301 exclusions to match 1 July HTS revisions

The Analysis

USTR has amended four Section 301 China product exclusions, covering pump parts under 8413.91.x and plastics under 3926.90.x, to align with the statistical HTS revisions that took effect on 1 July. The change is retroactive to 12:01 a.m. on 1 July and is procedural on its face: it adds no new excluded products and leaves 301 duty rates unchanged. CBP is expected to publish matching entry guidance.

The practical exposure is not the tariff rate. It is the gap between the code you declared and the code USTR now treats as correct for the same goods, a gap that surfaces as a request for information, a post-summary correction, or a reclassification with duty and interest attached. With only four exclusions in scope, most importers will find they are outside them. The work is to prove that in writing, quickly, and to fix the contracts that decide who pays when a classification moves.

The advice below is for five roles. It separates the checks that belong in the next 30 days from the contract and data work that can run through the fourth quarter.

For Exporters

• By 30 September, list every US consignment since 1 July in 8413.91.x and 3926.90.x with declared code, entry date, value and buyer, and ask each buyer to confirm the 10-digit code declared.
• By 10 October, issue corrected invoices wherever your invoice code and the entry code differ, and have the broker file before liquidation.
• By 31 October, add a standing contract clause making the buyer responsible for HTS classification and any retroactive code change at US Customs.
• By 30 November, re-verify origin evidence for both families, since a code change draws closer scrutiny to origin.
• Budget the hold explicitly: five days at USD 180 plus 8% financing is about USD 1,083 on a USD 166,667 consignment, or 0.65% of value.
• Never issue a corrected invoice without notifying the broker; two versions of one shipment is the fastest route to an audit.

The amendment touches pump parts under 8413.91.x and plastics under 3926.90.x, retroactive to 12:01 a.m. on 1 July. If you export either family, your first question is not whether you benefit from an exclusion, because most likely you do not; it is who owns the classification risk on the US side. Under FOB and CIF that risk sits with your buyer, and the buyer will price it back into the next order. Under DDP it sits with you. Either way, the documents that settle the argument are the invoice and the shipping bill: they must show the code your buyer will declare, and the origin evidence must support it.

Assume you are a pump-parts exporter shipping 12 consignments a year with a declared value of USD 2 million, four of them between 1 July and 10 September. If two of those consignments were declared under a superseded statistical code, the buyer's broker will raise a post-summary correction. At 1.5 hours of broker time per entry at USD 85 an hour, that is USD 128 per consignment, or USD 256 for the two. More importantly, a correction filed after liquidation can carry duty and interest, and a held entry adds storage. Assume a five-day hold at USD 180 a day on a consignment of USD 166,667, plus about USD 183 of financing cost at 8% a year: roughly USD 1,083 per held consignment, or 0.65% of its value, lost on a change that altered no duty rate.

Sequence the review. By 30 September, pull every US-bound consignment shipped since 1 July in the two families and list declared code, entry date, value and buyer, then send each buyer one line asking them to confirm the 10-digit code they declared. By 10 October, wherever your commercial invoice shows a code that differs from the buyer's entry, issue a corrected invoice set and ask the broker to file before liquidation. By 31 October, add a standing clause to your sales contract: HTS classification is the buyer's responsibility, any retroactive code change at US Customs is at the buyer's account, and the code to be declared is stated on the invoice. By 30 November, re-verify origin evidence for both families, because a code change usually brings a closer look at origin.

The alternatives and the traps. You can move to DDP and control the filing yourself, which gives you visibility and usually supports a higher quoted price, but it puts the retroactive exposure on your books. You can route affected SKUs through a different US gateway or an FTZ, which shifts timing rather than removing the issue, and FTZ admission carries its own documentation. Or you can accept the buyer's classification and rely on the contract to allocate it. The traps: assuming that because no products were added there is nothing to do; treating the 1 July retroactive date as a filing-only matter when it also reaches consignments already released; and issuing a corrected invoice without informing the broker, which leaves two versions of the same shipment in the record.

For Cross-Border E-commerce

• By 26 September, export US entry history from 1 July onward and filter for 8413.91.x and 3926.90.x; hand any hits to the broker the same week.
• By 5 October, split matched SKUs into excluded and amended (correct the filing), out of scope (document why), and unclear (seek a binding ruling or written broker opinion).
• By 20 October, add a per-unit re-clearance allowance and a five-day timing assumption to the landed-cost model for every code change.
• Budget two corrections and one five-day hold at about USD 2,166, including USD 1,083 per held consignment, on 12 consignments averaging USD 166,667.
• Screen by code, not SKU count: a superseded plastics code on 60,000 units a year at USD 0.03 re-clearance is USD 1,800, more than a 1.5% margin on that SKU.
• By 15 November, move the classification review to a quarterly calendar rather than a one-off exercise.

For an importer of small-value goods, four amended exclusions sound irrelevant, and for most catalogues they are. The two families in scope, pump parts 8413.91.x and plastics 3926.90.x, are component-level codes, so they matter only if you import spare parts, hardware accessories or plastic fittings for kits and aftermarket sales. The material point is the retroactive date of 12:01 a.m. on 1 July, which reaches consignments you have already sold and in some cases already reconciled into margin. The duty rate did not move; the code did, and a code error on a released entry is a post-clearance cost.

Assume 12 US-bound consignments in the two families across the year at an average declared value of USD 166,667, with two of them between 1 July and 10 September filed under a superseded code. A post-summary correction at 1.5 broker hours and USD 85 an hour costs USD 128 per consignment; a five-day hold at USD 180 a day adds USD 900 plus about USD 183 of financing at 8% a year, so roughly USD 1,083 per held consignment. On two consignments that is about USD 2,166. Now check the catalogue arithmetic: if a superseded plastics code sits on your top-selling accessory at 60,000 units a year with a landed cost of USD 1.80, and the corrected code forces a re-clearance fee of USD 0.03 per unit, the annual cost is USD 1,800, enough to wipe out a 1.5% margin on that SKU. Screen by code, not by SKU count.

Get it done in one pass. By 26 September, export your US entry history from 1 July onward, filter for the two families, and hand any hits to the broker that same week. By 5 October, split the matched SKUs into three groups: excluded and amended, where you correct the filing; out of scope, where you document why and keep the evidence; and unclear, where you request a binding ruling or a written broker opinion rather than guess. By 20 October, update the landed-cost model so every code change carries a per-unit re-clearance allowance and a five-day timing assumption. By 15 November, put the review on a quarterly calendar, because statistical revisions run on their own schedule, not on your planning cycle.

The alternatives and the traps. You can consolidate those SKUs with one supplier and one broker to make future code checks cheaper; you can move low-value accessories to a de minimis-compatible channel if the rules allow, which changes the compliance path entirely; or you can stop importing the marginal SKUs and buy locally at a higher unit cost with no classification exposure. The traps: assuming a component-level amendment cannot touch your catalogue, which is true only if you check; letting the broker own classification by default and finding the error at audit; and absorbing correction cost into product cost without telling the category owner, so the same SKU ships on the same wrong code next quarter.

For Manufacturing Plants

• By 30 September, pull the part numbers in both families out of the ERP and list every HTS code recorded against them for the last two quarters; two codes on one part number is a flag.
• By 10 October, reconcile one code per part number with brokers and suppliers, and record the source and decision date in the item master.
• By 31 October, reissue inbound documentation templates with the corrected code and a mandatory origin field, and reject receipts carrying only a commercial description.
• By 30 November, audit 20 receipts per family against the new template and require 100% compliance before the next purchase order cycle.
• Budget the fix: mislabelled receipts at 5% of 8,000 monthly units cost about USD 14,580 a year, which is 3.6% of the USD 403,200 annual spend on that part.
• Hold a 10-day buffer on affected parts during the correction window rather than risk a line stop.

If you buy 8413.91.x pump parts or 3926.90.x plastic components as inputs, the amendment changes the paper trail at both ends of the shipment: the code you receive goods under and the code your customer receives goods under. The retroactive date of 1 July means your Q3 inbound documentation may already reference a superseded statistical code, and your bills of material and cost cards inherit it. Duty rates are unchanged, so nothing shows up in price. The exposure is a correction, a hold, or a customs review of the same part number filed two different ways inside one year.

Assume you consume 8,000 pump-part units a month at USD 4.20 landed, and a quarterly internal audit finds 5% of receipts carrying the superseded code. That is 400 units a month mislabelled in your system. Cost it properly: re-clearance at USD 0.03 per unit is USD 12 a month, which is trivial; the real number is 1.5 hours of paperwork per affected receipt at USD 85 an hour, which across six receipts a month is USD 765, or USD 9,180 a year. Add a five-day hold on those six receipts at USD 180 a day and you add USD 5,400. Combined, roughly USD 14,580 a year, which is 3.6% of the USD 403,200 you spend on that part annually at 8,000 units a month and USD 4.20 landed. This is a master-data problem with a duty-shaped bill.

Fix the master data. By 30 September, pull the part numbers in both families out of the ERP and list every HTS code recorded against them over the last two quarters; any part number carrying two codes is a flag. By 10 October, reconcile one code per part number with your brokers and suppliers, and record the source and the date of that decision in the item master so it cannot drift back. By 31 October, reissue inbound documentation templates with the corrected code and a mandatory origin field, and stop accepting receipts that carry only a commercial description. By 30 November, audit 20 receipts per family against the new template and require 100% compliance before the next purchase order cycle.

The alternatives and the traps. You can pass classification duty to a broker with a written service standard, or bring it in-house for the two families only, which is cheaper than it sounds when the code set is small. You can hold a 10-day buffer on the affected parts through the correction window rather than risk a line stop, which costs carrying but not output. The traps: assuming your supplier's invoice code is right because it was right last year; fixing the ERP item master without fixing the receiving template, so the same error re-enters at the dock; and treating the amendment as an importer-only problem when your own export documentation and your customer's entry both cite the same part number.

For Brand Owners

• By 30 September, obtain a one-page written statement from every supplier and broker on which codes they use for the amended families and when they last verified them.
• By 15 October, merge the answers into a single brand-level code list and require any change to reach you before it is used on an entry.
• By 31 October, add a change-of-classification clause to supplier terms putting the notification duty and any retroactive assessment on whoever changed the code silently.
• By 15 December, add a classification-change line to the landed-cost model so corrections stop arriving as unbudgeted surprises.
• Weigh cost against exposure: three affected consignments cost about USD 3,633, which is 6.1% of the USD 60,000 net margin on a USD 4 million product line.
• Do not restructure a product line over four exclusions; escalate only where the code count is high.

For a brand, an amendment covering four exclusions and two HTS families is a reminder that classification is a margin input rather than a filing detail. The change is procedural, with no new exclusions and no rate move, and it is retroactive to 1 July. The reason to act is that your product cost, your duty drawback or refund position and your landed-cost model all run off HTS codes maintained by suppliers and brokers, and a statistical revision in July means that model has been running on a stale key for two months.

Assume a product line with USD 4 million of annual US-bound sales at a 1.5% net margin and USD 2.4 million of landed cost, of which USD 200,000 sits in the two amended families. If corrections and holds touch 5% of that balance, meaning USD 10,000 of goods, and each affected consignment carries USD 1,083 of hold and financing cost plus USD 128 of broker time, three consignments cost about USD 3,633. That is 0.09% of the product line's revenue and 6.1% of its USD 60,000 net margin. Small in absolute terms, but unbudgeted, and it repeats every time a statistical revision lands. Set the review cost against the size of the exposure, and escalate only when the code count is high.

Own the code list, not the filing. By 30 September, ask each supplier and each broker for a written statement of which codes they use for the amended families and when they last verified them, one page per party. By 15 October, reconcile the answers into a single brand-level code list, and require any change to come to you before it is used on an entry. By 31 October, add a change-of-classification clause to supplier terms that places the notification duty and any retroactive assessment on whoever changed the code without telling you. By 15 December, have finance add a classification-change line to the landed-cost model so that corrections stop arriving as unbudgeted surprises.

The alternatives and the traps. You can centralise classification with one broker across all lanes, which costs flexibility but ends the argument about whose code is right. You can keep the current split and rely on quarterly reconciliation, which is cheaper but slower. Or you can absorb the cost and raise the SKU price slightly, which is defensible only if the exposure is recurring. The traps: reading the phrase adds no new products and leaves 301 rates unchanged as nothing to do; letting a supplier's code change propagate into your own documentation without notification; and using a product-line average to decide whether to act, when the exposure is concentrated in one or two SKUs.

For Procurement Teams

• By 30 September, list every live contract covering 8413.91.x and 3926.90.x and mark who owns classification and who bears retroactive assessment; a blank is a finding.
• By 15 October, issue a contract amendment for the blanks: classification owner, a 15-day notification duty, retroactive cost allocation, and the required document set.
• By 31 October, require each supplier to state in writing the code it will use from the next shipment, and hold the next purchase order until the answer arrives.
• By 15 December, build a two-year HTS revision calendar into the supplier review rhythm so the next statistical update is planned for rather than discovered.
• At USD 2 million of annual spend, one correction plus one five-day hold is about USD 1,339; a notification clause is worth that per event and far more if a full reclassification follows.
• Do not accept a supplier assurance that its code is current without the verification date in writing.

Four amended exclusions, retroactive to 12:01 a.m. on 1 July, no new products and no rate change: on paper this is housekeeping. For procurement it is a contract test. The question is whether your purchase and logistics agreements say who pays when a classification changes after the goods have been entered, and for most companies the answer is a silence that gets filled in during a dispute. The two families in scope, pump parts 8413.91.x and plastics 3926.90.x, are exactly the kind of component-level purchases where the supplier controls classification and passes you the consequence.

Assume USD 2 million a year of spend in the two families delivered DDP across 12 consignments, four of them since 1 July. Suppose two consignments need post-summary correction and one is held for five days: broker time of USD 128 per consignment plus USD 1,083 of hold and financing on the held one gives about USD 1,339 of cost from a code change that altered no duty rate. Put a number on the negotiation instead. A clause requiring the supplier to notify you of any classification change 15 days before the shipping date, with the supplier bearing retroactive assessments where notice was not given, is worth roughly USD 1,339 per event at this volume, and materially more if a full reclassification follows, because that is not a correction but a duty claim across past entries.

Do it in four moves. By 30 September, list every live contract covering the two families and mark who owns classification and who bears retroactive assessment; a blank is a finding. By 15 October, send a contract amendment for the blanks covering the classification owner, a 15-day notification duty, retroactive cost allocation, and the required document set of invoice code, entry code and origin evidence. By 31 October, require every supplier to state in writing the code it will use from the next shipment, and hold the next purchase order until that answer arrives. By 15 December, build a two-year HTS revision calendar into your supplier review rhythm so the next statistical update is planned for rather than discovered.

The alternatives and the traps. You can consolidate the two families with one supplier that carries the classification risk, and pay a premium for the quiet life. You can keep multiple suppliers and reconcile quarterly, accepting slower detection. Or you can move to a landed-cost contract where classification disappears because the supplier owns the border, which is efficient but hides your exposure until renewal. The traps: assuming a procedural amendment needs no contract work; accepting a supplier's assurance that its code is current without asking for the verification date; and leaving the responsibility question unanswered because the amounts are small today. The amounts are small until the day they are not.

↑ Back to the key points