RoHS Exemption 7(a): Why supplier declarations need a second look in 2026

There is a sentence that appears in supplier declarations thousands of times a day across the electronics industry:

"Lead present. Exempt under RoHS Annex III, 7(a)."

For years, most compliance teams accepted that line and moved on. As of 1 July 2026, accepting it without a second question is a genuine risk — because 7(a) is no longer one exemption. It is seven.

What actually changed

On 21 November 2025 the Official Journal published a set of Commission Delegated Directives restructuring the lead-related entries in Annex III of RoHS 2 (2011/65/EU). Member States had to transpose them by 30 June 2026, and the provisions took effect on 1 July 2026.

The old, broad entry for lead in high melting temperature solders was refined into seven sub-entries, 7(a)-I through 7(a)-VII, each tied to a specific technical application:

• 7(a)-I — internal chip interconnections (edge over 0.3 mm, current at or above 0.1 A, voltage above 10 V)

• 7(a)-II — die-attach where high thermal or electrical conductivity is required

• 7(a)-III — primary solder joints that must survive a subsequent reflow

• 7(a)-IV — secondary joints, ceramic BGAs and plastic packaging above 220 °C

• 7(a)-V — hermetic seals in ceramic-metal housings

• 7(a)-VI — specialty lamps: infrared, HID, oven

• 7(a)-VII — audio transducers operating above 200 °C peak

Two conditions sit across all of them. The solder must contain at least 85% lead by weight, and the application has to genuinely match one of the seven descriptions. The whole entry expires 31 December 2027, and renewal applications had to be filed 18 months ahead — by 30 June 2026.The change matters because "RoHS exemption 7(a)" remains one of the most frequently cited exemptions in electronics supply chains. Companies that previously accepted a generic 7(a) declaration now need to determine which specific sub-entry applies and whether the technical conditions are actually met. 

Why this breaks the old supplier workflow

Think about what a declaration actually has to prove now.

Historically, 7(a) served as a generic fallback for lead-in-solder compliance questions, making it difficult for non-technical reviewers to challenge. Under current standards, invoking 7(a) requires a specific technical justification: verifying a high-lead alloy used strictly within one of seven approved applications and meeting defined threshold limits. 

As a result, reviewers can now catch invalid claims directly from the declaration text by checking whether:

The alloy is wrong. A solder measured at 60% lead by weight cannot sit under 7(a) at any sub-entry. The floor is 85%.

1. The application is wrong. A general-purpose through-hole joint on a consumer device is not a hermetic ceramic-metal seal, and it is not a chip interconnection. Calling it one does not make it one.

2. The sub-entry is missing. A declaration that simply cites "7(a)" without identifying the applicable sub-entry provides insufficient information to independently verify the exemption claim. There is no undifferentiated 7(a) to claim.

3. The clock is wrong. The entry runs out on 31 December 2027. A supplier telling you the part is "exempt indefinitely" is telling you something that is not true.

The enforcement side is already visible

None of this is theoretical. The EU Safety Gate — the rapid alert system for dangerous non-food products — publishes lead-in-solder cases continuously, and the risk type recorded is environment, with RoHS 2 cited as the legal basis.

Recent entries include headphones, a wireless mouse,  and a USB charger, all notified within days of each other. Sweden in particular has been notably active in submitting solder-testing results. When multiple alerts appear in a short period involving the same substance and component type, that is often a sign of an active market-surveillance programme rather than isolated findings. 

Look at the measured values in those cases. They tend to sit in ranges that are nowhere near the 85% floor — which is exactly the point. These are ordinary solder joints in ordinary consumer products, and no exemption reaches them. The measures recorded against them are the ones that hurt: withdrawal from market, import rejected at border, takedown requests to sellers.

A verification routine that actually catches this

You do not need a lab to catch most bad exemption claims. You need the declaration to answer four questions before it gets accepted:

1. Which sub-entry? Require the roman numeral. If the supplier cannot name it, they have not assessed it.

2. What is the lead percentage by weight? Below 85%, 7(a) is unavailable regardless of application. This one check eliminates a large share of incorrect claims immediately.

3. Does the described application match the sub-entry text? Ask for the application in the supplier's own words, then compare. "Standard SMT assembly" does not map to any of the seven.

4. What is the expiry, and what happens after? This exemption expires on 31 December 2027. Require the supplier to provide their transition timeline and technical substitution plan for post-expiry continuity.

Evaluate those four against your existing declaration library, not just new ones. Claims accepted under the old broad entry were assessed against a rule that no longer exists.

Where the manual approach breaks down

The problem is not that the checks are difficult. For example, a mid-size electronics company might hold tens of thousands of supplier declarations across multi-level BOMs, and every one of them was validated under the previous framework. Re-reading them by hand is not a project anyone finishes.

This is what the GoCompliance platform is built for. The OCR and Email Agents parse incoming supplier declarations automatically, extract the claimed exemptions, and check them against current Annex III entries — including sub-entry structure and expiry dates — without anyone opening a PDF. The Non-Compliance Agent flags parts where the claim doesn't hold and proposes pre-screened compliant alternatives from a database of over a billion component records, so the finding arrives with a fix attached rather than as another item on a list.

If your engineering team is already at capacity — and given that engineers can spend up to 30% of their time chasing supplier declarations, most are —  GoCompliance Managed Services runs the re-verification for you. Our regulatory team takes ownership of supplier outreach, collects corrected declarations, validates the chemistry, and delivers audit-ready documentation and Certificates of Conformity. You keep full ownership of the resulting data asset in a structured, transferable format.

The short version

An exemption claim is a technical assertion, not a formality. Since 1 July 2026 the assertion behind 7(a) is far more specific than it used to be, which cuts both ways: harder for a supplier to bluff, easier for you to check. The teams that come out ahead here are the ones treating this as a data-verification problem rather than a paperwork one.

Want your existing exemption claims checked against the current Annex III?  Book a demo | info@gocompliance.com FAQ block (for FAQPage schema)

Is exemption 7(a) still valid in 2026? Yes, but in restructured form. It now exists as seven sub-entries, 7(a)-I to 7(a)-VII, each with defined technical conditions, and expires 31 December 2027.

Does exemption 7(a) cover all lead in solder? No. It applies only to high melting temperature solders containing at least 85% lead by weight, used in one of seven specified applications.

What happens if a supplier claims an exemption incorrectly? The product is non-compliant with RoHS 2 regardless of what the declaration says. Enforcement outcomes recorded in the EU Safety Gate include withdrawal from market and rejection at the EU border.