A supplier sends you a PDF with an official-looking header and a certificate number. Most buyers file it. The ones who’ve been caught before read it — because a certificate is a much narrower claim than it appears, and almost every documentation failure comes from assuming it covers more than it does.
Every certification document is bounded on four dimensions, and verification means checking each one rather than accepting the document as a whole. Product: does it cover your exact model, or a sibling on the same platform? Holder: whose name is on it, and does that entity’s approval do anything for you in the market you’re entering? Time: is it still valid, and what happens when it expires? Scope: which document is this — a test report, a certificate of conformity, or a national homologation — because in several markets those are distinct things and having one is not having another. Most failures cluster in two places: paperwork for a “similar model,” which protects nobody because obligations attach to the exact product placed on the market; and certificates held in a name that can’t be used by the entity actually importing, which in markets like Brazil means no market access at all. The checklist below runs 24 checks across the four dimensions, with critical items marked as stops rather than deductions.
This is the document you open when a certificate arrives, not an article about certificates. Work the four blocks in order — product identity is cheapest to check and eliminates the most, so it goes first.
Checks marked STOP are structural: a failure means the document doesn’t do what you need, and no amount of other checks passing changes that. Everything else is a finding to record and weigh.
§01The four bounds
Think of a certificate not as a statement that “this product is approved,” but as a set of four simultaneous restrictions. It says: this specific configuration, approved for this specific entity, valid for this specific period, under this specific scheme. Widen any one of those in your head and you have a document that no longer describes your situation.
FIG.01 — The four bounds. Verification isn’t asking “is this certificate real?” — forgery is rare. It’s asking “is this certificate’s actual scope the same as the scope I’m assuming?” That question fails far more often, and quietly.
§02The four dimensions, and how each fails
Approvals attach to configurations, not to product families or platforms. A different screen size, a different antenna position, a different adapter, a different battery cell — any of these can put the unit outside what was assessed. The most common documentation failure in the entire category is paperwork for a lookalike model, usually offered in good faith as “the same product, small changes.”
HOW IT FAILS: the model number on the certificate is one suffix away from the model on your quotation, and nobody flags it because it looks like a typo rather than a different product.This is the dimension that has grown most consequential as sourcing has spread beyond the US and EU. In several markets an approval is issued to a specific entity and is not transferable: Brazil issues certification to a specific importer, so a certificate held for another importer is worth nothing to you. Elsewhere the holder question determines who is legally answerable, or which entity may import.
HOW IT FAILS: “we already have this certified for Brazil” is true and useless, because it’s certified for someone else’s import.Validity ranges from permanent to annual across markets, and the consequences of lapse differ. Some approvals last the life of the product unless the design changes. Others expire and require reassessment rather than a renewal form. Some carry a grace period after which full re-certification — including any local testing — becomes necessary.
HOW IT FAILS: a certificate is valid on the day it’s checked and expires mid-contract, with nobody assigned to notice.The least-understood dimension. In several markets, two distinct documents exist and are routinely confused: a certification body issues a certificate of conformity, and the national authority issues the homologation or registration — and having the first is not having the second. Separately, a test report and a certificate are different artefacts serving different purposes, and a certificate without its underlying reports can’t support a submission anywhere else.
HOW IT FAILS: a buyer holds a conformity certificate, believes they’re approved, and discovers at customs that the national registration was never completed.§03The 24-check verification list
- The model number on the certificate matches the model number on your quotation, exactly, character for character.STOP
- The model number on the certificate matches the physical sample and its rating label.STOP
- The model number matches across the certificate and every underlying test report, not just the cover page.STOP
- Any variant or suffix conventions are explained in writing — what does the trailing letter denote, and is your variant included?
- The product description on the certificate matches what you’re actually buying: screen size, radio configuration, adapter, battery.
- Photographs or drawings in the technical file, if present, show the product you recognise.
- If the certificate covers a family or series, the specific variants listed include yours by name.
- The company name on the certificate matches the business licence of the company you’re buying from.STOP
- You understand which entity is the legal holder — manufacturer, importer, or local representative.STOP
- For markets where certification is importer-bound, the holder is the entity that will actually be importing your goods.STOP
- If the holder is your supplier rather than you, you understand what happens to the approval if you change suppliers.
- If a local representative holds it, their appointment is documented and current.
- Where the market maintains a public register, the entry exists and the details match the certificate.
- The certificate is currently valid, with the expiry date read rather than assumed.STOP
- You know whether renewal is a form, a reassessment, or a full re-certification.
- You know who is responsible for renewal, by name, and they know it too.
- Any surveillance or periodic re-testing obligation attached to the scheme is understood and scheduled.
- Test report dates are consistent with the current hardware and firmware version, with no reports predating a known design change.
- A grace period, if the scheme has one, is documented — along with what happens if it lapses.
- You have the underlying multi-page test reports, not only the certificate.STOP
- You know which document you’re holding — test report, certificate of conformity, or national homologation — and whether the others exist.STOP
- The standards and directives named on the certificate match those actually tested in the reports.
- The named laboratory or certification body exists, is findable independently, and is recognised for that scheme in that market.
- Every regime the product engages is covered — radio, electrical safety, substances — since satisfying one says nothing about another.
§04Two documents, one market: where scope confusion lives
Check 21 deserves expansion, because it catches experienced buyers. Several markets issue two documents at different stages, and the first one arriving can feel like completion:
| Market | The first document | The one that actually grants access |
|---|---|---|
| BRAZIL | Certificate of conformity issued by a designated certification body | ANATEL homologation, with its identifier — a distinct document |
| MEXICO | Certificate of conformity from a certification body | The homologation certificate from the telecom authority |
| CANADA | Certification issued by a recognised body, with a number | Plus the entry in the public Radio Equipment List |
| SAUDI ARABIA | Product certificate of conformity | Plus a shipment certificate for every consignment |
| UAE | Type approval certificate | Plus a customs release permit matching the import purpose |
TABLE.01 — Where one document isn’t the whole picture. The pattern is consistent enough to be a habit: whenever a certificate arrives, ask what the next document is. In markets structured this way, holding the first while assuming it’s the last is how shipments end up stopped at a border with valid paperwork attached.
§05Red flags
- “It’s the same product, just a different model number.” Then it’s a different product as far as the approval is concerned.
- Only the certificate offered, reports described as unnecessary. Reports are the reusable asset and the evidence; a cover page is decoration.
- Company name on the certificate differs from the business licence, explained as “our factory’s certificate.” That’s an admission about who you’re actually dealing with.
- “We already have this certified for that market” without naming the holder. In importer-bound markets the answer determines whether it helps you at all.
- An unfindable laboratory or certification body, or one not recognised for that scheme in that market.
- Standards declared on the certificate that no report covers. Declared but never tested.
- Reports dated well before the current hardware revision, with no delta assessment.
- No answer on what the next document is in a market that issues two.
- Renewal responsibility unassigned. Certificates lapse in the gap between “someone’s handling it” and nobody being.
§06What this checklist doesn’t do
Two honest limits. First, it verifies documents, not products. A perfectly coherent certificate can describe a product that performs poorly — night vision that disappoints, range that overstates, batteries that fade. Document verification and sample testing are separate exercises and neither substitutes for the other.
Second, it isn’t a compliance opinion. Confirming that a document is coherent, current, and correctly scoped tells you the paperwork holds together. It doesn’t tell you that your product meets every requirement of your target market, or that you’ve identified every regime that applies. That determination belongs to qualified compliance professionals — this checklist just makes sure you’re not building on documents that were never going to support the weight.
§07Frequently asked questions
How do I verify a certification document is genuine?
Forgery is rarely the problem — mis-scoping is. Check four dimensions rather than authenticity alone: product (does the model number match your quotation, your sample, and every underlying test report exactly), holder (whose name is on it and is that entity usable for your import), time (is it currently valid and what does renewal involve), and scope (is this a test report, a certificate of conformity, or a national homologation, and do the others exist). Also confirm the named laboratory or certification body exists independently and is recognised for that scheme in that market.
What is the “similar model” documentation trap?
It’s the most common documentation failure in the category: paperwork belonging to a lookalike product — same housing, different board, or a model number one suffix away — offered as though it covers your unit. It usually isn’t deception; suppliers genuinely think of it as the same product with small changes. But approvals attach to specific configurations, and obligations attach to the exact product placed on the market, so a cousin model’s reports protect nobody. If the model number doesn’t line up across the certificate, the reports, your quotation and the physical sample, stop and resolve it before money moves.
Why does it matter whose name is on a certificate?
Because in a growing number of markets the approval is issued to a specific entity rather than to the product, and it isn’t transferable. Brazil issues certification to a specific importer, so an identical device certified for another importer requires a new certification for you. Korea limits imports to the certificate holder where an importer holds it. Saudi Arabia issues the product certificate under the importer of record’s name. Elsewhere the holder determines who is legally answerable. “This product is certified” is an incomplete statement — certified by whom, for whom, matters as much.
What’s the difference between a test report and a certificate?
A test report documents measurements — what the laboratory observed, against which standards, on which date. A certificate is a conclusion drawn from those reports by a certification body or declared by a manufacturer. The distinction matters practically because the report is the reusable asset: it’s what a submission in another market can build on, and what allows anyone to check whether the standards declared were actually tested. A certificate without its underlying reports can’t support work elsewhere and can’t be verified in any meaningful way. Always ask for the multi-page reports.
Can one certificate cover a whole product family?
Sometimes, but never by assumption. Some schemes allow family or series certification where variants are explicitly listed, and some require representative models within a family to be tested. What doesn’t work is inferring family coverage from a certificate that names one model — approvals attach to configurations, and a different screen size, antenna position, adapter or battery cell can put a unit outside what was assessed. If the certificate covers a family, your specific variant should appear by name; if it doesn’t appear, treat it as uncovered until confirmed.
What documents should I ask a supplier for?
The certificate and the full multi-page test reports behind it, for the exact model number you’re buying. Beyond that: confirmation of who holds the certificate and whether it’s usable for your import; the technical file or written confirmation that it exists and will be made available; the expiry date and what renewal involves; details of the issuing laboratory or certification body; and confirmation of which regimes the documents cover, since radio, electrical safety and substance requirements are usually separate. A supplier who produces this without friction has done it before.
Does True Bond provide documentation that passes these checks?
That’s the intended use — run the list on us. Documentation is issued against the exact model rather than a platform sibling, full test reports are provided rather than certificate cover pages alone, the holder position is stated openly for each market including where a local entity must hold it, expiry and renewal responsibilities are set out during project scoping, and written change control means the documents keep describing the product you actually receive across production batches. The checklist is published because a supplier confident in its paperwork benefits from buyers who read it.
Run the 24 checks on our documents
Exact model numbers, full test reports, an honest answer on who holds what in each market, and change control so the paperwork keeps matching the product. We publish the checklist because we’d rather be verified than believed.
Request the document pack → info@truebondtech.com · WhatsApp +86 189 2846 4489 · View productsCertification toolkit & markets