You do not protect a product design with one document, one password, or one carefully worded email.
You reduce exposure by deciding what matters, sharing only what the next step requires, keeping files under control, checking who receives them, and recording the commercial decisions around ownership and changes. This matters before a factory starts development, not after a detailed drawing, customer list, or tool design has been passed through several inboxes.
This article is general sourcing guidance, not legal advice. If the value of a design, brand, tooling investment, market plan, or commercial relationship is material to your business, obtain qualified legal advice for the relevant country and agreement. The practical steps below can still help you reduce avoidable exposure before, during, and after factory engagement.
Start by identifying what is actually worth protecting
“IP” can describe several different things. Treating every file as equally sensitive makes collaboration slow. Treating nothing as sensitive makes uncontrolled sharing easy.
The World Intellectual Property Organization explains that trade-secret protection generally depends on information being secret, commercially valuable because it is secret, and subject to reasonable steps to keep it secret. The applicable rules differ by jurisdiction and facts. 1
Make a simple asset list before you begin detailed supplier conversations.
| Asset or information | Why it may matter | Practical control question |
|---|---|---|
| Product concept and feature combination | May contain the differentiating idea or commercial direction | Does this supplier need the full concept at this stage? |
| CAD files, drawings, and tolerances | Allow a factory to reproduce or modify a design | Can you send a controlled PDF, watermarked view, or partial file before full release? |
| Formula, process, or settings | May contain know-how that is not visible in the finished product | Who needs access, and can the work be divided so no recipient sees more than needed? |
| BOM and component sources | Can reveal preferred materials, suppliers, and cost structure | Which components can be named later in the sourcing process? |
| Brand, logo, packaging, and artwork | Connect the product to your market identity | Is final production artwork being shared only when the supplier is ready to use it? |
| Customer, distributor, and pricing information | Can expose commercial relationships and market plans | Does the supplier need the customer identity or the final selling price to quote the product? |
| Tooling drawings and tool records | Affect who can make and use the physical production asset | Is ownership, storage, access, and transfer documented clearly? |
The point is not secrecy theatre. It is proportional disclosure. A supplier quoting a broad concept may need a different level of detail from a factory preparing final tooling.
Share in stages instead of sending the whole project folder
A common mistake is sending everything at once because the buyer wants a fast quotation. That can create a permanent copy of a complete project package before the buyer knows whether the supplier is a serious fit.
Break disclosure into stages. At each stage, ask what the supplier must know to complete the next job.
| Project stage | Information commonly needed | Information you may be able to hold back until later |
|---|---|---|
| Early supplier screen | Product category, target use, rough quantity, broad material or process needs | Full CAD, final artwork, exact customer list, detailed component source list |
| Initial quote | Controlled specification summary, key dimensions, performance needs, reference photos | Final production files, all supplier contacts, nonessential proprietary process details |
| Sample development | Current drawings, required materials, critical dimensions, controlled reference images | Final brand rollout plan, unrelated project files, access to all internal systems |
| Tooling or engineering release | Approved technical package, exact interfaces, change-control process | Information that the chosen supplier still does not need to manufacture the part |
| Production release | Final approved artwork, packaging, BOM, drawings, inspection requirements | Superseded versions and personal folders that can create confusion |
The structure also improves sourcing quality. Suppliers receive the information they need in a form they can quote or build from, rather than guessing which version matters. Use the Product Specification Sheet Template for China Manufacturing to control the product record before sharing final technical details.
Verify the recipient before you disclose sensitive files
File controls cannot compensate for sending an important design package to the wrong entity.
Before deep technical disclosure, connect the receiving company to the supplier you have assessed. Confirm the legal entity name, registered address, role in the project, and named contact. If a trading company is coordinating the work, ask which factory, subcontractor, designer, printer, or toolmaker will need the files and what each party will receive.
This does not require accusing the supplier of bad intent. It is normal project control. The article How to Read a Chinese Business License Before You Pay a Deposit explains how to check the company identity before you rely on it. The separate Supplier Verification Checklist Before Your First Order gives a wider pre-order process.
Ask a simple question in writing: Which legal entity and which team members will receive, store, use, or pass on these files? Keep the answer with the project record.
Use controlled files, not “final-final-v8” attachments
A file that cannot be identified cannot be controlled.
Put a project code, revision, issue date, and purpose on every important drawing, artwork file, specification, and photo sheet. Maintain a short release register so you can see exactly what was sent, to whom, and for what purpose.
| Field | Example |
|---|---|
| File ID | DWG-HSG-210-04 |
| Revision | Rev B |
| Issue date | 2026-08-18 |
| Release purpose | Sample quote only |
| Recipient entity | Supplier legal name |
| Named recipient | Engineering contact |
| Attached restrictions or notes | No production release; no change without written approval |
| Supersedes | Rev A |
| Record location | Controlled project folder |
WIPO lists need-to-know access, physical access controls, IT security measures, and confidentiality arrangements among examples of reasonable secrecy measures. What is reasonable depends on the information and circumstances. 1
In practice, use the least complicated control that works for your team: restricted project folders, named recipients, watermarked review copies, access expiration where available, and a release log. Do not assume that a watermark makes a design safe. It is one visible reminder and traceability aid, not a substitute for choosing the right counterparty or limiting disclosure.
Separate ownership questions from technical collaboration
A factory can contribute engineering ideas, tooling input, or process changes. That may be useful. It can also create ambiguity if the parties never record what is being developed, who contributes what, and who owns the resulting design, files, tooling, and improvements.
Harris Sliwoski’s China manufacturing overview identifies different agreements and registrations that may be relevant to a project, including product development, manufacturing, tooling, product ownership, trademarks, and patents. The appropriate approach depends on the product, stage, jurisdiction, and commercial relationship. 2
You do not need to write legal clauses yourself to manage the project well. Create an issue list for qualified counsel and for the supplier discussion.
| Project question | Record it before the expense or disclosure grows |
|---|---|
| Who owns existing buyer-supplied designs and files? | Identify the buyer-provided materials and their current revision. |
| Who owns tooling, molds, dies, fixtures, and associated drawings? | Record the asset, payer, storage location, permitted use, maintenance, and transfer question. |
| What is the factory being asked to develop? | Define the deliverable, acceptance point, source files, and change path. |
| Are subcontractors allowed? | Identify whether they may be used and what information they must receive. |
| What happens when the factory proposes an improvement? | Record who reviews it and whether it changes the product version or ownership discussion. |
| Which brand or artwork files may be used? | Tie use to a named product version and purpose. |
For a project with a meaningful design or tooling investment, give this issue list to counsel familiar with the relevant manufacturing jurisdiction. Avoid relying on a generic template from another country or a copied agreement from a marketplace listing.
Treat confidentiality paperwork as one layer, not the whole plan
A confidentiality agreement may be useful, but it cannot reverse a disclosure that was unnecessary or poorly documented.
Harris Sliwoski cautions that NNN-style agreements are not a universal solution. It says the right protection can depend on the information disclosed, deal stage, counterparty, and wider arrangements around manufacturing, tooling, brand protection, and due diligence. 3
That is a useful sourcing principle even before you speak with a lawyer: match the control to the risk. For example, a supplier quote may need a controlled brief and identity verification. A tooling project may raise ownership and access questions. A brand launch may require a separate review of trademark and packaging decisions. A development partnership may require a clearer record of contributions and deliverables.
Do not treat a signed document as permission to share more information than the supplier needs. A weaker disclosure package is often easier to manage than a stronger agreement applied after every file has already left your control.
Control subcontractors and side channels
The factory you email may not be the only party touching the product. Tooling, printing, plating, testing, assembly, packaging, and component supply can involve other businesses.
Ask the supplier to identify planned subcontracted processes before you issue final files. Then decide what each party needs. A printer may need final artwork and placement instructions. It may not need the complete BOM, customer list, or product-development history. A toolmaker may need geometry and tolerance information. It may not need the final retail pricing strategy.
Keep the same release discipline for outsourced work: version, recipient, purpose, and return of corrected files. If an outside party sends a revised drawing or artwork proof, add it to the controlled record rather than treating an email attachment as the new standard.
Build a change-control stop rule
A changed file can create an IP and quality problem at the same time.
Use the same change control that protects production quality to protect the design record. The article How to Reduce Sample-to-Production Differences shows how a structured change record prevents different teams from working against different requirements.
Stop rule: If a proposed change affects design geometry, material, component source, artwork, tooling, production method, product performance, packaging, or intended ownership, pause the release and record the decision before using the new version.
| Change record field | Why it helps |
|---|---|
| Current and proposed file version | Prevents a new attachment from becoming the default by accident |
| Description and reason | Shows what actually changed and why |
| Parties affected | Identifies which supplier, toolmaker, designer, or inspector must receive the update |
| Commercial and technical impact | Separates a cosmetic edit from a change that may affect cost, ownership, tooling, or performance |
| Evidence reviewed | Links the change to a drawing, sample, prototype, or written supplier explanation |
| Approval and effective date | Establishes when a new file may be used |
Keep proof of your own work and decisions
A disciplined record helps your team as well as any future adviser, supplier, inspector, or partner.
Keep dated original files, development notes, meeting decisions, version history, sample approvals, supplier proposals, and correspondence about material or design changes. Store them in a project folder with meaningful access controls. This is not a claim that records alone establish ownership or resolve a dispute. It is a practical way to preserve the project history and reduce internal confusion.
When you see a product or design that appears similar to yours, avoid making accusations by email before you understand the facts. Preserve the relevant records, compare the exact products and versions, and seek qualified advice if the issue is material. Do not assume a public similarity tells you who owns what or what legal remedy exists.
The practical rule
Protecting a product design starts with operational discipline: share less at the beginning, verify who receives sensitive files, issue controlled versions, identify development and tooling questions early, control changes, and keep a record of what your team created and approved.
Those steps do not eliminate risk, and they do not replace product- and jurisdiction-specific legal advice. They make it easier to work with a factory while reducing the number of avoidable ways a design package can be misused, misunderstood, or lost.