How to Audit a Box Build Manufacturer Before a PO

Quick answer: Audit a box build manufacturer against the actual product scope: PCB assembly, harnesses, enclosure integration, firmware, functional test, traceability and shipment. Ask for a process flow and evidence for each step, including which operations are in-house and which are subcontracted. A convincing supplier can connect the released files, work instructions, test limits and finished-unit records to the same order and revision.

Define the box-build scope before comparing suppliers

“Box build” can mean anything from fitting a PCBA into an enclosure to delivering a configured, tested system. List the mechanical parts, cables, labels, firmware, accessories, packaging and final acceptance tests. Clarify who owns design changes, procurement, tooling, software keys, test fixtures, repair, returns and regulatory documentation. A single purchase order does not guarantee that every task is done inside one factory.

How to verify real production capability

Ask the supplier to walk through a representative build of comparable complexity, from incoming inspection to pack-out. Check the equipment and skills needed for your product, not a generic equipment list. For cables, ask how continuity, pinout, strain relief and mating are checked. For enclosure work, examine torque control, ESD protection, labeling and visual criteria where applicable. If a process is subcontracted, ask who qualifies and audits that partner and who owns deviations.

Review mechanical and electrical fit before release

Compare the PCB outline and mounting holes with the current enclosure drawing, connector orientation, cable bend radius, fastener access, thermal path and service space. A 3D interference review can reveal some conflicts, but it does not replace a physical first article or validated tolerance stack. Record each open issue and approval in the controlled product file. Do not attach a generic percentage of “clashes prevented” or “rework saved” to this step without project records.

Treat firmware and system test as controlled operations

If the manufacturer programs units, define the approved image and version, authorized access, serial-number link, verification result and failed-flash recovery. The final test should reflect how the customer will accept the delivered system. PCB-level electrical test alone cannot prove a complete assembled unit, but not every product needs burn-in or environmental stress. Select those tests through product risk analysis, customer requirements and an agreed protocol; do not promise a universal failure-reduction rate.

Which certifications and standards should you ask about?

Start with the product, destination market, customer contract and regulatory role. Ask for certificates and scope only where they are relevant to the work being purchased. ISO explains that ISO 13485 certification itself is not a blanket legal requirement; medical-device obligations depend on the product and the legal manufacturer’s quality system. IPC-A-610 is an electronic assembly acceptance standard, not a supplier-wide quality certificate. Do not assume QueenEMS holds a particular certificate without verifying the current certificate, issuing body, site and scope.

Questions for the purchase-order review

• Which parts, process steps and tests are included in the quoted unit price?
• Who supplies and owns the enclosure, harnesses, firmware and test fixtures?
• What records link each finished unit to BOM, firmware, lot and test result?
• How are deviations, substitutes and design changes approved before build?
• What is the first-article sample and release gate before the full order?
• Which certificates or registrations apply to this product and this supplier site?

For a related decision about buying bare boards or complete assemblies, see bare PCB supplier versus turnkey PCBA. This audit framework is not a promise of a fixed lead-time reduction, yield result, or customer case; obtain current, order-specific evidence from each candidate manufacturer.