01 / Descriptions
Enrich descriptions
Paste a list of MPNs or upload a spreadsheet column. Get standardized technical descriptions back, in the same row order, ready to export.
Learn more →BOM preflight for sourcing teams
Prepare component data
before RFQ.
Give chip.parts a BOM spreadsheet or a list of part numbers. Get back standardized descriptions, distributor price and stock, datasheet links, and MSL ratings — matched to your rows and ready for quote preparation, review, and production planning.
- PART
- chip.parts
- INPUT
- MPN list / BOM (.xlsx)
- OUTPUT
- description · price/stock · MSL · datasheet
- USE CASE
- RFQ prep · PCBA review
- ACCESS
- app.chip.parts · instant signup
- STATUS
- LIVE
What it checks
One BOM, four preflight checks
Run any check on its own, or use the same MPN list across all four. The output stays row-oriented, so it can go straight back into sourcing and engineering workflows.
02 / Prices
Component prices
Batch-check distributor prices and stock in a single pass, with live results returned as they're found.
Learn more →03 / Datasheets
Datasheet finder
Find the manufacturer datasheet PDF for any part number, checked against the part before it's returned.
Learn more →04 / MSL
MSL lookup
Look up moisture sensitivity level ratings against IPC/JEDEC J-STD-020 for every part on your list.
Learn more →How it works
BOM in, checked rows out
Every workflow keeps the same shape: your rows in, matched component data out, export-ready.
- 1
Submit
Paste your MPNs, or upload a BOM spreadsheet as it came out of your design tool. No reformatting required.
- 2
Resolve
chip.parts resolves each part number against technical and distributor data, matching manufacturer, package, and part variant where available.
- 3
Export
Descriptions, prices, stock, MSL ratings, and datasheet links come back matched to your original list, ready to export.
Who it's for
EMS, CEM, PCBA, and OEM teams, same list
Engineering needs to know what a part actually is. Sourcing needs price, stock, and a quote-ready row. Production needs floor-life and handling context before reflow. chip.parts answers those questions from the same MPN list, so the BOM does not get re-typed three times for three teams.