This page explains the one certificate sentence this site uses, why no certificate list appears here, and how a buyer should request the certificate its market actually needs.
The one sentence this site uses
Wherever certificates are mentioned on this site, the sentence used is: Certificates available upon request. Ask in your inquiry which certificates apply to the line and market you have in mind, and the supplier will confirm the scope for your order.
A general sentence is honest in a way a list would not be: it tells a buyer that certificates can be asked for, without pretending that a particular certificate exists, applies to a particular line, or has been verified. Any buyer who needs more than that general assurance must turn the request into a named question, as the next sections explain.
Why no certificate list is published
Publishing a certificate list would require a source that names certificates, their scope and their issuing bodies, and no such source was available in the listing text reviewed for this project. Inventing a familiar certificate name from market knowledge would be worse than publishing nothing, because a buyer might rely on it for a project specification and discover at the last stage that the certificate was never held.
The same restraint applies to certificate numbers and issuing bodies, which are never written on this site, and to any suggestion that a certificate applies to all lines. A certificate that exists for one line or one market does not automatically cover another, and only the supplier can state the scope for the exact product and market in question.
How to request a certificate by name
A certificate request should name the certificate, the market or project specification that requires it, the line and design it must cover, and the form in which the buyer needs it, such as a copy for a project file or a statement for a tender. That precision lets the supplier answer yes, no or with a scope note, instead of returning a general assurance that may not satisfy the specification.
It also helps to state the timing, since a certificate needed for a tender deadline is different from one wanted for general records. A request that names certificate, market, line and deadline will get a precise answer, while a request that asks only whether certificates exist will usually get the general sentence back.
Certificates and the inquiry message
The certificate question belongs in the original inquiry message, beside backing, size, design and samples, rather than as a late addition after an order is placed. Early asking matters because a certificate gap discovered late can delay a project, while the same gap discovered early can be solved by choosing a different line, waiting for documentation, or adjusting the specification.
Buyers who need certificates for several markets should list each market separately, since a certificate that satisfies one market may not satisfy another. The inquiry page checklist includes the certificate question in that form, so a buyer can copy it into the message without forgetting a market.
What a reply about certificates should confirm
A useful supplier reply about certificates should confirm whether the named certificate exists, what product and market scope it covers, and what document the buyer will receive. If the supplier cannot confirm a named certificate, that answer is itself valuable, because it lets the buyer adjust the specification or the line choice before committing.
This site records no certificate outcome in advance, and no page on this site should be read as implying one. The general sentence is a route to asking, not an answer, and the answer always comes from the supplier reply to a named request.