Clay Tech

"clay-works make things real"

translated from clazytech.com

No certifying body exists for RoHS compliance

I’m sometimes asked, “Have you gotten RoHS certification?”

Every time, I answer, “There’s no such thing as RoHS certification.”

And most of the time, the air turns awkward, a mix of distrust and unease.

I’ve brought a few products to market carrying the CE mark. I’ve put together the technical documentation and signed the declaration of conformity myself. So I believe I understand the scheme. And yet, understanding it as I do, this conversation stalls at exactly the same point every time.

The other person isn’t wrong, either. The word “certification” circulates freely within the industry. Sales people say it, customers say it, even the people doing the actual design sometimes say “RoHS certification.” That the name of something that doesn’t exist rides this smoothly through conversation is, when you think about it, quite a situation.

The substance of the scheme is terse.

The manufacturer judges conformity itself and declares it itself. There’s no filing. No registration. No third-party review. All that’s required is technical documentation, an EU declaration of conformity, and the CE mark affixed to the product. The declaration of conformity itself is a single A4 page. You identify the product, write down the directives and standards it complies with, and sign it. That satisfies the entire legal requirement.

The technical documentation is assembled following the harmonized standard EN IEC 63000. Its content is risk-based, structured so that you gather evidence from one of three sources: a supplier’s non-use declaration, material composition data, or analysis results. The underlying design philosophy is “you only need to analyze the suspicious parts.”

This is, in fact, reasonable. RoHS thresholds apply per homogeneous material, so if you seriously analyzed every single material in one piece of electronic equipment, you’d be looking at hundreds of items. Nobody does that. If you did, you’d never ship the product.

So the cost is far lower than people imagine. The certification cost is $0. The actual labor involved is distributing and collecting supplier questionnaires, then analyzing a handful of risk points and drawing up documents. The risky spots are concentrated in predictable places. Modern electronic components are almost all compliant already, so what actually trips you up clusters around lead in free-machining brass, chromium in chromate treatments, and phthalates in PVC cable sheathing. I’m always wary of generic cables.

Incidentally, that lead in brass hangs off exemption 6(c).

This exemption has been extended for nearly twenty years running. Most recently, it was renewed in November 2025, pushing it out to the end of June 2027. And against that deadline, the next extension application has already been filed. Since the rule states that the exemption remains valid until the committee makes a decision, as long as applications keep getting filed, the deadline effectively never arrives.

(At this point, I’m no longer sure which one is the actual rule.)

So, that covers the scheme itself.

Now for the practical side: customers tell us to produce a test report.

Legally, it’s unnecessary. A declaration of conformity is sufficient. And yet they ask for it anyway. As a matter of business custom, this is, if anything, the mainstream practice.

So do we produce one? Honestly, I weigh it case by case.

Often it’s the third quote in a competitive bid, or a subcontract nested under a tender we’re not even sure we’ll win. In those cases, I push back. Or rather, pushing back is the more common outcome.

If it looks like it matters commercially, I produce it. I send a few key materials to an ISO/IEC 17025-accredited lab and get an analysis report. It runs somewhere between a few hundred and a couple thousand dollars, so for a serious deal it’s well worth the expense.

In other words, I’m not deciding whether to provide the documents based on regulation.

I’m deciding based on how real the deal is.

And presumably the customer isn’t asking because they actually want to verify anything. They’re asking to see whether we’ll produce the documents. If we do, they know we’re serious. If we push back, that tells them roughly how serious the deal was in the first place.

A document with zero legal meaning ends up functioning, for both sides, as a seriousness gauge.

The scheme decided not to install a verifier. It decided that no one would check. What the market slotted into that empty seat wasn’t a verifier. It was litmus paper with a price tag on it.

That awkward air, then, is the right response. Not trusting a scheme that nobody verifies isn’t a feeling, it’s a rational judgment. The scheme only ever said “trust me,” so answering “I won’t” is perfectly consistent.

Still, writing all this out, I notice something.

The technical documentation is still, in fact, talking about lead.

Past the declaration, nobody is talking about lead anymore.

I remember going pale over Chinese radio certification more than ten years ago. They demanded every schematic and all the software, and I thought: doesn’t that just let someone build a copy? I thought that was excessive, and I still think it was excessive.

But at least, in that case, someone was looking.

Nobody is looking at RoHS.

Asked which one feels safer, I find myself a little stuck for an answer.

Q. Does Chinese radio certification take so much time and money that you shouldn’t even bother launching products in China?

This piece was conceived and directed by Yuichiro Kuzuryu, with the writing by AI.


Originally published in Japanese at https://clazytech.com/2026/07/1703/. Translated with LLM assistance and reviewed before publication.