Incoming Inspection and Traceability for Semiconductor Sourcing: A Procurement Checklist
Incoming inspection is where a sourcing decision meets a physical part. A practical checklist for verifying semiconductor identity, visual condition, batch consistency, and the document chain that proves traceability.

The Short Answer
Incoming inspection is the point where a sourcing decision meets a physical part. For semiconductor components, it combines four checks: identity (is the part what the marking says), visual condition (is the package and lead finish genuine and undamaged), batch consistency (are date codes and lots coherent), and traceability (can the lot be connected to the original manufacturer document chain). A label is not evidence; the JEDEC ID readback and the document trail are. This checklist gives procurement and quality teams a practical go/no-go framework for semiconductor incoming inspection.
Why Incoming Inspection Is Part of Second-Source Qualification
Second sourcing moves the risk from "can we find a part" to "is this part what the paperwork says." Engineering qualification decides whether a candidate is electrically and functionally suitable; incoming inspection decides whether each physical lot that arrives matches the qualified part. Both stages are required.
Our guide to qualifying a Chinese MCU alternative covers the engineering stage. This guide covers the inspection stage that runs on every shipment, from every supplier — including the original manufacturer's channel.
The two stages share one rule: pin-compatible is not proof, and a printed mark is not proof. Verification is evidence-based.
The Incoming Inspection Checklist
| Check area | What to verify | Why it matters |
|---|---|---|
| Identity | JEDEC ID readback (for ICs), package marking, brand, part number, date code | The JEDEC ID is read from the silicon, not the label; a mismatch reveals a relabeled or wrong-silicon part |
| Visual condition | Package integrity, lead or pin condition, surface texture, signs of resurfacing or remarking | SAE AS6171/2A formalizes external visual inspection for suspect and counterfeit EEE parts |
| Batch consistency | Date codes within a lot, country of origin, marking font and alignment | Mixed date codes or inconsistent marking are classic redistribution red flags |
| Traceability documents | Original manufacturer invoice or authorized-distributor chain, lot number, datasheet | Traceability connects the physical lot to a verifiable source, not just a seller's claim |
| Electrical spot check | Continuity, power-on ID read, basic functional test where risk justifies it | Confirms the part behaves like the family it claims to be |
| Handling | MSL floor life, ESD precautions, storage conditions, moisture-barrier bag condition | A genuine part that is mishandled fails exactly like a counterfeit one |
For the visual inspection layer, two authoritative references are useful. The European Space Agency's ESCC Basic Specification No. 21004, Guidelines for Incoming Inspection of EEE Components, defines the inspection discipline used for high-reliability components. The SAE AS6171/2A standard covers detection of suspect or counterfeit parts by external visual inspection, remarking, resurfacing, and surface texture analysis. You do not need space-grade procedures to benefit from the same sequence: verify identity, inspect surfaces, and look for signs that a package was reworked or re-marked.
Traceability: What the Document Chain Must Contain
Traceability is a chain, not a single sheet. The minimum record connects four links:
- Original manufacturer — the invoice or distribution record from the component manufacturer or an authorized distributor.
- Intermediary — every broker or independent distributor in the chain, with the documentation that moved with the lot.
- Your purchase order — the PO that identifies the part, quantity, and date-code requirements.
- Incoming record — your inspection result for the lot, including photos and test data.
The GE Vernova EC-SRC-0008 counterfeit-parts avoidance requirement (Rev 7.0) is a practical example of what large buyers require from independent distributors and high-risk suppliers: documented traceability, inspection records, and record retention. Procurement teams that build the same expectations into their supplier agreements get the same protection at smaller scale.
What a Certificate of Conformance Does and Does Not Prove
A certificate of conformance (CoC) is a supplier's statement that a lot meets the agreed specification. It is useful, but it is not independent evidence. It does not prove the part was manufactured by the brand on the label, and it does not prove the lot is authorized or untouched.
Treat a CoC as one link in the chain, not the chain itself. The CALCE research on screening for counterfeit electronic parts and the ERAI screening recommendations both emphasize that counterfeits are detected by combining document review with physical inspection and electrical testing — no single document catches a relabeled part.
Building a Go/No-Go IQC Workflow
- Classify risk by part family and source. MCUs and high-value analog parts from a new or independent source get a higher inspection level than low-risk passives from a qualified authorized channel.
- Set the inspection level. Decide per class whether you do document review only, document review plus visual inspection, or a full check including electrical spot tests.
- Define the sample plan. For each lot, define how many units are inspected and what constitutes failure. Reject criteria must be explicit — one date-code mix or one marking anomaly is a reject.
- Capture evidence per lot. Photograph the lot, record the JEDEC ID readback, and store the document chain with the lot number.
- Feed findings back. A repeated anomaly is a supplier or qualification problem, not an inspection problem — escalate it to engineering and sourcing.
Common Mistakes to Avoid
- Trusting the label. A legible mark proves nothing by itself; read the JEDEC ID from the silicon.
- Accepting a CoC as proof of origin. It is a statement, not evidence of provenance.
- Skipping date-code checks. Mixed date codes are one of the most common redistribution signals.
- Ignoring MSL and ESD handling. A genuine part that is mishandled fails exactly like a counterfeit one.
- No record retention. If the lot fails in production six months later, the incoming record is your only defense.
How Senneon's Verification Process Maps to Incoming Inspection
Senneon's verification process applies the same evidence-first logic upstream: every graded cross-reference carries its evidence source and disclosed differences, and candidates that are not verified are labeled as such. When you evaluate a second-source candidate — for example an MCU such as the HK32U3009VDT7 or an analog MOSFET such as the SGMNQ61440 — the catalog record is the starting point, not the proof. The physical lot still has to pass incoming inspection.
We do not claim that a graded cross-reference is a substitute for your own inspection. Grade plus evidence tells you what to verify; incoming inspection tells you whether the lot in front of you matches.
What Senneon Provides
- Submit target part numbers or a BOM for an initial cross-reference or BOM triage when operationally available: RFQ.
- Read how we verify parts and evidence: Verification.
- See the full qualification process for MCU alternatives: How to Qualify a Chinese MCU Alternative.
- For flash-specific inspection checks, see the SPI NOR Replacement Checklist.
- Talk to the engineering desk about a specific family or document chain: Contact.
Published by Senneon Engineering Desk. Last reviewed 2026-08-19. This guide reflects current qualification and inspection practice; always verify against the exact part, package variant, datasheet, and your supplier's documented chain of custody.
Frequently asked questions
What is the difference between a certificate of conformance and traceability documentation?
A certificate of conformance (CoC) is a supplier's statement that a lot meets the agreed specification. Traceability documentation is the chain of records — original manufacturer or authorized-distributor invoice, lot number, and your purchase order — that connects the physical lot to a verifiable source. A CoC is one link in that chain, not proof of origin.
How do I verify a date code on a semiconductor component?
Compare the marking against the manufacturer's date-code convention in the datasheet or package-marking specification, confirm the code is consistent across the whole lot, and check it against the supplier documentation. A mixed or out-of-range date code within one lot is a classic redistribution red flag.
Can incoming inspection catch every counterfeit or relabeled part?
No single inspection catches everything. Document review, visual inspection and risk-based electrical testing substantially raise the odds, but sophisticated relabeling may require X-ray, SEM surface analysis or other techniques covered by standards such as SAE AS6171. Combine document review, visual inspection and electrical spot checks, and escalate anything ambiguous.