Home / Services

Adrian Liu · China-side legal work

China Product Development Agreement Lawyer

First published · Updated

Agree the milestones, deliverables and handover before development and production get mixed up. This is for overseas buyers paying a Chinese factory or design company to develop a product.

From USD 3,250new bilingual development agreement
From USD 950review of an existing agreement
5–7 business daystypical drafting time

Short answer

  • A product development agreement sets what a Chinese developer must create, in which stages and for what fees.
  • I draft or review it for overseas buyers paying a Chinese factory or design company to develop a product.
  • Drafting starts at USD 3,250 and usually takes 5–7 business days; review starts at USD 950.
  • Agree the terms at the quotation stage, before development and production get mixed up.

Scope and fees

New bilingual drafting from USD 3,250. Existing agreement review from USD 950. A full redline (tracked changes with new wording) and negotiation are scoped separately. Standard drafting covers one set of parties, one development project, one bilingual agreement and one round of client changes (send all your comments together). Narrower or very different matters may be quoted separately. The exact scope and fee are confirmed before paid work begins. Drafting typically takes 5–7 business days. That time starts once I have the agreed information and payment is made as agreed.

The fee doesn't cover the technical specifications themselves, which you and your engineers decide. Patent or design filings, and getting back files or tooling already withheld, are separate work.

Separate the commitments at each stage

What exists before the project

List the designs, know-how, software and other material each party brings. Keep these apart from the work the developer is asked to produce.

What each milestone delivers

Describe the samples, drawings, technical files and other outputs. Tie each approval, payment stage and written acceptance to the agreed deliverables.

What may change

Cover changes, extra costs, late decisions and failed samples. Say what approval is needed before a change is made. The contract should match how the teams work in practice.

What happens at handover

List the materials to be handed over, who may use what, who owns what, and any unfinished work. Treat the end of development as a separate step from the start of volume production.

Which terms does a factory resist in a development agreement?

When I draft the first version for an overseas buyer, I expect pushback in four places. The factory wants to know three things. Will its existing technology be taken? Will the requirements keep changing? Who pays for its work if the project is cancelled?

Ownership of results, technology and molds

Buyers often expect the development fee to make everything theirs. Factories want to keep their existing processes, general know-how and experience they can use on other projects. Deal separately with background technology, project results, improvements, the physical molds, and the handover of drawings and source files with any licence you need. Paying the development fee doesn't replace an agreement on ownership.

Limits on use and circumvention

Factories resist a ban on making any similar product, or an open-ended ban on serving every related customer. Tie the limits to the information you provide, your own designs, the named products and the business relationships you want to protect. Say separately what may not be disclosed, what may not be used and which deals may not go around you.

Timeline, acceptance and changes

A fixed total price, a hard deadline and revisions until you are "satisfied" leave all the uncertainty with the factory. It works better to accept the work against objective test criteria. Each time a requirement changes, confirm the fee, the deadline and the drawing version together.

Cancellation, refunds and compensation

A right for you to cancel at any time, a full refund and factory liability for every downstream loss often stall the talks. Treat a breach by the factory differently from a cancellation for your own business reasons. For each, say what happens to finished work, special materials, the handover and compensation.

What should happen between sample approval and mass production?

The stage I watch most closely runs from sample approval to pilot run to release for mass production. A sample that looks right doesn't confirm the materials, performance, tolerances and test methods that mass production needs. Give each step its own standard, test results, sign-off person and payment condition. A message saying "sample OK" can't stand in for a full acceptance plan for mass production.

Which technical deliverables should the agreement name?

Name each technical deliverable, so a handover can be checked. The test is whether you can modify, repair and mass-produce the product, or move it to another supplier, with what you receive. For an electronic or mechanical product, the list usually covers these items.

Handover problems often look like this. The files arrive, but project files won't open, code won't compile or a key module can't be changed. Or the drawings, code, BOM and test reports come from different versions and together don't rebuild the accepted product. So I pay close attention to version numbers, change records and how each item matches the final sample. Where the agreement provides for it, the handover includes an actual build, installation, flashing, function test or trial run. A proof-of-concept project and a mass-production project need acceptance standards that fit their aims.

What if the project moves to another factory?

Development projects stop, or move to another factory. "Delivered on completion" doesn't cover that. Agree how stage drawings, code, samples, test records, known defects and open issues are handed over, and when. Agree how fees are settled, depending on why the project ended, how far it got and what has been paid, and how you may use the work afterwards. Failed test records are worth having too, because they save a new team from repeating work.

What about know-how nobody wrote down?

Instructions, training and a check that your team can take over.

Some of what makes a product work is never written down, such as the order for adjusting parameters, special machining steps, manual calibration and how to recover from faults. If it is needed to reach the agreed result, the agreement can turn it into duties to write instructions, train, demonstrate and answer technical questions. It can also require a check that your team can take over. In a commissioned development contract, Civil Code art. 853 already requires a developer to provide the relevant technical materials and necessary technical guidance, and to help the client master the results.

Do the files come with the right to use them?

Using, changing and moving the work, and who can file a patent.

Receiving files and being allowed to use them are separate questions. The agreement should say whether you may modify and repair the product, have another factory make it, and give that factory the files it needs. It should also identify the developer's existing technology and any licence limits on third-party software or parts.

Paying for development doesn't automatically make all the IP yours. Under Civil Code art. 859, the right to apply for a patent on a commissioned invention belongs to the developer, unless the law or the contract says otherwise. So write down who owns what.

What does the development fee buy?

Agree it at the quotation stage.

Agree at the quotation stage what the development fee buys. You may expect the full technology and the freedom to move factories. The developer may plan to recover its costs through later production orders. If the two views differ from the start, a dispute tends to follow over files, rights of use and changing factories.

What you receive

The agreed drafting scope covers a bilingual development agreement and a framework schedule of milestones and deliverables. You also get an explanation of key terms and one round of changes. The framework lists the technical and business decisions still to be made. It doesn't supply a technical design or check that a product works.

How the documents fit together

An NNN agreement (non-use, non-disclosure and non-circumvention) can protect information you share before the development terms are agreed. A manufacturing agreement covers production duties, acceptance, payment and delivery. A single combined document may suit your project. Don't assume one fee covers every stage, recipient and contract. The usual order is the NNN before you share files, this agreement before development starts or a fee is paid, and a manufacturing agreement once the samples are approved. Which agreement comes first →

Questions from overseas buyers

What if the milestones aren't final yet?

We can set out the proposed stages and list the open decisions. You and your technical advisers still need to confirm the measurable outputs, tests and acceptance criteria.

Can the agreement cover tooling and new IP?

Yes. The draft can set out what you agree on ownership and use. Tell me what each party contributes, what will be created and who pays. Patent searches, filings and getting back property that is already being withheld are separate work.

What if the developer has already stopped work?

Start with the existing agreement and the record of payments and deliveries. Assessing a breach that has already happened is different from drafting new terms. So is negotiating an exit.

Does this include every discussion with the developer?

No. The proposal lists the meetings and revisions included. Ongoing negotiation, or a big change to the project, needs extra scope that we agree first.

A Chinese factory is developing my product. Who owns the source files?

It depends on the agreement. If it says nothing, the default rules favour the factory. Copyright in code, drawings and other files made on commission belongs to the side that made them (Copyright Law art. 19; Computer Software Protection Regulations art. 11). Paying for development doesn't automatically make all the IP yours. Under Civil Code art. 859, the right to apply for a patent on a commissioned invention belongs to the developer, unless the law or the contract says otherwise. Receiving the files and being allowed to use them are separate questions too, so write down who owns and may use what.

Can I move production to another factory after development is finished?

Plan for it in the agreement. It should say whether you may have another factory make the product and give that factory the files it needs. The test is whether you can mass-produce the product, or move it to another supplier, with what you receive at handover. Agree this at the quotation stage, because the developer may plan to recover its costs through later production orders.

Does an approved sample mean the product is ready for mass production?

No. A sample that looks right doesn't confirm the materials, performance, tolerances and test methods that mass production needs. Give each step, from sample to pilot run to release for mass production, its own standard, test results, sign-off and payment condition.

Selected matters

These examples are based on matters I have handled. Names, products, places, dates, amounts and other identifying details have been removed or changed. They show the kind of work involved. They don't promise any result.

Acting for a buyer

The factory's improvements belonged to the brand.

I drafted a combined NNN and product development agreement for a furniture brand and the Chinese factory that already made its products. A separate manufacturing agreement covered production. Any change or improvement built on the brand's information or products belonged to the brand as soon as it was made, whoever made it. The factory gave up any claim to joint ownership or prior use. Rejected samples and records of failed sampling were the brand's too. The factory could keep reference copies for current orders only, and had to return or delete them when the project ended. Both agreements were signed.

Acting for a buyer

The brand can stop after any stage.

An overseas brand was developing a plated plastic product with a Chinese supplier. I prepared the outline of the development and tooling agreement. It covers the work only up to approved, sealed samples. Production needs a separate agreement. Until then, the factory may not use the tooling for anyone, and the brand has no duty to order. The supplier wanted a deposit before its design-for-manufacture (DFM) review. Under the outline, the deposit is refunded in full if the review finds the part can't be made, or if the brand doesn't approve the review and the tool drawings. Where the supplier's quotation or invoices differ from it, the agreement prevails. After sample approval, materials, plating, tooling and process are frozen, and unit prices are held for a set period. The brand can stop at the end of any stage without liability.

Related services and reading

This page gives general information about the service and how to prepare. It isn't advice on any particular transaction. The documents, parties, legal questions and scope are assessed for each new matter.

Discuss your development project

English or Chinese.

Tell me the product, the parties, how far the project has got and the next payment or approval milestone. Say which documents you have, such as a quotation, a draft agreement or a milestone plan. I'll tell you where you stand and what your options are.

This first step is free. I'll also tell you what information I still need and what work I would propose. It isn't a full review of your documents. Send an outline without confidential details first. I then run a conflict check, to make sure I don't act for the other side. Sensitive documents follow after that, once we agree how to share them.

Start with a short summary and the parties’ names for a conflict check. Please wait for us to confirm how to share documents before sending sensitive files. Sending an enquiry does not make us your lawyers.

Deadline or contact preferences (optional)

Please do not include confidential documents, detailed personal records or sensitive business information. Sending an enquiry does not make us your lawyers. We take no action until you hire us. Don't rely on this form to meet a deadline. Privacy notice

Adrian receives your enquiry and coordinates with the responsible lawyer. English or Chinese.