The logo on a certificate may be familiar while the named holder, factory, product family or certification type is not the one proposed for the order. A disciplined review follows the evidence chain instead of treating the PDF as a transferable badge.
Certificate review is an applicability exercise. The reviewer must establish what kind of attestation is being offered, who holds it, which location and activity it covers, whether the issuing and accreditation records are current, and whether the proposed window configuration falls inside any product-specific scope. A genuine certificate can be irrelevant to an order; a relevant management-system certificate still does not certify the windows; and a laboratory report still needs specimen-to-project comparison. The practical conclusion is therefore bounded: supported for a stated question, limited, unresolved, or not applicable.
Evidence boundary: This is a buyer-side document review, not certification, accreditation, regulatory approval or legal advice. ISO develops standards but does not issue ISO certificates. IAF CertSearch covers accredited management-system certificates, not product certification. Use the current issuing body, scheme owner, regulator and accreditation-body records for the exact certificate.
1. Start with the decision the certificate is expected to support
Do not begin by asking whether the document looks real. Begin with the procurement decision. Is the buyer trying to confirm that a proposed contracting entity operates a quality management system, that a named plant is inside the certified scope, that a particular window model is authorised under a product programme, that a laboratory was competent for a stated test, or that a destination approval is current? Those are different questions, answered by different records.
Write one claim per row. A supplier statement such as ‘we are ISO and AAMA certified’ mixes an organization-level management-system claim with a product-programme claim. Separate the legal holder, site, standard or scheme, product identifier, performance characteristic, label and project configuration. If the seller cannot say what decision the document supports, the certificate should remain reference material rather than release evidence.
The word certificate is not a sufficient evidence type. ISO/IEC 17021-1 concerns bodies that audit and certify management systems. ISO/IEC 17065 concerns bodies certifying products, processes and services. ISO/IEC 17025 concerns laboratory competence. ISO’s conformity-assessment guidance also warns that a management-system certification mark must not be put on a product in a way that implies product certification. This distinction should control the rest of the review.
| Procurement question | Evidence type to locate | What it may support | What it does not settle |
|---|---|---|---|
| Does the named organization have a certified management system? | Current certificate and official management-system database result | Entity, sites, standard, scope and status shown | Exact window performance or project acceptance |
| Is the proposed product listed? | Scheme-owner directory, certificate schedule and required label | Listed manufacturer/product/configuration within programme rules | Unlisted variants, installation or every project requirement |
| Was a test performed by a competent laboratory? | Full report plus the laboratory's current accredited scope | Named test, specimen, method and reported result | Transfer of the result to a materially different unit |
| Is the product legally acceptable at destination? | Current regulator/scheme records and competent local review | Requirement-specific status when identities and scope match | Contract compliance or suitability for all building conditions |
| Are two companies related? | Current official company records and documented authority | Only the relationship actually evidenced | Automatic transfer of certificates, warranties or obligations |
2. Capture the certificate as data, not as a picture
A cropped phone image hides the fields needed for verification. Request the complete certificate and every schedule, annex and condition referenced by it. Record the original-language holder name, registration identifier where shown, certified address or site, certificate number, standard or scheme, scope wording, issue and expiry dates, status, issuing body, accreditation mark and any product or plant code. Preserve the file received and the date of the check.
Transcribe rather than paraphrase critical scope language. ‘Manufacture of aluminium doors and windows’ is not the same as design, extrusion, coating, insulating-glass fabrication or installation. A certified address may be a head office, one factory, several listed sites or a temporary site. An English trading name can differ from a Chinese legal name without proving either a match or a mismatch. Compare stable identifiers and obtain qualified translation when meaning is material.
Treat missing annexes as missing evidence. Product certificates often depend on schedules that define models, plants, ratings or authorised labels. Management-system certificates can have multi-site appendices. Laboratory accreditation is commonly defined by a detailed scope annex listing methods, standards, products and parameters. A front page without its controlled attachments may be impossible to apply correctly.
| Field | Record exactly | Cross-check | Hold condition |
|---|---|---|---|
| Certificate holder | Original-language legal name and shown identifier | Official entity and certificate records | Only brand, translated name or logo supplied |
| Certified location | Every site and address in certificate/annex | Proposed manufacturing and contracting roles | Proposed plant absent or address unexplained |
| Certificate type | Management system, product, process, service or other | Applicable ISO/CASCO route or programme rules | Document type cannot be distinguished |
| Scope | Verbatim activity/product/scheme wording | Order role and proposed configuration | Broad marketing paraphrase replaces formal scope |
| Status and dates | Issue, effective, expiry, suspension/withdrawal if shown | Issuer and official databases on review date | Only an undated PDF or expired screenshot |
| Issuer/accreditation | Names, marks, certificate and accreditation identifiers | Issuer directory and accreditation scope | Untraceable body or unsupported mark |
| Annex/label | Schedule revision, plant/model codes and label rules | Scheme directory and physical product evidence | Required annex or label identity missing |
3. Resolve the holder, factory and seller identity chain
List the entities in the proposed transaction before drawing a conclusion. The quotation may come from a trading company; the contract from another entity; the window assembly from a factory operator; glass, coating or hardware from external providers; and the certificate from a parent company, sister company, brand owner or component producer. Legitimate structures exist, but a shared brand, director, address, email domain or sales contact does not transfer a certificate.
Ask for a written relationship and authority map. It should show who owns the certificate, who operates each certified site, who is authorised to apply a product label, who accepts the purchase order, who controls production, and who carries warranty or conformity obligations. Then compare that map with current official company and certificate records. If a certificate belongs to another company, request the scheme-specific basis on which the proposed manufacturer or product is included. Do not accept a generic letter of authorisation when the scheme requires a listed plant or licensee.
Use neutral dispositions. An unexplained difference is not proof of fraud. It is a gap between the proposed order and the evidence. Mark it open, identify the clarification required and keep production or approval consequences proportionate to the risk. If the holder has changed name, address, legal status or ownership, check whether the issuer has updated the certificate rather than assuming continuity.
| Role | Proposed entity | Primary evidence | Certificate link to establish |
|---|---|---|---|
| Seller/contract party | [record legal name] | Current official registration and signed offer | Whether it is holder, authorised licensee or neither |
| Factory operator | [record legal name/site] | Official record, site evidence and production documents | Whether the certified site and activity include it |
| Certificate holder | [copy exact name] | Issuer/database record | Direct identity or scheme-authorised relationship |
| Product brand/licensee | [record] | Scheme directory and licence terms | Authority to mark the exact product |
| Component provider | [record by component] | Approved BOM, purchase and traceability records | Component certificate scope without transfer to whole window |
| Warranty/conformity owner | [record] | Contract, declaration and authorised signature | Obligation is explicit, not inferred from logo |
4. Verify status through the right official channel
Use the certificate number and exact holder name in the issuer's public validation service. For accredited management-system certificates, IAF CertSearch can show certificate status, standard or scheme, scope, locations, certification body and accreditation body when the record is in its covered database. Its own FAQ states that the database focuses on accredited management-system certification and does not cover product certification. A missing result therefore needs investigation; it is not a universal conclusion about every certificate type.
For China, the Certification and Accreditation Administration of China links to the national certification and accreditation public service platform, currently branded 认e云, and to certification, accreditation and testing information services. CNCA also requires certification bodies to provide a public route for checking certificate validity rather than relying only on a claim that a certificate is ‘CNCA searchable’. Check both the current public record and the issuing body's own validation route where applicable.
For laboratory or certification-body accreditation, inspect the accreditation body's published scope. CNAS guidance tells users to search recognised organizations and open the laboratory accreditation attachment to see the recognised capability, including applicable testing standards. A logo or accreditation number alone does not show that the body was accredited for the method, product and parameter in the report at the relevant time.
Capture the URL, query terms, date/time, result and any status explanation. If a database requires an account or cannot be accessed, request validation from the issuer using independently sourced contact details. Never use the phone number printed only on the disputed certificate as the sole verification route.
| Evidence offered | Primary check | Record from result | Important boundary |
|---|---|---|---|
| Accredited management-system certificate | Issuer plus IAF CertSearch where covered | Holder, sites, standard, scope, status, CB and AB | Not a product-certification database |
| China-issued certification | CNCA public platform plus issuing body's validation route | Certificate identity, holder, scope, status and dates | Current result controls over a saved screenshot |
| Laboratory accreditation | CNAS or relevant accreditation-body directory and scope annex | Location, methods, standards, products and parameters | Accreditation is scope-specific |
| Fenestration product programme | Current programme-owner certified-products directory | Manufacturer/plant code, model, grade/rating and status | Programme and label rules govern applicability |
| Test report | Issuing laboratory confirmation and accreditation scope | Full specimen, method, date, result and report status | A report is not automatically product certification |
5. Compare product scope configuration by configuration
When product certification is relevant, read the scheme rules and directory, not just the certificate title. FGIA states that its Gold Label programme is a third-party testing and quality-assurance programme, that certified products and manufacturers are listed in its directory, and that certification is valid when products bear the required official label. Its directory identifies authorised products and uses manufacturer or plant codes and performance fields. NFRC likewise provides a Certified Products Directory and label-verification route for window, door and skylight ratings. These are programme examples, not universal approval routes.
Build a feature-by-feature comparison between the listed or tested configuration and the proposed unit. At minimum compare operator type, frame and sash series, dimensions, mullions, glass build-up, reinforcement, hardware, seals, drainage, finish where material, plant, assembly route, product code, rating and test standard. Then ask the scheme owner, certification body or responsible professional how allowed variations and product families are defined. Do not invent an engineering rule for extension.
A matching family name is not enough. A fixed light and a large operable sash can share branding while having different structural and water risks. A thermally broken window with different glass, spacer and frame options can have different thermal ratings. A change in plant or label may affect certification authorisation. Where scope cannot be demonstrated, phrase the result as ‘no applicable product evidence identified for the proposed configuration’ rather than declaring that the product fails.
| Attribute | Certified/tested record | Proposed order | Match status and action |
|---|---|---|---|
| Programme and current edition | [record] | [project requirement] | Confirm scheme and acceptance basis |
| Manufacturer and plant | [record code/address] | [proposed operator/site] | Resolve exact identity and authorisation |
| Product family/operator type | [record] | [record] | Do not bridge unlike operations by brand |
| Size and configuration | [tested/listed range] | [schedule extremes] | Obtain scheme-specific extension basis |
| Glass and infill | [record] | [build-up] | Check thermal, structural and safety implications separately |
| Hardware/reinforcement | [record] | [record] | Treat unreviewed substitution as open |
| Performance grade/rating | [record exact value/method] | [required value/method] | Compare like with like; no interpolation without authority |
| Label/product code | [authorised format] | [production control] | Verify traceability on supplied units |
6. Keep certificate validity separate from project applicability
A valid certificate answers only the question defined by its certification activity and scope. A quality-management-system certificate may support that a named organization and sites were audited against the stated management-system standard for the stated scope. It does not assign a design pressure, confirm glass safety selection, validate an interface detail, prove capacity, approve a subcontractor or guarantee that every unit conforms.
A product certificate can be stronger product evidence, but only within the scheme, listed product and authorised variations. It does not automatically satisfy a different jurisdiction, contract specification, project size, wind load, acoustic target, fire requirement, installation detail or maintenance condition. A competent project review still has to compare each requirement with applicable evidence.
Likewise, an accredited laboratory report supports the result reported for the named specimen under the named method and conditions. Laboratory accreditation supports competence within a published scope; it is not a blanket endorsement of the client's product. Keep the report, accreditation scope and configuration comparison together, and record any engineering or scheme-authority decision used to extend the evidence.
| Evidence | Reasonable bounded statement | Unjustified leap | Separate project gate |
|---|---|---|---|
| ISO 9001 certificate | Named entity/site/scope has current management-system certification | All windows are certified or defect-free | Configuration, performance and production evidence |
| Product certification listing | Exact listed product is authorised under stated programme/status | Every variant or destination is approved | Project specification and permitted-variation review |
| Accredited test report | Named specimen achieved reported result by named method | Any similar-looking unit achieves it | Specimen-to-order applicability analysis |
| Component certificate | Named component falls within its programme scope | Complete window inherits whole-product performance | System integration and whole-product evidence |
| Official registry match | The current record matches selected identity/status fields | Factory capability, solvency or contract reliability | Transaction, capability and risk review |
7. Issue a bounded disposition and control changes
Finish with a short decision that another reviewer can reproduce. ‘Supported’ means the stated claim is supported by current primary evidence within recorded limits. ‘Limited’ means some identity or scope elements match but the evidence is narrower than the claim. ‘Open’ means necessary information is missing or awaiting confirmation. ‘Not applicable’ means the document addresses a different evidence question. Reserve ‘invalid’, ‘counterfeit’ or ‘fraudulent’ for competent authoritative findings.
Attach conditions to release. A product may remain on technical hold until the issuer confirms a plant, the current directory shows the code, a missing annex is supplied, or a qualified reviewer approves the configuration comparison. A management-system certificate can be accepted for prequalification while the product evidence remains open. This avoids both extremes: rejecting a supplier solely because a document is misunderstood, or allowing an impressive PDF to bypass technical review.
Recheck after material changes. Holder name, legal status, site, certification body, accreditation status, product model, components, plant, scheme edition, expiry, suspension and withdrawal can alter the conclusion. Record a review date and trigger rather than copying a certificate indefinitely between projects.
| Claim ID | Disposition | Evidence relied on | Limit/remaining gap | Owner and next gate |
|---|---|---|---|---|
| CERT-01 | Supported / limited / open / not applicable | Primary URLs, files and review date | Exact identity, scope or configuration limit | Named reviewer and release consequence |
| CERT-02 | [record] | Issuer/database confirmation | Annex, site or status question | Supplier/issuer response deadline |
| PROD-01 | [record] | Scheme directory and label/product schedule | Variant or project comparison | Technical/scheme review |
| LAB-01 | [record] | Full report and accreditation scope | Method/specimen applicability | Responsible engineer/specifier |
8. A practical twelve-step review workflow
- Define the exact procurement claim the document is expected to support.
- Classify the document as management-system, product, process, service, personnel, laboratory, inspection, regulatory or other evidence.
- Obtain the complete original certificate, annexes, schedules and label or product code rules.
- Transcribe holder, site, scope, standard/scheme, issuer, accreditation, number, dates and status.
- Map the seller, contract party, factory operator, certificate holder, licensee and obligation owner.
- Search the issuer, scheme owner, CNCA, IAF CertSearch or accreditation-body record appropriate to the document type.
- Confirm that the issuer or laboratory's accreditation scope covers the relevant certification or test activity where accreditation is claimed.
- For product evidence, compare the listed/tested configuration with the proposed schedule and document every difference.
- Ask the competent scheme, regulatory or project authority to decide material extensions rather than inventing transfer rules.
- Record the result as supported, limited, open or not applicable, with citations and review date.
- Attach the result to a defined approval or production gate; do not file it without consequence.
- Set recheck triggers for expiry, suspension, entity/site change, product substitution, scheme revision and project change.
The decisive sentence: This evidence supports [precise claim] for [named entity/site/product] under [standard or scheme] as of [review date], subject to [recorded limits]; it does not establish [separate product or project questions].
FAQ
Does an ISO 9001 certificate mean the windows are ISO certified?
No. ISO 9001 is a management-system standard. A current accredited certificate may support a bounded statement about the named organization's quality management system and scope; it does not certify each window or its performance.
Can a trading company use its factory's certificate?
Only in the precise way permitted by the certificate and scheme. Map both legal entities, the certified site, manufacturing role, authorisation and contract obligations. Do not assume a relationship transfers scope.
Is a certificate valid if it appears in IAF CertSearch?
The result can support authenticity and current status for an accredited management-system certificate in the database, together with its holder, locations, standard and scope. IAF CertSearch does not cover product certification, and the result does not prove product or project suitability.
What if the holder name differs only in English spelling?
Compare the original-language legal name, registration identifier, address and issuer record. English renderings can vary. Use qualified translation and issuer confirmation where the identity decision is material.
Does CNAS accreditation make every report from a laboratory acceptable?
No. Check the laboratory, location, dates and detailed accredited scope for the relevant product, method, standard and parameter, then assess the report and proposed configuration separately.
Can a component certificate cover the complete window?
Not by itself. It supports only its defined component or programme scope. Whole-window integration, performance, labelling and project requirements require their own evidence.
Should a missing database result be treated as fraud?
No. Check spelling, identifiers, status history, database coverage, issuer and accreditation body through independently sourced channels. Record the result as unresolved unless a competent authority establishes more.
How often should the certificate be checked?
At defined gates and after relevant changes: prequalification, contract award, production release, shipment where needed, expiry, suspension, entity/site change, product substitution or scheme revision.
Continue the project review
Connect this guide with the proposed window and door systems, then review how Cavorlen approaches manufacturing and quality control. When your schedule is ready, send it through the project review form.
Official sources used
ISO — Help and support: ISO does not issue certificates ↗ISO/CASCO — Attestations of conformity ↗ISO/IEC 17021-1:2015 — Management-system certification bodies ↗ISO/IEC 17065:2012 — Product, process and service certification bodies ↗ISO/IEC 17025:2017 — Testing and calibration laboratories ↗IAF CertSearch — Official FAQ and database scope ↗CNCA — Certification and accreditation online services ↗CNCA — 2025 notice on effective management-system certification ↗CNAS — Guidance on searching accreditation results and scopes ↗FGIA — Product certification programmes ↗FGIA — Certified Products Directory ↗NFRC — Certified Products Directory ↗Related buyer guides
This guide does not authenticate a certificate from an image, certify any company or product, determine legal affiliation between entities, approve a window for a destination or project, or imply that a management-system certificate proves product performance, capacity, workmanship or delivery. It makes no statement about Cavorlen certificates, factories, products or capability. Material conclusions require current primary records and competent scheme, regulatory and project review.