Quick answer
A PCB component alternate is not approved because it appears electrically similar or available. Before material is committed, identify the exact candidate manufacturer part number, affected references and reason; assess the form, fit, function and product-specific impact; obtain the named authority's decision; then update the controlled BOM, AVL or build record for the approved scope. A supplier proposal, PCN or email alone is not a production release.
A PCB component alternate needs a controlled approval workflow before production, not a quick substitution when stock changes. Start with the exact candidate manufacturer and part number, affected reference designators, reason for the request and released assembly revision. Then assess the form, fit and function questions that matter for the product, obtain the named decision authority's disposition, and update the BOM, approved vendor list (AVL) or build record before material release.
This guide owns the alternate-approval workflow. The component sourcing service page owns project sourcing support, while BOM preparation owns release-ready line-item data. For the commercial choice of who purchases material, use the turnkey versus consigned buyer guide.
What counts as an alternate decision?
An alternate proposal may be prompted by availability, lifecycle information, package change, commercial sourcing, a manufacturer product-change notification or a customer-controlled part. None of those triggers is an approval. The proposed item must be identified exactly and reviewed against the released configuration and the actual product requirements. Infineon and Texas Instruments describe formal product-change notification processes for changes that can affect form, fit, function, quality or reliability; a project team still has to determine its own product and release impact.
| Review question | Evidence to request | Decision owner |
|---|---|---|
| What exactly changes? | Original and candidate manufacturer, full MPN, affected references, BOM revision and reason | Named request owner |
| Does it fit the design and route? | Package, footprint, pinout, polarity, assembly and handling comparison | Engineering with manufacturing input |
| Does it meet intended function? | Relevant electrical, thermal, firmware, safety, qualification or regulatory impact assessment | Product technical authority |
| Where is it approved? | Approval scope: one build, variant, revision or controlled global rule | Named approval authority |
| What changes in the build record? | Revised BOM/AVL, purchasing instruction, traceability and release status | Configuration or quality owner |
Use form, fit and function as a review frame—not a shortcut
Form can cover physical envelope, package, pin count and material constraints. Fit can include footprint, pinout, polarity, placement, soldering, thermal path, enclosure and test access. Function can include electrical behavior, tolerance, ratings, timing, firmware interaction and the product's own acceptance requirements. The required evidence varies by line item and product; a generic similarity claim does not prove equivalence.
Make approval authority and scope explicit
The product owner controls design intent and the acceptance baseline. Procurement can surface a candidate and commercial context; manufacturing can explain route, packaging and process impacts; quality can define record or disposition needs. The person authorized to accept the product impact should be named before a shortage appears. Record whether the decision applies only to a stated quantity, one variant, a revision, a date window or a broader controlled rule.
Do not let an approval live only in an inbox. If accepted, update the controlling BOM or AVL and any affected drawing, placement, test, programming or traceability instruction. If rejected or deferred, preserve the original release state and make the hold visible. IPC-1782B's public table of contents highlights product-build records, risk assessment and user-supplier agreement as traceability topics; use that principle to connect the decision to the build, without assuming a universal record level.
Approval flow before material release
- Freeze the assembly part number, revision, variant and affected BOM line.
- Record the exact candidate MPN, source and reason for the request.
- Assess relevant form, fit, function, lifecycle, package, firmware, test and product impacts.
- Obtain the named technical authority's approve, reject or defer decision.
- State the approval scope and update the affected controlled data.
- Release procurement and assembly only against that updated state; reopen review after a later design, supplier, process or requirement change.
Prepare an alternate request for a project review
Provide the released BOM and active variant, the original and proposed MPNs, affected references, reason, datasheets or product-change notice where available, quantity and build stage, and the person authorized to decide. PCBArise can discuss the sourcing and assembly implications through component sourcing, PCB assembly and a project review. The quotation and agreed documents define any actual sourcing, approval and evidence scope.
Engineering review
Prepared and reviewed for project use
Engineering Director
Senior Quality Engineer
Review scope: technical accuracy, evidence wording, standards references, internal links and release readiness. Project requirements remain subject to the released files, applicable acceptance criteria and agreed test documentation.
FAQ
Questions engineers ask before release
Can a PCB assembler use an alternate component automatically?+
No. A candidate should be used only under the approval rule for the released BOM and project. Availability, a similar specification or an email proposal is not by itself a production authorization.
What information should an alternate request include?+
Include the original and proposed manufacturer part numbers, affected references, BOM revision and variant, reason, relevant datasheets or notices, quantity, build stage and the named approval authority.
What does form, fit and function mean for a component alternate?+
It is a review frame. Form can include physical package and dimensions; fit can include footprint, pinout, polarity, assembly and test access; function can include the product-relevant electrical, thermal, firmware and acceptance impact.
Who approves an alternate component?+
The approval should come from the authority responsible for the product's design and acceptance baseline. Procurement and manufacturing can supply evidence, but their roles do not automatically transfer technical approval authority.
Should an approved alternate update the BOM?+
Yes, the relevant controlled record should show the approved state and scope, such as a BOM, AVL, variant rule or build instruction. The precise record depends on the project's configuration-control method.
Does a manufacturer PCN automatically approve a replacement?+
No. A product-change notification provides change information. The product team still needs to assess the affected application and decide whether, where and under what conditions a replacement can be released.
Reference points
Sources and verification starting points
External standards and industry references help frame the decision. Confirm current supplier evidence and project-specific requirements before release.
- Infineon — product/process change notification and form-fit-function context
- Texas Instruments — product change notification process and early impact review
- Global Electronics Association — IPC-1782B traceability, product-build records and agreed requirements
- ECIA — current component-market context; not a project availability promise
- QueenEMS — professional buyer checklist context for sourcing ownership
- PCBA Group — professional comparison context for turnkey, partial and consigned models