Per-unit cost
PCBA Only Lower headline
Programmed, Tested, Serialized Higher headline, lower total ownership cost
Compare
PCBA Only vs Programmed, Tested, Serialized Electronics
Some products ship as bare boards to a downstream integrator. Others ship as finished, programmed, tested, serialized units. For connected electronics that go directly to end users or to large OEMs, integrated production often saves cost and field-failure risk that a bare board cannot.
At a glance
| Criterion | PCBA Only | Programmed, Tested, Serialized |
|---|---|---|
| Per-unit cost | Lower headline | Higher headline, lower total ownership cost |
| Field-flashed firmware risk | Buyer absorbs | Eliminated |
| Provisioning consistency | Buyer absorbs | Per-unit verified in production |
| Per-unit identity | Buyer assigns later | Assigned and logged in production |
| Test coverage | AOI only | AOI plus FCT against test plan |
| CRA and SBOM readiness | Buyer compiles separately | Production data feeds SBOM and traceability |
Field-flashed firmware risk
PCBA Only Buyer absorbs
Programmed, Tested, Serialized Eliminated
Provisioning consistency
PCBA Only Buyer absorbs
Programmed, Tested, Serialized Per-unit verified in production
Per-unit identity
PCBA Only Buyer assigns later
Programmed, Tested, Serialized Assigned and logged in production
Test coverage
PCBA Only AOI only
Programmed, Tested, Serialized AOI plus FCT against test plan
CRA and SBOM readiness
PCBA Only Buyer compiles separately
Programmed, Tested, Serialized Production data feeds SBOM and traceability
When to choose PCBA Only
- Bare boards go to a downstream integrator who handles flash, test, and label
- Product is uncomplicated, no firmware, no per-unit identity, no field-failure cost
When to choose Programmed, Tested, Serialized
- Connected device that needs cloud trust on first boot
- Product where field-flashing is operationally expensive or risky
- Product under CRA, RED, or customer security scrutiny
- Product where field-failure cost is high and FCT pays back quickly
Hybrid approach
Mid-volume connected devices often start PCBA-only during prototyping and switch to programmed-tested-serialized production once firmware stabilizes. The programmed-tested workflow then becomes the default for repeat production.
Decision FAQ
Can you load and provision firmware in production?
Yes. In-line firmware loading during functional test and offline programming via dedicated fixtures. We support SWD, JTAG, UART, and USB-DFU interfaces, multi-image programming (bootloader, application, file system), and signed bootloader chains.
Do we need a written test plan?
Yes. A production test plan defines pass and fail criteria, FCT vectors, calibration steps, and serialization rules. We help draft one if your team has not written one yet, based on your firmware behavior and target field performance.
How do you serialize and label units?
Per-unit MAC, UID, and serial number assignment with GS1 DataMatrix or QR labels. Polyimide or polyester label stock based on environmental requirements. Every label is logged against board lot, firmware hash, and test result for full traceability.
Talk through your specific case
Different products land in different places on these trade-offs. Send a short description and we will help scope what fits.