The short answer
A test report records what a laboratory tested, against which standard, on which sample and with what result. A certificate or declaration is a shorter statement built on top of one or more reports. For a dash cam buyer, the job is to confirm four things: the document names your exact model, the lab and report number can be traced, the standards fit the product type, and the report date and configuration match what is in production. If any of these fail, the document may be genuine and still not cover your goods. Roadtrace does not hold certificates; they come from the producing factory or lab, and we verify them by report number for each program.
Anatomy of a report
| Field | What to look for | Red flag |
|---|---|---|
| Report number and date | A unique number and a date before the declaration | No number, or a date after the shipment |
| Lab name and address | A real lab that can be contacted | Only a logo, no address or accreditation detail |
| Applicant and manufacturer | Names that match the factory | A different company with no explanation |
| Model and variants | Your model name, listed variants | A sibling model with a different board or module |
| Standards tested | The right standards for radio or no-radio type | Radio model with no radio standard listed |
| Test configuration | Photos, cables, power adapter, operating mode | No photos or a configuration unlike your unit |
| Result and conclusion | Clear pass statement with limits and margins | Pages missing or cropped |
Ask for the complete report, not a one-page summary. Many suspicious documents are edited or incomplete screenshots.
Reports, certificates and declarations compared
These terms are used loosely, which causes confusion. A test report is the lab's record. A certificate is issued by a certification body after review; an FCC grant or an E-mark approval are examples. A declaration of conformity is signed by the responsible company and relies on the reports behind it. Each answers a different question, and which one matters depends on the market. The market notes explain the specifics: FCC rules, CE and RED, E-mark and ECE R10 and UN38.3 for batteries.
Matching the report to your model
The most frequent real-world problem is not forgery but substitution. A factory has a certified base model and sells ten variants with different cameras, housings, screens or WiFi modules. Only some changes keep the report valid. Check, in this order:
- Model name on the report, label, manual and your order must be identical or explained in writing.
- Radio module in a WiFi or 4G version must be the one tested.
- Power adapter and cable included in the box must match the tested ones.
- Revision: ask whether the board or firmware changed after the test.
- Rebrand: ask how your brand name and model name are covered.
If the factory cannot answer a configuration question, treat the document as covering only the tested unit and plan a delta test or a supplementary declaration through your adviser.
Reading the result pages
Once the front matter checks out, most of a report is data plots and result tables. You do not need to be an engineer to read them usefully. On emission plots, look for measured levels against the limit line; a trace sitting just under the limit with a note about margin deserves a question, because production units vary and a design with no margin is fragile. On immunity tables, look for performance criteria: a device may be allowed a temporary glitch during a test as long as it recovers, but a criterion of permanent loss of function would be a problem for a recorder. Screenshots of the tested setup are worth a glance as well, because they show the cables and adapters used - and those should match what ships in your box. If any of this is unclear, your lab contact or an independent adviser can review a report in an hour, which is cheap compared with a rejected shipment.
Verifying authenticity
You can verify some documents publicly and others only with the lab. An FCC ID can be looked up in the FCC equipment authorization database. E-mark approvals can be checked with the approval holder or authority. Reports from private labs often carry a report number and a verification method such as a code or contact address on the cover. If a lab offers online verification, use it; if not, an email to the lab quoting the report number is a normal request. Consistency matters as well: fonts, page numbering, dates and the lab's address should agree across the document. If something looks off, ask the factory to explain before sending a deposit.
Building your own document pack
Treat documents as a program asset, not a folder of PDFs. A practical pack has one entry per market and one per model: the declaration or grant, the supporting reports, label photos, manual pages and a one-line note of who holds each original. Two habits make it durable. First, version it: when the factory updates a report or changes a component, add the new document with a date and keep the old one, so you can show history if a question arises. Second, record what you asked and what you received; a simple request log turns "we never got that" disputes into a five-minute check. Buyers who maintain a pack like this move faster through marketplace reviews, retailer onboarding and customs questions than buyers who re-request documents from the factory each time, and the factory relationship improves too, because requests become specific instead of general.
Dates, validity and renewals
Some documents have no expiry but become outdated when the standard is revised or the product changes. Others, such as certain approvals, have conditions for continued validity. Treat any document older than a few years as a prompt to ask whether the standard has changed or whether the model has been modified. For radio products in the EU, the relevant rules have been evolving, so for a WiFi or 4G model ask whether the report reflects the current requirements.
How we use documents in a program
During sampling, we collect the report set, compare model names and label photos and note any gaps. At pre-shipment, the quality check compares the label on production units against the documents; the physical side is described on the quality control page and the document side on the certifications page. Where a gap exists, we state it in writing so you can decide whether to accept it, request a supplement or change model. Start a program with the document status in the brief on the quote form, listing your markets.