PFAS RegulationsTSCA Reporting & State-Level Compliance Challeng

Informational only, not legal advice. If you manufacture, import, sell, or distribute products in the U.S., “PFAS compliance” probably isn’t a single project anymoreit’s a lifestyle. And not the cute “morning matcha” lifestyle. More like the “my spreadsheet has spreadsheets” lifestyle.

PFAS (per- and polyfluoroalkyl substances) are a huge family of chemicals used for grease resistance, stain repellency, water resistance, and heat toleranceaka the superpowers that keep pancakes from sticking and jackets from turning into soggy paper towels. Regulators, meanwhile, are treating PFAS like the houseguest who never leaves. The result: a federal reporting rule under TSCA and a patchwork of state bans, disclosures, and product reporting programs that can make even well-run compliance teams feel like they’re playing regulatory whack-a-mole.

This guide breaks down what’s happening with TSCA PFAS reporting, why state rules don’t line up neatly, and what a practical, modern compliance program looks like when your supply chain spans three continents and a dozen product categories.

Why PFAS Compliance Got Complicated (and Fast)

PFAS regulation in the U.S. is moving in two big directions at once:

• Federal data collection and oversight (especially through TSCA reporting), where the government wants a clear picture of who made or imported what, when, how it was used, and what’s known about hazards and exposures.
• State-level product controls, where states restrict PFAS in consumer goods, require labeling or disclosure, and (in some places) require manufacturers to report product-level PFAS information into public-facing databases.

These two tracks are relatedbut they don’t share one universal definition of “PFAS,” they don’t use the same thresholds, and they don’t ask for the same kind of information. That mismatch is where the compliance headaches begin.

TSCA PFAS Reporting: What It Is and Why It Matters

The TSCA PFAS reporting rule (often called the “TSCA Section 8(a)(7) PFAS reporting rule”) is designed to gather detailed information on PFAS manufactured or imported over a long lookback period. The point is to give EPA the kind of data it needs to evaluate risks, prioritize actions, and decide what restrictions might come next.

1) Who Has to Report?

In plain English: if your company manufactured PFAS or imported PFAS (including in certain products) during the covered years, you may have reporting obligations. This can include:

• Companies that manufactured PFAS in the U.S.
• Companies that imported PFAS as chemicals, in mixtures, or in certain finished goods (depending on scope and any future amendments).
• Businesses that no longer make the product but did during the lookback period.

One reason companies get blindsided: “manufacture” under TSCA includes import. So a company that never touched a reactor, never ran a chemical process, and never wore a lab coat can still be a “manufacturer” for TSCA purposes if it imported covered materials.

2) What PFAS Are Covered?

PFAS is not a short list. It’s a big chemical family. The reporting rule uses a structural approach to define which substances are in scope. Practically, you should expect that many fluorinated surfactants, processing aids, and performance additives used in coatings, textiles, electronics, and industrial applications can fall within the reporting definition.

Common surprise areas: surface treatments, durable water repellent (DWR) finishes, grease-resistant papers, certain polymer processing aids, fluorinated lubricants, and specialty coatings in components rather than the main product.

3) What Data Does TSCA Reporting Ask For?

TSCA PFAS reporting is not just “check a box: yes/no PFAS.” It’s closer to an organized data dump (the kind your team wishes you already had). Expect data elements along these lines:

• Chemical identity (for each PFAS substance or mixture component)
• Categories of use (industrial, commercial, consumer, sector-specific uses)
• Production/import volumes (often by year)
• Byproducts, disposal, and environmental release information (where known or reasonably ascertainable)
• Worker exposure and consumer exposure info (where known)
• Existing environmental or health effects information in your possession or reasonably ascertainable

The key phrase you’ll see again and again in TSCA land is “known to or reasonably ascertainable by” the company. That standard typically pushes companies to do meaningful internal diligence rather than simply saying, “If a supplier didn’t tell us, we didn’t know.”

4) Timing: Submission Window and Deadlines You Can Actually Put on a Calendar

EPA extended the reporting timeline via an interim final rule. As things stand today, the data submission window begins April 13, 2026, and ends October 13, 2026 for most manufacturers. There is a later deadlineApril 13, 2027for small businesses reporting solely as importers of PFAS in articles.

Two practical takeaways:

• Don’t wait until 2026 to start. The reporting window is when you file, not when you discover whether you’re in scope.
• Watch for changes. EPA also issued a proposal in late 2025 that could narrow or modify the scope and timelines, so the “final” shape of obligations may evolve.

5) Filing Mechanics: It’s Data Work, Not Just Legal Work

TSCA reporting is filed through EPA’s electronic systems. In practice, the companies that do this smoothly treat it as a cross-functional project:

• Legal/Regulatory sets interpretation, scope decisions, and defensible documentation.
• Product/Engineering identifies where PFAS could exist (including coatings and components).
• Supply Chain obtains supplier disclosures and specs.
• EHS/Stewardship gathers hazard/exposure and waste management information.
• IT/Data helps map product, material, and chemical data into a usable reporting format.

If your current plan is “have Legal do it in a long weekend,” please send Legal a sympathy card now.

State-Level PFAS Rules: Same Problem, Different Flavors

State PFAS laws often focus on consumer product categories and intentionally added PFAS, sometimes with thresholds (like total organic fluorine) or special rules for certain uses. Here are a few of the state programs that commonly drive multi-state compliance strategy.

Maine: “Products Containing PFAS” (and the Moving Target Problem)

Maine has been a bellwether state for broad PFAS product regulation. The state has made amendments that changed earlier expectations (including changes that affected what a general notification program would have looked like). Maine also moved forward with implementing rules for products containing PFAS.

Compliance lesson: even when your product portfolio stays the same, the legal obligations can change midstream. Teams that build adaptable data systems and supplier contracts handle this far better than teams that treat each state as a one-off fire drill.

Minnesota: Amara’s LawPhased Bans Plus a Product Reporting Program

Minnesota’s approach is big, phased, and very real. It includes staged prohibitions on intentionally added PFAS in certain product categories and a broader “endgame” restriction laterplus a reporting program that requires manufacturers to submit product-level PFAS information.

Importantly for planning: Minnesota’s initial PFAS reporting due date is July 1, 2026. Minnesota has also communicated practical features like grouping options, supplier reporting arrangements, trade secret requests, and a fee structuredetails that matter when you’re building a process that won’t collapse on launch day.

Washington: Safer Products for WashingtonPFAS Restrictions and Ongoing Reporting

Washington runs PFAS controls through its Safer Products program, using rules that restrict PFAS in certain categories and require reporting in others. In late 2025, Washington adopted amendments (often called “Cycle 1.5”) that:

• Set reporting requirements beginning January 1, 2026 for newly covered categories, and
• Make restrictions take effect January 1, 2027, with
• Reports due January 31, 2027 (and then annually by January 31).

Compliance lesson: Washington is a reminder that “reporting” isn’t always one-and-done. Some state programs create recurring cyclesmeaning your organization needs a repeatable annual rhythm, not a single heroic sprint.

California (and New York): Textiles and ApparelThresholds, Testing, and Certificates

Textiles are a major front in PFAS regulation. California’s approach is especially concrete: it ties “regulated PFAS” to intentionally added PFAS and to thresholds measured as total organic fluorine100 ppm starting January 1, 2025, dropping to 50 ppm starting January 1, 2027. California also restricts new textile articles containing regulated PFAS, and creates special disclosure mechanics for severe wet condition outdoor apparel.

New York also has PFAS restrictions for textiles/apparel that align in timing and general concept, adding to the reality that apparel brands can’t treat PFAS as a single-state problem.

Compliance lesson: if you sell textiles nationally, you need a strategy for (1) supplier declarations, (2) certificates of compliance, and (3) a testing philosophy that is consistent, defensible, and scalable.

Colorado: Phased Consumer Product Bans, Cookware Labeling, and More

Colorado’s PFAS rules demonstrate how fast the “product category list” can expand. The state has laws that:

• Phase in bans across categories (some starting in 2024, others later),
• Include labeling requirements for cookware containing intentionally added PFAS, and
• Create restrictions and disclosure rules for other product types (including outdoor apparel for severe wet conditions and additional categories in later phases).

Compliance lesson: product teams need to know what’s in a coating, a handle, a gasket, or a surface treatmentnot just the “main material.” PFAS risk often hides in the parts list.

Other States to Watch (Because Your Customers Live There, Too)

Several states have enacted or proposed PFAS product restrictions and reporting frameworks. For example:

• Connecticut has requirements tied to disclosure for severe wet condition outdoor apparel and certain gear beginning in 2026.
• New Mexico enacted a PFAS Protection Act framework that includes a reporting requirement starting in 2027 (with additional program details developing over time).

The big picture: the state map is filling in. Even if your “high-risk” states are currently a short list, the trend line points in one direction.

Where TSCA Reporting and State Compliance Collide

It’s tempting to think of TSCA reporting as “chemical compliance” and state PFAS laws as “product compliance.” In practice, they overlap in ways that can create duplicate work unless you design for efficiency.

1) Different Definitions of “PFAS”

TSCA reporting uses a structural definition of PFAS for the rule’s scope. State laws often focus on “intentionally added PFAS,” and some add thresholds (like total organic fluorine). That means:

• A chemical might be in scope under TSCA even if your marketing team has never heard of it.
• A product might be restricted in a state even if PFAS is present below a practical supplier disclosure thresholdor shows up via contamination or impurities.

2) “Articles” and Finished Goods: The Supply Chain Visibility Trap

Many companies import finished goods or components. But PFAS details are often buried in:

• proprietary coatings,
• process aids used during manufacturing,
• component treatments, and
• supplier formulations treated as confidential.

That creates a predictable dynamic: the company with the legal obligation is not always the company with the best information. Solving that requires supplier engagement and contracts, not wishful thinking.

3) Testing vs. Declarations: The “Total Fluorine” Problem

Some state frameworks reference measurements like total organic fluorine. That raises technical questions:

• What test method is appropriate for the product type?
• Do you screen with total fluorine first, then confirm with targeted PFAS analysis?
• How do you handle false positives from non-PFAS fluorinated chemistry (where relevant)?

Testing can be a powerful toolbut it can also become a very expensive way to discover you should have started with supplier specifications and a risk-ranked approach.

4) Confidential Business Information (CBI) and Trade Secrets

Both federal and state systems can involve trade secret considerations. Companies often need to balance:

• Supplier confidentiality,
• Customer disclosure requirements, and
• Regulator reporting obligations.

A strong program documents decisions and preserves defensibility: what you asked suppliers, what you received, what you tested, and how you interpreted scope.

5) The Time Machine Element: Multi-Year Lookbacks

TSCA PFAS reporting covers a historical period. That means you may be chasing:

• old SKUs and retired product lines,
• legacy suppliers that merged or disappeared, and
• formulations that changed quietly over time (“Same product name, different chemistrygood luck!”).

If you don’t already have strong records management, the “lookback” is where your program either proves it has legsor trips over its own shoelaces.

A Practical PFAS Compliance Playbook (That Won’t Melt Down in Q4)

Here’s what tends to work for companies managing TSCA reporting plus multi-state product compliance.

Step 1: Build a PFAS “Where Could It Be?” Map

Start with categories where PFAS is historically common:

• Textiles and apparel with water/stain resistance
• Food-contact and grease-resistant materials
• Coatings, sealers, and surface treatments
• Cookware and nonstick surfaces
• Cosmetics and personal care (certain functional additives)
• Automotive care products, waxes, cleaners
• Ski waxes and high-performance recreational gear

This map helps you prioritize outreach and testing rather than treating every SKU like a crime scene.

Step 2: Create One Data Model That Serves Both Federal and State Needs

A “PFAS compliance data model” should connect:

• Product → component → material
• Material → supplier formulation or specification
• Formulation/spec → chemical identifiers (where available)
• Chemical identifiers → regulatory attributes (TSCA scope, state restrictions, thresholds)

The goal is to avoid building separate data universes for each regulation. One source of truth beats twelve frantic email threads every time.

Step 3: Use Supplier Contracts Like You Mean It

Supplier questionnaires are fine. Supplier obligations are better. Strong agreements often include:

• Disclosure obligations for intentionally added PFAS and relevant thresholds
• Notice obligations when formulations change
• Rights to request supporting documentation (SDS, specs, test summaries)
• Allocation of responsibility for state portal reporting (where allowed)

Translation: you can’t “audit your way” out of a contract that never required the supplier to tell you what you need to know.

Step 4: Decide When Testing Adds Value

Testing is most valuable when it’s targeted. A sensible approach often looks like:

• Risk-rank product lines (high, medium, low likelihood of PFAS)
• Start with supplier documentation for high-risk lines
• Use screening (where appropriate) to validate claims or identify outliers
• Confirm with targeted PFAS methods when a restriction or threshold hinges on chemistry details

Testing everything is rarely the best plan. Testing the right things at the right time is.

Step 5: Build a Compliance Calendar (and Give It an Owner)

PFAS compliance spans multiple deadlines and reporting windows. Your calendar should track:

• TSCA PFAS reporting preparation milestones and the federal submission window
• State reporting go-live dates and recurring annual reporting cycles
• Sales restriction effective dates by state and product category
• Product redesign timelines (because chemistry changes don’t happen overnight)

Step 6: Document “Reasonable Diligence” Like It Might Matter (Because It Might)

For TSCA especially, you want a clear record of:

• how you determined scope,
• what suppliers you contacted,
• what you received (and what you didn’t), and
• how you resolved uncertain cases.

If you ever need to explain your approach, “we tried our best” is not a process. Documentation is.

What to Expect Next

Two trends are likely to continue:

• Federal PFAS activity will keep evolving as EPA refines reporting scope and uses data to inform future actions.
• States will keep expanding category-based restrictions and disclosures, especially for consumer-facing products, while developing more detailed reporting systems.

If there’s a silver lining, it’s this: once you build a real PFAS data foundation, each new rule becomes an updatenot a reinvention. That’s the difference between a compliance program and a compliance panic attack.

of Real-World “Experience” (Common Lessons Companies Are Living Through)

I don’t have personal on-the-ground experience, but there are clear patterns that show up again and again in how organizations actually experience PFAS compliance. Think of these as “things compliance teams keep discovering the hard way”shared here so you can discover them the easy way.

Experience #1: The PFAS You Didn’t Know You Had Is Usually in a Finish, Not the Main Material

Teams often start by looking at the product’s primary substance (“It’s cotton!” “It’s stainless steel!”). Then someone asks about the coating, treatment, or performance layerwater resistance, stain release, anti-fog, anti-smudge, grease resistance, low-frictionand the room gets quiet. PFAS frequently enters through performance additives applied late in manufacturing or embedded in components sourced from specialty suppliers. The lesson: ask about functional effects and performance claims. “Repels water and oil” is not just marketingit’s a chemistry clue.

Experience #2: Supplier Data Collection Is a Relationship Project

Many suppliers can provide PFAS statements quicklyuntil you ask for specifics that align with different legal definitions. “No intentionally added PFAS” may be true, but then a state threshold framework (like total organic fluorine) triggers a second question: “What’s the measured level?” Some suppliers don’t test. Others test but don’t want to share. Still others share in a format that doesn’t map cleanly to reporting portals. Companies that succeed build a tiered strategy: preferred supplier templates, contract clauses, escalation paths, and (when needed) third-party testing. The “relationship” part matters, because a supplier that trusts your process is more likely to provide usable information.

Experience #3: Old Product Lines Create New Work

TSCA-style lookbacks and state “legacy” products can pull retired SKUs back into the spotlight. Companies end up digging through archived bills of materials, old SDS files, and supplier emails from “the before times.” The common surprise is that product names remain the same while formulations drift over timeespecially when suppliers substitute materials due to price or availability. Organizations that built strong change-control and specification management can reconstruct history. Organizations that didn’t may face a scramble that feels like compliance archaeology.

Experience #4: The First Year Is the HardestIf You Build a System

Year one can be brutal because it’s when you build the structure: PFAS inventory logic, supplier workflows, internal ownership, and reporting mechanics. But a well-built system pays off. By year two, the work often shifts from “find everything” to “maintain and update.” That’s why a scalable data model and a compliance calendar are not boring admin workthey’re the difference between predictable operations and perpetual emergencies.

Experience #5: The Best PFAS Program Is Also a Product Strategy Program

Finally, many companies learn that PFAS compliance is easier when product strategy aligns early. If R&D teams have clear guidance (“avoid intentionally added PFAS where feasible,” “use alternative chemistries,” “document performance needs”), compliance becomes a design input rather than a last-minute constraint. The most mature organizations treat PFAS as a lifecycle issuedesign, sourcing, testing, documentation, and end-of-lifebecause regulators and customers increasingly see it that way too.

Conclusion

PFAS regulations in the U.S. are no longer a niche environmental storythey’re an operational reality for manufacturers, importers, and brand owners. TSCA reporting asks for deep chemical and historical data. State laws add product-level restrictions, disclosures, and recurring reporting programs. The companies that handle this best don’t chase every rule with a brand-new spreadsheet. They build one PFAS foundation: a data model, supplier obligations, targeted testing, and a calendar-driven compliance rhythm.

If you do that, TSCA reporting becomes a structured filing rather than a fire drilland state compliance becomes manageable even as the map keeps changing.