BuildTrace
Start free

Every unit you ship, traced from part to field.

For hardware companies tired of bending their ERP to fit how they build. Each serial keeps how it was built, with BOM revision, change orders, component lots and test results, in the same record as the firmware it runs in the field.

BuildTrace
PRODUCT
Parts & Revisions
BOMs
Change Orders
OPERATIONS
Inventory
Build Orders
Serials
Quality
FIELD
Devices
Firmware
Recalls

Your build record and your fleet record never meet.

Your supplier reports that MCU lot L-2291 is bad. To find the units to fix, you need to know which shipped units contain that lot and what firmware each one runs. The first answer lives in your ERP, a FileMaker app or a spreadsheet, the second in your OTA tool.

PLM / MRP
Knows how it was built
SN-HUB3-004127
RevisionRev C
MCU lotL-2291
End-of-line test14/14 pass
Firmware todaynot in this tool
Where it isnot in this tool
OTA platform
Knows what it runs
SN-HUB3-004127
Revisionnot in this tool
MCU lotnot in this tool
End-of-line testnot in this tool
Firmware today2.3.9
Where it isCustomer A, online
BuildTrace
One record per serial
SN-HUB3-004127
RevisionRev C
MCU lotL-2291
End-of-line test14/14 pass
Firmware today2.3.9
Where it isCustomer A, online
Affected: has L-2291 and runs firmware older than 2.4

BuildTrace runs that check on every shipped unit in one query. See the recall query

Released revisions are locked.

To change one, you open a change order with a BOM diff and get it signed off. Every unit built afterwards records which change order it was built under.

ECO-031 · Hub 3 Rev B to Rev CApproved 2 of 2
RefRev BRev C
C14CAP-10U-0603CAP-22U-0805
U3MCU-0142 r1MCU-0142 r1
ENCENC-14 r1ENC-14 r2
BO-1187 · 40 × Sensor Hub 3Unit 27 of 40
Step 6 of 14
Fit radio module, scan its serial
RM-88213Matches BOM line RM-12 r3
Consumed so far: MCU-0142 from L-2291, PCA-220 from stock

The record fills itself in on the line.

Operators follow the build steps on screen and scan each part as they fit it. Stock moves through a ledger, so you can trace every lot to the units it went into.

Shipped units check in to the same record.

Each device reports its firmware with its own token. You publish releases per component, such as the main MCU and the radio, and every update lands in the unit's history next to how it was built.

Sensor Hub 3 · firmware in the field
ReleaseStatusDevices
2.4.1Released212
2.3.9Superseded41
2.3.7Superseded9

Your devices talk to BuildTrace with one HTTP call.

A device reports what it runs and gets back what it should run. Your own updater downloads and verifies the file, so you keep whatever transport you already have.

API reference (OpenAPI)Device check-in guideAnything you can do in the web app, you can do through the API, with permissions per role.
Using a coding agent?Read https://dev.buildtrace.eu/llms.txt and add a BuildTrace check-in to our firmware update task.

A supplier flags lot L-2291. Which units are affected?

Filter by what went into a unit and what it runs now, in one query. From the result, open a recall or a service order for each unit.

contains lot = L-2291 firmware < 2.4.0 status = in field
SerialRevFirmwareShippedCustomer
SN-HUB3-003981C2.3.72026-07-30Customer A
SN-HUB3-003994C2.3.72026-07-30Customer A
SN-HUB3-004012C2.3.92026-08-04Customer B
3 units

EU Cyber Resilience Act

If you sell connected hardware in the EU, you will need a machine-readable SBOM and a record of which software went onto which product. BuildTrace already keeps that per serial, so you can export it.

11 Sep 2026Vulnerability reporting obligations
11 Dec 2027Full requirements, including SBOM and technical documentation

Pricing

Start free and pay per serial as you ship more. Team and Scale cover both the factory and the field.

Free
One product, getting started
Starter
Production runs
Team
Production and a fleet in the field
Scale
Several products or sites
PriceFree[PRICE] / month[PRICE] / monthOn request
Serials included[N][N][N]By agreement
Extra serialsNo[PRICE] per 100[PRICE] per 100By agreement
Parts, BOMs, change ordersYesYesYesYes
Build orders, inventory, qualityYesYesYesYes
Devices and firmware releasesNoNoYesYes
Recalls, service, SBOM exportNoNoYesYes
SSO and custom rolesNoNoNoYes
Start freeStart freeStart freeContact us

What teams like yours would pay

400 units a year, about 250 in the fieldTeam, [PRICE] / month
3,000 units across two productsTeam, [PRICE] / month incl. extra serials
10,000 units across several products and sitesScale, on request

No surprise bills

You set a monthly cap on extra serials. We email you at 80% and never charge past it. [CONFIRM POLICY]

Monthly billing, cancel any time. Your data exports as CSV and JSON whenever you want it. [CONFIRM]

We're looking for [N] design partners.

BuildTrace is new. We would rather build it with a few hardware companies who ship real units than guess. Design partners get [DISCOUNT] off for the first year, a direct line to the people building it, and a say in what we build next.

You should be building serialized hardware in production, with firmware you update in the field, and an ERP that was never made to track it. Applications close [DATE].

Apply as a design partner[Founder name], [role] at Erbo

Try it with one of your own BOMs.

Export your parts and BOMs from Exact, Odoo or FileMaker as CSV, import them, run a small build order and open the first serial. Free up to [N] serials, no card needed.