Minnesota narrowed the scope of its PFAS-in-products reporting law in May 2026. Under SF 4612, signed into law on May 26, 2026, only products manufactured after July 1, 2023 must be reported under Amara's Law. Products manufactured on or before that date are now excluded from the reporting requirement. For manufacturers preparing Minnesota PFAS reports, this is a genuine reduction in reporting burden for legacy product lines, but it changes nothing about the deadline, the fee, or the eventual sales ban.

This article explains exactly what changed, what did not, and how to re-scope your PFAS compliance inventory before the September 15, 2026 deadline. It also clarifies a common point of confusion: SF 4612 is not the same as the separate HF 4257 bill, and using the wrong cutoff date in customer guidance would misstate obligations.

📌 Book a compliance risk assessment to confirm which of your Minnesota SKUs remain in scope after the SF 4612 change.

Key Takeaways

📌 SF 4612 narrows reporting scope only. Signed May 26, 2026 as part of 2026 Minn. Laws ch. 127, it amends Minn. Stat. § 116.943, subd. 2, so that only products manufactured after July 1, 2023 must be reported.

⏳ The deadline did not move. The September 15, 2026 initial reporting deadline, the August 16, 2026 extension-request postmark date, and the December 14, 2026 extended deadline are all unaffected.

📄 Documentation burden shifts, it does not disappear. For any SKU excluded on manufacture-date grounds, you must retain production or batch records establishing the actual manufacture date.

⚠️ The 2032 ban is broader than the reporting exclusion. The January 1, 2032 prohibition on intentionally added PFAS carries no manufacture-date carve-out.

🏭 Biggest relief lands on legacy and replacement parts. Older SKUs still sold but built on or before July 1, 2023, especially long-run or discontinued-but-inventoried parts, drop out of the reporting inventory.

📌 Do not confuse SF 4612 with HF 4257. HF 4257/SF 5092 (July 1, 2027 cutoff, deadline postponement, fluoropolymer CUUs) did not advance out of committee in 2026 and is materially different.

🤖 Re-scoping is a data problem. Applying a manufacture-date filter across thousands of SKUs is where BOM-level compliance intelligence and automated supplier data collection do the heavy lifting.

What SF 4612 Actually Changed

Before this amendment, the reporting trigger in Minn. Stat. § 116.943, subd. 2 applied without any manufacture-date limitation. Every product containing intentionally added PFAS, sold or distributed in Minnesota, had to be reported regardless of when it was made.

SF 4612 adds a single threshold condition. Reporting now applies only to products manufactured after July 1, 2023. Products manufactured on or before that date are excluded from the reporting obligation entirely. According to the Minnesota Pollution Control Agency, the change responded to manufacturers of replacement parts made years ago, for whom sourcing PFAS composition data on older products was often impossible.

This is a scope-narrowing amendment and nothing more. It does not touch the reporting deadline, the fee, the extension process, or the 2032 sales ban. If your Minnesota program treats template scope and deadlines as one setting, this is the moment to separate them. Certivo positions PFAS scope as a re-runnable filter inside a centralized compliance data backbone, not a one-time manual pass.

Minnesota SF 4612 PFAS reporting scope narrowed to products made after July 2023

Click on image to view full

What Did Not Change: Deadlines, Fees, and the 2032 Ban

It is easy to misread a scope reduction as deadline relief. It is not. The table below separates what SF 4612 changed from what remains exactly as previously tracked.

The September 15, 2026 deadline was set administratively through MPCA rulemaking, not by SF 4612, which is why the amendment leaves it intact. Manufacturers tracking multiple state deadlines can keep Minnesota on its existing timeline while adjusting only the scope filter. For teams juggling several jurisdictions at once, continuous compliance monitoring matters more than any single date, because the next state framework will not share Minnesota's cutoff.

Critically, the January 1, 2032 prohibition on intentionally added PFAS applies without a manufacture-date exclusion. A product made on or before July 1, 2023 may drop out of the reporting inventory yet still fall under the 2032 ban. Treating the reporting exclusion as ban relief would be a serious error.

The Three Conditions That Now Trigger Reporting

Post-amendment, a product must meet all three conditions together to require reporting:

1. Manufactured after July 1, 2023. This is the new condition SF 4612 introduced.

2. Sold, offered for sale, or distributed in Minnesota. This includes online sales shipped into the state.

3. Contains intentionally added PFAS. This includes PFAS in internal or electronic components, which MPCA has confirmed are not exempt from disclosure.

Miss any one and the product is out of scope for reporting. All three together and it stays fully in scope, filed through Minnesota's PRISM system. This three-part logic is exactly what makes BOM substance and threshold management valuable: the decision has to be made per SKU, per component, at scale.

The Documentation Burden Behind the Exclusion

The exclusion is not automatic. For every SKU you remove from the reporting inventory on manufacture-date grounds, you should be able to prove the manufacture date. MPCA's due-diligence expectations extend to supporting an exclusion claim, not just an inclusion.

That means retaining production records, batch or lot data, or equivalent evidence establishing the actual manufacture date. For long-production-run parts that straddle July 1, 2023, this is harder than it looks, because a single SKU may have units on both sides of the cutoff. This is where automated supplier data collection and structured evidence retention keep an exclusion defensible rather than assumed.

The practical takeaway: SF 4612 reduces how many products you report, but it adds a new evidentiary obligation for the products you choose to exclude. Documentation burden shifts, it does not disappear.

Three conditions triggering Minnesota PFAS reporting after SF 4612 scope change

Click on image to view full

SF 4612 vs HF 4257: Do Not Confuse the Two

There are two different Minnesota PFAS bills in circulation, and mixing them up would misstate obligations in customer-facing guidance.

Any internal alert, tracker, or customer note referencing "Minnesota PFAS scope narrowing" must specify which bill and which cutoff is meant. July 1, 2023 is already law. July 1, 2027 is a proposal that did not pass in 2026. Certivo covers the pending bill separately in its HF 4257 analysis, and keeping the two straight is exactly the kind of distinction CORA-powered regulatory intelligence is built to preserve across a fast-moving state landscape.

Industries Most Affected by the Scope Change

The relief is concentrated where legacy product lines are common:

• Manufacturers with older, still-sold SKUs. Discontinued-but-inventoried or long-production-run products built on or before July 1, 2023 fall out of scope. This is the clearest benefit.

• Electronics, automotive, and industrial makers with fluoropolymer components. PTFE seals, gaskets, and coatings are widespread, so electronics manufacturers and automotive suppliers gain relief for pre-2023 production, but none for anything built since.

• Consumer goods brands selling into Minnesota. Any consumer goods manufacturer maintaining a PRISM inventory should re-run its scoping logic against the July 1, 2023 cutoff before the deadline.

The common thread: relief applies to pre-2023 production only. Anything manufactured after July 1, 2023 remains fully in scope.

How to Re-Scope Your Minnesota PFAS Inventory

A practical checklist before September 15, 2026:

✅ 1. Apply the cutoff. Filter your PRISM inventory to exclude products manufactured on or before July 1, 2023.

✅ 2. Document each exclusion. Capture the manufacture-date basis (production, batch, or lot records) for every excluded SKU.

✅ 3. Handle straddle SKUs carefully. For parts produced across the cutoff, confirm which units are in scope rather than excluding the whole SKU.

✅ 4. Keep the deadline separate. Do not treat scope narrowing as deadline relief. September 15, 2026 stands.

✅ 5. Confirm the boundary date. For the exact-date edge case (products made on July 1, 2023 itself), confirm treatment against verbatim § 116.943, subd. 2 before finalizing customer guidance.

✅ 6. Clean the dataset for reuse. Because PRISM was designed for multistate adoption, a manufacture-date-aware Minnesota dataset is likely reusable as Maine, Connecticut, Washington, and New Mexico frameworks advance.

📌 Struggling to apply a manufacture-date filter across thousands of SKUs? Request a compliance review to see how Certivo re-scopes a PRISM inventory in hours, not weeks.

Audit Readiness and Evidence Integrity

PFAS disclosures are public once MPCA's review period closes, which raises the bar on evidence quality. Whether the trigger is a customer audit, a regulatory inspection, or a certification review, the questions are the same: who submitted the manufacture-date evidence, when, and on what authority.

That points to three capabilities: immutable audit logs, time-stamped declarations, and point-in-time retrieval of what your reporting position was on a given date. No software makes a program audit-proof, and Certivo does not claim otherwise. The realistic goal is audit-ready: fewer surprises and a shorter path from an auditor's question to a documented answer. Continuous audit-ready documentation is what turns a scope decision into a defensible record rather than an assertion.

The Role of AI in Managing PFAS Reporting Scope

Re-scoping thousands of SKUs against a single date sounds trivial and rarely is. Manufacture dates live in disparate systems, supplier records, and batch logs, and the exclusion is only as good as the evidence behind it.

CORA-driven compliance intelligence helps in three ways. It parses supplier documents and certificates to extract and validate manufacture-date evidence, reducing manual review. It maps PFAS presence to specific products and components so the three-part reporting test can be applied at the BOM level. And its regulatory intelligence layer distinguishes SF 4612 from HF 4257 automatically, so an enacted July 1, 2023 cutoff never gets confused with a proposed July 1, 2027 one. The result is a shift from reactive, spreadsheet-driven reporting toward continuous, multi-tier PFAS visibility that carries forward as other states adopt similar rules.

Before the September 15, 2026 deadline, the practical priority is simple: apply the July 1, 2023 cutoff, document every exclusion, and keep the deadline untouched. Certivo gives manufacturers a single system of record where PFAS scope, supplier evidence, and audit history live together, so a change like SF 4612 becomes a re-run of a filter rather than a manual scramble across spreadsheets.

📌 Book a compliance risk assessment to confirm your post-SF 4612 Minnesota reporting scope and evidence readiness.