Adding a semiconductor supplier to an approved vendor list is not simply a purchasing task. It is a cross-functional decision involving engineering, quality, operations, compliance, and finance.
The wrong question is, “Is this a well-known chip company?”
The better question is, “Can this supplier support this exact component, through an acceptable route, for the technical and commercial life of our product?”
Here are seven questions that make that review more useful.
- What Exactly Are We Approving?
Define the approval unit before evaluating it.
Are you approving a manufacturer, a product family, an exact MPN, a manufacturing site, a distributor, or a specific manufacturer-channel combination? These are not interchangeable.
A company's reputation does not prove that every device, suffix, lot, or route meets the same requirements. Record the full ordering code, package, temperature grade, qualification level, packing format, and any approved revisions or date-code limits.
This prevents a general brand approval from being treated as permission to buy an adjacent but unreviewed part.
- Does the Part Pass Every Technical Gate?
Commercial comparison should begin only after the device passes the non-negotiable requirements.
Engineering should verify guaranteed electrical limits, timing, thermals, package constraints, environmental range, safety behavior, and application-specific performance. Review errata as well as the datasheet. For programmable devices, include tool versions, libraries, middleware, security support, and licensing.
A matching pinout or similar function is not sufficient evidence of drop-in compatibility. Differences in reset behavior, analog performance, startup sequencing, package dimensions, thermal resistance, or firmware can force a redesign.
- What Is the Product's Real Lifecycle Position?
“Active” describes the present. The AVL has to support the future.
Ask for the exact MPN's product status, longevity-program eligibility, planned support horizon, PCN/PDN history, and last-time-buy procedure. Then compare those dates with production, warranty, repair, and regulatory obligations.
Renesas, for example, publishes a Product Longevity Program with participating products and program conditions. The detail matters: even a formal program can include exceptions, changes, or required migration to an equivalent product. A company-level promise should never replace an MPN-level check.
- How Concentrated Is the Manufacturing Path?
Do not stop at the manufacturer's headquarters.
For the part under review, identify what can reasonably be disclosed about wafer fabrication, assembly, and final test. Are multiple sites qualified? Is the package tied to one line? Does the device use a constrained or legacy process? How are site transfers communicated and qualified?
A supplier with factories around the world can still have a single-site dependency for one device. A fabless supplier can also have a resilient, well-managed production plan. The business model is context; the part-level evidence is the decision.
For teams that need a clear explanation of how fabless firms, foundries, IDMs, and other semiconductor businesses differ, this semiconductor manufacturer and company guide provides a useful reference.
- How Will We Receive and Process Changes?
A PCN subscription is useful only when it reaches an accountable person and triggers a defined review.
The workflow should answer:
Who receives product and process change notices?
Who decides whether samples or requalification are required?
Which customers or regulators must be notified?
How are BOMs, drawings, firmware baselines, and inspection plans updated?
Who owns last-time-buy decisions?
Texas Instruments' PCN process lists items such as the change description, reason, affected products, impact assessment, qualification information, sample timing, and projected shipment date. Your internal process has to convert that information into action.
- Is the Proposed Supply Route Acceptable?
Manufacturer approval and channel approval are separate.
For standard production demand, manufacturer-direct or authorized distribution normally provides the cleanest chain of custody. When scarcity or obsolescence makes independent sourcing necessary, define the additional documentation, inspection, testing, and approval required for the application's risk level.
ECIA's overview of SAE AS6496 shows how authorization status, purchasing controls, traceability, record retention, returns, and suspect-part controls are treated in the authorized distribution chain.
At quotation stage, require the full MPN, quantity, manufacturer, product condition, packaging, lot/date-code information when available, lead time, source category, and applicable conformity documents. A low price is not comparable if the scope of supply is vague.
- What Is the Cost of Leaving This Supplier?
Every approval should include an exit question.
If the part becomes constrained, expensive, changed, or obsolete, what must be redone? Consider:
firmware and software porting;
PCB layout and tooling;
thermal and mechanical validation;
EMC and RF testing;
safety or automotive qualification;
customer approval;
field-service inventory;
new supplier audits and documentation.
That switching cost should influence the original decision. The higher the exit cost, the stronger the case for an alternate path, early lifecycle evidence, and closer supply monitoring.
Turn Unknowns Into Actions
An AVL review does not need perfect information. It needs controlled uncertainty.
For each unanswered question, choose an action:
request a document;
run an engineering test;
add a purchase condition;
restrict the approved channel;
qualify an alternate;
create a monitoring owner;
reject the candidate.
This is more defensible than assigning a vague “preferred supplier” label based on market visibility.
The best semiconductor company for one project may be unsuitable for another. An AVL should capture that context. When approval is anchored to the exact part, the intended application, the supply route, and a defined lifecycle, it becomes a risk-control system rather than a static list of familiar logos.
Top comments (0)