Three questions a certificate has to answer
A product certificate is a short document that answers three questions. Which models does it cover? Which market is it for? Which standard was applied? When all three answers are on the page, the document is evidence. When only one of them is, it is a picture of a logo with a signature under it.
Buyers ask for “the certificate” as though there were one, and suppliers send the one they have. Most of the friction in that exchange comes from the two sides counting differently: the buyer is counting answers, the supplier is counting pages.
Model scope: a range is not a scope
The first question is the one that decides whether the document applies to your order at all. Certification is granted to a product, or to a defined family of products, and the document says which. It does not say “all ceramic sanitary ware” and it does not say “our range”. If a supplier’s certificate cannot be matched to the codes in your purchase order, the certificate is about something else.
This is where a curious asymmetry appears in practice. Suppliers describe their range as a family and their certification as a family, and the two families are not always the same set. A certificate that covers the two-piece models in a range says nothing about the wall-hung ones, even though both are made from the same body, in the same plant, on the same line.
The check is mechanical: take the model codes you intend to buy, put them beside the scope statement, and see whether each one is inside. If the answer requires an interpretation, it is not inside.
Market: a certificate speaks for one jurisdiction
The second question is where the product is going. Certification is granted against a national or regional framework, and it is meaningful inside that framework. A European declaration does not make a product certified for Australia, and an Australian certificate does not make it certified for the Gulf. The documents are not translations of one another.
This is not a technicality about paperwork. Each framework tests different things, in different ways, with different acceptance criteria. A product that performs well under one set of tests may or may not perform under another, and the only way to know is to have it assessed. Claiming coverage across markets because the product is the same is the most common overstatement in this category, and it is usually made by people who believe it.
Standard: which document, and which edition
The third question is the standard. A certificate names one, and the name matters twice: because standards differ in content, and because a standard is revised. A certificate referring to an edition that has been superseded is still a real document. It is simply about a criterion that may not be the current one.
Buyers rarely ask which edition. It is the field that most often reveals a gap, because a supplier can hold a valid certificate under an older edition and be entirely truthful while being out of date. Whether that matters depends on your market’s rules and on your project’s specification, and it is not something a supplier should decide for you.
Reading the first page: what has to be there
A useful certificate front page carries a small set of facts. You do not need the annexes to make the first judgement; you need to find these on one page and be able to read them without interpretation.
- The legal entity that holds the certificate, in the name it trades under rather than a brand name invented for a catalogue.
- The product identification, by model or by a defined family, in terms that can be matched to an order.
- The standard applied, including the edition.
- The scope statement, which is the sentence that says what is and is not covered.
- The issuing body and the issue information that lets you tell one revision from another.
Five items, and a reviewer can work with them. What a reviewer cannot work with is a photograph of a framed certificate taken at an angle, or a scan of a cover page with no scope statement, or a statement in a catalogue that says the range is certified. Those are three different ways of not answering the question.
Why “we have CE” is not an answer
“We have CE” is a sentence about the supplier, not about the product. It does not name a model, it does not name a market beyond the obvious, and it does not name a standard. It is a claim that somewhere in the company there is a document with a mark on it, and it invites the buyer to assume the rest.
The sentence is not usually dishonest. It is what happens when a sales team is asked a technical question in a commercial conversation and answers with the shortest true thing it knows. The problem is that the shortest true thing is not the thing the project needs, and the gap gets discovered later, by somebody who has no authority to fix it.
The remedy is a question rather than an accusation: which models, which market, which standard. A supplier who can answer all three in one reply has a file worth having. A supplier who answers one and repeats it has told you what the file contains.
When the scope does not reach your model
The most useful thing a supplier can do in that situation is say no quickly. A model that is outside a certificate’s scope is outside it, and no amount of correspondence changes the scope. The options are to specify a model that is inside, to ask whether an extension is possible and on what timetable, or to find another route for that market.
What damages a project is the fourth option, which is to send a document that covers a neighbouring model and let the buyer assume the difference does not matter. It usually does matter, and it matters at the worst moment: during a submission review, after the order has been placed and the cartons have been printed.
What we publish, and what we send
Six items are public, and they are public because they are the ones a buyer asks for first: CE marking on our wall-hung models, WaterMark certification for Australia, a WELS rating of 3.5 stars, an AS 1976 test report recording water absorption of 0.14%, ISO 9001 for the plant at Chaozhou, and two SGS VOC reports.
Everything else we hold is provided as certificate documents on request. That phrasing is deliberate. There is no download link and no PDF behind a page, so the document arrives with its scope attached and a person able to answer the next question. It also means we can tell you when a document does not exist for a model, which is a more useful answer than a folder that appears to cover everything.
We will not invent a certificate number, an issuing body’s detail or a validity period to make a reply look complete. If you need a specific field for a submission, ask for it and we will tell you what the document says, or that we do not have the document.
Frequently asked questions
What three things should a certificate tell me?
Which models it covers, which market it applies to, and which standard was used. A document that answers one of those is not evidence for the other two. Ask for the front page that carries all three, then check the model codes against the scope statement yourself.
Does a certificate for one model cover the rest of the range?
No. Scope is defined per model or per family, and a family is not the range. Models made from the same body on the same line can sit outside a certificate’s scope. The check is to place your model codes beside the scope statement and confirm each one appears inside it.
Can I use an EU certificate in Australia?
No. Certification is granted within a framework, and the Australian route for a WC pan runs through WaterMark with assessment to AS 1172.1. A European document speaks for the European framework. Using one in place of the other is a substitution that a reviewer will identify immediately.
Why does the edition of the standard matter?
Because standards are revised, and a certificate referring to an earlier edition describes an earlier criterion. It remains a genuine document. Whether it satisfies your market or your specification is a question for the rules that apply there, and it is worth asking rather than assuming either way.
Do you send certificates as PDFs?
Six items are published on the site. Anything else we hold is provided as certificate documents on request, sent with the scope attached so the coverage is visible in the same message. There is no download page for those, and we will say when a document does not exist for a model.
What if the certificate does not cover my model?
Then the honest answer is that the model is not covered, and the options are to specify a covered model, to ask about extending the certification, or to use a different route for that market. What should not happen is a neighbouring model’s document being sent as a substitute.
Related on this site
Documents and certificates
- Certificates and the markets each one covers
- Published reports, catalogues and drawings
- The plant, the kiln and the QC record
Related reading
- ISO 9001 and product certification
- How to read a sanitary ware spec sheet
- EN 997: What the Standard Actually Tests