A finished electronics product may require PCB fabrication, component purchasing, PCBA, firmware programming, cable or antenna installation, enclosure preparation, final assembly, functional test, serial labels, packaging, and shipment preparation. A supplier may say “turnkey” while including only some of those steps.
The sourcing task is therefore to make the complete deliverable visible before comparing factories or prices.
1. Search for the right supplier type
| Supplier type | Useful when | Typical boundary to confirm |
|---|---|---|
| PCB / PCBA service | You can manage enclosure, firmware, final assembly, and test | Whether programming, fixture work, or mechanical assembly is included |
| Low-volume EMS | You need controlled electronics purchasing, assembly, programming, and test | Whether it accepts the quantity and supports non-PCB work |
| Box-build partner | You need assembled products rather than boards | Enclosure, cable, label, packaging, and final-test responsibility |
| Product-development firm | Design, firmware, DFM, or integration is still unfinished | Engineering fees, file ownership, handover, and production responsibility |
A company does not need every process under one roof. It does need to disclose subcontracted work, control incoming parts, approve changes, and own the final deliverable.
2. Freeze one build revision
Do not send candidates a folder of mixed prototypes and ask for a finished unit. Name one release and identify every file that controls it.
- PCB package: Gerbers or ODB++, drill files, stack-up notes, BOM, centroid or pick-and-place file, assembly drawing, and approved alternates.
- Firmware package: production binary, version, programming interface, keys or credentials boundary, programming instructions, and verification step.
- Mechanical package: enclosure CAD and drawings, finish, inserts, fasteners, cable routing, connector positions, adhesive, and assembly order.
- Product identity: serial-number rule, labels, artwork, regulatory marks if applicable, and traceability requirement.
- Packaging package: unit accessories, protective materials, printed items, carton configuration, warehouse labels, and destination requirements.
If files are still changing, call the build a pilot and price engineering changes separately. A production-style unit price cannot absorb an undefined design.
3. Turn “it works” into a test procedure
The buyer should define what the supplier must prove before shipment. Separate board-level checks, programming verification, product-level function, and visual inspection.
- Incoming control: identify critical components, enclosure finish, and customer-supplied parts.
- PCBA checks: inspection, power rails, shorts, programming access, and any required electrical test.
- Functional test: user actions, interfaces, radio or connectivity behavior, charging, sensors, indicators, and failure states relevant to the product.
- Final assembly check: cable routing, torque or fastening method, gaps, orientation, labels, and cosmetic limits.
- Pack-out check: correct firmware version, serial number, accessories, packaging, quantity, and shipping label.
Define the result record: a pass label, serial-number log, measured values, photos, or another agreed form of evidence. “QC included” is not a test plan.
4. Release a pilot before the remaining units
A controlled pilot exposes missing files, ambiguous assembly steps, programming problems, enclosure variation, test time, and packaging errors. Approve a golden sample or written deviation list before releasing the remaining quantity.
The pilot is not only a product test. It is a test of whether the supplier can follow the package, report uncertainty, request decisions, and preserve revision control.
5. Ask for a quote that exposes the real scope
| Quote section | What should be separated |
|---|---|
| Engineering / NRE | DFM, file cleanup, programming setup, fixture design, assembly instructions, pilot support |
| Materials | PCB, electronic parts, enclosure, cables, fasteners, labels, packaging, excess material |
| Recurring work | PCBA, programming, mechanical assembly, test, rework allowance, pack-out |
| Logistics | Delivery term, freight, export packing, destination, tax or duty boundary |
| Uncertainty | Assumptions, exclusions, proposed substitutions, dependencies, quote validity |
Also define who owns unused components, custom fixtures, programming tools, source files, packaging inventory, and rejected units. These details become important when the next build changes or moves.
6. Qualify behavior, not only equipment
- Does the supplier identify missing information before quoting?
- Does it name which processes are in-house and subcontracted?
- Can one project owner explain the complete build flow?
- Are substitutions and deviations approved in writing?
- Can the supplier return a traceable pilot result and failure list?
- Does the handover package remain usable if the relationship ends?
For a low-volume build, the safest “yes” is not the fastest one. It is the one that makes the remaining unknowns visible.
A minimum 50-unit box-build RFQ
- Context: product use, current stage, target market, destination, and required timing.
- Controlled release: one named PCB, firmware, enclosure, and packaging revision.
- Build scope: customer-supplied versus supplier-procured items and every required process.
- Pilot plan: pilot quantity, approval owner, deviation handling, and release rule for the balance.
- Acceptance plan: inspection points, functional tests, evidence, cosmetic limits, and failure handling.
- Commercial template: NRE, materials, recurring work, logistics, assumptions, exclusions, and ownership.
Frequently asked questions
Can a Shenzhen supplier build only 50 finished units?
Some low-volume EMS, box-build, and integration teams can support this stage. Fit depends on design maturity, purchasing, testing, enclosure work, packaging, and unresolved engineering—not quantity alone.
What files should I send?
Send controlled PCB and assembly files, BOM, firmware programming instructions, enclosure and assembly drawings, test procedure, labels, packaging, quantity, destination, and acceptance criteria.
Must everything be in one factory?
No. A useful integrator may coordinate specialist suppliers. Require disclosure, one accountable owner, controlled substitutions, incoming checks, and final acceptance evidence.
How should I compare quotes?
Normalize the product revision, component basis, engineering, fixtures, programming, assembly, test, packaging, logistics, assumptions, exclusions, ownership, and rework terms.
Clarify the box-build route and missing RFQ inputs.
Send your current product revision, quantity, and required finished-unit scope. Aixumo can help identify the supplier type, pilot sequence, quote boundaries, and next sourcing step.