Direct answer: A supplier IP warranty page is not "the supplier warrants non-infringement". The website page should state: which rights are involved (patents, trademarks, copyright, trade secrets, designs, software/open source, drawings/molds), who warrants (the supplier has the right to dispose/deliver, does not infringe, and has a complete chain of title), how to prove it (contract, invoice, payment, authorisation, manufacturer certificate, lawful source), what to do on an infringement notice (stop use/sale, replace, recall), how indemnity and recovery are agreed, and how the buyer preserves its own lawful-source defence. On the law: a seller warrants that no third party has any right over the delivered subject matter, unless otherwise provided by law (Civil Code Article 612); if the buyer knew or should have known of a third-party right at contract formation, the seller does not bear that obligation (Article 613); if the buyer has conclusive evidence of a third-party right, it may suspend payment of the corresponding price unless the seller provides appropriate security (Article 614). Trademark Law Article 57 lists "selling goods infringing a registered trademark" as infringement; Article 64 provides that a seller who does not know the goods infringe, can prove lawful acquisition and identifies the supplier does not bear damages. Copyright Law Article 59 provides that a publisher/producer of copies who cannot prove lawful authorisation, or a distributor/lessor who cannot prove a lawful source, bears legal liability; in litigation, the alleged infringer must prove a licence or a statutory exception. Information is current to 2026-11-07. This is a review of public rules and page practice, not legal or IP advice; the contract, chain of title, evidence and the court's finding control.
This guide is for procurement, legal, R&D, quality and website teams at equipment, electronics/electrical, automotive, medical device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby areas. This page most often misses rights types, chain of title, lawful source, notice handling and indemnity, ending up as "the supplier warrants non-infringement".
First separate the rights: patents, trademarks, copyright, trade secrets, software/open source, drawings/molds; then the warranty and chain of title: who warrants, what proves it, whether upstream is lawful; finally handling and indemnity: notice, stop/replace, defence support, indemnity/recovery, lawful-source evidence. The website should state rights, warranty, evidence, handling and indemnity—not "warrants non-infringement".
How does this page relate to technical-data/NDA, product liability and procurement contract pages?
The IP warranty page answers "does the supplier's goods/drawings/software have a rights defect, who is liable if it infringes, how to prove lawful source"; the technical data/drawing request page answers grading, NDA, watermark, versions and download logs; the product liability and insurance page answers defects, evidence, exemptions, damages and policies; the contract/technical and quality agreement signing page answers document precedence, deviations, seals and versions. The IP page is the "rights warranty + infringement handling" clause; an NDA or product liability page cannot replace it.
Common breakpoints: only "warrants non-infringement"; upstream authorisation not checked; drawings/molds reused without restriction; software/open source/fonts without licences; a warning letter does not stop use; lawful-source evidence is only an invoice; indemnity/legal fees unclear; settlement/recovery not agreed. Separate "rights—warranty—chain—evidence—notice—handling—indemnity"; then procurement, legal, R&D and quality share one playbook.
| Page | Answers | Key content | Cannot replace |
|---|---|---|---|
| IP warranty/indemnity | Rights defect/who is liable | Rights, warranty, chain, evidence, handling, indemnity | NDA/product liability/contract |
| Technical data/NDA | Grading/confidentiality | NDA, watermark, versions, logs | Rights warranty |
| Product liability/insurance | Defect/damages/policy | Defect, evidence, exemptions, claims | Intellectual property |
| Contract/quality agreement | Precedence/deviation/seals | Versions, clauses, seals | Infringement handling |
| Procurement/onboarding | Qualifications/capability/audit | Questionnaire, audit, samples | Chain of title |
| Dispute resolution | Jurisdiction/arbitration | Litigation/arbitration, evidence | Ownership |
This page map is editorial; the contract, chain of title, evidence and the court's finding control.
Which IP rights are involved?
At least: patents (invention/utility model/design), trademarks (supplier/customer/third-party logos, packaging, model names), copyright (drawings, software, manuals, packaging design, photos, fonts), trade secrets (formulas, processes, customer lists), software/open source (licences, copyleft, commercial restrictions), and drawings/molds/tooling (ownership, licence, reuse restrictions). Infringement tests, defences and evidence differ by right; the page should state "whose right, what authorisation, what evidence, what handling" for each type, not bundle everything as "intellectual property".
Acceptance checks: right type; owner; authorisation; territory/term; licence limits; evidence; handling. Common gaps: patents only; trademarks/copyright ignored; software unlicensed; open source unchecked; drawings/molds reused without limits; territory/term unclear; evidence missing.
| Type | Typical subject | Evidence | Common gap |
|---|---|---|---|
| Patent | Product/structure/design | Patent number/search/FTO | No search |
| Trademark | Logo/packaging/model name | Registration/licence | No authorisation |
| Copyright | Drawings/software/manuals/images | Registration/creation/licence | No licence |
| Trade secret | Formula/process/customer list | NDA/measures | No measures |
| Software/open source | Embedded/tools/libraries | Licence/SBOM | No list |
| Drawings/molds | Tooling/molds/programs | Ownership/licence/handover | Reuse unrestricted |
| Territory/term | Export/term | Authorisation | Out of scope |
Right types are editorial; registration, authorisation and the contract control.
How should the rights-defect warranty be accepted?
Civil Code Article 612 provides that a seller warrants that no third party has any right over the delivered subject matter, unless otherwise provided by law; Article 613 provides that if the buyer knew or should have known of a third-party right at contract formation, the seller does not bear that obligation; Article 614 provides that if the buyer has conclusive evidence of a third-party right, it may suspend payment of the corresponding price unless the seller provides appropriate security. The page should state "supplier warrants no rights defect", "buyer knowledge exception", "on a claim, suspend payment/require security", and "damages/termination for breach". This applies to all third-party rights, not just patents.
Acceptance checks: warranty; knowledge exception; suspension; security; damages; termination; notice; records. Common gaps: only "non-infringement"; unaware of suspension; no security mechanism; buys with knowledge; unclear damages; no termination.
| Clause | Key point | Basis | Common gap |
|---|---|---|---|
| Warranty | No third-party right | Civil Code 612 | Non-infringement only |
| Knowledge | Buyer knew/should know | Civil Code 613 | Ignored |
| Suspension | Evidence + security | Civil Code 614 | Unaware |
| Security | Appropriate security | Civil Code 614 | No mechanism |
| Damages | Loss/costs | Contract | Unclear |
| Termination | Fundamental breach | Contract/Civil Code | None |
| Notice/record | Written/time | Contract | None |
Rights defects follow Civil Code Articles 612–614; the contract and evidence control.
How should supplier warranties be written?
At least: the supplier has the right to dispose/deliver; goods, drawings, software, packaging and manuals do not infringe third-party patents/trademarks/copyright/trade secrets; the upstream chain of title is complete; on a third-party claim, the supplier defends/assists/settles/indemnifies; the buyer's stop-use/replacement/recall/litigation costs are borne by the supplier; the buyer may suspend payment/require security/terminate; the supplier may not reuse the buyer's drawings/molds/customer information. The warranty must be enforceable: notice period, cooperation, indemnity scope (including legal/valuation fees and settlement), liability cap (if any) and exceptions (buyer-supplied design/trademark/formula).
Acceptance checks: scope; chain; defence support; indemnity; costs; suspension/termination; reuse restriction; exceptions; deadline. Common gaps: generic warranty; no defence support; no legal fees; no suspension/termination; reuse unrestricted; unclear exceptions; no deadline.
| Clause | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Right to dispose | Ownership/licence | Contract/authorisation | None |
| Non-infringement | Patent/trademark/copyright/secret | Search/statement | Generic |
| Chain of title | Upstream/manufacturer | Authorisation | Broken |
| Defence support | Notice/cooperation/settlement | Clause | None |
| Indemnity | Loss/legal/valuation/settlement | Clause | No costs |
| Suspension/termination | Trigger/process | Clause | None |
| Reuse restriction | Drawings/molds/customer info | NDA/clause | None |
| Exceptions | Buyer-supplied/instruction | Clause | Unclear |
Warranty clauses are editorial; the contract, authorisation and evidence control.
How should trademarks and copyright be accepted?
Trademarks: Trademark Law Article 57 lists "selling goods infringing a registered trademark" as infringement; Article 64 provides that a seller who does not know the goods infringe, can prove lawful acquisition and identifies the supplier does not bear damages. The buyer should keep lawful-acquisition evidence (contract, invoice, payment, supplier information) and stop selling/using the infringing goods. Copyright: Article 59 provides that a publisher/producer of copies who cannot prove lawful authorisation, or a distributor/lessor who cannot prove a lawful source, bears legal liability; in litigation, the alleged infringer must prove a licence or statutory exception. Drawings, software, manuals, packaging design, images and fonts may all be involved; check the chain, scope, territory and term.
Acceptance checks: trademark registration/authorisation; packaging/logo source; copyright registration/creation; software licence; font/image licence; lawful-source evidence; stop sale/use. Common gaps: logo unlicensed; packaging copied; drawings unlicensed; pirated software; font without commercial licence; invoice lost; no stop on notice.
| Type | Key point | Basis | Common gap |
|---|---|---|---|
| Trademark infringement | Sale/use/packaging | Trademark Law 57 | No authorisation |
| Trademark lawful source | No knowledge + lawful acquisition + supplier | Trademark Law 64 | No evidence |
| Copyright licence | Reproduce/distribute/adapt | Copyright Law 59 | No licence |
| Software/open source | Licence/commercial/copyleft | Licence | No list |
| Fonts/images | Commercial/scope/term | Authorisation | Out of scope |
| Stop sale | After notice | Record | Continue |
| Evidence | Contract/invoice/payment | File | Missing |
Trademark/copyright follow Articles 57 and 64 of the Trademark Law and Article 59 of the Copyright Law; the authorisation and evidence control.
How should patents and software/open source be accepted?
Patents: conduct a basic search/FTO analysis before purchase (especially for export markets), ask the supplier for a patent list/non-infringement statement/authorisation, and handle claims through the contract's defence/assistance/indemnity. Software/open source: build a component list (SBOM) and licence list (MIT/Apache/GPL/AGPL/commercial), check commercial use/distribution/modification/patent grant/copyleft obligations; embedded software, toolchains, libraries, fonts and icons all need checking. The page should state who provides the list, who reviews, and how to replace/isolate on issues—not just "use licensed software".
Acceptance checks: patent search; FTO; export markets; software list; licence; copyleft; commercial limits; replacement; records. Common gaps: no search; no export analysis; no SBOM; GPL/AGPL misuse; fonts/icons unlicensed; no replacement.
| Item | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Patent search | Market/technology | Search report | None |
| FTO | Claim comparison | Analysis | None |
| Export markets | Territory/portfolio | List | Ignored |
| Software list | Components/versions | SBOM | None |
| Licence | Commercial/distribution/modification | Licence | Misused |
| Copyleft | GPL/AGPL obligations | Analysis | Ignored |
| Replace/isolate | On issue | Record | No action |
Patent/software compliance is editorial; the Patent Law, licences and contract control.
How to preserve lawful-source and chain-of-title evidence?
The lawful-source defence rests on "no knowledge + lawful acquisition + identifying the supplier/source". Keep at least: purchase contract/order, invoice, payment record, delivery note/receipt, supplier name/address/contact, supplier's rights statement/authorisation, manufacturer/upstream chain, software licence/purchase proof, trademark registration/licence, copyright registration/creation proof. The evidence must connect "who sold to whom, when, at what price, what subject matter". An invoice alone is not enough; an oral warranty is not enough. The page should state "evidence list + retention + who retrieves".
Acceptance checks: contract; invoice; payment; delivery/receipt; supplier information; authorisation; upstream chain; software proof; retention. Common gaps: invoice only; payment to an individual; supplier unreachable; expired authorisation; broken chain; no software proof; no retention.
| Evidence | Proves | Key point | Common gap |
|---|---|---|---|
| Contract/order | Transaction | Subject/price/date | None |
| Invoice | Lawful acquisition | Title/tax number/item | Incomplete |
| Payment | Real transaction | Corporate/flow | Personal account |
| Delivery/receipt | Delivery | Signature/batch | None |
| Supplier information | Identify supplier | Name/address/contact | Unreachable |
| Authorisation | Licence/upstream | Scope/term | Expired |
| Software proof | Genuine/licensed | Order/key | None |
| Retention | Retrievable | Period/access | None |
Lawful-source/chain evidence is editorial; Trademark Law Article 64, Copyright Law Article 59 and evidence rules control.
How to handle an infringement notice?
On a lawyer's letter/platform notice/litigation materials: first stop using/selling/isolating the accused subject matter (avoid escalation), preserve evidence (letter, link, time, sales/use records), notify the supplier and activate the contract's defence/assistance clause, and have counsel assess replacement/recall/settlement. Do not "keep selling first"; do not publicly admit infringement before verification. The page should state who receives, response time, who stops use, who liaises with counsel, who notifies the supplier and who decides settlement. For exports, also assess customs seizure/platform takedown/customer claims.
Acceptance checks: channel; response time; stop use/sale; evidence; supplier notice; counsel; replacement/recall; settlement; records. Common gaps: no owner; continue selling; lost evidence; no supplier notice; no counsel; no replacement; settlement without approval.
| Step | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Receipt | Channel/registration | Letter/email | No owner |
| Response | Time/owner | Record | Delay |
| Stop use/sale | Scope/isolation | Record | Keep selling |
| Evidence | Sales/use/links | File | Lost |
| Supplier notice | Contract clause | Notice | None |
| Counsel | Internal/external | Engagement | None |
| Replacement/recall | Plan/cost | Record | None |
| Settlement | Approval/scope | Agreement | No approval |
Handling process is editorial; the contract, legal advice and case facts control.
How should indemnity, recovery and insurance be accepted?
Indemnity should state: the supplier bears the buyer's loss/costs arising from third-party claims (legal fees, valuation fees, settlement, damages, stop-use/replacement/recall costs, customer claims); the buyer may suspend payment/set off; the supplier defends or assists; liability caps/exclusions (buyer-supplied design/trademark/formula, buyer's out-of-scope use); insurance (if any) coverage. Recovery needs an evidence chain and limitation period; settlements need approval. The page should state who pays, for what, caps, exclusions and how to recover—not just "the supplier bears all liability".
Acceptance checks: scope; costs; set-off; defence; cap; exclusions; insurance; recovery; limitation; approval. Common gaps: generic scope; no legal fees; no set-off; no defence; no cap; unclear exclusions; no insurance; no evidence for recovery.
| Clause | What to confirm | Evidence | Common gap |
|---|---|---|---|
| Indemnity scope | Loss/costs/customer claims | Contract | Generic |
| Legal/valuation | Included? | Clause | Excluded |
| Set-off | Suspension/offset | Clause | None |
| Defence | Who leads/assists | Clause | None |
| Cap | Amount/multiple | Clause | None |
| Exclusions | Buyer-supplied/out-of-scope | Clause | Unclear |
| Insurance | Scope/limit | Policy | None |
| Recovery | Evidence/limitation/approval | Record | None |
Indemnity/recovery is editorial; the contract, policy and the court's finding control.
How should the IP warranty page be written?
Suggested content: (1) scope (procurement/subcontracting/software/drawings); (2) rights types; (3) supplier warranty (right to dispose/non-infringement/chain); (4) chain of title and lawful-source evidence; (5) trademarks/copyright/patents/software open source; (6) handling of notices; (7) indemnity/recovery/insurance; (8) buyer obligations (no out-of-scope use/confidentiality/no reverse engineering); (9) dispute resolution; (10) contact/version/update date. The public page explains rules and entry points; it should not publish specific supplier contracts, full authorisations or customer information; after login, suppliers can submit chain-of-title/statements. State "the contract, chain of title, evidence and the court's finding control"; do not write "the supplier warrants non-infringement".
Use consistent English terms (IP warranty, indemnity, chain of title, lawful source, trademark, copyright, patent, open-source licence, takedown, recall, subrogation) and state the review date. Link to technical data/NDA, product liability and contract signing pages, but do not turn the IP page into an NDA page.
| Section | What to write | Evidence | Avoid |
|---|---|---|---|
| Scope/rights | Procurement/subcontracting/software/drawings | Contract | Vague |
| Warranty | Right/non-infringement/chain | Statement/authorisation | Non-infringement only |
| Lawful source | Contract/invoice/payment/supplier | File | Invoice only |
| Trademark/copyright | Registration/licence | Certificate | No authorisation |
| Patent/software | Search/licence/SBOM | Report | No list |
| Notice/handling | Stop/replace/recall | Record | Keep selling |
| Indemnity/recovery | Scope/cap/exclusions | Clause | Generic |
| Buyer obligations | No out-of-scope/confidentiality | Clause | None |
This structure is editorial; external statements must be truthful and verifiable, per the contract, chain of title, evidence and the court's finding.
What must not be written?
High-risk claims: "the supplier warrants non-infringement, so the buyer has no liability" (the buyer's sale/use may still be challenged; lawful source is only a defence against damages); "an invoice proves lawful source" (also need contract/payment/supplier/no knowledge); "keep selling after a lawyer's letter" (may increase loss); "no need to check trademarks/copyright" (selling infringing goods may infringe); "all open source is free for commercial use" (GPL/AGPL/commercial limits differ); "drawings/molds can be reused freely" (ownership/licence limits); "indemnify all losses" (subject to caps/exclusions/causation); "publish full authorisations" (sensitive). These are inaccurate or misstate rights, defences or liability.
Safer wording: "This page applies to [procurement/subcontracting/software/drawings]; rights [list]; supplier warranty [right/non-infringement/chain]; lawful source [contract/invoice/payment/supplier]; trademark/copyright/patent/software [authorisation/licence]; notice handling [stop/replace/recall]; indemnity [scope/cap/exclusions]; buyer obligations [no out-of-scope/confidentiality]. The contract, chain of title, evidence and the court's finding control." External promotion must comply with advertising and fair-competition rules; supplier/authorisation/customer information needs authorisation or redaction.
Go-live acceptance checklist
Ten checks: rights types, rights-defect warranty, supplier warranty, chain/lawful source, trademarks/copyright, patents/software open source, notice handling, indemnity/recovery, buyer obligations, page wording and version. Each needs an owner, evidence and review date. The pass condition is not "the page says non-infringement", but that procurement, legal, R&D and quality can identify rights, verify authorisation, preserve evidence, stop/replace and recover from the page.
Before go-live, run one real (anonymised) subject matter through: rights identification → warranty → chain → lawful source → notice → stop → indemnity → record. Any step that fails is a gap in the page or the clause.
| Check | Pass condition | Evidence | If it fails |
|---|---|---|---|
| Rights types | List/classification | Contract | Add list |
| Rights defect | Warranty/suspension/security | Clause | Add clause |
| Supplier warranty | Right/non-infringement/chain | Statement | Add statement |
| Lawful source | Contract/invoice/payment/supplier | File | Add evidence |
| Trademark/copyright | Registration/licence | Certificate | Add licence |
| Patent/software | Search/licence/SBOM | Report | Add analysis |
| Notice handling | Stop/replace/recall | Record | Add process |
| Indemnity/recovery | Scope/cap/exclusions | Clause | Add clause |
| Buyer obligations | No out-of-scope/confidentiality | Clause | Add clause |
| Wording/version | No misleading/date | Page | Rewrite |
This checklist is editorial; the contract, chain of title, evidence and the court's finding control.
Who should read this, who should not, and what decisions does it support?
It suits procurement, legal, R&D, quality and website teams at equipment, electronics/electrical, automotive, medical device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby areas; also companies drafting IP warranty clauses for the first time, or facing "supplier goods challenged / software licence / drawing reuse". It does not suit teams that do not procure, subcontract, use third-party software/drawings, or those wanting one page to replace legal/IP advice.
Read it if you are building an IP warranty page; only "warrants non-infringement" is written; chain of title is not checked; drawings/molds are reused without limits; software/open source has no list; you keep selling after notice; lawful source is only an invoice; indemnity is unclear. Skip it if you treat a warranty as a full release, an invoice as lawful source, open source as free for all commercial use, or want to publish authorisations/customer information. It supports self-review of rights, warranty, chain, trademarks/copyright, patents/software, notice handling, indemnity and page wording.
FAQ
Is a supplier's non-infringement warranty enough?
No. The warranty should state the rights types, chain of title, defence support, indemnity scope (including legal/valuation fees and settlement), suspension/termination, reuse restrictions and exceptions; the buyer must also keep lawful-source evidence. Even with a warranty, the buyer's sale/use may still be challenged; the warranty is a basis for recovery afterwards.
If we buy infringing goods, is the buyer liable?
The buyer may be sued. Trademark Law Article 57 lists selling infringing goods as infringement; Article 64 provides that a seller who does not know, can prove lawful acquisition and identifies the supplier does not bear damages (but may still be required to stop selling). Copyright Law Article 59 also requires lawful authorisation/source. Patent infringement is judged under the Patent Law; the rights, evidence and the court's finding control.
What evidence is needed for the lawful-source defence?
Contract/order, invoice, payment record, delivery/receipt, supplier name/address/contact, authorisation/upstream chain, software purchase proof, trademark registration/licence, copyright registration/creation proof. The evidence must connect who sold to whom, when, at what price and what subject matter; an invoice or oral warranty alone is not enough.
What should we do on an infringement warning letter?
Stop using/selling/isolating the accused subject matter, preserve the letter/link/sales records, notify the supplier and activate the contract's defence/assistance clause, and have counsel assess replacement/recall/settlement. Do not keep selling and increase the loss, and do not publicly admit infringement before verification. For exports, also assess customs seizure/platform takedown/customer claims.
What should we check for software/open source/fonts?
Build a component list (SBOM) and licence list, distinguish MIT/Apache/GPL/AGPL/commercial licences, and check commercial use/distribution/modification/patent grant/copyleft obligations; embedded software, toolchains, libraries, fonts and icons all need checking. Replace/isolate and record on issues.
Should the website publish supplier lists/authorisations?
It may publish the rules, required documents and entry points to help suppliers prepare; do not publish specific contracts, full authorisations, customer information or unredacted rights evidence. After login, suppliers can submit chain-of-title/statements; the public page states that the contract, chain of title, evidence and the court's finding control.
One-sentence takeaway
A Changzhou manufacturer's supplier IP warranty page is not about "warrants non-infringement". It should turn rights types, rights-defect warranty, chain of title/lawful source, trademarks/copyright, patents/software open source, notice handling, indemnity/recovery and buyer obligations into a reviewable checklist—so procurement, legal, R&D and quality can identify rights, verify authorisation, preserve evidence, stop/replace and recover.
Method and limitations
This is a review of public rules and page practice, not legal or IP advice. No undisclosed customer, price, authorisation or supplier data were used; processes, tables and acceptance items are editorial, not legal conclusions. Rights defects follow Civil Code Articles 612–614; trademark infringement/lawful source follow Trademark Law Articles 57 and 64; copyright authorisation/lawful source follows Copyright Law Article 59; patents and software/open source are treated as general process guidance without citing the Patent Law or specific licences; the contract, chain of title, evidence, licences and the court's finding control. This article does not determine whether any specific subject matter infringes; companies should search and verify item by item.
Sources and scope
Information is current to 2026-11-07. The following are official pages; their text controls.
- Civil Code of the People's Republic of China: Supreme People's Court. Rights-defect warranty (Article 612), buyer knowledge exception (Article 613), suspension and security (Article 614).
- Trademark Law of the People's Republic of China (2019 revision): NPC website. Infringement of registered trademark (Article 57), lawful-source defence (Article 64).
- Copyright Law of the People's Republic of China (2020 revision): The State Council of China. Authorisation/lawful source and burden of proof (Article 59).