RF Transceiver Part Number Verification

Customer Problem

A BOM may contain only a family name, a distributor stock code or a suffix that was lost during spreadsheet editing. A quote can then look correct while referring to a different purchasing or packing option.

The goal is a traceable identity decision before ordering, not a claim that text verification proves the offered goods are authentic or electrically qualified.

Technical Background

Use the manufacturer’s ordering information and package documentation to resolve the complete reference. Keep the original customer string and the normalized manufacturer MPN in separate fields until any difference is approved.

For firmware-sensitive devices, include software applicability in the technical record. The LR1121 baseline explicitly associates a document revision with a use case and firmware version; consult its current user documentation for the actual integration.

Evidence: Semtech SX1261/2 datasheet · Rev. 2.1 · December 2021 / Semtech SX1268 datasheet · Rev. 1.1 · June 2019 / Semtech SX1276/77/78/79 datasheet · Rev. 7 · May 2020 / Semtech LR1121 datasheet · Rev. 1.1 · March 2023

Selection or Sourcing Risks

Do not infer what a suffix means across manufacturers or product families. A suffix may describe an option that is irrelevant in another family, and a distributor’s cut-tape code is not necessarily the manufacturer’s order code.

A matching footprint name does not verify a land pattern or pin function. A matching SPI label does not establish compatible commands or timing. Ambiguities should remain open review items rather than being silently “corrected.”

Verification Checklist

• Original BOM string and exact manufacturer identity.
• Manufacturer ordering-table match and documented delivery format.
• Package code, dimensions, pin count, land pattern and temperature grade.
• Document revision, errata, lifecycle evidence and verification date.
• Firmware/use-case applicability when stated by the manufacturer.
• Written approval for any difference from the customer’s released MPN.

Practical Recommendations

Create a one-line evidence record per full MPN: requested identity, proposed identity, source document, page or section, checked date and unresolved items. This makes later quotation changes reviewable.

Recheck identification when a source proposes a different suffix, package, packing option or date-code restriction. Do not treat a previous family-level check as approval of every later offer.

RFVero Sourcing Support

RFVero can help organize the identity review and ask suppliers for labels, packing and documentation information that is available. It can flag a mismatch before a quote is accepted.

Goods authentication, electrical testing and customer system qualification are separate activities with separately agreed evidence. RFVero does not imply a laboratory result from an MPN check.

Sources & Technical Review

Evidence checked on 28 October 2026. The document versions below are the actual reviewed baselines. A newer listing date is not treated as evidence that a later full document was inspected. Manufacturer specifications are separate from offered-lot verification and customer system validation.

Related Resources