Who owns the design files when a Chinese company develops my product?

It depends entirely on the contract. Without a written clause, assume nothing. Decide ownership of schematics, PCB layout, mechanical files, firmware source and app source before the first payment, and tie the transfer to payment milestones.

Do I get the firmware source code?

Only if the agreement says so. Some partners deliver binaries only. If you may change factories or add features later, require source delivery and a build instruction in the contract.

Who owns the tooling?

Normally the party that paid for it, but this must be written down, together with where the moulds are stored and what happens if you change factory.

What about the cloud and app accounts?

Create the developer, cloud and app-store accounts under your own company from the start. A product whose server and store listing sit in another company's account is a product you do not fully control.

Who Owns the Design Files and Firmware When You Develop a Product in China?

Buyers ask about price, schedule and certification long before they ask who owns what. The ownership question tends to come up at the end, when a second factory is being considered or a feature has to be added. By then the answer is fixed by whatever was, or was not, written down at the start.

The five things that carry ownership

Hardware design files: schematics, PCB layout, bill of materials.
Mechanical files: industrial design, structure, drawings, and the moulds made from them.
Firmware: source code, build instructions and the signing keys used for updates.
App and server: source code, the cloud tenancy it runs in, the developer and app-store accounts.
Test and production data: fixtures, test programs and the production process documents.

For each one, three points should be settled in writing: who owns it, whether you receive the source or only the output, and when the transfer happens.

Tie the transfer to payments

A practical pattern is to link delivery to the development milestones. When a phase is paid for, its files are delivered to you. This keeps both sides honest and avoids the situation where the whole project is paid and nothing can be moved.

Firmware: source or binary

A binary lets you sell the product. Source lets you maintain it, fix it and move it. If you may change factories, add models or hire your own team, require source delivery with a working build instruction. A build nobody can reproduce is not a delivery.

Tooling and where it sits

Moulds are usually owned by whoever paid for them. The contract should also say where they are kept, what the factory may and may not make with them, and how you retrieve them if the relationship ends.

Accounts that outlast the project

Open the developer accounts, cloud tenancy and app-store listings under your own company from day one, and give the partner access. The reverse arrangement is where products get stuck.

Third-party components and licences

Silicon vendors’ SDKs, operating systems and open-source parts come with their own licence terms. A good partner lists them for you, so you know what you may ship and under what conditions.

How we handle it

At 3CBAY the scope of each project, the deliverables and the ownership terms are agreed before the paid development phase starts, and the deliverables are listed in the agreement. Industrial design, structure, hardware, firmware, app, server and production are one team, so the files that come out are consistent with each other. This article is a planning guide, not legal advice; have the agreement reviewed by your own counsel.

Planning a development project? Tell us what you are building.