PFAS Rules Are Fragmenting — Build One Process, Not Fifty

If you sell into both the EU and the US, PFAS compliance can start to feel like tracking several different regulations that all happen to be about the same chemicals. In a narrow legal sense, that's true: the EU's REACH-based restriction proposal, EPA's TSCA section 8(a)(7) reporting rule, and a growing patchwork of US state laws (packaging, textiles, food contact materials) are separate legal instruments, each with its own scope, thresholds, and deadlines.

Treated as separate compliance projects, they multiply your workload. Treated as one substance-data problem viewed through several regulatory lenses, they don't.

The common denominator is the same question

Every PFAS regime, regardless of jurisdiction, eventually asks a version of the same thing: which of your parts, materials, or formulations contain a PFAS substance, at what concentration, and where did that data come from?

If you already have that answer at the material level — not a supplier's one-line assurance, but an actual substance inventory — every downstream reporting obligation becomes a filtering exercise against a rule set, not a fresh data-collection project.

Where teams lose time

• Re-asking suppliers per regulation. Sending a REACH PFAS request, then a TSCA request, then a state-law request to the same supplier for the same part is redundant and erodes supplier goodwill.
• Treating "PFAS-free" claims as sufficient. PFAS is a class of thousands of substances; a usable declaration needs to say which ones were assessed and against what test method, not just assert absence.
• Missing historical reporting scope. TSCA 8(a)(7), notably, reaches back to cover PFAS manufactured or imported in past years, not just current production — a detail that catches companies who assume reporting only applies going forward.

A structure that holds up across jurisdictions

Build a single PFAS substance inventory, mapped to material and supplier, refreshed on the same cycle as your other substance data. Layer jurisdiction-specific rule sets on top of that inventory as filters, not as separate data-collection efforts. When a new state law or EU restriction lands, the question becomes "does our existing data already answer this," rather than "who do we need to email again."