When the original part cannot be obtained, the next question is what can work in the installed application. A successor, an exact replacement and a retrofit candidate involve different evidence and acceptance conditions.
Begin with the original identity
Enter the installed MPN on the RFQ form. In Add optional details add the machine or application, hardware revision, firmware where relevant, reason for replacement and required date. Use Notes for electrical, connector and mechanical constraints, and whether software changes or rewiring are acceptable.
Distinguish a failed unit from a planned migration or an additional spare.
Keep the current MPN and a suggested alternative separately identified.
Upload is unavailable; start with label text and ask for an approved transfer method if manuals or photos are needed.
How a candidate should be described
OEM migration documentation and application evidence take priority. A documented successor may still require configuration or installation changes. A retrofit candidate must identify those changes and unresolved assumptions. Supplier listings, naming similarity and AI suggestions cannot confirm fit.
Record the relationship: documented successor, reviewed direct replacement, retrofit candidate or insufficient evidence.
If evidence conflicts or is incomplete, request clarification instead of presenting compatibility as confirmed.
Safety-critical or unsupported applications require an explicit technical scope before any supply commitment.
Technical acceptance and commercial quotation
Submitting the form requests human review and creates an RFQ for the original requirement. It does not approve a replacement or promise engineering validation. Any proposed option needs stated application assumptions and buyer acceptance, as well as exact identity, condition, quantity, price, lead time, delivery, warranty and validity in writing.