This guide is part of the XingLiao sourcing series for buyers specifying smart switches, video doorbells and security cameras with a Shenzhen OEM. In short, Who Owns Firmware Device is the deciding factor for most buyers.
The short answer
Firmware and software ownership rarely transfer by default. In a typical ODM arrangement you get the right to sell and brand the product, not ownership of the code running inside it. If you need the source, an SDK, or the ability to move the software elsewhere, those are separate commercial terms you must negotiate before contracting — not after.
Who this page is for
Anyone planning to offer their own branded app, integrate devices into an existing ecosystem, or concerned about what happens to their product line if the supply relationship ends.
Four distinct layers, four different answers
| Layer | What it covers | Typical position |
|---|---|---|
| Device firmware | What runs on the hardware | Supplier-controlled, customised per customer |
| Cloud or platform service | Accounts, remote access, state | Usually the ecosystem owner’s — Tuya, Smart Life or similar |
| Mobile application | End-user app | White-label available on most platforms |
| Integration surface | APIs, SDKs, ecosystem support | Varies — often the most valuable and least discussed |
The trap is assuming “white-label” means “ours.” A white-label app means your brand appears in it. It does not mean you can take it elsewhere.
Five questions worth asking before signing
1. Who controls the update path?
If firmware updates are pushed by someone else, you do not control when behaviour changes. Ask whether you can approve releases, schedule them, or lock a version.
2. Is there an SDK or documented API?
This determines whether you can build anything above the device yourself. Availability, documentation quality and long-term support commitments vary enormously, and it is unrealistic to plan an integration before confirming.
3. Which ecosystem does it assume?
Many products are built on a Tuya or Smart Life foundation. That is often a feature — broad compatibility and mature apps. But it means your product’s account layer belongs to that ecosystem, and end-users’ expectations are set by it.
4. What happens to user accounts if we part ways?
Device accounts often live with the platform. Ask what continuity exists for existing end-users if you change supplier, because that is a customer-service problem rather than a technical one.
5. Are there per-device or platform fees?
Cloud-connected products can carry ongoing costs on top of unit price. Establish whether those exist, who pays them, and for how long.
What we can actually commit to
Programmes run on Tuya WiFi and Tuya ZigBee foundations, with OEM and OBM options depending on how much you want to own. What we will not do is imply software ownership that the arrangement does not convey.
If source code access, exclusive firmware development, or a bespoke application layer is required, that is a development scope with its own cost and timeline, and it is far cheaper to agree up front than to discover later.
Standard platform orders start at MOQ 500 pieces per colour, sampling in 7-15 days, tooling in 25-40 days where required. Warranty is 12 months with lifetime technical support, under NDA by default.
This is general guidance, not contractual terms. Any software entitlement must be set out in your agreement.
Frequently Asked Questions
Does buying the product buy the firmware?
Normally no. You buy the right to sell the hardware under your brand. Source access is a separate arrangement.
Can I get my own branded app?
Yes on most platforms. Be clear about whether you need branding only, or genuine control.
Who pushes firmware updates?
Ask explicitly. If someone else controls updates, your product can change behaviour without your involvement.
Will my devices work if I change supplier?
That depends entirely on how much of the software stack you own or can port. Decide before choosing, not after.
Are there recurring software costs?
Sometimes. Cloud-connected devices may carry platform fees that sit on top of unit price. Confirm who pays and for how long.
Can I lock a firmware version?
Often possible to hold a particular release, though security updates are generally worth accepting. Ask what control you have.
IsTuya or Smart Life a problem for my brand?
Usually the opposite — it gives mature app infrastructure and wide compatibility. The consideration is dependency, not quality.
What should go into the contract?
Software licence scope, update control, SDK availability, API documentation, account ownership, fee responsibility and what happens on termination.
Need clarity on software scope before you commit? Ask at xingliaotech.com/contact, or review manufacturing and ODM capability at xingliaotech.com. That is why Who Owns Firmware Device keeps gaining attention in this category.
Related Articles
- After Launch: Firmware Updates, Security Patches and Who Maintains Your Product
- Matter vs ZigBee vs WiFi Switches
- Tuya vs eWeLink vs Smart Life: OEM Guide
- ODM Hardware Development Process: From Concept to Mass Production
- How Much Does It Cost to Develop a Smart Home Product with an ODM?
XingLiao Smart Home — OEM/ODM Sourcing Guides
- How to Choose a Smart Switch Manufacturer in China
- Smart Switch Board Manufacturer (OEM/ODM)
- Tuya Smart Switch OEM
- Video Intercom Manufacturer
- China Factory vs Trading Company — How to Tell
Need a quote? Talk to our Shenzhen factory →
Planning an ODM project?
Tell us the product, target market and volume. We reply with a quotation, sample list and production schedule, usually within one working day.