PCB BOM Checker
Find missing part data and inconsistent quantities before assembly sourcing. Import a CSV or paste a spreadsheet; your BOM stays in this browser page.
How to Use the BOM Checker
- Read your parts list. Paste cells from a spreadsheet or choose a UTF-8 CSV / TSV file. Keep the header row, then click Read BOM.
- Confirm the columns. Map reference designators, quantity per board and MPN. Check whether your status column means DNP or Fitted, and enter the build quantity.
- Run checks and resolve issues. Filter the results, correct your source BOM and read it again. Download the checked list or issues; the checker does not approve parts for purchase.
Check Your BOM Before Assembly
Local data · no upload to FLJ1 Import or paste data
The sample contains deliberate issues. Replace it with your own BOM, or read it to try the checks.
UTF-8 text only; export .xlsx files as CSV first. Up to 5,000 component records, 60 columns and 2 MB file size. Values remain text, so leading zeros in part numbers are preserved.
2 Confirm columns and build quantity
Suggested mappings are based on header names. Confirm them against the first source record shown below each selection.
Mapping changes and build quantity edits require running the checks again.
3 Review the findings
| Record | References / quantity | Part identity | Fit / build demand | Findings |
|---|
Downloads stay local. You decide which files to send to FLJ.
Read the sample or replace it with your BOM to begin.
What the BOM Checker Looks For
Identity and quantity checks
The checker flags missing or placeholder MPNs, empty references, repeated references, and quantities that differ from the expanded reference count. It can also flag missing manufacturer / package text and conflicting text on records with the same MPN.
Use whole quantities per board without thousands separators. Common references such as R1, C12 and U3A are supported. Ranges such as R1-R5 are expanded; unrecognized reference formats are reported for review, rather than silently discarded.
DNP and demand have separate roles
DNP records are excluded from listed build demand. Unknown fit status is reported and also excluded. The provisional total adds fitted records with valid quantities; unresolved duplicate references can still make it double count.
This is a completeness and consistency check. It does not verify datasheets, footprints against PCB pads, genuine parts, stock, lifecycle, approved alternatives or procurement allowances. See the BOM and component guide for the handoff context.
CSV parsing uses locally hosted Papa Parse 5.5.3 under its MIT license. Exported text cells that could be interpreted as spreadsheet formulas are prefixed with an apostrophe; original imported values are retained in the browser. When opening the CSV in a spreadsheet, import MPN and reference columns as Text to preserve leading zeros.
Resolve the purchasing questions behind the list
Our component sourcing team reviews the specified devices, supply options and proposed alternatives with you. Pair the BOM with placement data and assembly instructions so the chosen parts and selected build version reach production together.
BOM Checker Questions
Is my BOM sent to a server?
No. Parsing, checking and downloads run in this page. Page loading still makes normal site and asset requests. The tool does not send your BOM to FLJ or keep it after the page is closed.
Can the same MPN appear on several rows?
Yes. Separate rows for one MPN can be valid. Repeated reference designators are flagged; differing manufacturer or package text on the same MPN receives a warning for comparison.
Does a clean report mean the BOM is ready to buy?
No. It means this tool found no listed consistency issues with the chosen mappings. Device suitability, approved sources, availability and assembly requirements still need review.