How Do You Know Which Manufacturing Batches Were Built With the Previous Hardware Revision?

A hardware revision changes for many reasons. A component becomes obsolete, a supplier changes, a better alternative is introduced, or an engineering team identifies a reliability issue.

The new revision gets approved and production moves forward. But one question remains:

Which manufacturing batches were built with the previous hardware revision?

The Current BOM Doesn't Tell the Whole Story

Your current BOM tells the team what the product should be using today. It doesn't always tell you what was actually used in production six months or a year ago.

For that, the team needs to connect engineering revisions with manufacturing history.

You may need to find:

• Which BOM revision was active during a specific production period
• Which component revision was used
• Which manufacturing batches were produced with it
• How many units were built in those batches
• Which serial numbers belong to those units
• Where those devices were shipped or deployed

When these records are maintained across spreadsheets, ERP systems, production documents, and separate engineering tools, finding this information can become a manual investigation.

When a Component Changes

Imagine a critical component is replaced because the original part is becoming obsolete.

The engineering team releases a new hardware revision. Production starts using the replacement component.

A few months later, the original component is discovered to have a reliability concern.

Now the team needs to determine whether the issue affects every device or only products manufactured before the change.

The important questions become:

• Which batches used the original component?
• How many units were produced from those batches?
• Which serialised devices came from them?
• Are those devices still in the field?
• Are there existing complaints, RMAs, or failures associated with them?

Without batch-level traceability, teams may have to manually compare old BOMs, production records, and device information before they can even begin the investigation.

Why Manufacturing Batch History Matters

A hardware change doesn't stop at the engineering release.

The previous revision may already exist in hundreds or thousands of manufactured devices. Some may be sitting in inventory, some may have been shipped, and others may already be operating in the field.

Knowing the manufacturing history helps teams quickly identify the affected population and make better decisions around:

• Quality investigations
• Field failures
• Product recalls
• Rework and replacement
• Warranty analysis
• Supplier issues
• Component obsolescence
• Engineering changes

It also helps avoid unnecessarily treating every device as affected when the issue is limited to specific production batches.

What Hardware Teams Should Be Able to Answer

When someone asks, “Which products were built with the previous revision?”, the answer shouldn't require searching through multiple files and systems.

The team should be able to quickly determine:

Which revision was used, when it was used, which batches were affected, and which devices came from those batches.

That historical context becomes especially important when products have multiple variants, contract manufacturers, production locations, and frequent engineering changes.

From Engineering Change to Physical Product

A revision number in an engineering system is only one part of the story.

Hardware teams also need visibility into how that revision moved into manufacturing and which physical products were ultimately built with it.

S3Suite helps connect BOM revisions, components, manufacturing records, batches, and serialised devices in one product history.

So when a hardware change happens, teams can understand not only what changed, but also which products were built before the change and may still be affected today.