Direct answer: A manufacturer's COA/inspection-report page is not "a stamped PDF in the downloads folder." It should explain which products and batches are covered, what the report contains, which standard the tests follow, how sampling and retention work, whether a batch can be traced forward and backward, how a customer looks up or downloads the report, and how inspection periods and objections are handled. Without that, a buyer cannot tell which batch the report belongs to, what was tested, or whether it supports acceptance.
This guide is for quality, engineering, procurement, sales, legal, IT, and website vendors at manufacturers in Changzhou and nearby industrial areas. It explains how to build and accept a website section for certificates of analysis (COA), outgoing inspection reports, and batch traceability. Information is current to 2026-10-31. It is a review of public rules and project practice, not legal, certification, or testing advice; specific standards, report formats, sampling plans, acceptance periods, and contractual duties depend on the applicable law, contract, quality agreement, product standard, and company procedures.
A COA records what was tested in a specific batch and what the results were. It is not a product certification and not a substitute for the contract. The report must connect to a batch, standard, test items, methods, and signatures. The website's job is to make the report findable, checkable, and traceable, not to pile up PDFs that cannot be matched to a batch.
How does the COA page relate to the contract and quality agreement?
The contract or quality agreement sets acceptance criteria, test items, sampling, objection periods, and liability. The COA or inspection report is the batch record and delivery evidence. The website is the public explanation and lookup route. All four must agree, and none replaces another.
Quality documents usually live in contract annexes, quality agreements, shipping packets, email, and chat, while the website says only "test reports available." Buyers ask: which batch does the report cover, which standard applies, what was tested, whether the sample was representative, whether the lab is in-house or third-party, whether the report number can be verified, and how long they have to raise an objection. A clear page reduces repeated explanations and prevents the "the report exists but does not match the batch" dispute at acceptance.
| Layer | What it does | What it governs | What it cannot replace |
|---|---|---|---|
| Law | Baseline for quality, labelling, inspection, and objections | Statutory duties of both parties | Specific contract terms |
| Contract / quality agreement | Sets standards, items, sampling, periods, liability | Rights and duties for that deal | Public website page |
| COA / inspection report | Records results for a specific batch/sample | The verifiable result for that batch | Product certification / contract |
| Website page | Public scope, document checklist, lookup/download route | Buyer expectations and inquiry quality | Specific report / quality agreement |
This layered view is editorial; the sale-of-goods rules on quality, inspection, and objections are in Articles 615–623 of the Civil Code. Specific terms depend on the contract and counsel.
What fields should a COA contain?
At minimum: product/model, batch/lot and production date, executed standard, test item/unit/limit/result/verdict, test method, sampling and sample source, tester/reviewer/approver, report number/date/page count, and remarks. Missing one of these makes the report hard to verify.
The value of a COA is not the red stamp; it is reproducibility. A buyer should be able to see which batch it covers, which standard applies, what was tested, which method was used, what the result was, how the verdict was reached, who tested/reviewed/approved it, and whether the report is complete. The website can publish a redacted template and a lookup route, but the actual report must match the shipping batch, the contract, and the original records.
| Field | What to write | Why it matters | Common gap |
|---|---|---|---|
| Product/model | Match contract, label, drawing | Identifies the subject | Trade name only |
| Batch / date | Unique ID, linked to production records | Identifies the batch | Random or duplicate IDs |
| Standard | Number, title, revision/year | Verdict basis | Only "pass" |
| Item/unit/limit | Item, specification range, unit, result, item verdict | Verifiable | Conclusion without data |
| Method | Standard method or internal method ID | Comparable results | Method unspecified |
| Sampling/source | Plan, sample source, sampling date | Representativeness | Unknown sample |
| Signatures/report no. | Tester, reviewer, approver, date, report number | Accountability and anti-forgery | No signature/number |
| Pages/remarks | Page x of y, deviations/non-accredited items, exceptions | Completeness | Missing pages / hidden exceptions |
This field list is editorial; product labelling and quality-inspection certificate requirements are in Article 27 of the Product Quality Law. The actual format follows the product standard, customer requirements, and quality-system documents.
How do outgoing inspection, type testing, and third-party reports differ?
Outgoing inspection is the routine release check for each batch. Type testing verifies design/standard conformity, usually for a new product, a material/process change, or a periodic point. A third-party report is an independent lab's test of a specific sample/batch. They serve different purposes and cannot impersonate one another.
A common misuse is treating an old type-test report as the COA for every batch, or treating a third-party test report as product certification. Buyers should check which batch or sample the report covers, whether the test items cover the contract, the report date, and whether the lab's scope covers the method. The website should explain the three report types separately so sales does not use one old report for every shipment.
| Type | Purpose | Timing/frequency | Issued by | Website display |
|---|---|---|---|---|
| Outgoing inspection | Batch release decision | Each batch / sampling plan | In-house QC | Lookup by batch / redacted sample |
| Type testing | Verify design/standard conformity | New product, change, periodic | In-house or third party | Model/revision/date scope |
| Third-party test | Independent verification / customer request | Per contract/regulation | Qualified lab | Report number/lab/scope |
| Calibration | Equipment traceability | Calibration interval | Calibration lab | Not a product test report |
| System/product certification | Conformity to a certification scheme | Per scheme | Certification body | Not a COA / batch report |
This classification is editorial; industries and customers may use different names. Actual test types, frequency, and report requirements follow the product standard, quality agreement, and customer requirements.
How should batch, sampling, and retention samples be defined?
A batch should uniquely correspond to continuous production with the same material, equipment/line, shift/time window, and process parameters. Sampling should follow the contract/standard plan and record quantity, location, and date. Retention samples should link to the batch, storage conditions, and retention period. Without these, the COA is not representative.
A batch number is not an arbitrary serial. It must lead back to raw-material lots, production records, equipment/parameters, inspection records, and shipments. If material, process, equipment, shift, or a critical parameter changes, a new batch usually starts; any split/merge needs rules and records. The sampling plan belongs in the quality agreement or product standard; if absent, quality and the customer should agree, not just say "we took a few." Retention quantity, storage conditions, retention period, and disposal also need a register.
| Item | Definition/practice | Evidence | Common dispute |
|---|---|---|---|
| Batch | Same material, equipment/line, shift/time window, parameters; change starts a new batch | Batch record / work order | Split/merged batches |
| Sampling | Contract/standard plan; random/stratified; record quantity, location, date | Sampling record | Only easy samples |
| Retention | Quantity, conditions, period; linked to batch/report | Retention register | None / expired |
| Re-test | Conditions, method, verdict, approver | Re-test record | Only passing items retested |
| Record retention | Period, access, backup, destruction | Archive / system log | Deleted on expiry |
These practices are editorial; the actual plan follows the product standard, quality agreement, customer requirements, and the company's quality-system documents.
How should forward and backward batch traceability work?
Forward: from raw material/production/inspection to customers and inventory. Backward: from a complaint/return to the finished batch, production records, raw-material lot, and equipment parameters. Both directions must work, with consistent times, batch IDs, and owners.
Traceability is more than having a batch number. Forward must answer which raw materials, line, parameters, operators, inspectors, and customers are involved. Backward must answer which raw material/process/equipment/shift produced the complained batch, who else received it, and whether a recall is needed. Records can be paper plus electronic, but they must be linkable, readable, protected from tampering, and retained for a defined period.
| Link | Forward (raw material → customer) | Backward (complaint → raw material) | Record |
|---|---|---|---|
| Raw material | Supplier/lot/COA/incoming inspection → finished batch | Finished batch → raw lot/supplier | Incoming inspection / requisition |
| Production | Batch record/equipment/parameters/operator/shift → batch | Batch → equipment/parameters/shift | Batch record / work order |
| Inspection | Sampling/items/results/report → batch | Report → sample/batch | Original inspection record |
| Release | Verdict/approval → warehouse | Finished goods → release record | Release note |
| Shipment | Batch → customer/order/shipment | Customer/order → batch | Shipping note / trace table |
| Recall | Batch → customers/inventory | Complaint/recall → batch | Recall record |
This traceability chain is editorial; actual depth, retention periods, and recall procedures follow product regulations, customer requirements, and quality-system documents.
How should the website lookup and download work?
Let customers query by batch + model or scan a code. Separate public redacted samples from customer-authorised reports. Provide read-only PDFs with report number/watermark, hide customer names, formulas, and process parameters, and keep query/download logs.
The website does not need to publish every original COA. A safer design is: publish the report template, field definitions, and a lookup route; let a customer retrieve the report for their own batch by batch number/model; redact sensitive data; add a report number, watermark, page count, and "for customer acceptance" note; route exceptions to a human. This helps customers without exposing customer lists, formulas, or process parameters to competitors.
| Design item | Recommendation | Risk | Evidence |
|---|---|---|---|
| Query input | Batch + model, or scan code; fuzzy cases to human | Product-name-only search cannot find batch | Query log |
| Output | Read-only PDF/field page with report number | Editable file altered | Watermark / permissions |
| Access | Public sample / customer login / one-time link | Exposes another customer's report | Permission matrix |
| Privacy | Hide customer name, contact, formula/parameters | Personal data / trade secrets | Redaction rules |
| Version | Report revision, amendment, void status | Old report reused | Version record |
| Anti-forgery | Report number / check code / QR | Forged report | Verification route |
| Rate limit | Prevent bulk scraping/enumeration | Data scraping | Rate limiting |
| Support | Route missing batch/objection to a ticket | Customer gives up | Ticket record |
This design is editorial; personal-information and trade-secret protection follow the Personal Information Protection Law, Anti-Unfair Competition Law, and company policy. This article does not cover them in detail.
How do inspection periods, objections, and warranty periods work?
First check whether the contract sets an inspection period. If it does, notify non-conformity within that period; failing to notify may deem the goods conforming. If it does not, notify within a reasonable period after discovery, subject to the two-year limit from receipt; a quality warranty period displaces the two-year limit. An unreasonably short inspection period is generally only an appearance-defect objection period.
Article 620 of the Civil Code requires the buyer to inspect within the agreed period, or promptly if no period is agreed. Article 621 requires notice of quantity/quality non-conformity within the agreed period; failure to notify deems conformity. Without an agreed period, notice must be given within a reasonable period after discovery; failure to notify within a reasonable period or within two years of receipt deems conformity, unless a quality warranty period applies. Article 622 provides that an unreasonably short inspection period is only an appearance-defect objection period, and a contractual period shorter than a statutory period follows the statute. Article 623 provides that, absent an inspection period, signing a delivery note stating quantity/model/specification presumes inspection of quantity and appearance, rebuttable by contrary evidence.
| Scenario | Rule | What to write | Evidence |
|---|---|---|---|
| Agreed inspection period | Notify within the period; silence deems conformity | Period, method, contact | Contract / acceptance form |
| No agreed period | Reasonable period after discovery; two-year limit; warranty period prevails | Prompt inspection, no "signing waives all claims" | Receipt / inspection record |
| Period too short | Only appearance-defect objection period; longer statutory/agreed period prevails | Do not cut off latent defects | Contract / quality standard |
| Delivery note | Absent a period, quantity/model/spec note presumes quantity/appearance inspection, rebuttable | Signing is not a waiver of latent defects | Delivery note / photos |
| Warranty period | Warranty applies; two-year limit does not | Scope, period, start | Warranty clause |
| Seller's knowledge | Not subject to the notice periods | Do not conceal known defects | Communications / test records |
This summary follows Articles 620–623 of the Civil Code; specific periods, notice methods, and liability depend on the contract, quality agreement, and counsel.
How should third-party reports and the CNAS mark be verified?
First check that the report matches this batch/sample, then check whether the test items fall within the lab's accreditation/qualification scope, and whether the report number, date, signatures, and methods are complete. CNAS accredits a lab's or inspection body's competence; it is not product certification. A report with a CNAS mark is not proof that the product is certified.
CNAS-R01:2023 states that a report or certificate bearing the CNAS accreditation mark or status statement must be issued by an authorised signatory within the authorised scope; if all results fall outside the accredited scope or all come from an external provider, the mark must not be used; partially non-accredited items or externally provided results must be clearly identified; the mark must not be applied to samples or products in a way that suggests product certification. A buyer should check the body's accreditation status and scope on the CNAS website, and verify the report number, sample source, method, date, and signatory, not just the logo.
Also, a third-party report is normally for the submitted sample, not a full inspection of the whole batch; a COA is not a "product certificate" or "certification certificate." If the contract requires third-party full inspection, a specific standard, or a specific body, follow the contract; a routine commissioned test report is not a substitute.
What changes for export or overseas customers?
State the language, units, standard/method revision, sample source, testing body, and destination-country/customer requirements. Do not use a Chinese-standard report to claim compliance with foreign regulations, and do not describe a test report as product certification.
Overseas buyers often ask: is the report in Chinese or English, metric or imperial, GB/ISO/ASTM or the customer's standard, was the sample taken by the factory or submitted by the customer, is the third-party lab accepted in their country, and do the report date/batch match. The English page should say "confirmed per contract/destination requirements," not promise "globally accepted." If destination-country mandatory certification/registration applies, the customer, local agent, and specialist should confirm.
Go-live acceptance checklist
Ten checks: covered products/batches, report fields, standard basis, report type, sampling/retention, forward/backward traceability, lookup/download, inspection periods/objections, third party/CNAS, and privacy/version. Each needs an owner, evidence, and update date.
Quality, engineering, procurement, sales, legal, IT, and the website vendor can share this list. The pass condition is not "the page mentions COA"; it is that a customer can find the right batch, understand the items and methods, verify the report source, know the objection period, and the company can produce the original records and traceability chain.
| Check | Pass condition | Evidence | If it fails |
|---|---|---|---|
| Products/batches | States which products/batches are covered and which are custom | Scope / quality agreement | Add scope / edit copy |
| Report fields | Product, batch, standard, items, method, result, signature, number | COA template | Add fields |
| Standard basis | Number/title/revision; enterprise standard published where applicable | Standard / public record | Add standard / publish |
| Report type | Outgoing/type/third-party/certification separated | Report samples | Correct wording |
| Sampling/retention | Plan, quantity, location, retention register | Sampling / retention records | Add records |
| Traceability | Raw→finished→customer; complaint→batch→raw | Trace exercise record | Add links |
| Lookup/download | Batch + model search; read-only/watermark/access | Page test record | Fix system / add route |
| Periods/objections | Contract period, notice method, warranty | Contract / acceptance form | Add clause / train |
| Third party/CNAS | Body/scope/number/sample source verifiable | Accreditation query / report | Replace report / correct wording |
| Privacy/version | Customer data redacted; versions/void traceable | Redaction rules / version log | Add access / versioning |
This checklist is editorial; specific report, sampling, traceability, period, and privacy requirements follow the law, contract, quality agreement, product standard, company policy, and counsel.
Who should read this, who should not, and what decisions does it support?
It suits manufacturers in Changzhou and nearby areas that issue COAs or inspection reports, or whose customers require batch traceability or third-party reports. It does not suit teams that want one old report to cover every batch, or that treat the COA as product certification or a contract substitute.
Read it if you are in quality, engineering, procurement, sales, legal, IT, or a website vendor; you are building a COA/inspection page, quality agreement, customer audit pack, or batch-traceability process; or you need to decide what the report contains, how it is looked up, how a batch is traced, and how the objection period is set. Skip it if you have no original inspection records but want a "beautiful report"; you use one report for every batch/model; or you want a checklist to replace a contract, product standard, or counsel. It supports self-review of report fields, report types, sampling/retention, forward/backward traceability, lookup/download, inspection periods/objections, third-party/CNAS, and privacy/versioning.
Lingyi Information is a website development and enterprise AI project provider, not a testing body, certification body, or law firm. This article is not a substitute for product standards, test reports, certification, contracts, or legal advice. Changzhou projects are delivered remotely or on site as confirmed per project; Lingyi is one candidate, does not claim a local office or team, and does not promise test results, certification, lead times, traffic, or inquiries.
FAQ
Is a COA the same as an inspection report or a certificate of conformity?
No. A COA is usually a record of analysis results for a specific batch/sample; an inspection report records the inspection process and results; a certificate of conformity is a product label/release document. They can be linked but cannot replace one another. The Product Quality Law requires a quality inspection conformity certificate on the product or packaging (Article 27), but that does not make a COA a product certification.
Must a COA be issued by a third party?
Not necessarily. The manufacturer's outgoing inspection can issue a COA; when the customer or regulation requires a third party, commission a qualified lab under the contract. A third-party report must match that batch/sample, not another batch or an old report; it covers the submitted sample, not necessarily the whole batch.
Does an inspection report have a "validity period"?
A report is normally a record for a specific sample/batch, time, and method, not a certificate with a universal expiry date. Customers or regulations may require periodic type testing, annual reports, or re-testing after changes; follow the contract, product standard, and customer requirements, and do not use an old report for a new batch.
How should batch numbers be designed for traceability?
The company can set its own rule, but the number must be unique and link to production date/line/shift/material/inspection/shipment, without duplicates or arbitrary numbering. When material, process, equipment, or a critical parameter changes, a new batch usually starts; split/merge needs rules and records.
Can a customer raise a latent defect after signing?
It depends on the contract inspection period, warranty period, and evidence. Articles 621–623 of the Civil Code cover agreed periods, no agreed period, too-short periods, and delivery notes. A signed delivery note may presume quantity/appearance inspection, but latent defects, warranty periods, and the seller's knowledge have separate rules. Handle it under the contract, evidence, and counsel.
Can the website publish COAs directly?
It can publish a template, field definitions, redacted samples, and a lookup route, but publishing original reports with customer names, contacts, formulas, process parameters, or unauthorised information is not advisable. Batch + model lookup, customer authorisation, read-only PDFs, watermark/report numbers, and access logs balance convenience and confidentiality.
One-sentence takeaway
A Changzhou manufacturer's COA/inspection and batch-traceability page should not just post a report; it should let a customer confirm the batch, standard, items, results, traceability chain, and objection period. The report, contract, quality agreement, and website must tell the same story, and every claim must be backed by original records.
Method and limitations
This is a review of public rules and project practice, not a compliance certification or legal opinion on any company, product, inspection report, lab, or quality system. No undisclosed customer reports, formulas, process parameters, or test data were used. The field list, sampling/retention, traceability, lookup, and acceptance checklist are editorial suggestions; actual standards, methods, periods, and liability depend on the law, contract, quality agreement, product standard, company procedures, and professional advice.
Sources and scope
Information is current to 2026-10-31. The following are public official/primary pages; their scope, version, and wording control.
- Civil Code of the PRC, sale-of-goods chapter: Supreme People's Court. Articles 615, 619, 620, 621, 622, and 623.
- Product Quality Law of the PRC (2018 amendment): NPC. Articles 26, 27, 33, and 40.
- Standardization Law of the PRC (2017 revision): NPC. Article 27 (enterprise standard self-declaration).
- CNAS-R01:2023, Rules for the Use of Accreditation Symbols and Statements of Accreditation Status: CNAS. Accreditation scope, symbol use, non-accredited items, and no implication of product certification.
If shipping documents also involve packaging, marks, or delivery terms, see the packaging and shipping page acceptance checklist.