What is box build assembly? The process, explained
Box build assembly is the assembly of a finished, enclosed product — the stage where a populated circuit board stops being a board and becomes a unit someone can power on. It covers everything above bare board assembly: mounting the PCBA, display, power supply, and wiring into an enclosure, routing and dressing the harness, loading firmware, labeling, and, in many scopes, functionally testing the whole thing before it ships. The term gets used loosely across the contract manufacturing industry, and it can mean anything from fitting hardware into a chassis to full system integration with burn-in and custom packaging. This guide defines what box build includes, draws the line between it and PCB assembly, walks the process steps in order, sorts out the levels, and lists what a manufacturer needs from you to quote one.
Box build assembly, defined — and what's usually in it
The name is literal: you are building the box. Box build assembly — also called box-build, final assembly, system integration, or higher-level assembly — is the operation that takes finished sub-assemblies and turns them into a complete, enclosed, shippable product. It ends with a unit in its final housing, carrying its final labels, that has, in many scopes, been powered up and checked against a written pass/fail standard.
A typical box build scope pulls together most or all of the following: the enclosure (sheet metal, machined, injection-molded, extruded, or modified off-the-shelf); one or more PCBAs; a display and its operator interface — a touchscreen, or a membrane switch, keypad, or graphic overlay; a power supply, converter, or battery pack; internal wire harnesses and cable assemblies; panel-mount connectors and hardware; fasteners, standoffs, gaskets, and thermal interface material; self-clinching inserts, which appear on the BOM but commonly arrive already installed by the enclosure fabricator; heat-set inserts are sometimes fitted at assembly instead; the firmware image; serial, rating, and compliance labels; and the packaging and printed documentation the unit ships in.
What box build is not is design. A contract manufacturer running a box build works to your drawings, your BOM, and your test specification. It may push back on tolerances, fastener access, connector choice, or assembly sequence through a DFM review — that feedback is worth having — but the product remains yours. The same applies to code: firmware is loaded as a production step, and it stays the customer's intellectual property. A manufacturer that offers to write your firmware or design your circuit from a blank sheet is offering a different service, sold separately, and you should price it as such.
Box build vs PCB assembly: where one ends and the other begins
PCB assembly (PCBA) is the population of a bare board: solder paste through a stencil, SMT placement, reflow, then wave, selective, or hand soldering for any through-hole content, cleaning where the flux system requires it — most modern lines run no-clean flux and skip a wash — AOI, and board-level electrical test, whether in-circuit, flying probe, or a boundary-scan routine. The deliverable is a tested board, in a tray or on a rail, with nothing around it.
Box build begins when that board is installed into something. One way to draw the line: PCB assembly ends when the board passes its board-level test; box build starts at the first operation that joins the board to another part of the product. Everything downstream of that join — enclosure integration, cabling, display mounting, firmware, labeling, final functional test — is box build.
There is a grey zone, and it is a common source of quoting confusion. Heatsink attach, conformal coating, connector potting, board-to-board jumper cables, and press-fit hardware get quoted on either side of the line depending on the shop. So does first-article inspection. None of that matters as long as you know which line item covers it, so read the quote for scope rather than assuming a convention.
The two also price differently. PCBA is typically quoted per board with setup and NRE for the stencil and the pick-and-place program, and cost is driven by placement count and part difficulty. Box build is quoted per unit, and in a turnkey scope the purchased material is normally the largest single share of that unit price; the conversion cost — what the manufacturer adds on top of materials — is driven by labor minutes and test time. Mechanical complexity, fastener count, harness routing, and how long the functional test runs matter as much as how many boards are inside. That is one argument for buying both from the same supplier: when a finished unit fails final test, the investigation sits with one party rather than being split across two.
The box build process, step by step
The sequence below is the common order of operations. Names vary between shops; the operations do not.
Step 1 — Kitting and sub-assembly prep. Components are pulled against a BOM locked at a named revision and inspected on receipt (IQC), with sampling and criteria agreed in advance. Parts the manufacturer buys are purchased from franchised or approved sources and inspected incoming; parts you consign are checked for count and visible damage on arrival, but no contract manufacturer can warrant the authenticity of material it did not buy. Boards, displays, harnesses, and enclosure parts are staged as a kit per unit or per lot. A first-article or golden sample stays at each workstation as the visual reference. Electronic handling runs under ESD control from this point forward — grounded mats, wrist straps, ESD-safe bins and packaging.
Step 2 — Mechanical integration. The enclosure is prepped (inserts, gaskets, standoffs, light pipes), then the PCBA, display, power supply, and any sub-chassis are mounted. Fastening is torque-controlled to the spec for each joint — the value follows from fastener size and from both mating materials, not from a blanket shop setting — and sequenced so nothing gets trapped behind a part installed too early. Display mounting is a decision of its own: an air-gap stack behind a cover lens with anti-glare, anti-reflective, or anti-fingerprint coating is a common approach for indoor and general industrial equipment, and coating choice is driven by ambient light and whether the operator wears gloves.
Step 3 — Cable and harness routing. Harnesses are cut, crimped, and assembled to a wire list, then routed along a documented path with service loops, strain relief, and tie-down points, clear of heat sources, sharp edges, and moving parts. Connectors are seated until the latch is confirmed. Crimps are pull-tested to sample. The workmanship standard for cable and wire harness assemblies is IPC/WHMA-A-620. It is prescriptive for a reason: intermittent field faults traced back to a pinched conductor or a half-seated connector are a familiar failure mode, and they are expensive to find once the unit is closed.
Step 4 — Firmware loading and configuration. The customer's firmware image is programmed at a dedicated programming station or fixture, and the image version is recorded against the unit's serial number. This step often also carries calibration, MAC address or unique-ID injection, region or feature configuration, and license key writing. The code is loaded, not written, and the IP does not change hands.
Step 5 — Labeling, serialization, and marking. Serial and UID labels, rating labels, regulatory marks, and any customer asset tags are applied to the positions shown on the drawing. Barcodes or data-matrix codes are scan-verified rather than eyeballed, because an unreadable label is a return.
Step 6 — Final QC and functional test. Units are powered up and run against a written Go/No-Go checklist: the specific inputs, the expected outputs, and the tolerance on each. Depending on the product this can include hipot and ground bond for mains-powered equipment, ingress checks on sealed units, burn-in, and calibration verification. Cosmetic and dimensional inspection is commonly sampled to an AQL plan (ANSI/ASQ Z1.4), while functional test is commonly 100% where the specification calls for it. The output is a record — an OQC report tied to the lot — followed by pack-out to the packaging spec.
Levels of box build: from a populated enclosure to a tested system
"Box build" describes a range of scope, not a fixed package, and the range is wide enough that two quotes both labelled "box build" can cover very different amounts of labor.
Basic — mechanical box build. Enclosure population and mechanical assembly only. Hardware fitted, brackets and boards mounted, cover closed. Electrical work is minimal, and verification is visual and dimensional rather than functional. It is the lightest tier, and it is easily misread as the whole service.
Intermediate — electro-mechanical integration. A common middle ground, and what many buyers mean by box build: mechanical assembly plus power, display, internal harnessing, firmware loading, labeling, and a functional power-on test against defined criteria. The unit ships ready to run.
Full system integration. Multiple sub-assemblies or multiple enclosures brought together — cabinets, racks, remote panels — with calibration, burn-in, automated test with logged per-unit data, serialization, custom or retail-ready packaging, and often direct fulfillment to the end destination.
One warning that will save you money: there is no industry-standard numbering for these tiers. Some suppliers say Level 3 / Level 4 / Level 5 assembly, others say Class 1/2/3, others invent their own. The words carry no guaranteed meaning across companies, and they should never be confused with IPC-A-610 acceptability classes, which describe workmanship standards for electronic assemblies rather than assembly scope. Ask for scope written line by line in the quote — which operations, which tests, which inspections, what documentation ships with the goods.
What a manufacturer needs from you to quote a box build
In a turnkey box build, purchased material is normally the largest single share of the unit price, and labor and test are the conversion cost added on top. The manufacturer can only estimate what it can see, so the completeness of your data package determines how firm the number is.
Electrical. Gerbers describe the bare board only — copper layers, solder mask, silkscreen, drill — so they are not enough to assemble anything on their own. ODB++ is an intelligent format that can also carry component data, but it is often supplied as fabrication data only, so confirm what yours contains. Assembly also needs the centroid or pick-and-place file, with XY position and rotation for each placement, and a BOM in CSV or XLSX with manufacturer part numbers, approved alternates, and any consigned parts flagged. Assembly drawings, test point locations, and programming header details if they exist.
Mechanical. STEP files for the enclosure and the major mechanical parts, plus 2D drawings carrying the tolerances that actually matter, finish, color, texture, and any cosmetic surface callouts. A fastener schedule if you have one.
Interconnect. The wire list or harness drawing: connector part numbers and pinouts, wire gauge and color, lengths, sleeving, and label text. This is a commonly missing document, and its absence is a frequent cause of a quote that moves after the first build.
Software. The firmware image, how it is loaded (JTAG, SWD, USB, bootloader), any fixture required, and the calibration or configuration procedure that goes with it.
Test. The Go/No-Go criteria in writing — what is measured, expected values, tolerances, and what happens to a failing unit. This is commonly under-specified. If "pass" is not defined, the test step cannot be priced and cannot be repeated consistently from unit to unit.
Commercial. Prototype and first-article quantities, the initial production order, and an estimated annual usage; the target market and its compliance regime; labeling and serialization requirements; the packaging specification; and whether you want turnkey (the manufacturer buys the whole BOM) or consigned (you supply some or all parts). Many programs land in between, which is fine as long as the split is itemized line by line in the quote.
Partial packages are normal. Send what exists — a manufacturer that works this way should quote on what it has and tell you plainly which line items are estimates until the gaps close.
Where Essen fits
Essen Industries is an American-led box-build contract manufacturer built on Taiwan's electronics ecosystem. It manages full electronic box builds — enclosures, PCB assemblies, displays, and cabling — engineered, assembled, and functionally tested in Taiwan for US hardware OEMs, with an American point of contact.
A few things stated plainly, because they are the questions a hardware director asks early. Essen manages and is accountable for production across its own team and vetted specialist partner facilities; it does not own the machines or the lines. Those production facilities in Taiwan operate under ISO 9001:2015 quality management systems. Electronic assembly is to IPC-A-610 Class 2 acceptability. Firmware is loaded in production and remains entirely your IP — Essen does not write it, and does not design circuits from a blank sheet. Turnkey, consigned, and partial BOM splits are all workable, and the split is itemized line by line in the quote.
If you are scoping a build, the box-build service page lists the operations covered and what ships with the goods. If you already have files, send the data package — or whatever stage it is at — through the RFQ form; DFM review comes back before you commit to anything, and Go/No-Go test criteria are agreed in writing before production starts.
Frequently asked
What is box build assembly?
Box build assembly is the assembly of a finished, enclosed product — the stage above bare board assembly where the PCBA, display, power supply, and internal wiring are integrated into an enclosure, firmware is loaded, the unit is labeled, and, in many scopes, it is functionally tested before shipping. It is also called final assembly, system integration, or higher-level assembly.
What is the difference between box build and PCB assembly?
PCB assembly is the population of a bare board — solder paste, SMT placement, reflow for surface-mount parts, then wave, selective, or hand soldering for through-hole content, AOI, and board-level test — and its deliverable is a tested board on its own. Box build begins at the first operation that joins that board to something else: the enclosure, a display, a harness, a power supply. In short, PCB assembly ends when the board passes board-level test; box build starts when the board goes into the product.
What are the steps in the box build process?
The common order is: kitting and sub-assembly preparation against a BOM locked at a named revision; mechanical integration of the PCBA, display, and power into the enclosure with torque-controlled fastening; cable and wire harness routing to a documented path with strain relief and seated connectors; firmware loading and configuration; labeling, serialization, and compliance marking; and final QC with a functional test against written Go/No-Go criteria, followed by pack-out.
What are the levels of box build assembly?
Broadly three. Basic box build is enclosure population and mechanical assembly with little or no electrical test. Intermediate electro-mechanical integration adds power, display, harnessing, firmware loading, and a functional power-on test — this is what many buyers mean by box build. Full system integration adds multiple sub-assemblies or cabinets, calibration, burn-in, logged automated test, serialization, and custom packaging or direct fulfillment. Level numbering is not standardized across suppliers, so confirm scope in writing rather than relying on the label.
What do I need to send to get a box build quote?
Gerbers or ODB++ plus the centroid file for the boards — Gerbers describe the bare board only, so a board cannot be assembled from them alone; a BOM with manufacturer part numbers, approved alternates, and consigned parts flagged; STEP files and 2D drawings for the enclosure with tolerances and finish callouts; a wire list or harness drawing with connector pinouts; the firmware image and how it is loaded; written test pass/fail criteria; and your quantities, target market, labeling, and packaging requirements. Partial packages are normal — a manufacturer should quote on what exists and flag which items are estimates.
Does a box build manufacturer write my firmware?
Generally no. Firmware loading is a production step: the manufacturer programs your image at a dedicated station and records the version against the unit's serial number. The code and its IP remain yours throughout. Firmware development and circuit design from a blank sheet are separate engineering services, sold separately, and should be priced that way.
What drives the price of a box build?
In a turnkey scope, where the manufacturer buys the BOM, purchased material is normally the largest single share of the unit price. On top of that sits the conversion cost — labor minutes and test time — which is driven by mechanical complexity, fastener count, harness routing, and how long the functional test runs. That is why a quote should itemize material, labor, and test separately, and why turnkey, consigned, and partial-BOM splits produce very different-looking numbers for the same product.
Is box build assembly the same as contract manufacturing?
Box build is one service within contract manufacturing, not a synonym for it. A contract manufacturer may offer PCB assembly, component sourcing, box build, test, and fulfillment as separate or combined scopes. Box build specifically refers to the higher-level assembly that produces the finished, enclosed unit.
Sourcing HMI hardware? Send a drawing.
Every quote comes back with DFM notes and a delivered USD price — one US vendor of record, parts made in Taiwan.