Two brands can read the same requirement and plan two different programmes. One treats the requirement as a document to obtain; the other treats it as an obligation that follows the product and the market. The first approach usually survives a first shipment and fails at the first audit, and the six beliefs below are the ones that cause that pattern.
Charger certification requirements: six widely held beliefs, examined
Each belief contains a part that is true, which is why it spreads. The cost comes from the part that is not.
The pattern across all six is the same: certification is treated as an event rather than as a description of a product revision and the market it is placed in. Once that distinction is clear, the requirements become a list of decisions rather than a sequence of forms.
Belief 1: CE marking is a certificate you receive
CE marking is a declaration supported by a technical file, not an award issued by an authority.
The manufacturer, or the importer where the manufacturer is outside the market, declares conformity and holds the evidence behind it. What can be obtained is a test report from a laboratory and, for some product families, a notified body’s involvement. The practical consequence is that the brand is expected to be able to produce the file, which is a different obligation from storing a certificate.
Belief 2: the factory’s reports cover our brand automatically
Reports describe a configuration and name a responsible party.
Where the product is identical to the tested configuration and the arrangement is documented, existing evidence supports the branded build. Where the enclosure, the components or the accessory differ, the difference is assessed. The expensive version of this belief is discovering the gap at the point where a marketplace or a distributor asks for the file in the brand’s own name.
Belief 3: one test covers every market
Requirements are set by destination, and they overlap without being identical.
Safety, electromagnetic behaviour, chemical restrictions and energy requirements are each covered by their own instruments, and the market list decides which apply. A product designed and tested for one region may need additional assessment for another, and the plug and adapter arrangement changes with the destination as well. Writing the market list first turns this into a scope decision instead of a surprise.
Belief 4: certification is a one-off task
The file describes a revision, so it stops being current when the revision changes.
Component substitutions, a new enclosure, a different coil or a change to the marking each move the product away from what was assessed, and the assessment obligation returns with the change. Keeping the file current is a maintenance activity attached to the responsible party, and it is cheaper than reconstructing it after a review has begun.
Belief 5: a certificate without a scope is enough for a marketplace
Reviewers read the scope because the scope is the part that matters.
A document that names a product family without stating the configuration, the standard version or the holder tells a reviewer very little. Ask for the scope statement, the tested configuration and the revision identifier, and check that those match the product being shipped. A file that passes a template check and fails a substantive one has not solved the problem.
Belief 6: the cheapest test house is the cheapest route
Total cost depends on how many times the work has to be done.
A quotation that omits pre-compliance measurement, that books a submission before the configuration is frozen, or that leaves the documentation to the brand can be cheaper on the invoice and more expensive overall. The comparison that matters is against a defined scope: the tests, the samples, the documentation deliverable and the assumption about how many rounds the work will take.
| Belief | What is actually true | What it costs when believed |
|---|---|---|
| CE is a certificate | It is a declaration with a technical file | A file that cannot be produced on request |
| Factory reports cover the brand | Reports describe a configuration and a holder | A rejected listing or a late re-test |
| One test covers all markets | Requirements are set by destination | A second programme after the launch date |
| Certification is one-off | A file describes a revision | An assessment obligation discovered in a review |
| Any certificate is enough | The scope and holder are what matter | A documentation failure after shipment |
| Cheapest test house wins | Total cost includes repeat work | More rounds, at a worse moment |
What to ask for in writing instead
Six questions replace the six beliefs.
Which configuration was tested and under which revision identifier; who is named as the responsible party; which markets and standards the file covers; which parts of the construction are listed as approved components; which documents transfer to the brand; and what triggers a re-assessment. Each question has a documentary answer, and asking them before an order is placed costs nothing but an email.
FAQ
Who is responsible for compliance when a brand sells a factory platform product?
Responsibility follows the role the company takes in the market. Where the brand puts its name on the product and places it on the market, it is the practical holder of the obligation, even though the evidence may originate with the manufacturer. Responsibility follows the role the company takes, so a brand putting its name on the product is the practical holder of the obligation.
Do we need a notified body for a charger?
It depends on the product family and the market. Many charger programmes are supported by testing and self-declaration, while certain product categories require a notified body’s involvement. The market list and the product family decide, not the supplier. It depends on the product family and the market, and the market list and the product family decide rather than the supplier’s preference.
How often does the technical file have to be updated?
It has to be updated when the product changes, and it has to remain available for as long as the product is placed on the market. There is no calendar interval that substitutes for updating it when the revision moves. It has to be updated when the product changes and remain available while the product is on the market, because no calendar interval substitutes for that.
Can a supplier’s certificate be transferred to our company?
Certificates and listings are issued to a holder, so they are not transferred by endorsement. What can be arranged is a new listing or report in the brand’s name, or an arrangement where the brand is named as the responsible party on the documented configuration. Certificates are issued to a holder rather than transferred by endorsement, so a new listing in the brand’s name is arranged instead.
Next step
Send the product, the markets and the channel to Wecent Group through the contact page. The reply answers the six questions in writing for that configuration, so the scope can be compared with any other supplier’s before an order is placed. Related reading: charger quality control, charger manufacturing services and GaN charger applications. External references: EU CE marking rules, EU RoHS Directive, EU REACH Regulation, EU energy-efficient products, UK UKCA marking guidance and US FCC Part 15 rules.
{“@context”:”https://schema.org”,”@type”:”FAQPage”,”mainEntity”:[{“@type”:”Question”,”name”:”Who is responsible for compliance when a brand sells a factory platform product?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”Responsibility follows the role the company takes in the market. Where the brand puts its name on the product and places it on the market, it is the practical holder of the obligation, even though the evidence may originate with the manufacturer.”}},{“@type”:”Question”,”name”:”Do we need a notified body for a charger?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”It depends on the product family and the market. Many charger programmes are supported by testing and self-declaration, while certain product categories require a notified body’s involvement. The market list and the product family decide, not the supplier.”}},{“@type”:”Question”,”name”:”How often does the technical file have to be updated?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”It has to be updated when the product changes, and it has to remain available for as long as the product is placed on the market. There is no calendar interval that substitutes for updating it when the revision moves.”}},{“@type”:”Question”,”name”:”Can a supplier’s certificate be transferred to our company?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”Certificates and listings are issued to a holder, so they are not transferred by endorsement. What can be arranged is a new listing or report in the brand’s name, or an arrangement where the brand is named as the responsible party on the documented configuration.”}}]}