BOM Kitting and Component Sourcing: The Version Control Trap

Most assembly problems that are blamed on the factory start in the bill of materials. A part number that exists in two variants, a footprint that matches the first variant and not the second, an approved alternate that was never written down, a quantity that ignores attrition: none of these are manufacturing failures, and all of them stop the line.

That is why BOM kitting and component sourcing deserve to be treated as an engineering activity rather than a purchasing one. The output is not only a box of parts, it is a record of which revision of which component went into which build.

What BOM Kitting Actually Involves

Kitting begins with a line-by-line review of the bill of materials against the design. Each line has to resolve to a real, orderable part, with a package that matches the footprint, a temperature range that suits the application, and a lifecycle status that supports the production plan.

The review then checks quantities. Attrition is not a fixed percentage that can be guessed: it depends on the package, the feeder capacity, the number of placements and the handling steps. A fine-pitch device on a reel behaves differently from a tray of connectors, and a part that must be baked before reflow has its own logistics.

Finally, kitting produces the kit list itself: what was ordered, what arrived, what was inspected, and what is still outstanding. That list is the document that allows an assembly date to be quoted with any confidence.

The Cost of a Version Mismatch

A version mismatch is the failure mode that costs the most, because it is often invisible until after assembly. The common cases are well known.

A part is substituted by an equivalent that differs in a parameter nobody checked, such as the tolerance on a resistor used for current sensing, or the ESR of a capacitor in a switching supply. The boards assemble and fail a functional test, or worse, they pass and drift in the field.

A footprint is drawn for one package variant and the purchased part is the other, so the device sits on pads that are a fraction of a millimetre out. Reflow appears to work, and the joints fail under thermal cycling.

A firmware configuration, a programming file or a jumper setting is changed for one batch and not recorded, so two builds that are documented as identical behave differently.

Every one of those failures is prevented by the same discipline: the part, the footprint, the program and the substitution must all be traceable to a revision, and the revision must be the one the design authorised.

Defining Approved Alternates Properly

Component sourcing becomes much easier when the design states its substitution policy in advance. The useful format has three levels: parts that are interchangeable with no further approval, parts that may be used when a defined condition is met, and parts that must not be used.

An approved alternates list should give the manufacturer and full part number, the parameters that are critical to the function, and the tolerance or range that is acceptable. Writing down the critical parameters is what allows a sourcing team to evaluate a candidate without waiting for the design engineer, which is exactly the situation that a shortage creates.

Where the supplier also performs component sourcing as a service, the same list becomes a working document: candidates are proposed against it, and each proposal carries a rationale rather than an assumption. For products that will be built repeatedly, a turnkey PCBA assembly arrangement makes the list part of the controlled data package rather than a note in an email thread.

Shortages, Long Lead Times and the Options

When a part is unavailable, there are only a few honest options. Use an approved alternate. Buy from a broker with the added verification risk that brings. Redesign around a different device. Or delay the build.

Each option has a cost that can be estimated if the critical parameters are known. What makes shortages expensive is discovering them late, after the boards have been fabricated and the assembly date announced. That is why kitting should start as early as the design allows, using the pre-release bill of materials as a risk list rather than waiting for the frozen version.

Buying from the open market deserves an explicit policy. Parts from unverified channels need incoming inspection, and for high-reliability or safety-related products the correct answer is often that they are not acceptable at all, regardless of the price.

Version Control Across Batches

A single build with a complete record is a good start. The harder requirement is keeping that record coherent as the product is built again months later.

BOM version control means that each batch can be described by the version of the bill of materials, the coordinate file and the assembly program that produced it, together with every substitution and engineering change approved for that batch. When a failure appears later, that description is what makes the investigation possible.

It also protects the supplier. A clear record shows what was built to the customer specification and what was changed at the customer request, which removes the ambiguity that turns a technical discussion into a commercial one.

What a Purchase Order Should State

• Reference designator, quantity, manufacturer, full part number and package for every line.
• Which lines allow substitution and which do not, with the approving contact named.
• Build quantity, attrition allowance and the ownership of surplus material.
• Consigned versus supplied material, with the incoming inspection responsibility stated.
• Programming, functional test and reporting requirements.
• Version number, change history and the revision of the design that is being built.

A purchase order containing those items produces a comparable quotation and an audit-friendly record. It also removes the most common cause of mid-build negotiations.

What the Supplier Should Report Back

The value of a kitting process is only realised if its findings reach the customer. A useful material report states what was ordered, what arrived, what was short, what was substituted and against which approval.

It should also flag the lines that carry risk for the next build: parts with long lead times, parts approaching end of life, and parts where the purchased quantity exceeded the build by a margin that will affect the next purchase. That information is what allows a design team to plan a redesign deliberately rather than respond to one.

Where the batch includes programming and functional testing, the same report should state what was programmed, what was tested and what the failure disposition was. Ordering PCBA testing together with the assembly keeps those records in one document instead of separating the manufacturing story from the verification story.

Finally, the report should identify the revision that was actually built. That single line is what makes a later investigation possible and turns a supplier relationship into something that can be managed with evidence.

FAQ

Who should approve a substitute part? The design owner, in writing, against a stated set of acceptable parameters. A supplier can propose, but the approval belongs to the customer.

How is incoming material verified? By inspection appropriate to the part and the risk, from a visual and dimensional check on connectors to a counterfeit assessment for high-value semiconductors bought outside authorised channels.

What should happen to leftover components? Agree in advance whether they are stored for the next batch, returned or scrapped, and how they are identified if they are kept.

Can kitting be done without a frozen design? Yes, as a risk review, but material should not be committed against a revision that is still changing.

Summary

Component sourcing is where a design meets the real supply chain, and BOM kitting is the process that keeps the meeting orderly. Resolve every line to an orderable part, define the alternates with their critical parameters, start the material review before the design is frozen, and record which revision was built. A partner whose quality management system treats that record as part of the build, rather than as paperwork around it, is the one that makes repeat production predictable, whether the next order is a low volume PCB assembly run or a full production release.