Linking Bills of Materials to products and projects

Associate Bills of Materials with products and projects for better tracking.

Why linking BOMs matters

A Bill of Materials becomes far more useful when it’s linked to the right Product or Project. Instead of existing in isolation, the BOM becomes part of the larger operational context: what product it belongs to, which project it supports, and how teams should reference it.

Linking BOMs ensures:

  • Product teams know which BOM defines each assembly
  • Project managers can track what materials a project depends on
  • Procurement teams know which BOM is relevant when orders are raised
  • Everyone works from the same, single, authoritative source

This guide walks you through how to link BOMs to Products and Projects using the Laminar UI.

Where BOM linking happens

Linking happens directly inside the BOM Detail Page.

To reach it:

  1. Open the BOM using Global Search, or
  2. Go to the BOMs module and select the BOM you want to manage

Once the page loads, you’ll see designated fields or sections for:

  • Product (optional)
  • Project (optional)

If your organisation uses both modules, these fields appear clearly near the top of the detail view.

Tip You can link a BOM during creation or anytime afterward—both methods work exactly the same.

Linking a BOM to a Product

Products represent higher-level items that your organisation manufactures or sells. Linking a BOM to a Product allows your Product team to keep track of which assemblies belong to which finished good.

How to link

  1. Navigate to the BOM Detail Page
  2. Click Edit
  3. Look for the Product field
  4. Start typing the product name
  5. Select the correct match from the dropdown
  6. Click Save

Once saved:

  • The BOM becomes part of the product’s structure
  • Global search will show relationships
  • Product-level reports can reference the BOM
  • Users viewing the product can see its linked BOMs

Tip Use clear names for products to avoid mixing up similar items. For example: “Smart Charger – V3” instead of “Charger”.

When to link a BOM to a Product

Link a BOM when:

  • A new product is released and needs a manufacturing breakdown
  • A prototype matures into a production-ready version
  • A revision of a product uses a new or updated BOM
  • Multiple sub-assemblies belong to one final product

You can link one BOM to one Product. If a product has many sub-assemblies, each may have its own BOM, and each can individually link to the same product.

Linking a BOM to a Project

Projects represent workstreams—internal builds, client initiatives, prototypes, rollouts, or testing cycles. Linking a BOM to a project helps project managers and engineers understand what materials are required and where the effort stands.

How to link

  1. Open the BOM’s detail page
  2. Click Edit
  3. Find the Project field
  4. Search for the correct project by name
  5. Select it from the dropdown
  6. Save your changes

After saving:

  • The BOM becomes part of that project’s scope
  • Teams reviewing the project can see associated BOMs
  • It helps track consumption of materials
  • Useful for planning and reporting

Note A BOM can link to a Product and/or a Project. These are independent associations.

When to link a BOM to a Project

You should link a BOM to a Project when:

  • The BOM is part of a specific build or initiative
  • A testing cycle or prototype needs material tracking
  • You want to support project costing or planning
  • A project spans multiple BOMs and you want everything consolidated

This helps project teams stay aware of what materials are involved.

Working with linked BOMs

Once a BOM is linked, the detail page shows the associations clearly. Typical UI indicators include:

  • A Product name with a link to its page
  • A Project name with a link to its page

You can click these to explore related items instantly.

During editing

You can always:

  • Change the linked product
  • Switch to a different project
  • Remove the link entirely (by clearing the field)

Changes apply immediately on save.

Why linking improves workflows

At the Product level

Product managers can:

  • Track which BOM defines the product
  • See all sub-assemblies in one place
  • Prepare better documentation
  • Understand revisions and dependencies

At the Project level

Project managers can:

  • Track materials needed for the project
  • Ensure procurement knows what to order
  • Estimate costs more accurately
  • Avoid missing items during assembly or testing

For procurement and operations

Your operations team benefits from linked BOMs because:

  • They can trace requirements quickly
  • Ordering becomes easier with the right Bill of Materials
  • Miscommunication reduces dramatically

For organisation-wide consistency

Linking creates a single source of truth. Everyone knows which BOM is the correct one for each initiative or product.

Editing or removing links

You can update or remove links anytime:

To update

  1. Click Edit
  2. Choose a new product or project

To remove

  1. Click Edit
  2. Clear the field (delete text or choose “None”)
  3. Save

Removing a link does not delete the product, project, or BOM. It simply unlinks them so they no longer reference each other.

If you cannot find the Product or Project in the dropdown

This usually happens when:

  • The record exists in another organisation
  • You misspelled part of the name
  • You lack permission to view that product/project
  • The item hasn’t been created yet
  • The project is archived (in future versions)

Try:

  • Searching with fewer letters
  • Checking your organisation via the avatar menu
  • Asking an admin if you should have access

Tip If the product or project’s name is long, enter a unique keyword instead of matching exact phrases.

Best practices

  • Create a BOM first, then link it to a product or project—this keeps creation clean
  • Use versioned BOM names (Rev A, Rev B) and link only the active version
  • Link BOMs as soon as they’re created to avoid confusion across teams
  • Confirm that your product naming scheme is clear and consistent
  • Only link BOMs to projects that actively use them
  • Keep product and project lists organised so linking remains intuitive

These habits help maintain system-wide clarity and avoid mistakes in procurement and planning.

Common issues

“The Product/Project field is empty.”

You may not have access to these modules or your organisation doesn’t use them yet.

“The BOM shows a linked product but the product page doesn’t list it.”

Refresh both pages. If still mismatched, the product may not support reverse linking yet (future enhancement).

“I changed the product but search still shows the old association.”

Search indexing may take a brief moment. Refresh and try again.

“My BOM isn’t showing inside the project.”

Ensure it’s saved properly and that you’re in the correct organisation.

Related guides