Updated: — Added product-series identification links to the qualification review; no certificate scope, validity or product approval claims added.
Separate company evidence from product evidence
An ISO management-system certificate, an API authorization and a product-level test record answer different questions. Keep the certificate scope and the product model or family visible together.
A supplier qualification file is easier to review when every record has a clear issuer, identifier, stated scope and validity date.
Match the record to the project duty
Check the pressure class, material, end connection, temperature and applicable design or test standard against the project data. A valid certificate does not automatically cover every valve or every service. When reviewing a soft-seated trunnion-mounted ball valve or forged steel gate valve quotation, record the offered series and model before requesting the applicable evidence. A link to a catalogue page does not establish certificate scope, validity or project approval.
If a project requires an inspection plan, material traceability or special testing, request those records as part of the RFQ rather than treating them as an afterthought.
Keep an auditable revision trail
Record the file name, issue date, certificate number and the person who reviewed it. When a document is replaced, keep the superseded version identifiable so procurement and inspection teams are working from the same package.
Kehua's resources page provides an RFQ checklist and a direct route to request the relevant qualification documents for review.
Compare valve families
Use this guide together with the relevant valve family and project operating data.
More technical notes