Resolve Ambiguous Component Values Before a BOM Is Matched

A BOM value is a description of one component property, not a complete purchasing identity. Text such as 10, 100n, or 4R7 can become ambiguous when a spreadsheet changes formatting or when an automated importer expects a different convention. Resolve that ambiguity before accepting a matched component.

JLCPCB’s BOM guidance specifies the fields its assembly workflow expects. Follow the selected assembler’s format while preserving an exact manufacturer part number where required. A value-only match should not silently decide package, tolerance, voltage rating, or other design requirements.

Separate identity from description

Use dedicated fields for manufacturer, manufacturer part number, package, value, and relevant procurement information. Keep distributor stock numbers in their own field. A supplier code can be useful for ordering, but it should not obscure which manufacturer’s component the design approved.

For each passively named item, verify that the displayed value contains a clear unit or an agreed unambiguous notation. Check resistance, capacitance, inductance, frequency, and voltage descriptions separately. A single generic number format cannot safely describe every component family. Keep ambiguous legacy descriptions in a review list until their intended values can be confirmed from the controlled design and approved component records.

Inspect the file after export

Open a copy of the actual submitted file rather than relying on the original spreadsheet view. Inspect representative rows with leading zeros, punctuation, long identifiers, and unusual value notation. These are more likely to expose a formatting problem than a short, simple part number.

Approve the match against the design

1. Compare the matched manufacturer and full part number.
2. Verify package and physical dimensions against the footprint.
3. Check the properties that drove the original component choice.
4. Resolve every substitution through the designated engineering process.
5. Save the accepted match list with the build revision.

Do not let a portal’s successful import stand in for component approval. The importer can parse a row correctly and still select an unsuitable item if the source description is incomplete.

If a recurring ambiguity comes from the source library, fix it there and regenerate the BOM. Editing only the manufacturing spreadsheet leaves the problem ready to return on the next revision. See assembly file preparation for the surrounding release information.