Turn an AI parts list into a buildable BOM.

Identify what each row actually means

Include a line number, reference designators, quantity per assembly, description, manufacturer, full manufacturer part number, package or module revision, and a datasheet link. Keep supplier ordering codes in a separate column: they are not always the manufacturer part number.

For a module, identify the complete breakout board rather than only the chip fitted to it. Different boards using the same sensor may have different dimensions, connectors, regulators or pin labels. For fasteners, specify the thread, length and head type that the assembly actually needs.

Check the interfaces before ordering

Compare supply voltage, logic levels, pin assignments and interface type with the actual controller and schematic. Confirm connector pitch, mating part and polarity. Check footprint and package details against the PCB, and component height against the enclosure.

Make uncertainty visible. An example row might say “temperature sensor breakout; exact board pending; quantity 1; check 3.3 V interface and mounting.” Keep it on hold until those checks are resolved instead of letting an invented part number look approved.

Use the manufacturer documentation for the proposed item. Stock, price and delivery are separate facts to check with the selected supplier when purchasing; an AI answer or an old quote is not a stock reservation.

Control substitutions and quantities

A substitute needs a stated reason and a compatibility review. Compare function, ratings, pinout, package, software support and mechanical fit as applicable. Record the proposed replacement and obtain approval before it becomes part of the build.

Separate the quantity needed for one assembly from the order quantity. Prototype spares, pack sizes and minimum orders affect purchasing. Record items intentionally not fitted so an assembler does not interpret an omitted component as a missing line.

Release a consistent set of build files

For a custom PCB, a BOM is only one part of the handoff. Depending on the manufacturer, fabrication can require copper and outline data, drill files and stack-up requirements; assembly can require placement files, drawings and fitting notes. KiCad documents separate fabrication and placement outputs.

Use one release identifier across the schematic, PCB, BOM, mechanical files and assembly notes. Open the exported outputs to review them before sending. Keep a list of unresolved items and nominate who can approve a change.

For a module-based prototype, the equivalent package can be a module BOM, wiring diagram, pin map, firmware version and mounting drawing. It still needs a clear revision even when there is no custom PCB.