Map Purchasing Identity Fields Before Exporting IPC-2581

A manufacturing dataset can contain correct copper geometry and still communicate an incomplete purchasing identity. When an export carries BOM information, verify the source field behind each purchasing field and inspect what the recipient actually imports. A populated column is not proof that it contains the right type of identifier.

Distinguish three identities

The internal item number identifies a part in your own system. The manufacturer name identifies the organization supplying the defined component, and the manufacturer part number identifies its orderable product. A distributor stock number belongs to another namespace. Do not substitute one for another merely because both fields contain plausible alphanumeric strings.

KiCad 9’s IPC-2581 exporter provides separate field mappings for internal ID, manufacturer, and manufacturer part number. Use the documentation matching the installed version when locating these controls.

Audit the mapped values by reference

1. Select a representative component from each purchasing class in the design.
2. Compare its schematic/library values with the board instance used for export.
3. Verify each export field’s source and treatment of missing values.
4. Inspect the resulting dataset with a capable viewer or the recipient’s import report.
5. Reconcile the imported identities against the released purchasing BOM.

Include a component with an approved alternate, a mechanical item, and an intentionally unpopulated position. These cases reveal assumptions hidden by ordinary resistors and capacitors. The approved-manufacturer-set snapshot remains necessary when one internal item can map to several permitted products.

Resolve conflicts before the dataset becomes an order

For example, a field called Part Number may contain a company inventory code while the exporter maps it to manufacturer part number. The file remains readable and can pass a syntax check, but procurement may search for the wrong item. Rename or map the source field deliberately and regenerate the output; do not rely on the assembler inferring intent from the component value.

A successful import should report the expected component identities, population, and quantities. Use the BOM-to-placement reconciliation to check that the same reference set is represented across outputs. If a separate BOM remains the purchasing authority, say so explicitly and still resolve conflicting embedded fields.

Archive the mapping configuration with the released data. A library update or exporter change may alter field availability without changing the board’s appearance, so this check belongs to the release process rather than only the initial software setup.