When PCB Assembly (PCBA) files disagree, no single document should silently override the others. A BOM, component placement list, assembly drawing, fabrication package, and product-variant record each answer different questions. The conflict should be logged, assigned, approved by the product authority, and closed through a re-released manufacturing baseline.
At Venture Electronics, our rule is simple: production should not guess which file the customer intended. This framework is based on our public PCB Assembly input and review scope; its examples are hypothetical. We can review file completeness and consistency, identify questions, and coordinate the approved build scope, but this does not imply an automated file-checking platform or permission to change the product definition.
What the BOM and CPL are supposed to control
The bill of materials, or BOM, normally identifies what is fitted: reference designator, manufacturer, exact manufacturer part number, description, package, quantity, and substitution restrictions. The component placement list, or CPL, normally identifies where and how a component is placed: reference designator, X/Y position, side, and rotation.
Assembly drawings, Gerber or ODB++ data, panel information, product-variant rules, and approved change records provide additional context. These files need not repeat every field, but their shared identifiers and revision intent must agree well enough to create one executable release.
Conflict 1: the reference-designator sets do not match
A BOM may list R37 while the CPL has no R37, or a placement file may include C18 while the approved BOM does not. The difference could indicate a missing coordinate, an unapproved component, a design-not-populated condition, a variant rule, or a simple export error. It should not be resolved by choosing whichever file was opened first.
Venture Electronics can compare the available reference-designator sets and return a discrepancy list. The customer should confirm whether the position is fitted, not fitted, variant-specific, or removed, then issue files that express the same decision.
Conflict 2: the exact MPN disagrees with the description or package
A generic description such as “10 µF capacitor, 0805” does not replace an exact manufacturer part number when the design requires a particular dielectric, voltage, tolerance, temperature characteristic, qualification, or termination. Conversely, an exact MPN may point to a package that does not match the land pattern or description in another file.
BOM review should separate the exact MPN, manufacturer, generic function, package or land pattern, and approved-alternative rule. Venture Electronics can flag the inconsistency and discuss availability, but it should not select a replacement merely because the body size or description looks similar. Substitutions remain subject to customer approval and any required validation.
Conflict 3: DNP or DNI status is inconsistent
Do-not-populate or do-not-install status should be clear across the BOM, CPL, assembly drawing, and variant matrix. A blank coordinate does not automatically mean DNP. A listed component with zero quantity may still conflict with the placement and assembly files.
This matters especially when one hardware platform supports multiple regional or functional SKUs. The release should state which positions are populated for each variant and which file or controlled matrix carries that decision. A manufacturing team should not turn missing data into a product rule.
Conflict 4: polarity, pin 1, or rotation definitions conflict
The CPL can provide a rotation value, while the assembly drawing shows polarity, pin 1, cathode, connector orientation, or a visual reference. CAD export conventions differ, so a numerical angle is not safe without the applicable coordinate and rotation convention. Component packaging and the land pattern add further context.
Use a representative board view, assembly drawing, component documentation, and first-article confirmation where appropriate. DFM/DFA or assembly review can identify ambiguous orientations, but no universal degree convention should be assumed across all CAD tools and projects.
Conflict 5: quantity does not match the assembly object
A BOM quantity may mean pieces per finished unit, pieces per panel, or total order quantity. The CPL may contain coordinates for one board, an array, or only part of a panel. If those units are not stated, purchasing, feeder preparation, attrition planning, placement count, and quotation can all use different denominators.
The release should identify unit quantity, panel quantity, number of units per panel, fitted quantity per unit, and target build quantity. The review can return differences between the BOM, CPL, panel information, and order quantity, while the customer confirms the intended assembly and purchasing baseline.
Conflict 6: the board revision and file release status disagree
A filename marked “final” is not a release system. Gerber, BOM, CPL, drawings, firmware, and test files can carry different revision dates or identifiers, and the newest timestamp may reflect an export rather than an approved design change.
Check the product or board revision, file revision, release status, approval record, and effective build. For a repeat order, do not assume the previous batch package automatically applies. Venture Electronics can use approved prior records as context, but changed files, BOM availability, testing, packaging, and delivery requirements should be reviewed before the next build.
Conflict 7: the product-variant mapping is incomplete
One hardware design may become different customer, region, feature, or firmware variants. The manufacturing baseline should map SKU to hardware revision, BOM and DNP status, CPL, firmware, test configuration, product label, packaging, and destination requirements.
If the mapping ends at “same board,” downstream teams can program, test, label, or ship the wrong deliverable even when assembly itself is correct. The customer defines and approves each variant. Venture Electronics can coordinate the project-specific manufacturing relationship without inventing the variant logic.
Close the conflict through four controlled steps
- Log the conflict. Quote the exact fields, filenames, revisions, and affected reference designators or SKUs.
- Assign the authority. Identify who can decide the design, component, variant, test, or commercial question.
- Approve the disposition. Record the confirmed interpretation, deviation, or design change and any required validation.
- Re-release and freeze. Issue a mutually consistent package, remove superseded production copies, and identify the approved as-built baseline.
An email answer can unblock a question, but a repeatable build needs the answer reflected in the controlled files or deviation record. The as-built record should show what was actually manufactured, including approved substitutions or deviations that affect future orders.
Files to send for a completeness review
- Gerber or ODB++ fabrication and assembly data.
- BOM with reference designators, exact MPN, manufacturer, package, quantity, and substitution limits.
- CPL or pick-and-place data with side, X/Y coordinates, rotation, units, and origin convention.
- Assembly drawings showing polarity, connectors, DNP status, and special instructions.
- Panel drawing or array information where applicable.
- Revision history, approved deviations, product-variant matrix, firmware, and test requirements.
When Venture Electronics receives these inputs, the useful engineering output is not a vague “files checked” statement. It is a bounded list of conflicts, missing information, manufacturing questions, and customer approvals required before the related step proceeds.
Frequently asked questions
Which file wins when the BOM and CPL disagree?
Neither should automatically win. The files control different attributes, and the product authority should clarify the intended design and issue a consistent release or approved deviation.
Does a missing CPL row mean the part is DNP?
No. It may be DNP, but it may also be an export omission, a manually assembled part, or a variant issue. Confirm it against the approved BOM, drawing, and variant definition.
Can a previous-order file package be reused?
Only after confirming the board revision, BOM status, component availability, test requirements, firmware, labels, packaging, and any approved changes for the new order.
Make “ready to build” a controlled status
A file package is ready when its shared identifiers, revisions, quantities, orientations, variant rules, and approvals tell one manufacturing story. The goal is not to make every document identical; it is to remove decisions that would otherwise be guessed on the production floor.
Venture Electronics supports international teams with PCB Assembly, BOM review, DFM/DFA review, component sourcing, and project-specific testing discussions. Share the Gerber or ODB++, BOM, CPL, assembly drawings, revision history, and variant requirements. Venture Electronics can return the discrepancies and confirmation points needed to establish an executable manufacturing baseline.