One list
The workbook is suitable while one owner can review the whole flat structure.
Editable Excel BOM template
Download a clean, working XLSX with a populated component list, explicit units and calculated material cost. Use it to define one product structure; move to Jodoo when revisions, variants and release decisions need to stay connected.
Sign in to inspect fictional sample records. Copy the app before adapting it to live product data.
Workbook preview

| Field | What good data looks like | Why it matters |
|---|---|---|
| Finished item and revision | One stable item identifier and an explicit revision. | The list can be tied to the product definition it describes. |
| Component item | A reusable identifier plus a reader-friendly description. | Teams can trace usage even when descriptions change. |
| Quantity and unit | A number that means the same thing to engineering, purchasing and production. | Ten millimetres must not be interpreted as ten pieces. |
| Unit cost | A known value, or blank when it is genuinely unknown. | A missing price should not quietly look like a zero-cost material. |
| Notes or specification | Only context that affects selection or use. | A component line stays understandable without a separate email thread. |
When the file reaches its limit
The workbook is suitable while one owner can review the whole flat structure.
Separate variants need their own current revision and comparable component differences.
A release needs review tasks, returned corrections and a traceable update to the exact product record.
The Jodoo example retains the same useful facts but gives them explicit relationships and lifecycle states. It complements the workbook; it does not pretend the XLSX is a workflow engine.
Practical questions
Identify the finished item and revision, then record each component number, description, quantity per assembly, unit of measure and source or cost information needed for the task. Add notes for approved substitutions or specifications rather than hiding them in email.
No. This download deliberately keeps one parent and one component list so it stays easy to inspect. Use the multi-level BOM workbook when subassemblies must be exploded and rolled up.
A blank unit cost remains unknown; it is not converted into a genuine zero-cost component. Complete or explicitly exclude those values before relying on the material total.
Move when several people edit the structure, variants need separate revisions, reviews must be assigned, or teams need a dependable current-versus-draft distinction. The workbook is a useful starting asset, not a controlled release system.
Yes. Copy the example and adapt component fields, revision states, review responsibilities and views. Keep stable item identifiers and test the release rule before importing live structures.