Guide
Certificates and Documents to Request from a Lighting Supplier
Documents are requested per configuration, not per company. This checklist sets out what to ask for, how to match it to your order, and what to do when a document and a product page disagree.
The standing position
Certificates available upon request. The documents themselves are the evidence: they are produced against a named configuration in a quotation, and they are what your market, your insurer or your client's consultant will actually read — no second-hand mention of a certificate name or number settles anything in their place.
What to request
- Certificate documents for the exact model and variant in your quotation — wattage, input voltage and control variant included, since coverage can differ between variants.
- The model's datasheet, to check the certificate's model naming against the same document your specifications came from.
- Test or supporting reports your market requires for import or project approval, named by your market's rules rather than by a generic list.
- A written confirmation of any value your order depends on where a source page shows two values — the protection grade of the LX-SC-002 is the standing example.
Matching documents to the order
When the documents arrive, check three things: the model name matches the quotation line for line; the configuration covered matches the variant being shipped; and the document is complete and legible, including dates and standard references. A certificate that names a sibling model or a different variant is not coverage for yours — raise it and have the correct document supplied before payment. Company background for the request sits on the about page, and the request itself can be sent from the certificates page.
Confirm before ordering
Ask for the documents with the quotation, not after it: a document gap found at shipping stage costs the whole schedule.
Worked example: the sibling-model certificate
A buyer orders a mid-range submersible and receives, with the quotation, a certificate document naming the model's larger sibling — same family name, different wattage and a different LED count. It happens innocently: a documentation pack assembled by family rather than by variant. It also matters completely, because the document's coverage follows the model it names, and an inspector, an insurer or a client's consultant will read it exactly that way. The check that catches it takes one minute: lay the certificate's model name beside the quotation line and the datasheet's model name, and require all three to agree. Where they do not, the correct document is requested before payment — a routine exchange when caught at quotation stage, and a project-stopping problem when caught at the destination port.
Keeping the document set with the order
File the received documents against the order they belong to: quotation, datasheets, certificates, written confirmations. Years later, when a variant must be matched or a compliance question lands from a new facilities manager, the set answers in minutes. The discipline costs a folder; its absence costs a re-investigation of decisions nobody remembers making.
Asking well: the request itself
A document request gets a faster, cleaner answer when it is written the way the documents are filed: by model and variant. Name the model from the product page, the variant from the quotation, and the market the goods are bound for; attach the quotation reference. A request that asks for "all certificates" invites a bundle assembled by guesswork; a request that names its configuration invites the exact file. If the reply bundle and the request disagree, the written request is the evidence of what was asked — one more reason to keep requests specific and in writing from the start.