YIVAHUBShenzhen Hardware: Design Houses, Board Fabrication and the Certification Route
2026-11-09 · YIVAHUB Team
Shenzhen is the head of the electronics chain rather than the hands. The assembly happens an hour up the road in Dongguan and Huizhou; what sits here is the design layer, the board layer and the component market, and those three are what a buyer is actually purchasing when they develop a connected product in this city.
A solution house sells you a reference design, not a factory service, and that changes what you own. The layer that makes Shenzhen distinctive is the design house that has already solved your product category: it holds a working schematic, firmware, a mobile app and a tested radio module, and it will adapt that platform to your enclosure and your requirements in weeks rather than developing from nothing. What you are buying is time and de-risking, and it is genuinely the right purchase for most first products. What you are not buying is a design that belongs to you.
The commercial shapes of a design house deal decide your margin for the product's life, so negotiate them deliberately. There are three common structures. A non-recurring engineering fee plus a per-unit price, where you pay once for the adaptation and then buy boards. A per-unit royalty on top of the hardware price, which is cheaper up front and more expensive at volume. And a turnkey price where the design house keeps the intellectual property and sells you finished units, which is the simplest to start and the hardest to leave. Ask which one you are being offered, ask who owns the schematic, the firmware source and the app, and ask what happens to your product if the design house stops trading, because in the turnkey shape the answer is that your product stops with it.
The structural risk of a reference design is that it is not only your reference design. If three other brands are shipping the same platform with a different case, your differentiation is the case and the brand, and your competitor's firmware bug is your firmware bug. That is an acceptable trade for a first product and a poor one for a flagship. The way to manage it is to ask, before you sign, how many other customers ship this platform, and to specify which parts of the design must be exclusive to you, if any.
Board fabrication is fast and cheap in layers and slow in specifications, and the specifications are where it goes wrong. A two or four layer board in prototype quantity is a matter of days, with an expedite option measured in hours, and the panel minimum is small enough that a hundred boards is a normal order. What is not fast is getting the specification right: the base material, the copper weight, the surface finish, and whether the board needs controlled impedance because it carries a radio. A radio board made on the wrong stack-up will pass assembly and fail range tests, and no amount of debugging finds it quickly. Specify the stack-up with the fabrication order rather than leaving it to the board house.
On assembly, the question that matters is who buys the components. A board assembler that sources the bill of materials for you is convenient and opaque: you cannot see the component margin, and you cannot see substitutions. An assembler that works to a bill of materials you supply and control is more work for you and considerably more transparent, and it is the shape to insist on for anything you intend to sell at volume. Ask for the bill of materials with manufacturer part numbers, the distributor it was bought from, and the date code on the reel, and keep that record. When a part goes on allocation, the buyer who controls the bill of materials is the one who can redesign around it.
The component market is a prototyping tool, not a production channel, and treating it as production is how counterfeits enter a product. Huaqiangbei is unmatched for finding a specific chip in small quantity, for obsolete parts, and for arming a prototype in a week. It is also a market where parts are re-marked, where a lower grade is sold as a higher one, and where nothing is traceable to a manufacturer. The discipline that works is simple and absolute: market purchases are for prototypes only, and every production order buys from an authorised distributor with a traceable chain. The cost difference is real and it is small compared to the cost of a field failure.
Certification is per model and per market, and there are two specific shortcuts worth designing for. In the United States, an unintentional radiator is tested under the general emissions rules while a device with a radio is tested as an intentional radiator and receives an identifier; a mains-powered product also needs safety certification to the applicable equipment standard. In the European Union the electromagnetic compatibility directive applies, a radio product falls under the radio equipment directive, and a mains product falls under the low voltage directive, with a technical file behind the marking. The United Kingdom has its own mark, and most other markets have their own radio approval. The two shortcuts are these. Using a radio module that already holds modular approval lets you inherit much of its certification rather than testing a radio from scratch. And keeping one hardware platform across a product family, changing only the enclosure, can let several models ride on one certification — which is a design decision, not a paperwork one.
Battery certification is a schedule item that stops shipments rather than a formality. A product with a lithium cell needs transport testing before it can be shipped by air, and the cell itself needs its own safety certification, which is separate again from the finished product's certification. Each is weeks of testing and each is a hard gate: goods without the transport documentation do not board the aircraft, regardless of how well the product performs. Put both on the development schedule next to the enclosure tooling, not after it.
Write five things into the agreement, and the rest of the project becomes ordinary. The bill of materials with manufacturer part numbers and the requirement to buy from authorised distribution. Ownership of the schematic, the firmware source and the app, or an explicit statement that you are licensing them and on what terms. Which party holds the certification and in whose name it is issued, because a certificate held by the design house is not yours to use with another assembler. The radio module by part number and its approval status. And the transition terms, meaning what you receive if you move to another assembler. Those five lines are the difference between a product you own and a product you rent.
Where this lands with us. For connected hardware we separate the three layers in the plan: what is licensed from a design house and on what terms, what is fabricated and assembled to a bill of materials you control, and which certification route each market needs with the module shortcut identified. Send the product, the quantity and the destination, and the plan comes back with the ownership position stated rather than assumed.