Semiconductor Tariffs in 2026: Landed-Cost and RFQ Controls

Table of Contents

• Separate Effective Rules From Policy Risk
• Understand the Narrow 2026 Section 232 Action
• Collect Product Facts Before Requesting a Duty Rate
• Do Not Confuse Brand, Ship-From, and Country of Origin
• Put Tariff Responsibility Into the RFQ and PO
• Model Landed Cost as Scenarios
• Preserve an Entry Evidence Package
• Monitor Rules at Defined Triggers

Semiconductor tariff planning in 2026 requires two separate facts: what is effective now, and what policymakers may do next. Mixing those facts creates opposite errors. A buyer may add 25% to every chip and reject a workable quote, or ignore an applicable Chapter 99 measure because the base integrated-circuit duty appears low.

As of September 5, 2026, the clearest effective semiconductor-specific U.S. action is the January Section 232 proclamation covering a narrow group of advanced computing chips and derivative products. The same proclamation contemplates broader negotiations and possible later measures. On August 27, Reuters reported that another round was being considered. A reported proposal is a budget scenario, not an entry instruction.

This article is a procurement-control guide, not legal advice or a tariff determination. The current Harmonized Tariff Schedule of the United States (HTSUS), Federal Register notices, U.S. Customs and Border Protection guidance, transaction facts, and qualified customs advice control the actual entry.

Separate Effective Rules From Policy Risk

The January 2026 Federal Register proclamation imposed a 25% ad valorem duty on covered advanced computing chips and certain derivative products, effective for covered goods entered for consumption or withdrawn from warehouse on or after January 15, 2026. It added HTSUS heading 9903.79.01 and related exception headings.

The action did not state that every diode, analog IC, MCU, memory device, FPGA, or finished electronics assembly is subject to a universal 25% semiconductor tariff. Coverage depends on the Annex, product classification, entry facts, and any applicable end-use provision.

The proclamation also directed continued negotiations and stated that broader semiconductor tariffs could be considered. That second phase should be monitored, but procurement should label it as policy exposure until an operative document defines products, rates, dates, exceptions, and filing instructions.

A tariff tracker should therefore use at least three statuses:

• Effective: published measure with applicable date and entry instructions;
• Announced but not yet effective: final action with a future date or pending implementation detail;
• Proposed or reported: scenario for budgeting and contract protection, not a rate to declare.

Keep a link and retrieval date for every status. Headlines alone do not show the exact HTS scope or exception mechanics.

Understand the Narrow 2026 Section 232 Action

The January proclamation describes a two-phase approach. Its first immediate tariff applies to certain advanced computing chips and derivative products listed in the Annex when the import does not contribute to specified U.S. technology-supply-chain and manufacturing purposes.

The document lists exceptions for covered products used in U.S. data centers, U.S. repairs or replacements, U.S. research and development, startups, non-data-center consumer applications, non-data-center civil industrial applications, public-sector applications, and other uses determined by the Secretary of Commerce to strengthen the U.S. technology supply chain or domestic manufacturing capacity for semiconductor derivatives.

An exception is not a phrase to add casually to an invoice. Procurement and compliance teams need to identify the exact heading and evidence required for the entry. The proclamation authorizes administrative measures such as HTSUS modifications and end-use certifications. Check current implementation before shipment.

The 25% duty is also only one layer of the customs analysis. The Annex explains interactions with other Chapter 99 measures, antidumping or countervailing duties, and other charges. Do not add every headline rate together without reading the non-stacking rules and applicable notes.

Collect Product Facts Before Requesting a Duty Rate

A supplier cannot responsibly answer “tariff included?” without knowing the product and transaction. The RFQ should collect:

Data field	Procurement reason
Complete manufacturer part number	Connects the quote to controlled technical data
Detailed article description	Supports classification beyond a generic “IC” label
Proposed HTS and Chapter 99 headings	Makes the duty assumption visible
Legal country of origin and basis	Determines origin-dependent treatment
Wafer diffusion, assembly, and test sites	Supports—but does not alone decide—origin review
Seller, ship-from, and entry country	Clarifies logistics without confusing them with origin
Intended end use and end user	May affect a listed exception or other compliance rule
Customs value elements	Supports the duty calculation
Entry date and port	Anchors the version of the rule and implementation
Importer of record	Assigns filing and reasonable-care responsibility

The CBP HTS overview explains that the U.S. International Trade Commission publishes the HTS while CBP administers, interprets, and enforces it. A supplier’s suggested classification can help, but it does not transfer the importer’s responsibility.

For a material classification or origin uncertainty, CBP maintains an advance binding ruling process. That process requires detailed facts and should be planned before the shipment is at the border.

Do Not Confuse Brand, Ship-From, and Country of Origin

Semiconductor supply chains split wafer fabrication, probe, assembly, final test, programming, warehousing, and sale across jurisdictions. The manufacturer’s headquarters country is a corporate fact. Country of diffusion and country of assembly are manufacturing facts. Ship-from country is a logistics fact. Legal country of origin is a customs conclusion under the applicable rule.

A distributor label may list several of these facts. Procurement should preserve them rather than choosing the country that produces the lowest modeled duty. When a supplier changes the assembly/test site or ships a different lot, the origin analysis may need to be reviewed.

Request a written origin statement and the basis used. For a critical or unusual product, involve a customs broker or trade counsel and retain the supporting manufacturing description. Do not assume that repacking, programming, or distribution changes origin, and do not assume it never can; the applicable rule depends on what was done and where.

The same discipline helps with export controls, but import duty and export authorization are separate analyses. Use the site’s semiconductor export-controls guide for destination and licensing questions rather than treating an HTS result as an export classification.

Put Tariff Responsibility Into the RFQ and PO

The commercial agreement should answer who quotes, pays, files, and bears changes. State the Incoterm and named place, importer of record, included duties and fees, validity period, customs-value basis, and treatment of post-quote tariff changes.

Ask the supplier to separate:

1. component price;
2. freight and insurance;
3. ordinary duty;
4. Section 232 or Section 301 duty;
5. brokerage and entry fees;
6. testing, programming, or value-added services;
7. sales, use, or value-added taxes where applicable.

“Duty paid” without an Incoterm, entry country, importer, and supporting document is not a comparable quote. Likewise, “tariffs excluded” leaves procurement unable to approve the final cost unless the buyer has a controlled estimate.

For NCNR or long-lead orders, define whether a new tariff can be passed through and what evidence the seller must provide. Tie any adjustment to the affected quantity and actual entry, not a blanket surcharge. The companion electronic component RFQ comparison guide provides a broader structure for normalizing price and contract fields.

Model Landed Cost as Scenarios

A landed-cost model should have a confirmed base case and named policy scenarios. It should not present a rumored rate as a forecast with false precision.

Landed cost = merchandise value + freight + insurance + ordinary duty + applicable trade-remedy duty + brokerage/entry fees + compliance and handling costs

Apply the rate to the correct customs value under professional guidance. Then test changes in origin, entry date, product classification, seller route, and end-use treatment. A scenario table might use:

Scenario	Status	Procurement use
Current confirmed treatment	Effective rules and documented facts	PO approval and accrual
Supplier or origin changes	Known alternate route	Quote comparison and change control
Broader tariff announced but not effective	Final notice with future date	Shipment timing and contract review
Policy proposal or press report	Not operative	Budget sensitivity only

The business decision can include schedule and continuity. A domestic-stock offer with a higher unit price may reduce import timing risk, but procurement still needs proof of ownership, location, duty-paid status, and transfer terms.

Preserve an Entry Evidence Package

Link the customs package to the exact purchase-order and lot identifiers. Retain the RFQ, quote, PO, commercial invoice, packing list, airway bill or bill of lading, entry summary, HTS analysis, Chapter 99 analysis, origin statement, manufacturing-route evidence, end-use documentation, and approvals for changes.

Reconcile quantities and values across records. If a shipment contains multiple parts or origins, maintain line-level data rather than applying one description to the entire shipment. Keep the version of the HTS and Federal Register notice used for the decision.

For high-risk entries, establish a pre-shipment review gate. The broker should receive enough technical detail to classify the article, while engineering and the supplier should answer factual questions about function and manufacturing. Procurement should not rewrite a technical description merely to fit a preferred code.

Monitor Rules at Defined Triggers

Review tariff exposure when the RFQ is issued, before order acceptance, when the supplier or manufacturing route changes, before shipment, and before entry if a policy update occurred. Assign an owner to monitor the Federal Register, the current USITC HTS, and relevant CBP trade-remedy guidance.

A market-news alert can prompt the review; it should not update the ERP duty rate by itself. Record the effective document, entry date, affected HTS lines, exception or exclusion, and responsible approver before changing purchasing assumptions.

Geopolitical and export-policy developments may affect the same supply route through different mechanisms. Keep a separate watchlist using the mid-2026 semiconductor geopolitics analysis so the tariff file remains auditable.