A time-based BOM navigator built for ERP data.

BOM scroller is a local web tool for exploring how a Bill of Materials (BOM) evolves over time. It does not compare static version snapshots. Instead, it reconstructs BOMs from a data source and compares them visually.

The goal is:

Understand what changed, where, and when — in a way that matches how BOMs actually behave in real systems.

Change highlight for parts that are: added / removed / replaced / qty changed

Green indicates the current version

• Fast navigation across many revisions
• Rapid review of BOM changes
• Clear visual overview of structural changes
• For teams that currently export to Excel or manually compare versions

Built for:

• date-effective ERP data
• human understanding, not raw diff output

Under the hood, BOMs are reconstructed from a row-based ERP model where each row is defined by:

• SKU
• item group (structural position in the BOM)
• part number
• quantity
• validity period (from_date / to_date)

Rows are aligned using a structural key (item_grp), not by part identity.

This means:

• comparisons follow the structure of the BOM, not the part numbers
• part replacements appear as in-place changes at the same position
• new parts appear as local insertions into the existing structure

The BOM can be rebuilt at any point in time directly from the data model, without relying on stored snapshots.

This approach assumes that BOM structure is stable over time and evolves incrementally. For a detailed explanation of the underlying design and assumptions, see BOM assumptions

pip install flask
python app.py

Then open:

http://127.0.0.1:5000

bom-diff
→ Upload and compare two BOM files (Excel/CSV)

BOM Compare Tool (Sierra Circuits)
→ Upload BOM files and highlight added/removed/changed parts

Excel BOM Comparer
→ Compare two revisions directly in Excel

eg. OpenBOM, NetSuite tools, ERPNext BOM compare

These allow comparing BOM revisions inside a system, typically:

• select BOM A
• select BOM B
• view differences

BOM scroller takes a different approach:

• No file upload
• No “compare A vs B”
• No static snapshots

Instead:

→ Scroll through BOM versions over time, directly from ERP data

This is a concept prototype.

The focus is on:

• data model correctness
• visual clarity
• realistic BOM behavior

Not production readiness.