Quality System Certificate Pages on Changzhou Manufacturer Websites: How Should They Be Accepted?

Direct answer: In 2026 the biggest change for a website's quality-certificate page is not "add a few more images", but that ISO 9001:2026 has been published and ISO 9001:2015 is in a three-year transition; meanwhile IATF 16949:2016 is still the current edition (the second edition is still being revised and has not been published) and ISO 13485:2016 remains current. Customers/procurement do not just look for the word "certificate"; they check the standard/version, certification scope (product/process/site), certificate number, certification body, accreditation/IAF mark, validity/surveillance status, whether it can be verified, and whether the certificate covers the model and factory you are selling. A website page should turn these into reviewable information—not just put an "ISO 9001" logo on the homepage. Information is current to 2026-11-05. This is a review of public rules and project practice, not certification, legal or procurement-audit advice; specific rules follow ISO/IATF/IAF, the accreditation body and the certification body.

This guide is for quality, procurement, sales and website teams at electronics/electrical, automotive, medical device, equipment, hardware/tools, connector/harness, chemical, packaging and export manufacturers in Changzhou and nearby areas. It explains how to write and accept a quality-system certificate page. The certificate page is both a customer trust entry and the first piece of evidence in supplier onboarding/customer audits; a wrong version, scope or validity date is worse than no page.

How does the certificate page relate to supplier onboarding, audits, IQC and quality agreements?

The supplier onboarding/AVL page answers "how to become a supplier"; the supplier audit page answers "how to audit"; the IQC page answers "how incoming goods are inspected"; the quality agreement page answers "how quality responsibility is agreed"; the certificate page only answers "which system certificates we hold, what they cover, when they expire, and how to verify them". A certificate is one piece of onboarding/audit evidence; it does not replace a site audit, PPAP, IQC, CAPA or contract. Conversely, a certificate does not mean every batch is conforming.

Common breakpoints: only a blurry image; expired/suspended certificates left online; scope does not cover the customer's model; only the HQ certificate for multiple factories; ISO 9001 described as "product quality certification"; "IATF certified" without scope; ISO 13485 described as "CE certification"; ISO logo used without authorisation; certificate number cannot be verified; Chinese/English pages inconsistent. A page that states "certificate—scope—site—verification" saves the customer/procurement repeated emails.

This page map is editorial; certificate requirements follow ISO/IATF/IAF, the accreditation body and the customer contract.

What does each common system certificate cover?

ISO 9001 is a general quality management system (QMS), and the 2026 edition has replaced 2015; ISO 14001 is an environmental management system; ISO 45001 is occupational health and safety; IATF 16949 is the automotive QMS (built on ISO 9001, current 2016 edition); ISO 13485 is the medical device QMS (current 2016 edition); ISO/IEC 27001 is information security management. All are "system certifications", not product certification/CE/FDA approval. Which certificate a customer wants depends on the industry/contract: automotive customers often want IATF 16949, medical customers often want ISO 13485, general manufacturing often wants ISO 9001, and data-sensitive customers may want ISO 27001. Separate the standards on the page; do not merge them into "international certification".

Acceptance checks: standard/version; scope; industry-specific requirements; customer acceptance; relationship to product/process. Common gaps: only "ISO certified"; treating ISO 9001 as IATF 16949; treating ISO 13485 as CE; treating ISO 14001/45001 as product quality; outdated versions; one image for all standards; no version/scope.

Standards/versions follow ISO/IATF official pages and the certificate itself; other systems' current versions should be checked against ISO updates.

ISO 9001:2026 transition: what should the website and certificate say?

ISO has confirmed that ISO 9001:2026 is the current edition, replacing ISO 9001:2015; organisations already certified to 2015 have a three-year transition to 2026, without starting certification from scratch; the exact timing/audit arrangements are set by the certification body under accreditation rules. During the transition, a 2015 certificate may still be valid, but the website cannot show only 2015 forever: state the current certificate version, the transition plan, the expected change date and what the customer needs to do. The 2026 edition strengthens leadership/quality culture/ethical behaviour, alignment with strategy, risk and opportunity, and people awareness, while retaining the process approach, risk-based thinking and continual improvement; it is not a "rebuild from zero". If a customer asks for 2026, the company should show a transition plan/timeline, not change the year on the 2015 certificate.

Acceptance checks: certificate version; 2015/2026; transition plan; certification-body confirmation; transition audit date; customer communication; old-certificate removal date. Common gaps: in 2026 still only 2015 with no plan; photoshopping 2015 into 2026; claiming "fully transitioned" before the certificate is updated; ignoring surveillance audits; different sites at different stages; explaining only when the customer asks.

Transition rules follow the ISO official explanation and the certification/accreditation body; the three-year transition is ISO's public statement, and specific audit dates follow the certification body.

Which fields should be checked on a certificate?

At least nine: (1) standard name/version (ISO 9001:2026, IATF 16949:2016, ISO 13485:2016, etc.); (2) certification scope (products/services/processes); (3) site/address (HQ/factory/multi-site); (4) certificate number; (5) certification body; (6) accreditation body/IAF MLA mark (if applicable); (7) validity/first certification/latest audit; (8) status (active/suspended/withdrawn/expired); (9) signature/issuer/verification route. The page should not just show a thumbnail; provide a readable PDF/large image, certificate number, scope and verification link. Customers/procurement use these fields to check "is this your certificate, does it cover my product, and is it still valid".

Acceptance checks: completeness; page text matches the certificate; scope coverage; site coverage; validity; status; verification link; PDF version. Common gaps: image too blurry to read the number; scope says "various products" but is actually narrow; HQ certificate does not cover branch factories; number differs from the PDF; only the year is shown; suspended certificate still displayed; verification link broken; Chinese/English versions differ.

Certificate fields follow the certificate text; different schemes may have additional fields/annexes.

How should a certificate be verified?

Use three routes: (1) IAF CertSearch: the IAF global database of accredited management-system certificates, to check certificate validity, whether the certification body is accredited, and whether the accreditation body is an IAF MLA signatory; (2) certification body website/customer service: search by certificate number/company name to confirm scope, site and status; (3) CNAS/accreditation body: check whether the certification body/laboratory is accredited and use its certificate-verification route (per CNAS/CB). IATF 16949 can also be checked via IATF-related databases/the certification body; ISO 13485 via the certification/accreditation body. Do not trust only a PDF/image from the customer; scans can be forged and status can be suspended. Keep the verification screenshot/record with the query date.

Acceptance checks: verification route; query date; certificate number; company name/address; scope; status; CB accreditation; screenshot/archive. Common gaps: checking a "sample" page only; using search-engine results as verification; displaying a certificate that cannot be found; company name change not updated; address/site mismatch; suspended status missed; no query record.

Verification routes follow IAF/CNAS/certification-body official pages; a query result is not customer approval or a product-compliance conclusion.

How should scope, site and multi-site be accepted?

The certificate scope is "which products/services/processes are covered", and the site is "which addresses/factories were audited". If the customer's product is outside the scope, a beautiful certificate is not applicable; multi-factory companies must confirm whether each production address is in the certificate/annex or only HQ/one workshop. Remote support, outsourced processes, temporary sites and design/development functions should also be checked in the annex/audit report. A scope that is too broad ("various metal products") but the actual process is narrow will trigger audit questions; too narrow may lose orders. The right approach is to list product lines/processes/sites clearly and align with the customer contract/audit form.

Acceptance checks: products/processes; site list; multi-site annex; outsourcing/remote; design function; exclusions; whether the customer's product is covered. Common gaps: HQ certificate covers all branches; "various" with no detail; customer model not in scope; outsourced process not covered; address change not updated; multi-site annex missing; design excluded but "design capability" claimed.

Scope/site interpretation is editorial; the certificate text, annex and certification-body rules control.

Is IATF 16949 2016 or 2026?

As of the date of this article, IATF 16949:2016 (1st Edition) is still the current edition; the IATF has started the second-edition revision but has not published it, and the official 30 July 2026 status communiqué (SC-2026-005) is still updating progress. IATF Rules 6th Edition has been effective since 1 January 2025; it is the "certification rules", not a standard revision. Automotive customers also add Customer Specific Requirements (CSR), PPAP, APQP, MSA, SPC, etc.; an IATF 16949 certificate does not replace these, nor the ISO 9001:2026 transition. Do not write "IATF 16949:2026" or "passed the second edition" before the IATF officially publishes it and the certificate is updated.

Acceptance checks: standard version; Rules version; second-edition status; CSR; certificate scope; transition plan. Common gaps: writing "IATF 2026"; treating Rules 6 as a standard revision; using IATF to replace ISO 9001:2026; ignoring CSR; scope not covering automotive products; writing "compliant with IATF" as "IATF certified".

IATF versions/rules follow IATF official publications; the second-edition date and transition are not predicted here.

What is the relationship between ISO 13485 and CE/MDR?

ISO 13485:2016 is the medical device quality management system standard, currently valid (ISO confirmed it after a 2025 review); it demonstrates the organisation can consistently meet medical device and applicable regulatory requirements, but it is not a CE certificate, not an MDR compliance certificate, and not product registration. EU MDR requires manufacturers to establish a QMS; ISO 13485 is often used as a basis, but CE also requires conformity assessment, technical documentation, clinical evaluation/PMS, UDI/EUDAMED and a Notified Body (where applicable). The website can say "ISO 13485 system certified"; it cannot say "ISO 13485 = CE/MDR certification", nor treat the ISO 13485 certificate as a product marketing authorisation.

Acceptance checks: standard version; certification scope (design/production/service); Notified Body/CE status; MDR technical file; customer/regulatory requirements. Common gaps: ISO 13485 described as CE; system certificate treated as product registration; scope excludes design; wrong Notified Body number; MDR file missing; ISO 13485 used to replace a customer audit.

The ISO 13485/MDR relationship is editorial; ISO, EU MDR, the Notified Body and the competent authority control.

How should the website certificate page display them?

Use a "certificate card" for each: standard/version, certification scope, site, certificate number, certification body, accreditation body/IAF mark (if applicable), validity, status, PDF/large image, verification link/QR code, query date. Group multiple certificates by standard/site; remove expired/suspended/withdrawn certificates or mark their status; keep Chinese/English pages in sync. The public page should show the certificate and scope summary only; full audit reports, customer-specific documents and internal remediation records are provided under NDA/permission. Do not use only a compressed image or an unsearchable scan; customers must be able to copy the certificate number and verify it.

Acceptance checks: field completeness; readable PDF; verification link; version/validity; status; multi-site; Chinese/English consistency; update date; permission boundary. Common gaps: blurry image; no number; broken link; only old version; expired but online; inconsistent Chinese/English; publishing customer audit reports; no query date; QR code points to the homepage instead of the verification page.

Display is editorial; the certificate text and certification/accreditation-body rules control.

What must not be written?

High-risk claims: "ISO-certified company/international certification" (without standard/scope/site); "ISO 9001 product quality certification" (system ≠ product); "IATF 16949:2026/passed the second edition" (not published); "ISO 13485 = CE/MDR certification" (not); "FDA certified/approved" (the FDA does not "certify" a QMS as "FDA certified"; specific products are cleared/approved); "certificate valid forever" (validity/surveillance); "all factories certified" (only HQ covered); "ISO logo can be used freely" (registered trademark, authorisation required); "a certificate guarantees customer approval/product conformity" (not). These are either inaccurate or confuse system/product/customer approval.

Safer wording: "We hold [standard/version] certificate no. [x], issued by [CB], accreditation [AB/IAF], scope [products/processes/sites], valid until [date], verifiable at [route]; ISO 9001 is a QMS certification, not product CE/FDA or customer approval." Provide audit reports/technical files under NDA when requested; do not publish customer-specific documents.

These red lines are editorial; whether a claim is false advertising/non-compliant is determined by regulators and the contract—not this article.

How should expiry, suspension, withdrawal and transition be handled?

A certificate has a lifecycle: initial certification → surveillance audit (usually annual) → recertification (usually 3 years) → transition/change. When nonconformity, missed audits, scope changes, address changes, suspension/withdrawal occur, update the website promptly: suspended/withdrawn certificates cannot continue to be shown as valid; expired certificates should be removed or marked "expired"; transition should update the standard/version and validity; company name/address changes require a new certificate/annex. Keep an internal certificate register (standard, number, site, validity, next audit, status, owner) with reminders; sales/tender teams should check status before using a certificate. A customer audit finding an expired/suspended certificate online directly affects onboarding.

Acceptance checks: register; expiry reminders; surveillance/recertification; suspension/withdrawal; transition; name/address changes; page updates; sales use. Common gaps: no register; discover expiry too late; suspended still online; transition only changes text; address change without a new certificate; sales uses old PDF; no status check before a customer audit; multiple sites expire at different times.

The certificate lifecycle follows the certification/accreditation rules; the website should reflect the latest status.

Go-live acceptance checklist

Ten checks: standard/version, scope, site, certificate number, CB/accreditation, validity/status, verification route, PDF/readability, Chinese/English consistency, update/removal mechanism. Each needs an owner, evidence and review date. The pass condition is not "the page has a certificate image", but that a customer/procurement can copy the number and verify it, and confirm it covers their product and factory.

Before go-live, run one real certificate through: check standard/version → scope/site → number/CB/AB → validity/status → open PDF/verification link → compare with the customer's product. Any step that fails is a gap in the page or certificate management. Companies in the ISO 9001:2026 transition should add a "transition plan/timeline" item.

This checklist is editorial; specific certificate requirements follow ISO/IATF/IAF, the accreditation body and the certification body.

Who should read this, who should not, and what decisions does it support?

It suits quality, procurement, sales, legal and website teams at electronics/electrical, automotive, medical device, equipment, hardware/tools, connector/harness, chemical, packaging and export manufacturers in Changzhou and nearby areas; also companies doing supplier onboarding, customer audits, tenders or website redesign. It does not suit teams with no system certificates, teams wanting to "buy an image", or teams wanting a certificate to replace a site audit/product compliance.

Read it if your website has a certificate/qualification page; a customer asks for ISO 9001/IATF 16949/ISO 13485; you are transitioning to ISO 9001:2026; a certificate is expiring/renewing; you have multiple factories/sites; a customer audit found the scope does not cover the product. Skip it if you treat ISO 9001 as product certification, ISO 13485 as CE, write "IATF 2026", or use the ISO logo without authorisation. It supports self-review of fields, scope/site, verification, transition, display and red lines.

FAQ

After ISO 9001:2026 is published, can 2015 certificates still be used?

For a period. ISO states that ISO 9001:2026 has replaced 2015 and organisations certified to 2015 have a three-year transition; specific audit arrangements are set by the certification body under accreditation rules. A 2015 certificate may remain valid during the transition, but the website should state the current version, transition plan and expected date; do not photoshop 2015 into 2026, and do not write "already transitioned" before the certificate is updated.

Can the website say "ISO 9001 certified company"?

Not just that sentence. Write "holds ISO 9001:2026 (or 2015) certificate no., certification body, accreditation body, scope, site, validity and verification route". ISO 9001 is a QMS certification, not product certification/CE; products or factories outside the scope cannot use it in marketing.

Is IATF 16949 2016 or 2026 now?

As of the date of this article, IATF 16949:2016 is still current; the second edition is in revision and not published, and the IATF official 30 July 2026 status communiqué (SC-2026-005) is still updating progress. IATF Rules 6th Edition has been effective since 1 January 2025; it is certification rules, not a standard revision. Do not write "IATF 16949:2026/passed the second edition" in advance.

Is ISO 13485 the same as CE/MDR?

No. ISO 13485:2016 is a medical device QMS standard, currently valid; CE/MDR also requires product conformity assessment, technical documentation, clinical evaluation/PMS, UDI/EUDAMED and a Notified Body (where applicable). The website can say "ISO 13485 system certified"; it cannot say "ISO 13485 = CE/MDR certification".

How can a certificate be verified?

Use IAF CertSearch to check certificate validity, whether the certification body is accredited and whether the accreditation body is an IAF MLA signatory; then use the certification body's website/customer service to check the number/company name, scope, site and status; CNAS/accreditation bodies can confirm accreditation. Do not trust only a PDF/image; keep a screenshot with the query date.

What if a certificate is expired, suspended or does not cover the product?

Expired/suspended/withdrawn certificates cannot be shown as valid; remove them or mark the status, and complete surveillance/recertification/remediation. If the scope does not cover the customer's product/factory, either extend the scope/add the site, or explain honestly and use other evidence (audit, PPAP, testing); do not use an HQ certificate as a branch certificate. Customer approval/product compliance still follows the contract and regulations.

One-sentence takeaway

A Changzhou manufacturer's certificate page is not about "hanging a few ISO images". It should turn standard/version, scope, site, number, CB/accreditation, validity/status, verification route and transition plan into reviewable information—so a customer can copy the number, verify it, and confirm it covers their product and factory.

Method and limitations

This is a review of public rules and project practice, not an audit, certification, procurement-approval or legal opinion on any company, certificate, certification body, product or contract. No undisclosed customer, certificate, audit or product data were used. The standard matrix, fields, verification routes, display and acceptance items are editorial suggestions, not certification/legal conclusions. Specific standard versions, certification scope, certificate status, transition timing and customer requirements depend on ISO/IATF/IAF, the accreditation body, the certification body and the contract; standards/rules may change, so recheck before publication.

Sources and scope

Information is current to 2026-11-05. The following are ISO/IATF/IAF/CNAS official pages; their versions, rules and certificate status control.

1. ISO, ISO 9001:2026: What businesses need to know: ISO. 2026 edition replaces 2015, three-year transition, voluntary certification, transition steps.
2. ISO, ISO 9001:2026 — Quality management systems — Requirements: ISO. Standard status/edition/publication date.
3. IATF, IATF 16949:2016 / Publications: IATF. IATF 16949:2016 1st Edition, Rules 6th Edition and second-edition revision status.
4. ISO, ISO 13485:2016 — Medical devices — Quality management systems — Requirements for regulatory purposes: ISO. Current edition, 2025 review confirmation and medical device QMS.
5. IAF CertSearch: IAF CertSearch. Global database of accredited management-system certificates; check certificate/CB/AB/IAF MLA.
6. China National Accreditation Service for Conformity Assessment (CNAS): CNAS. Accreditation and certificate-lookup entry for certification bodies/laboratories.
7. ISO, Certification: ISO. Certification definition, ISO logo/authorisation rules and certificate verification route.