Country of Diffusion: Semiconductor Tariffs and the Trade Compliance Data Gap
A chip can be designed in one country, built from a wafer fabricated in a second, and assembled and tested in a third. Here is what that means for tariff exposure, and for the systems that track it.
For years, many supply chain systems could get away with tracking the last major manufacturing step. Semiconductor trade is making that assumption harder to defend.
The data point now showing up in trade conversations is Country of Diffusion (COD): the country where the wafer used in a semiconductor was fabricated. Industry documentation already treats COD as distinct from Country of Assembly (COA) and Country of Origin (COO). Texas Instruments, for example, defines chip country of origin as the country where wafer fabrication occurs and notes that it is sometimes referred to as Country of Diffusion.
That distinction matters because a finished semiconductor can carry several geographic identities across its manufacturing journey, and tariff exposure may depend on which one a particular customs regime uses.
For supply chain and trade compliance teams, the implication is simple: if your systems only know where a semiconductor was finally assembled, they may not hold the data needed to evaluate every applicable tariff rule. That turns country of diffusion into a semiconductor data architecture problem, not just a customs question.
What Is Country of Diffusion in Semiconductors?
In semiconductor manufacturing, diffusion is the front-end process where impurities are introduced into a silicon wafer to change its electrical properties. The country where this wafer fabrication happens is the country of diffusion.
Suppliers already record these steps separately. Published part data for Microchip components, for example, lists country of fabrication, country of assembly and country of origin as separate fields alongside the HTS code. Customs paperwork does the same: in CBP ruling W968421, commercial invoices for imported semiconductors denoted the country of diffusion and the country of origin, tied to the wafer lot number.
Country of Diffusion vs Country of Origin vs Country of Assembly
The three terms answer three different questions, which is why they should never be collapsed into one generic "country" field.
How Country of Diffusion Affects Semiconductor Tariffs
Recent trade developments have made COD more than a terminology exercise.
Why Semiconductor BOMs Need Deeper Traceability
A conventional bill of materials tells an ERP which components belong inside a product. That works for manufacturing. It is often insufficient for semiconductor tariff compliance.
A processor might appear as one line item in a finished product's BOM, but that processor has its own manufacturing history. Compliance teams may need its part number, wafer fabrication location, assembly location, supplier, HTS classification, and how all of these relate to the finished product.
This is where BOM digitization becomes more than a procurement exercise. The BOM needs to become a structured compliance data model with BOM traceability below the finished part:
Without that structure, BOM tariff classification depends on spreadsheets, supplier emails and manual lookups. That does not scale, especially when one component appears across dozens of products.
Semiconductor Tariff Classification Needs Live Supply Chain Data
A compliance system cannot calculate tariff exposure accurately if its underlying data is stale. In semiconductor supply chains, change is constant:
Those answers cannot depend on someone manually reconciling five systems every time trade rules move.
Building an Audit Trail for Automated Tariff Classification
Automated tariff classification does not mean letting software make unexplained customs decisions. The strongest setups use automation and AI to surface suggestions, flag changes and assemble evidence, while trade compliance specialists review and own the final call.
A defensible tariff engineering workflow should retain the evidence behind each classification or exposure assessment:
The result is an explainable compliance record, which matters most when the same component appears across multiple products or jurisdictions.
How APIs Connect ERP, PLM, Supplier and Compliance Data
Most enterprises already hold much of the necessary information. The problem is that it is scattered:
The architecture should also preserve source provenance. If a COD value changes, the system should know where that information came from and when it became effective. This is the same principle behind industry efforts such as Catena-X supply chain data sharing: shared, structured data beats disconnected records.
Why Legacy ERP Models Lose Semiconductor Origin Data
The challenge is especially visible in semiconductors because manufacturing is distributed by design. Wafer fabrication, assembly, testing, packaging and distribution can involve different facilities and countries.
If a supplier provides three distinct geographic attributes but the internal ERP stores one generic origin field, information is being lost somewhere between procurement and compliance. Once lost, it is expensive to reconstruct.
What a Trade Compliance Dashboard Should Show
A trade compliance dashboard should not become another spreadsheet with better colors. Its purpose is decision support, with different views of the same underlying data:
How to Track Country of Diffusion: A Practical Roadmap
The practical roadmap is not "replace the ERP." It is to build the missing semiconductor supply chain data layer around it, guided by a clear data strategy:
This architecture lets tariff analysis respond when the supply chain changes, instead of waiting for a compliance team to discover the change manually.
How Seaflux Builds Semiconductor Trade Compliance Data Architecture
Off-the-shelf tariff classification software handles HTS lookups well, but few tools are built around your BOM structure, your supplier feeds and your ERP. That gap is where Seaflux works.
The Tariff Risk Is Moving Deeper Into the Product
Country of diffusion does not eliminate country of origin. It adds another data point that may become decisive under particular trade regimes.
The compliance challenge is no longer simply knowing where the finished semiconductor was assembled. It is knowing enough about the component's manufacturing chain to determine which geographic attribute matters for the rule being applied.
For supply chain CTOs and trade compliance leaders, that makes COD tracking an infrastructure requirement wherever the applicable tariff regime requires or uses it. The companies prepared for that environment will have something more valuable than a larger compliance spreadsheet: a traceable product data model that connects the BOM, semiconductor manufacturing footprint, tariff rules and shipment activity in one system.
Frequently Asked Questions (FAQ): Get the Answers You Need
What is country of diffusion in semiconductors?
Country of diffusion (COD) is the country where the silicon wafer used in a semiconductor was fabricated. Diffusion refers to the front-end process that introduces impurities into the wafer to set its electrical properties. Some suppliers also call it chip country of origin.
What is the difference between country of diffusion and country of origin?
Country of origin is a legal designation that depends on the customs regime and purpose, generally tied to where a product was produced or substantially transformed. Country of diffusion is a manufacturing attribute that records where the wafer was fabricated. Some regimes may use COD to determine origin for semiconductors, so both should be stored separately.
How does country of diffusion affect semiconductor tariffs?
When a customs authority uses wafer fabrication location to determine semiconductor origin, the applicable tariff can change even if assembly happened elsewhere. China moved toward this approach in 2025, and there have been reports of COD being considered in U.S. enforcement, without an officially confirmed federal policy change.
How do you track country of diffusion in an ERP system?
Start by adding COO, COA and COD as separate attributes on semiconductor component records rather than using one origin field. Then link those components to the BOMs of finished products, feed supplier manufacturing-site updates through APIs, and keep the source and effective date for every value.
What is BOM to HTS code mapping?
BOM to HTS code mapping links each component in a bill of materials to its Harmonized Tariff Schedule classification. Combined with origin attributes such as COD, it allows teams to calculate tariff exposure at the component level instead of estimating it at the shipment level.
Can trade compliance software automate tariff classification?
Trade compliance software can automate parts of tariff classification, such as suggesting HTS codes, flagging rule changes and assembling evidence. The most defensible approach keeps a full audit trail and leaves final classification decisions with trade compliance specialists.
How do you calculate tariff exposure on a BOM?
Identify each component, its HTS classification and the origin attribute the relevant customs regime uses, then apply the current duty rules for that combination. Rolling those results up through the BOM shows exposure per product, supplier and shipment.

Krunal Bhimani
Business Development Executive