IoT Device Manufacturing in China: A Practical Build Guide

IoT Device Manufacturing · PCBA + RF · Enclosure · Firmware Flashing IoT Device Manufacturing in China: A Practical Build Guide What an IoT device actually is — sensor, MCU, radio and enclosure — and how it gets built, flashed, tested and shipped through a Dongguan EMS with no MOQ and CNC in the same facility. Request a quoteSee services What an IoT device actually is An IoT device is four subsystems wired into one box: a sensor that reads the physical world, an MCU that processes and decides, a connectivity block that moves data to the cloud, and an enclosure that protects all of it and lets the radio signal through. Most sourcing problems come from treating these as one part instead of four, since each has its own DFM rules, test plan and failure modes. The build follows that same split. You design a PCB that carries the MCU, the power tree and the radio, place the wireless module and its antenna, drop it into an enclosure that is sealed but RF-transparent, flash firmware onto the MCU, and pair it to the cloud so it proves the full loop before it ships. Miss any one and the device is a paperweight — a sealed metal enclosure kills a radio, a flashed-but-unpaired device fails at the customer's kitchen table, and an untested RF stage fails certification. The bill of materials: what actually goes into an IoT device An IoT BOM is small in line count and dense in risk. The typical device carries fewer than a hundred components, but every one of them sits on a critical path. Sensor or actuator. Temperature, humidity, motion, pressure, light, current, or a switch and relay on the actuation side. This is the reason the product exists, so it is specified first. MCU. The brain — an Arm Cortex-M or a low-power wireless SoC. It reads the sensor, runs the logic and manages sleep, which is where battery life is won or lost. Connectivity. A discrete module (ESP32, nRF52, cellular modem) or a SoC with the radio on-die. Modules carry their own approval, which shortens the path to market. Power. A battery, a regulator and a charging or energy-harvesting path. Power architecture decides the enclosure size more than the PCB does. Passives and connectors. The decoupling caps, crystals, antennas and programming headers that make the rest work. Enclosure and mechanicals. Housing, gaskets, buttons, light pipes, mounting — the parts that turn a board into a product a person can hold and install. The sourcing lesson is that the BOM is not a shopping list, it is a dependency map. The sensor drives the MCU choice, the MCU drives the module, the module drives the antenna and the antenna drives the enclosure. A partner who manages the whole BOM — not just the PCB — is the difference between a build that fits and one that fights itself. PCB design and fabrication for IoT The IoT PCB is a mixed-signal board wearing a radio, and the layout rules are unforgiving. The RF section needs a clean ground plane and short, impedance-controlled traces; the antenna needs a keep-out zone free of copper and components; the power section needs decoupling close to every rail. Run a switching supply trace under the antenna and you have raised the noise floor and lost range before the first unit is built. Fabrication follows the board's class. A four-layer stack — signal, ground, power, signal — is the default for anything with a radio, because a solid internal ground plane is both the return path and the shield that keeps digital noise out of the RF. Controlled impedance on the antenna feed is standard, and the fab spec should state it explicitly rather than assume it. We build these boards to IPC standards for fabrication and assembly, so the board is manufacturable and inspectable, not just correct on a schematic. Component placement is where most first-pass IoT boards go wrong. The module, the antenna, the crystal and the switching supply all want the same quiet corner of the board, and one of them has to lose. The rule of thumb: keep the antenna at the edge with its keep-out, keep the crystal away from heat and flex, and keep the switching regulator as far from the RF front end as the outline allows. A DFM review at EVT catches these conflicts while a change is still a redline instead of a respin. RF modules, wireless chips and antenna integration The radio is the part that separates an IoT device from a generic PCB, and it is also the part that is easiest to get subtly wrong. Most teams use a pre-certified module — an ESP32, an nRF52, a LoRa or cellular modem — rather than a bare chip, and for good reason: the module vendor has already done the tricky RF layout, matched the antenna, and obtained the modular approvals that shorten your own certification path. Antenna choice is the next fork. Three options dominate: PCB trace antenna. Etched into the board — cheap, zero BOM cost, but sensitive to enclosure metal and hard to tune after the fact. Chip or ceramic antenna. A small SMT part — consistent, compact, but needs a ground plane and a proper keep-out. External antenna. A whip or a pigtail through the enclosure — best performance, at the cost of a hole, a seal and a connector. The decision is driven by the enclosure, not by preference. A plastic enclosure with a plastic face lets a trace or chip antenna radiate; a metal enclosure forces the signal out through a window or onto an external antenna. This is where building the enclosure and the board under one roof pays off, because the RF engineer and the mechanical engineer are looking at the same model instead of exchanging emails about it. The enclosure: DFM for RF and sealing The enclosure is where most IoT products either succeed quietly or fail loudly, because it has to do three contradictory jobs at once. It has to protect the board from water, dust and impact; it has to let the radio signal through; and it has to fit the battery, the antenna and the connector with real tolerances. RF transparency is the one that catches people. Metal is an RF shield — a full aluminum enclosure is a faraday cage unless you leave an aperture, route the antenna outside, or use a plastic window. Plastic is RF-transparent but weak and thermally poor. The practical answer is usually hybrid: a plastic shell with a metal frame for strength, or an aluminum body with a plastic or glass window over the antenna. Gaskets matter too — an IP-rated seal that closes a metal lid over the antenna just re-shields the signal it was meant to protect. Sealing and ingress protection follow the deployment. An indoor sensor needs IP42 and a gasket; an outdoor tracker needs IP65 or IP67, with a sealed connector, a pressure vent and a conformal-coated board. Each step up the IP ladder adds a gasket, a test and a cost, so specify the rating the product actually needs and prove it with a test, not a label. The DFM rules: decide the RF window before the material, the seal before the fasteners, and leave the antenna a keep-out in the mechanical model as well as the layout. Firmware flashing and cloud pairing A device that leaves the factory unflashed or unpaired is not finished — it is a kit that your customer assembles in the field, badly. Flashing and provisioning are manufacturing steps, and they belong on the production line, not in the customer's hands. Firmware flashing writes the application image to the MCU. It can be done at the panel level, at ICT, or end-of-line, and it needs to be repeatable and logged. Every unit should carry a known firmware version and a unique identifier — usually a MAC address or a serial burned into the flash or read from a secure element. Flashing is not just "program the chip"; it is the moment the device stops being a board and becomes a specific, traceable unit. Cloud pairing is the step most people forget to plan. The device has to claim its identity with your cloud — provision its keys, register its serial, and complete at least one message round-trip — before it ships. Doing this at the factory means every unit is verified end-to-end: the sensor reads, the MCU processes, the radio connects, the cloud receives. Doing it in the field means the first power-on is a support ticket. The production flow we run is: flash → test → provision → verify the round-trip → seal → ship. The provisioning step is where a device earns its "connected" label. Connectivity choices: WiFi, BLE, LoRa and cellular The radio technology is a product decision, not a manufacturing decision, but it sets the manufacturing and test plan, so it deserves a seat at the sourcing table. Four protocols cover most of the IoT landscape, and they solve four different problems. TechnologyTypical rangePower drawData rateBest fit WiFi30–50 m indoorHighHighMains-powered hubs, cameras, gateways BLE10–30 mVery lowLowWearables, beacons, phone-paired sensors LoRa / LoRaWAN1–15 kmLowVery lowSmart meters, agriculture, long-range telemetry Cellular (LTE-M / NB-IoT)KilometersLow–moderateLowFleet tracking, asset monitoring, remote sensors The choice ripples into the build. WiFi and BLE are cheap to test with a standard radio test set; LoRa and cellular need the right carrier bands and, in the case of cellular, a SIM or eSIM provisioning step at the factory. Battery-powered devices push you toward BLE or LTE-M, where a device sleeps and sips current; mains-powered devices can afford WiFi's appetite. Pick the protocol before the module, the module before the antenna, and the antenna before the enclosure — the order is not negotiable. Testing: RF, functional and environmental An IoT device is proven at three layers, and a build is not done until all three pass. A device that works on the bench and fails on a roof did not pass the test it actually needed. Test layerWhat it verifiesTypical methods RFRadiated power, receiver sensitivity, antenna match, emissionsVNA, spectrum analyzer, OTA chamber, pre-compliance scan FunctionalMCU boot, sensor read, radio link, cloud round-tripBed-of-nails, automated bench, end-of-line script EnvironmentalTemperature, humidity, vibration, ingressThermal cycling, HALT, IP-rated sealing test RF testing confirms the radio actually radiates and receives at the right level and does not splatter emissions across the band. A pre-compliance scan early in DVT is the cheapest insurance in the program, because it catches the emission that would fail a certification lab before you have paid for the chamber time. Functional testing proves the product logic end to end — boot, sense, transmit, receive. Environmental testing proves it survives the world it will live in. The three are not interchangeable; a device that passes RF and functional but fails a thermal cycle will still come back as a field return, just later. Certifications context: FCC and CE, handled per market Certification is the part of an IoT program where honesty is worth more than a logo, because the cost of a wrong claim lands in a customs hold or a rejected filing, not in a warranty drawer. FCC applies to the United States, CE to Europe, and each market has its own emissions, radio and safety rules that a device must meet before it can be legally sold there. Here is what we claim, and what we do not. We do not claim FCC or CE certification on our own letterhead, and we will not stamp a device with a mark it has not earned for that specific program. Certification is handled per the customer's market requirements — we build the device to the design that will be submitted, support the pre-compliance RF testing that makes the filing likely to pass, and work with the customer's qualified lab or partner for the actual approval. The device you design for FCC Part 15 or the CE Radio Equipment Directive is the device we build; the certificate itself belongs to you and your market, and we keep our claims inside that line. The practical move is to plan certification into the schedule from the first day — pick a pre-certified module where you can, run pre-compliance at DVT, and freeze the RF design before PVT so the lab does not test a different device than the one you are shipping. Supply chain: sensors and modules in China One quiet advantage of building an IoT device in China is that the entire component chain is a few hours' drive from the assembly line. The Pearl River Delta — where our Dongguan facility sits — is dense with the exact suppliers an IoT BOM depends on: sensor vendors, module makers, antenna manufacturers, connector houses and the enclosure shops that turn a board into a product. That proximity does two things. It shortens lead time on the long-pole items — a custom antenna or a specific sensor is not crossing an ocean mid-build, it is coming across town. And it keeps the BOM honest, because the assembler is not importing the very parts it is assembling. The risk to manage is the flip side: a deep supply chain rewards a partner who holds vendor quality, incoming inspection and a disciplined BOM, because cheap availability is not the same as reliable availability. Counterfeit or out-of-spec parts flow through loose channels, and a gray-market radio module fails in ways that are expensive to trace. Vetting the supplier matters as much as vetted part numbers — which is the point of a QA-managed EMS rather than a broker. The Nex-G anchor: EMS and CNC under one roof Most IoT builds split across two vendors — an EMS for the board and a machine shop for the enclosure — and the integration risk lands in the gap between them, where the antenna does not clear the lid and the gasket does not seat. Nex-G closes that gap because the electronics and the enclosure come out of the same facility, managed by one BOM and one quality system. The electronics side is EMS: PCBA and SMT, box build, testing and firmware flashing, run through EVT → DVT → PVT with no MOQ — we build from one unit to mass production. The mechanical side is CNC: 80+ machines holding ±0.005 mm on standard work and ±0.002 mm on precision work, with critical characteristics held to Cpk ≥ 1.67. That means the enclosure you model is the enclosure we machine, and the board you route is the board we place — same roof, same revision, same RF engineer looking at both. The anchor is our Dongguan Hengli facility — 6,800 m², 100+ staff, building since 2006. Quality runs on ISO 9001, IATF 16949 (build-to-print — design excluded under clause 8.3) and ISO 14001, with URS certification through 2027. Lead times run roughly 3 days for a prototype, 7 for a small batch and 30 for production, with MOQ of one. An IoT device is the textbook case for why that integration matters: the board and the box have to agree on the antenna, and when they are made in the same building, they do. EVT → DVT → PVT: how we get you to production An IoT device does not jump from CAD to a container; it walks through three gates, and each gate exists to catch the failure the last one could not see. EVT — engineering validation. Does the design work at all? A small run proves the schematic, the layout and the RF stage, and the first enclosure proves the fit and the antenna window. Changes here are cheap and expected. DVT — design validation. Does it work reliably and pass? The design is frozen enough to test against spec — RF pre-compliance, thermal, ingress — and the DFM issues are resolved while the tooling is still moving. PVT — production validation. Can we make it repeatably? The production line, fixtures and test scripts are validated on real tooling, and the yield and the Cpk prove the process, not just the prototype. We run all three gates on the same line that builds production, so the process you validate at PVT is the process that ships your units — no handoff to a different factory with different habits. With no MOQ, EVT is a handful of units, not a thousand-unit commitment, which is exactly what a hardware founder needs before the demand curve proves itself. Read the full EVT → DVT → PVT breakdown. Frequently asked questions What is your MOQ for IoT devices?One unit. We build from a single prototype through mass production with no MOQ, so EVT and DVT runs get the same documentation and process as the production line. Per-unit cost is higher at low volume because setup and procurement are near-fixed. Do you provide FCC or CE certification?We do not claim FCC or CE certification on our own letterhead. Certification is handled per your market requirements — we build the device to the design that will be submitted, support pre-compliance RF testing, and work with your qualified lab for the approval. The certificate is yours. Can you build the enclosure and the electronics together?Yes — that is the point of the model. EMS (PCBA, SMT, box build, testing, firmware flashing) and CNC machining run in the same Dongguan Hengli facility, so the board and the enclosure share one BOM and one RF review. Antenna placement and sealing are checked against the same mechanical model. Do you design IoT hardware?No — we are build-to-print. We manufacture to your design and hold IATF 16949 with design excluded under clause 8.3. We do provide DFM feedback on antenna placement, enclosure sealing and manufacturability, so your design survives the transition from CAD to production. Do you flash firmware and pair devices to the cloud?Yes. Flashing and provisioning are production-line steps for us: we write the application image, burn or read the unique ID, provision the device to your cloud, and verify a message round-trip before the unit ships. Every unit leaves traceable and connected. What CNC tolerances can you hold on the enclosure?±0.005 mm on standard work and ±0.002 mm on precision work, with critical characteristics held to Cpk ≥ 1.67. That is tight enough for a sealed enclosure with a precise antenna window and a consistent gasket groove. What quality certifications do you hold?ISO 9001, IATF 16949 (build-to-print, design excluded under clause 8.3) and ISO 14001, with URS certification through 2027. Boards are built to IPC standards for fabrication and assembly. What are your lead times?Roughly 3 days for a prototype, 7 days for a small batch and 30 days for production, with the enclosure machined in parallel with the board so neither becomes the long pole. Ready to build your IoT device with one partner for the board and the box?Send the BOM, the schematic or just the enclosure model — we will quote the PCBA, CNC enclosure, flashing and testing as one build.Request a quote Related articlesTurnkey Electronics ManufacturingElectronics Prototype ManufacturingCNC Machining Housings & Enclosures