PFAS Restrictions and Your SDS Portfolio: How to Prepare Before the 2027 EU Deadline

The EU PFAS restriction proposal uses a broad structural definition: any substance containing at least one fully fluorinated methyl (CF3) or methylene (CF2) carbon atom. This encompasses more than 10,000 individual substances, ranging from legacy long-chain PFAS like PFOA and PFOS (many of which are already restricted) to shorter-chain alternatives that industry adopted as replacements, fluoropolymers used in coatings and textiles, and side-chain fluorinated polymers used in water-repellent treatments. The breadth of the definition is what makes portfolio screening essential — many companies discover PFAS exposure in raw materials, processing aids, surface treatments, and additives that they did not initially consider. Unlike previous substance-by-substance restrictions, this proposal targets the entire PFAS class, meaning companies cannot simply substitute one PFAS for another. The screening exercise should cover not only finished product formulations but also the full supply chain of incoming raw materials.

ECHA’s scientific evaluation is assessing sector-specific derogations and transition periods across the 14 application sectors covered by the restriction. Sectors where no viable alternatives currently exist — such as certain medical device applications or semiconductor manufacturing — may receive time-limited exemptions or extended transition periods. However, even exempted applications are not exempt from SDS obligations. If the underlying substance classification changes as part of the restriction process, every SDS containing that substance must be updated to reflect the new classification data, regardless of whether the application itself is exempted from the restriction. This means that even companies operating in exempted sectors will need mass recalculation capability to update their SDS portfolios when substance classifications change. The exemption applies to continued use of the substance in the exempted application — not to the obligation to communicate updated hazard information through compliant SDSs.

Companies selling globally must manage PFAS compliance alongside the GHS requirements of every jurisdiction they sell into. A PFAS substance reclassified under EU CLP may not trigger the same classification change in the US under OSHA HazCom, in China under GB standards, or in other GHS jurisdictions — each country applies GHS independently with different classification thresholds and implementation rules. This creates a complex multi-jurisdictional compliance challenge: the same substance may require different SDS content, different hazard statements, and different label elements depending on the destination market. Cloud SDS platforms covering 20+ GHS jurisdictions manage each jurisdiction independently from a single substance database. When the EU classification changes, the platform updates EU-market SDSs while maintaining the correct (potentially different) classification for US, Chinese, Japanese, and other market SDSs. Companies managing this manually face the risk of applying EU classification changes to non-EU markets where they may not yet apply — or missing the EU change entirely while updating other jurisdictions.

Yes — retroactive mass recalculation is precisely what cloud SDS platforms are designed for. When a PFAS restriction takes effect and substance classifications change, the platform’s mass recalculation engine automatically identifies every mixture containing the affected substance, recalculates hazard classifications for each mixture across every applicable GHS jurisdiction, regenerates every SDS in every required language (up to 47 available), regenerates every label with updated hazard statements and pictograms, and flags which downstream recipients need the updated version. The system can automate distribution with timestamps, recipient records, and open-date proof — creating the audit trail regulators require. A €122M+ coatings manufacturer already operates at this scale: 500,000 data items extracted in 20–25 minutes across 15,000+ products and 50+ countries. The retroactive update process is measured in minutes on a cloud platform. The same process executed manually — substance identification, mixture-by-mixture recalculation, document regeneration, translation, and tracked redistribution — is measured in weeks per restriction event.

The scale of PFAS compliance — potentially thousands of affected mixtures, dozens of GHS jurisdictions, up to 47 languages, and complete audit trail requirements — exceeds what manual processes can deliver within any reasonable timeline. Consider the math: if 500 mixtures in your portfolio contain PFAS substances, and you sell into 15 markets requiring 10 languages, a single restriction event generates 5,000+ individual SDS documents requiring recalculation, regeneration, and redistribution. Manually, each document requires human review, recalculation, formatting, translation coordination, and tracked delivery. At best, a team might process 20–30 SDSs per day. That is 6–8 months of work for a single restriction event. Standard cloud SDS implementation takes 5 business days (fastest recorded: 2.5 days). Companies that implement now will have their system operational, data migrated, and mass recalculation capability in place before the PFAS restriction triggers. Companies that wait until 2027 will face simultaneous system implementation and mass portfolio recalculation — the worst possible operational scenario.