BOM
The BOM tab lets you import, edit, and enrich Bill of Materials data. It supports BOM groups, AI-powered enrichment, multiple manufacturers per line, customer-provided component tracking, and live pricing integration via the Elexess API.
BOM line list
The left panel shows all BOM lines with:
- References – component designators (C1, C2, R1, etc.)
- Description – component description
- Type badge – SMD, THT, or MNT
- Quantity – reference count with board multiplier (click to edit inline)
- Unit price and total – from pricing data when available
Click any line to open its detail pane on the right.
BOM groups
Organize BOM lines into named groups (e.g., Passives, ICs, Connectors) for easier navigation and review.
- Create a group – click the + button in the toolbar
- Rename a group – double-click the group header
- Delete a group – click the trash icon on the group header (lines move to the ungrouped section)
- Assign lines – drag and drop BOM lines onto a group header, or use the group dropdown in the detail pane
- Collapse/expand – click the chevron on a group header to toggle visibility
- Reorder – drag and drop lines within and across groups
Spark AI enrichment
When Spark AI is enabled in Team Settings, Gerbtrace can suggest improvements for BOM data using AI. Click the sparkles button in the toolbar to enrich all lines.
The AI analyzes each BOM line and may suggest:
- Description – standardized formatting (e.g., "MLCC 100nF 50V X7R 0402")
- Type – SMD, THT, Mounting, or Other classification
- SMD classification – Fast, Slow, Finepitch, or BGA
- Manufacturer – primary manufacturer name and part number
- Second source – alternative manufacturer suggestion
- Group – suggested group name for the line
Suggestions appear as highlighted fields in the detail pane. For each suggestion you can:
- Accept – apply the suggestion to the BOM line
- Dismiss – remove the suggestion without applying it
- Accept all – apply all pending suggestions for the line at once
Lines with pending suggestions show a sparkles icon in the table.
Filters
Quick-filter buttons in the toolbar:
- SMD / THT – filter by mounting type
- DNP – Do Not Populate components
- CP – customer-provided components
- Long Lead – items flagged as structurally long lead (see Long lead items)
- No Mfr – lines missing a manufacturer
- No Price – lines without pricing data
- Missing PnP – lines with no matching PnP reference
Each filter shows a count badge indicating how many lines match.
Long lead items
Some components are structurally long lead — their procurement time is a property of the commodity class itself, not of current market conditions. Typical examples are custom cables and harnesses (often 8+ weeks build-to-order), custom-wound transformers and inductors, factory-programmed parts, and custom-marked devices.
Lines flagged this way get an amber Long Lead pill in the BOM list and a matching badge in the detail pane. Hover the pill to see why it was flagged.
There are two ways a line gets flagged:
- Imported from the BOM file. Add a
Long Lead(orLead Time Risk) column to your BOM. Values can beYes/No/True/False/1/0, or a free-form note like12 week vendor quote— see the BOM File Format reference for the full list of recognised header names. - Auto-detected at import time. When no column is present, Gerbtrace runs a conservative heuristic against each line's description and comment to flag obvious structurally long-lead items (cables, harnesses, custom magnetics, programmed parts, custom marking).
You can always override either source from the detail pane: toggle Long Lead on or off and add a short reason note (e.g. Custom 12-week harness, vendor confirmed). Manual edits persist across re-imports.
The flag is intentionally limited to structural lead times. Market-driven shortages and allocation cycles change too quickly to track on the BOM itself — use the distributor lead times that come back with Supplier pricing for that.
Quantity tiers
The quantity selector at the top sets the production quantity. Multiple quantity tiers can be added (e.g., 10, 50, 100, 500, 1000). Pricing calculations update for each tier. Remove tiers with the X button or add new ones by typing in the input field.
Detail pane
Clicking a BOM line opens the detail pane with editable fields:
- Description and Comment
- Type (SMD, THT, Mounting, Other)
- Package footprint name
- Customer Item number
- Qty / board count
- Customer Provided and DNP toggles
- Long Lead toggle and reason note – flag structurally long-lead items (see Long lead items)
- References – add or remove component designators
- Group – assign the line to a BOM group
Fields that differ from the original customer BOM are visually highlighted.
Manufacturers
Each BOM line can have multiple manufacturer entries. Each entry includes:
- Manufacturer name
- Manufacturer part number (MPN)
- Refresh pricing button
- Remove manufacturer button
Click + Add manufacturer to add alternatives.
Supplier pricing
When the Elexess API is configured in Team Settings, Gerbtrace fetches live distributor pricing for each manufacturer part number. Expand the suppliers section under a manufacturer to see:
- Supplier name (Weltron, Anglia, Abacus, TME, LCSC, Farnell, etc.)
- Stock – available quantity
- MOQ – minimum order quantity
- Unit price – per-component cost
- Total – extended price for the selected quantity
The best price is highlighted in green. In the BOM line list, each priced line shows the supplier of its best in-stock offer next to the unit and line price; hover the name to see the full supplier and country. Click Fetch Prices in the toolbar to fetch pricing for all lines at once. A progress bar shows the pricing queue status. Use the refresh button on individual manufacturers to update pricing for a single MPN. The pricing age is displayed next to each supplier result.
Copy CP List
The Copy CP List button in the toolbar header copies a formatted list of all customer-provided component references to the clipboard. This is useful for sending to the customer to confirm which components they need to supply.
Compare revisions
When the customer sends a new BOM, click Compare revisions in the toolbar to see which lines, designators, MPNs and quantities changed, export the changes, and replace the project BOM with the new file. See BOM Revisions.
Pull from the ERP
Newmatik teams can take a project's BOM straight from an approved BOM in the Newmatik ERP instead of exporting and uploading a file. The ERP BOM menu in the toolbar shows up only for teams the ERP connection is enabled for, in team projects you can edit.
- Pull from ERP BOM… – enter the ERP item code of the assembly (for example
ITM-0017B-01B-DE-S). When the project name gives the assembly (ITM-0017B-01B-DE), the field starts with its step BOM, and an item of another assembly of the same PCB (ITM-0017B-01C-…) is refused: add that one as a variant. Gerbtrace reads the item's default approved BOM: designators, item codes, quantities, packages, customer-provided parts and every approved MPN. A step BOM that contains an earlier step of the same board brings that step's parts too: pulling…-DE-STlists the SMD parts of its…-DE-Sboard with the THT parts, quantities per finished board. Other sub-assemblies with their own BOM, such as a cable or a second board, stay one line. A project without a BOM file gets it as the fileERP BOM <name>.tsv. If the project already has a BOM file, Compare revisions opens with the ERP BOM as the new revision, so you see what changes before you replace it. - Refresh from ERP – pulls the same item again. If nothing changed, Gerbtrace says so. Otherwise the comparison shows the added, removed and changed designators and parts, and Replace BOM with this revision applies them.
The project remembers which ERP BOM and revision its BOM came from; hover the ERP BOM button to see it.
Assembly variants
A team project is one PCB revision, for example ABC-0001A: its Gerber data, drill files, pick-and-place data and drawing setup. The base project is the board's first assembly (ABC-0001A-01A in a project named ABC-0001A-01A-DE): its BOM (pulled from the ERP in this tab), its drawing and its approval live on the base, and a project with one assembly has no variants. Further assemblies of that board (-01B, -02A) are added as variants in the same project, so you don't upload and set up the board again for each of them. A new PCB revision (ABC-0001B) still needs its own project: see Copy as new PCB revision.
Each variant has its own BOM. It doesn't need a BOM in the Newmatik ERP: you can start from the project's BOM or a file and pull the ERP BOM later. The variant menu next to the project name switches between the base project and its variants. It names the base project by its assembly code when the project name has one (for example Base (ABC-0001A-01A)), else by the PCB code.
Add another assembly (under Manage variants…) refuses the base project's own assembly code: pull its BOM in the BOM tab instead. It offers three sources:
- From the project BOM – the variant follows the project's own BOM as it changes. What differs in the variant (another value, item code or MPN, a part left out) you set as overrides.
- Empty or from a file – the variant gets its own BOM: upload a BOM file (CSV, TSV or Excel, read like a BOM import), or start empty, where every placement is DNP until you add parts as overrides.
- From the ERP – enter the item codes of the variant's step BOMs, for example
ABC-0001A-01B-DE-S, ABC-0001A-01B-DE-ST, and Gerbtrace pulls their approved BOMs. A variant that lists only a later step, for exampleABC-0001A-01B-DE-STwithout-DE-S, also gets the parts of the earlier step of the same board from that BOM, as in the BOM tab; when you list both steps, each step's parts come from its own BOM and are listed once. Only for teams with the ERP connection.
For the first two, enter the variant code (ABC-0001A-01B) or its step item codes; step item codes are kept for the drawing and a later ERP pull. Item codes are checked the same way for every source: a code with another revision letter, or an ERP BOM whose PCB line is another PCB item, is refused with "new PCB revision: copy the project instead". Before you save, Gerbtrace lists the placements that become DNP and the BOM designators without a placement.
- DNP is derived – a placement that isn't in the variant's BOM isn't fitted in that variant. A designator in the BOM without a placement is an error: fix the designator (for example
U$1instead ofU1) before the variant can be approved. Two exceptions, for parts fitted by hand: Mounting lines (screws, standoffs) need no placement, and an Other line (a cable, a label) needs none once you confirm it with Confirm fitted by hand in the variant list or under Fitted by hand in the overrides. Other lines need the confirmation because a BOM imported without a Type column makes every line Other. - What changes – while a variant is shown, the canvas, the SMD and THT tabs and the exports use its BOM: DNP, value (the ERP item name or the BOM description), item code and MPN per designator. Assembly images, pick-and-place exports, assembly layouts, the ERP Assembly Specification and the assembly drawing are named after the variant and its site, for example
ABC-0001A-01B-DE_Assembly-Image-TOP_full.pngand the assembly drawingsABC-0001A-01B-DE-S_Assembly-Drawing.pdfandABC-0001A-01B-DE-ST_Assembly-Drawing.pdf(one per step, each stamped with the variant's ERP BOM of that step). PCB images and PCB data keep the project name. The BOM tab shows the variant's BOM read-only. - Packages – a part is drawn with the package outline of its item in the variant's ERP BOM (the ERP's Package Outline linked from the Item), so a designator that is a different part in one variant gets that part's package without a mapping. When the item has no outline, or no package library of the part's type (SMD or THT) has exactly that name or alias, the part keeps the package of its CAD footprint (its mapping, name or aliases). The variant's BOM view lists each line's outline, and the package's tooltip in the SMD and THT tabs says when it comes from the item. Outlines are read when the BOM is pulled or re-pulled; a variant pulled before this has none until its next re-pull.
- Overrides – a variant can force designators to DNP although its BOM lists them, set a rotation per designator (for example for a different MPN in the same footprint), set a package per designator as
R12=0603(for this variant only; it wins over the item's outline and the footprint), give a designator another part, one per line asR12: R 10k 0603 | item code | manufacturer | MPN(trailing fields can be left out), and list the Other lines fitted by hand. A part override also fits a designator the BOM leaves out; one with another item code drops the outline of the line it replaces. The step item codes are edited here too. - Processes – a variant can set its own process settings (electrical test, coating with its material and sides, inspection, soldering, depanelization) on the Assembly tab while it is shown. What it doesn't set follows the project.
- Re-pull – pulls the variant's ERP BOMs again and shows the added, removed and changed designators before you apply them. For a variant from the project BOM or its own BOM, Pull ERP BOM fetches the BOMs of its step item codes and compares them with what the variant shows now; applying makes the ERP BOM the variant's BOM, drops its part overrides and keeps the DNP and rotation overrides. A variant with its own BOM can also take a new file with Upload BOM, again with the differences shown first.
- Approval – each variant is approved on its own, by a team admin or the project's selected approver, in the toolbar's workflow menu while the variant is shown: the menu always acts on what is shown, the variant (its button reads e.g. TLG-0066B-01A · Draft) or, with the base shown, the base project. Manage variants shows each variant's status. Approve checks the shown drawing first: a variant with a BOM designator without a placement, or with a fitted part that has neither a library package nor pads on the board (the drawing would show only a small placeholder box), or with a fitted part drawn with a team package that was proposed to the ERP and is still a Draft there, cannot be approved until that is fixed. Drawings made after the approval print the approver's initials (from their profile) and the approval date in the title block; a stale drawing does not. Re-pulling, uploading or changing the overrides, process settings or step item codes of an approved variant marks its drawing stale, and so does a change to the project BOM for a variant that follows it. A change to the shared data (a rotation fix, a replaced Gerber file, placements, PCB or panel data) marks the drawing of every approved variant stale. Approving again clears the flag; Reopen (same menu) returns a variant to draft, and only a draft variant can be deleted. While a variant is shown, the menu names the base project's status; show the base to request, approve or reopen the base project.
While a variant is shown, the BOM tab is read-only. The SMD and THT tabs stay editable for the placements, which all variants share: add a placement the pick-and-place file lacks (Add Item, for example diodes the customer left out or a THT part without pick-and-place data), move or rename one, set its rotation, polarity, group or note, or delete it. These edits change the base project and every variant, and mark the drawings of approved variants stale. What belongs to the variant stays with it: DNP follows its BOM (force DNP in its overrides), the value comes from its BOM, a part's package comes from its item or its package overrides, and a designator with a rotation override keeps that rotation. Other shared data (Gerber files, PCB and panel data) is edited on the base project.
Copy as new PCB revision
A new PCB revision (ABC-0001A → ABC-0001B) gets its own project. On the dashboard, editors use the Copy as new PCB revision button on a viewer team project: enter the new PCB code (Gerbtrace suggests the next revision letter) and the project name, which takes the new code.
- Copied – the files, the pick-and-place corrections (rotations, DNP, packages, manual parts, groups and sort order), the project BOM, the PCB, panel, paste and coating data, PCB notes and fiducials, the ERP Assembly Specification data, the import settings, the assembly drawing settings and the uploaded documents. The PCB code in the assembly drawing settings (title block, notes) is changed to the new revision.
- Variants – copied with the new PCB code in their item codes and step item codes (
ABC-0001A-01BbecomesABC-0001B-01B), except a variant with the base project's own assembly code (from before the base became the first assembly), which is left behind; pull that assembly's BOM onto the new base. Copied variants keep their overrides, process settings and drawing settings, but not their BOMs: pull or upload each variant's BOM again. A variant that follows the project BOM keeps following it. - Not copied – the workflow state, assignee and approvals (the copy starts as an unassigned draft, and its variants as drafts), the conversation, the generated assembly drawings, the 3D model and its renders, the preview image and the record of the ERP BOM pull.
- New files – the Gerber, drill and pick-and-place files are copied so the project opens with the old board, and marked "replace with revision B". The new project shows a bar listing them until each one is removed or its content changed: import the new revision's files, then remove the old ones. Editors can close the bar with Done.
Sorting
Use the Ref and Price sort buttons to order BOM lines by designator (alphabetical) or by total cost (highest first, to identify cost drivers).
BOM and PnP cross-referencing
When both BOM and PnP data are loaded, Gerbtrace surfaces mismatches:
- References in BOM but missing from PnP
- References in PnP but missing from BOM
- Quantity discrepancies
The Missing PnP filter highlights lines with cross-reference issues. A warning badge also appears in the detail pane for affected lines.
Lock
The Unlocked / Locked toggle prevents BOM line edits, manufacturer changes, and pricing fetches. Use this in team projects when the BOM has been verified and approved.