Inspect the assembly handoff.
Compare population intent with placement evidence. Find the mismatch, then trace it back to the export.
Files and column mapping CSV files stay in this tab
Add both files, read their columns, then confirm each mapping. Suggestions are not format detection.
BOM What should be fitted
CPL Where it will be placed
Factory-neutral checks use your mapping. They do not establish compatibility with a manufacturer's uploader.
Population flags and grouped references
DNP, DNI, no, false, 0, unpopulated, not fitted mean excluded. yes, true, 1, fit, populated and blank mean populated. A Boolean DNP column often means the opposite: convert it to a Populate column first.
References accept letters plus digits, lists and ascending ranges such as R1-R3. Quote CSV cells containing commas. Population examples
Ready for your CSV files. Nothing has been checked.
Issue review
Read columns, confirm mappings and choose units to begin.
Every mismatch needs a source.
Your issues will appear here with their original CSV lines. Select one to compare both files and see what to check next.
The synthetic example includes a duplicate R3, a missing C2 and an excluded J1.
Evidence, before edits.
A discrepancy report does not repair a design. Use the source values to find the cause, correct your CAD export, and check the new pair.
Why a KiCad part can disappear from the CPLWhat to check
Read the worked guidePhysical lines include the header and quoted multiline fields. Matching ignores case; original values are preserved.
Consistency is one part of the handoff. No Gerber, polarity, footprint, pin-1, origin, mirroring or stock checks. A clean report still needs CAD and factory preview review. Exports contain all issues, including those hidden by filters.