OEM / ODM — your brand on TUODI sensor lights and white noise machines
Put your logo, packaging, firmware and housing on a proven TUODI platform, or develop a new product with the factory's engineers. Brand and adapt an existing platform (OEM), or start from your own sample, drawing or specification (ODM). The factory holds 79 granted patents (63 Chinese, 16 international; see the patents and registered designs on file) and has run custom projects for export markets.
Brand a TUODI product on WhatsApp Describe your branding request
Three ways to start
Catalogue product
Send a model or shortlist, quantity and destination. Ask for the current configuration, sample and quotation.
- MOQ: small wholesale orders of stock product; mixed-model trials negotiable
- Timing, as a guide: samples 3–5 days; standard bulk orders 20–25 days from order and payment
Your brand
Name the base model and the logo, finish, packaging or manual changes you want. The quotation sets out the scope and price for that model.
- MOQ: higher than stock product, set by printing minimums
- Timing, as a guide: 25–30 days for bulk orders with a custom logo or custom packaging, from order and payment
Custom development
Describe the required behaviour, interfaces and sample tests. Engineering feasibility comes before a production commitment.
- MOQ and tooling: project-specific; a custom bar length is a tooling job with its own minimum order
- Timing: set on the project quotation after feasibility review
For a product-specific brief: furniture lighting, sound machines or sensor modules. Matter, Zigbee and Z-Wave products are development projects, not catalogue products: see what to specify for a connected product.
What you can put your brand on
- Logo and finish: logo printing or laser engraving, custom colourways
- Packaging and manuals: giftbox and blister packaging, multi-language manuals
- Firmware and function: sensing behaviour (range, hold time, daylight threshold), colour temperatures, brightness levels, sound libraries on white-noise products, PCB and firmware modifications
- Housing and hardware: housing changes, custom bar lengths cut from an existing aluminium profile (a tooling job with its own minimum order), battery capacity, connector type
- Full ODM: new product development from your sample, drawing or functional specification
Base platforms with their own pages: TDL-6110X rechargeable PIR cabinet light, MC330 white noise clock and sensor modules.
How a project runs
- 1 · You describe the requirement (or pick a catalogue item to modify)
- 2 · Feasibility review and quotation by the factory engineering team
- 3 · Samples are made to the agreed specification
- 4 · You test and give feedback; samples are revised until you approve them
- 5 · Order placed against the approved sample — which becomes the golden sample production is measured against; changes after approval go through agreement, not improvisation
- 6 · Delivery — with export documentation for your market


Connected and smart products: what to specify
Available today: proprietary RF/2.4G products and one Tuya Wi-Fi sensor-switch variant. Matter, Zigbee or Z-Wave products and mains-outage logging are ODM development projects. Buyer inquiries often combine a sensor, a wireless protocol, a hub, an app and event reporting in one sentence; those are separate interfaces, and a product that can switch a load does not automatically report power cuts, keep timestamps offline or join a buyer's Matter, Zigbee or Z-Wave system.
| Layer | Define before feasibility | Sample test |
|---|---|---|
| Radio & commissioning | Protocol and version, frequency/region, hub/controller, pairing/reset flow, maximum network and coexistence requirements. | Pair, remove and re-pair on the buyer's target hub; test range and recovery after an interrupted setup. |
| Events & telemetry | Which events are reported—motion, relay state, mains-off/on time or outage duration—plus timestamp source, accuracy, time zone and offline buffer. | Create real power cuts and network outages; compare the local state, stored log and app/API record after reconnection. |
| App, API & cloud | Buyer app or supplier app, API/data format, accounts, cloud region, retention, export, privacy roles and ongoing service dependency. | Complete the intended user journey and export the required event data; document what stops working without internet or cloud service. |
| Firmware ownership | Source/binary ownership, credentials, signing, OTA update path, support period, vulnerability handling and change approval. | Record firmware and module revisions on the golden sample; define which changes force re-testing or re-certification. |
| Market documents | Exact radio module, final host product, destination schemes and who pays for or owns testing and registrations. | Issued documents mapped to the production hardware—not a module name, lab quotation or proposed certification route. |
If drawings, firmware or manuals are confidential, request the mutual-NDA step in the project brief before technical exchange.