Three checks that decide whether a factory report can carry your brand into the EU, the US or a marketplace listing - and what to do when it cannot.
A factory sends a PDF, usually titled something like "CE Certificate" or "Test Report", and the question is whether that document can carry your own brand into the EU, the US or an Amazon listing. The answer depends on three things, and two of them have nothing to do with the measurements inside it.
A report is evidence about a specific unit. It stops being your evidence the moment the unit you ship differs from the unit that was measured, or the moment nobody can show that the two are the same thing. Checking that takes about twenty minutes and saves a lot of money later, so it is worth doing before the packaging is printed rather than after.
Open the report and read the first page properly. It names an applicant, a model, a rating, a manufacturer and a list of standards. Further in, it records the construction that was actually tested: the adapter model, the cable, the antenna, the firmware version, which radio modes were exercised, and the configuration in which the worst case was found.
None of that changes because you print your logo on the box. A brand is not a physical characteristic. If your product uses the same board, the same enclosure, the same adapter and the same firmware behaviour as the one measured, the data describes your product too.
What the brand does change is who answers for the product. In the EU, a company that places equipment on the market under its own name or trademark is treated as the manufacturer, and takes on the manufacturer's obligations: technical documentation, the declaration of conformity, corrective action, and keeping records. That is a separate question from whether the test data is valid, and it is the one sellers usually miss.
| Check | What you are verifying | Where it usually fails |
|---|---|---|
| Coverage | The report covers the exact configuration you ship - model, adapter, cable, antenna, firmware behaviour and every radio mode | The model number matches, but the shipped version uses a different power adapter or an added radio mode |
| Completeness | You hold the full report, not a summary: measurements, plots, test setup photos, product photos, standards with clause-level results, and the laboratory's accreditation details | Only the one-page certificate was forwarded, and the factory treats the report as internal |
| Chain of responsibility | Written permission to reference the report, and a declaration of conformity in your name that you can back with a technical file | The factory's DoC names the factory, the label names you, and nothing explains the relationship |
All three have to hold. A complete report with no permission leaves you unable to answer a buyer who asks the factory directly. Permission with an incomplete report leaves you unable to answer anyone at all.
This is where most private-label plans quietly break. The model number on the report matches, so everyone assumes the product matches.
| What changed | Does the supplier report still apply? |
|---|---|
| Trade name or model designation only, unit otherwise identical | Yes. Test data still describes the product; the paperwork around it has to be rebuilt |
| Different AC adapter, different PD board or a different output rating | No. Emissions and safety results were produced with the tested combination |
| Extra radio mode or higher output power enabled in firmware | No. The tested configuration did not include it |
| Different cell, different pack capacity or a different BMS | No for battery safety, and the transport test summary is affected as well |
| New PCB revision, same layout and same bill of materials | Usually yes, provided you can document it with a change note and photographs |
| Same design built at a different factory | In principle yes, but you need evidence of identical construction, and buyers increasingly ask for it |
The first row trips people up in the opposite direction. A change limited to the trade name or model number is not treated as a change of identification under the FCC rules (47 CFR 2.933(a)), and in the EU a private label of an unchanged product is the normal case rather than an exception. The data still applies; what has to be rebuilt is the file, not the test.
If the product carries your brand, the declaration carries your company name and address, and the technical file has to be one you could produce tomorrow if asked. For EMC that file includes the product description, drawings and schematics, the bill of materials with critical components, the test reports, the instructions, and the risk assessment, and it has to be kept for ten years after the equipment is placed on the market.
A factory DoC is an input, not a substitute. We see the same pattern repeatedly: the seller holds a DoC issued by the factory, the device label shows the seller's brand, and the two documents name different companies with no explanation of the relationship. That gap is the first thing a buyer's compliance team asks about, and it is not a comfortable conversation to have while a shipment is waiting.
The clean arrangement costs nothing. Ask the supplier for a short written statement that your company is authorised to reference the report for the listed models, together with the report in full. Keep it with the technical file. If the supplier refuses to put that in writing, treat it as information about the supplier.
An FCC ID is granted to a company, not to a product in the abstract. The grantee holds the authorisation, and the label on the device has to show that grantee's ID. There are two legitimate arrangements.
The first is to keep the factory's FCC ID. Selling under your own brand with someone else's FCC ID on the label is normal and permitted, as long as the equipment is unchanged and the label otherwise meets the Part 15 requirements. Your brand lives on the packaging and in the listing; the FCC ID identifies the authorised equipment.
The second is to have the ID in your own name. That is a change in identification under 47 CFR 2.933: a new application, but no resubmission of the equipment and no repeat of the measurements if the design, circuitry and construction are unchanged. Instead the applicant files a statement giving the original identification, the date of the original grant, how the modified identification differs, whether the original results remain representative, and photographs of the exterior and the label. If the change also touches design or circuitry beyond what a permissive change allows, 2.933(c) sends you back to a full application. In practice the filing goes through a TCB and needs the original grantee to cooperate, which is why the supplier relationship matters as much as the technical file.
Some documents cannot be rescued, and it is cheaper to hear that early.
In every one of those cases the same thing happens later: the buyer's QA asks for the technical file, the marketplace requests a report that matches the listing, or the shipment stalls. You pay for testing anyway, at the worst possible moment, with the product already manufactured. That is the real cost of reusing a document that does not fit - not the test fee, but the delay.
| Route | What it involves | When it fits |
|---|---|---|
| Reference the existing report | Supplier's written authorisation, the full report, your own declaration of conformity, and a technical file assembled from their data | Product, adapter, firmware and radio modes are identical; only the brand changes |
| Delta testing under your name | A new report covering only the affected items - for example the new adapter, the added mode, or the new enclosure - using the original data as the baseline | The product differs in defined, limited ways you can list precisely |
| Full test | A complete programme against the applicable standards, on production-representative samples | No usable original data, several changes at once, or a buyer who will not accept third-party evidence |
One thing no laboratory can do is reissue another laboratory's report under your company name. Permission to reference a report and a report issued to you are different documents, and a lab that offers to "change the name on the report" is telling you something about how it works. What a lab can do is test the parts that differ, which is normally a fraction of a full programme.
Most of this arrives within a day from a factory that owns its own test file. A supplier that cannot produce item four or item six is usually telling you that the report belongs to somebody else in the chain.
You can normally sell under your own brand using a supplier's test report, provided three conditions hold: the report covers the exact configuration you ship, you hold it in full with the underlying measurements rather than a certificate summary, and you have written authorisation to reference it - because the declaration of conformity will be in your name and the technical file has to be yours. If only the trade name or model number changes, the data still applies and no retesting is needed: under 47 CFR 2.933(a) that is not even a change of identification for FCC purposes. If the adapter, the radio modes, the battery or the construction changed, the old data no longer describes your product, and the choice is between a narrow delta test and a full programme. What never works is a one-page certificate, an undocumented design change, or a report for a factory that did not build your units.
Where a laboratory is genuinely useful in this situation is the middle route. Reading a supplier report against the product actually being shipped, listing which clauses are still covered and which are not, and issuing a report in your company's name for the parts that changed is ordinary work for us - it sits inside our testing and certification programme, alongside the full programmes we run for products with no usable history. When the review ends with "you do not need to test again", that is a good result, not a lost sale. The expensive outcome is discovering the gap after the cartons are printed.
Send the supplier report and a description of what you actually ship - model list, adapter, battery, firmware version and every radio mode. We will tell you which of the three routes applies, and if it is a delta test, which clauses it has to cover.
Usually not on its own. A laboratory certificate is an attestation, not the technical documentation. What you need is the full test report covering your exact configuration, written authorisation to reference it, and a declaration of conformity issued in your company's name, backed by a technical file you can produce on request.
No. A report belongs to the applicant it was issued to, and no laboratory can simply rename someone else's report. What is possible is a new report for the parts that differ, using the original data as a baseline, or a full test if the differences are extensive.
No, not for the test data itself. In the EU a private label of an unchanged product is normal, and for FCC purposes 47 CFR 2.933(a) does not treat a change of trade name or model designation as a change of identification. What changes is the paperwork: the declaration of conformity, the label and the technical file.
Only for the module in the configurations it was tested in. The host enclosure, power supply, wiring and antenna arrangement affect emissions and safety, so the finished product needs its own assessment. A module grant does not transfer to the appliance built around it.
Then you cannot rely on it. Without the measurements and annexes there is nothing to audit, and without written authorisation you cannot show a buyer or an authority why the report applies to your product. Budget for a delta or full test instead of arguing about it.
Yes, as long as the equipment is unchanged and the label shows the grantee's FCC ID together with the other required statements. If you want the ID registered to your own company, that is a change in identification under 47 CFR 2.933, which does not require retesting when the design and construction are identical.