Country of Diffusion: Semiconductor Tariffs and the Trade Compliance Data Gap

COD
Wafer fabricated
Country A
COA
Assembled and tested
Country B
COO
Finished part ships
Country C
Which country does the tariff rule use?

One semiconductor, three geographic identities. The legal origin depends on the regime.

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.

COD
Country of Diffusion

The country where the silicon wafer used in a semiconductor was fabricated.

Some suppliers also call it chip country of origin.

A typical manufacturing path can look like this:

1
Country A
The wafer is fabricated
COD
2
Country B
The die is assembled, packaged, or tested
COA
3
Country C
The finished component ships
Ship-from

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.

The information exists. The question is whether your systems keep it.

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.

COO
Country of Origin
Which origin does this customs authority recognize?
COA
Country of Assembly
Where was the chip assembled and tested?
COD
Country of Diffusion
Where was the silicon made?
Field
What It Records
Question It Answers
COO (Country of Origin)
Legal origin under the applicable regime, generally where the product was produced or underwent substantial transformation
Which origin does this customs authority recognize?
COA (Country of Assembly)
Where packaging and final assembly occur
Where was the chip assembled and tested?
COD (Country of Diffusion)
Where the semiconductor wafer was fabricated
Where was the silicon made?

Even supplier definitions differ:

Supplier knowledge base
Infineon

Describes country of origin as the country where the product is assembled.

VS
Manufacturing terminology
Texas Instruments

Describes COO as a legal concept that varies by country and purpose.

That inconsistency is exactly why compliance data models must store each attribute separately and apply the right one per rule.

The important nuance

Country of diffusion is not simply a new definition of country of origin. It is a distinct semiconductor manufacturing attribute that may become decisive for origin and tariff analysis under particular trade regimes.

How Country of Diffusion Affects Semiconductor Tariffs

Recent trade developments have made COD more than a terminology exercise.

April 2025
China moved to wafer fabrication location

China's customs authority shifted semiconductor origin determination away from the assembly, test and packaging location and toward the country where the wafer was fabricated, according to Z2Data's analysis.

Emerging
U.S. enforcement signals are emerging

The same analysis reports anecdotal cases of customs officials using COD to determine tariff rates on imported semiconductors, while noting no official federal policy change had been confirmed.

January 15, 2026
Semiconductor tariffs in 2026 keep evolving

A new Section 232 duty of 25% now applies to a defined set of advanced semiconductors, effective January 15, 2026, as outlined in C.H. Robinson's guidance. Every new measure is another rule your semiconductor tariff classification logic must evaluate against the correct origin attribute.

25% Section 232 duty on a defined set of advanced semiconductors
When the rule changes, the question is no longer "what is the tariff rate?" It becomes "do we have the right data to know which rate applies?"
Not sure your systems hold COD today?

We'll review where origin data enters your stack and where it gets lost between procurement and compliance.

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:

Finished Product
Semiconductor A
COO COA COD / Wafer Fab HTS / Tariff Classification
Semiconductor B
COO COA COD / Wafer Fab HTS / Tariff Classification
Other Components
COD is the attribute most legacy BOMs never capture.

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:

Events your compliance data must absorb Constant
Supplier
A supplier qualifies an additional wafer fabrication site.
Fab move
A manufacturing flow moves from one fab to another.
Assembly
A component changes assembly locations.
Regulation
A tariff rule changes.
Substitution
A replacement part arrives with a different manufacturing footprint.

The compliance architecture therefore needs to connect product data with supply chain events. This is where supply chain data integration becomes central. Supplier information, BOMs, part attributes, manufacturing locations, HTS codes, customs rulings and shipment records need to flow into a common data layer, ideally through real-time data pipelines rather than quarterly exports.

That data layer should be able to answer:

Which products contain affected components?
Which semiconductor lots were fabricated in the relevant country?
Which shipments are exposed?
Which tariff classification applies?
What changed since the last review?

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:

Evidence Field
Why It Matters
Part number and BOM relationship
Connects the component to every affected product
COO, COA and COD
Allows the correct origin attribute to be applied per regime
Wafer fabrication information
Supports COD-based rules
HTS / tariff classification
Determines the duty line
Supplier source and effective date
Shows where data came from and when it was valid
Applicable rule and decision logic
Makes the outcome explainable
Supporting documentation
Backs the decision during a customs review

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:

ERP
Product and procurement data
PLM
Engineering structures
Supplier portals
Manufacturing information
Trade platforms
Classification and customs data in customs compliance software
Logistics systems
Shipment movements
Compliance teams
Additional records outside all of these

A modern trade compliance data architecture uses APIs to connect these sources without forcing any single application to become the master system for tariff information:

ERP / PLM / Supplier Data
Systems you already run
Integration APIs
Compliance Data Layer
Unified, provenance-tracked
BOM Graph
Origin Data
COO, COA, COD
Tariff Rules Engine
Jurisdiction-specific logic
Exposure + Compliance Dashboard

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.

Supplier part record
COO Country C
COA Country B
COD Country A
Legacy ERP record
Origin Country B
COA not stored
COD not stored
Two attributes lost before compliance sees them

The broader industry is moving in the same direction. NIST's Semiconductor Traceability and Provenance Workshop in January 2026 built on an earlier workshop that identified traceability as the top priority of semiconductor industry stakeholders. Semiconductor provenance is becoming an infrastructure topic, not a niche one.

#1
Traceability was identified as the top priority of semiconductor industry stakeholders in the NIST workshop series.

The fix is rarely to replace the ERP. As covered in our build vs buy guide, the better path is often to build the missing data layer around existing systems.

Keep your ERP. Close the data gap around it.

Seaflux builds the compliance data layer that captures COO, COA and COD without replacing the systems your teams rely on.

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:

Stakeholder
What They Need to See
Procurement leaders
Suppliers whose semiconductor sourcing creates new tariff exposure
Compliance teams
Affected part numbers and their classification evidence
Supply chain leaders
Products exposed by a manufacturing-site change
Finance teams
Estimated duty impact from tariff exposure analysis
Remember

The dashboard is only the presentation layer. The real asset is the structured data and tariff rules engine underneath it.

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:

1
Identify
Semiconductor components where wafer fabrication location matters.
2
Structure
BOM relationships down to those components.
3
Capture
COO, COA and COD as separate attributes.
4
Connect
Supplier and manufacturing-site updates through APIs.
5
Map
Each component to its HTS code and tariff classification.
6
Apply
Jurisdiction-specific rules through a tariff rules engine.
7
Record
The evidence behind every decision.
8
Expose
The resulting exposure through operational dashboards.

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.

Supply chain data engineering

Our data engineering services design the compliance data layer that unifies BOM, supplier, origin and shipment data. With DataOps practices, those pipelines stay monitored, governed and lineage-tracked, so every COD value can be traced to its source.

ERP and API integration services

Through custom software development, we build the integration APIs that connect ERP, PLM, supplier portals and trade platforms, keeping your existing systems in place while closing the data gaps between them.

Tariff rules engines and audit trails

We engineer rules engines that apply jurisdiction-specific origin logic and store the evidence behind each classification, so automation supports your trade compliance experts rather than replacing their judgment. Where useful, our AI and machine learning development team adds assistive capabilities such as document extraction from supplier certificates of origin.

Compliance dashboard development

Our data analytics and visualization services turn the compliance data layer into role-based exposure views for procurement, compliance, supply chain and finance teams.

Supply chain domain experience

From custom logistics software development to SupplyPulse AI and our supply chain intelligence case study, Seaflux builds data platforms that give operations teams visibility they can act on.

If your semiconductor origin data lives in one generic field today, book a consultation with our team to map what a traceable compliance data model would look like for your products.

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.

The next tariff exposure may not begin when a product crosses the border. It may begin much earlier, when a wafer is fabricated and your systems fail to record where it happened.

Frequently Asked Questions (FAQ): Get the Answers You Need

Krunal Bhimani

Krunal Bhimani

Business Development Executive

Claim Your No-Cost Consultation!

Let's Connect