Test Report vs Certificate: What Is the Difference?

← All guides

Somebody asks you for "the certificate". A buyer, a marketplace compliance team, a tender document, a customs broker. What they picture is one official-looking page with a logo at the top and a conclusion at the bottom. What a testing project actually produces is a different set of documents, and the difference decides whether you answer that email in ten minutes or spend two weeks getting the wrong paper reissued.

A test report, a declaration of conformity and a third-party certificate are three different documents, written by three different parties and carrying three different levels of responsibility. Most arguments about "the certificate" are really disagreements about which of the three is being asked for.

The four documents that get called "the certificate"

Document	Who issues it	What it actually says
Test report	The laboratory that ran the tests	This sample was tested against these standards, on these dates, with these results.
Declaration of Conformity	The manufacturer, or the importer placing the product on the market	We take responsibility that this product meets the listed legislation and the standards named.
Third-party certificate	A certification body, approved body or national body	We have assessed the product - and usually the factory behind it - and confirm it conforms, subject to continuing surveillance.
Equipment authorisation	A regulator, or a body acting on its behalf	This equipment is authorised under this identifier, for the procedure it was filed under.

A test report is evidence, not an approval

A test report records what was done to a sample: the standards applied, the test conditions, the measured values, the instrumentation, and the exact configuration of the unit that sat on the bench. It is written by the laboratory that performed the work, and it speaks in the past tense - this sample, tested on these dates, behaved like this.

What it does not do is approve the product or take responsibility for it. It cannot, because the laboratory did not design the product and does not run the factory. A report also only describes what was actually in front of the technician. Change the power supply, the radio module, the firmware version or the antenna, and the report now describes a product you no longer build. Two laboratories testing the same configuration to the same standards can also write reports that read differently, because the sample, the set-up and the measurement uncertainty are theirs, not yours.

So a report can be perfectly good evidence and still not be the document a buyer wants to see.

The declaration is the document that carries the responsibility

For products placed on the EU market, the document that means something legally is the Declaration of Conformity. It is issued and signed by the manufacturer - or by the importer, where the manufacturer sits outside the EU - and it states, in that company's own name, that the product meets the directives listed and the standards used to demonstrate it.

Nobody certifies it. It is not issued by a laboratory and not stamped by an authority. Its weight comes from the signature: the company whose name is on it is the one that answers if the claim turns out to be wrong. The test reports sit behind it in the technical file as the evidence, and the CE marking on the product is the visible outcome of that assessment.

This is the misunderstanding we deal with most often. A customer forwards a request for a "CE certificate" and expects us to email one back. For an ordinary electronic product there is no such single document. What exists is the declaration signed by the manufacturer or importer, the reports that support it, and - in a few product categories - a certificate from an approved body where the rules require third-party involvement.

When there really is a certificate

Third-party certificates do exist, and sometimes a buyer genuinely needs one. They usually take one of these forms:

• A CB test certificate. Under the IECEE CB Scheme, a national certification body issues a CB test report and a CB test certificate against an IEC standard, with the national differences listed. The manufacturer holds it, and it can be used as the basis for national certification in member countries - which is why it saves time and samples when the same product goes into several markets.
• A notified body certificate. Where a directive requires a notified body, that body assesses the product or its design and issues the certificate. Radio equipment with features that trigger the third-party route is the familiar case.
• A safety listing certificate. UL, TUV, ETL and similar marks are backed by a certificate from a certification organisation, and they carry continuing obligations: the factory is inspected at intervals to confirm that what is produced still matches what was tested. Stop the inspections and the right to use the mark stops with them.
• A compulsory national certificate. Where a market runs a compulsory certification scheme, the certificate comes from a designated body and brings its own follow-up regime.

The pattern behind all four: a party that is not the manufacturer has assessed the product, usually the production process as well, and stays involved afterwards. That continuing involvement is what separates a certificate from a report, and it is why a certificate carries more weight with a buyer who has never visited your factory.

There is no "FCC certificate" for most products

US terminology adds its own confusion, because the two equipment authorisation procedures are called SDoC and Certification - and the second one reads like "getting a certificate".

Equipment on the Supplier's Declaration of Conformity route is exactly that: a declaration made by the supplier, supported by test data, with a responsible party named. Nothing is issued to you and no identifier is granted. Equipment that goes through the Certification route is tested and an equipment authorisation is granted, which is what produces the FCC ID printed on the product. The grant is the regulator's authorisation for that equipment, recorded in its database - not a certificate in the European or safety-listing sense. So when a buyer asks for "the FCC certificate", the useful reply is a question: do you mean the FCC ID with its grant, or the SDoC with its supporting report? Which of the two applies depends on whether your device is an intentional radiator.

Four situations where the difference costs time and money

The buyer asks for "the CE certificate" and what they need is the declaration. Many distributor checklists say "certificate", because that is what their own paperwork calls it. Sending the signed declaration, the report that supports it and the label artwork usually closes the request in one email. Sending nothing, and waiting a fortnight to see whether a certificate appears, does not. Ask what they will do with the document - file it, pass it to an authority, or use it to release a listing. That answer tells you which document they are really after.

The report names one factory and production moves to another. A report describes the sample that was submitted, and the manufacturer named on it is part of that description. Moving production to a second plant or to a contract manufacturer with a different quality system changes something the file describes. Whether it needs retesting depends on the scheme: for a CB certificate or a listing mark there is usually a defined route to extend the approval to another factory, and it is worth asking about before the new plant starts shipping.

The marketplace asks for a certificate and a report satisfies the check. Platform compliance reviews normally look for a document that ties the tested product to the listing: a report naming the model, or a declaration, or both. Customers regularly pay for a certificate they did not need because the request used the word "certificate". Read the platform's own document requirement before ordering anything.

The certificate lapsed and nobody noticed. Reports do not come with inspections; listings and compulsory certificates do. An unpaid follow-up inspection, a change of address in the file, or a factory that quietly stopped working to the audited process are all ways a certificate stops being valid while the logo stays on the artwork. If your product carries a certification mark, somebody on your side has to own the renewal calendar.

What answers a request for "a certificate"

What was asked for	What usually answers it
A "CE certificate" for the EU	The signed Declaration of Conformity plus the supporting test report, with the technical file kept on hand.
An "FCC certificate"	The FCC ID and its grant where the product went through Certification, or the SDoC with its test data where it did not. Depends on the device.
A certificate for the buyer's own file	A report naming the model plus the declaration. Ask whether their contract requires a third-party certificate specifically.
A certificate for a compulsory scheme	The certificate from the designated body, plus evidence that the follow-up obligations are still current.
A certificate for a marketplace	Whatever the platform's requirement document names - usually a report that carries the model number.
A certificate for shipping	Product-specific documents such as the battery transport test summary, which is a separate document again.

One habit removes most of the risk. When a request arrives, write down three things before ordering any document: the market, the exact wording of the request, and who the document will be shown to. Those three answers identify the right paper in almost every case, and they cost nothing to collect.

Where we come in

Reports and declarations are produced together on every project, and the question of which document a buyer will accept is normally settled before testing starts rather than after. We agree the standards, run the testing, issue the report, and where a market requires a certificate we bring in the certification body that issues it - so the document set that reaches your customer is the one their checklist is actually asking for. How the report, the declaration and the technical file fit together is set out in our testing and certification scope, and what happens to a report as it ages is covered in how long a test report stays valid.