Minnesota PFAS Reporting: Requirements, Deadlines, and How to File

Minnesota is the first US state to require manufacturers to report intentionally added PFAS in the products they sell. Initial reports are due to the Minnesota Pollution Control Agency (MPCA) by 15 September 2026, with updates due each 1 February thereafter. The obligation is broad, the data sits with your suppliers rather than in your own systems, and the reporting portal asks for detail at the component level.

This guide covers what the law requires, who has to file, what a report actually contains, what it costs, and how to get PFAS composition data out of a supply chain that has never been asked for it before.

What Amara's Law requires

The reporting duty comes from Minn. Stat. § 116.943, known as Amara's Law after Amara Strande, a Minnesota woman who died of a rare cancer her family linked to PFAS contamination. The MPCA adopted the implementing rules under Minnesota Rules chapter 7026.

The law has two halves. The first is prohibition. Since 1 January 2025, products in eleven categories may not be sold in Minnesota if they contain intentionally added PFAS: carpets or rugs, cleaning products, cookware, cosmetics, dental floss, fabric treatments, juvenile products, menstruation products, textile furnishings, ski wax, and upholstered furniture.

The second is reporting, which is what falls due in September 2026 and applies far more widely than those eleven categories. If a product contains intentionally added PFAS and is sold, offered for sale, or distributed in Minnesota, it is reportable, whatever it is.

Both halves work towards the same objectives. Minnesota's stated goal is to end all non-essential PFAS use by 2032, after which products containing intentionally added PFAS are prohibited unless the use is determined to be a currently unavoidable use.

Who counts as a manufacturer

The definition is wider than the word suggests. Under the MPCA's guidance, a manufacturer includes:

• the entity that actually produces the product
• the entity that contracts production of the product under its own brand or label
• the importer or first domestic distributor, where the producer or brand owner has no US presence

The practical consequence is that brand owners who outsource all production still carry the obligation, and a US distributor can inherit it from an overseas producer. Consultants and trade associations can file on a manufacturer's behalf, but they register in the reporting system first and then request authorisation from the client.

What is in scope — and what the 2026 amendment excludes

In May 2026, Governor Walz signed an amendment that meaningfully narrowed the scope. Products manufactured before 1 July 2023 are now excluded from the reporting requirement. The change took effect immediately and applies to the initial reports due in September 2026.

So a product is reportable only if all three are true:

1. It was manufactured on or after 1 July 2023
2. It is sold, offered for sale, or distributed in Minnesota
3. It contains intentionally added PFAS

That exclusion was a direct response to manufacturers of replacement and service parts, for whom reconstructing the chemistry of components made years before the law existed was often simply impossible. If a large share of your Minnesota revenue is legacy spares, this amendment may remove much of your reporting burden. It is important to confirm manufacture dates rather than assuming them.

Whether or not PFAS were intentionally added is the other boundary worth understanding. It means PFAS deliberately added to serve a function in the product, not those PFAS present as an incidental contaminant. A fluoropolymer coating applied for non-stick performance is intentionally added; trace contamination migrating from processing equipment generally is not.

What a PRISM report actually asks for

Reports are filed through PRISM (the PFAS Reporting Information System for Manufacturers) operated by the Interstate Chemicals Clearinghouse on the MPCA's behalf. This is where the work turns out to be harder than the statute makes it sound.

PRISM does not want a yes-or-no answer per product. It wants, for each product, the components that contain PFAS, and for each of those components, each PFAS chemical present. In practice, a single product with several treated parts can generate many rows. For each one you provide:

• Product identification: brand name plus an identifier such as a product code, UPC, SKU, or HTS code
• Component: the part or homogeneous material within the product that carries the PFAS
• PFAS chemical identity: normally a CAS number; where the specific chemical is unknown, total organic fluorine may be reported instead
• Function: what the PFAS does in that component, such as water repellency, non-stick performance, or surfactancy
• Concentration: reported as a range rather than an exact figure, with an option to record that PFAS is present but the amount is unknown
• Trade secret claim:where chemical identity or supply-chain detail is genuinely confidential

Two points matter operationally. First, the concentration ranges mean you do not need laboratory-grade precision. A supplier attestation placing a substance in a band is usually sufficient, which is a much lower bar than most teams assume when they start. Second, everything you submit other than approved trade secret claims becomes publicly accessible after MPCA review. Treat the submission as a public disclosure, because it is one.

What it costs

Each manufacturer pays a one-time initial reporting fee of $800. It is assessed per manufacturer, not per product, so the fee does not scale with how many products you report. For most companies the filing fee is a rounding error next to the internal cost of assembling the data.

The real bottleneck is supplier data

Almost nobody fails this requirement because they misread the statute. They fail because they cannot get answers from their suppliers in time.

PFAS composition data lives several tiers down. Your direct supplier often does not know what is in the coating their own sub-supplier applied, and the specification sheets you already hold were written to describe performance, not chemistry. Response rates to unsolicited compliance questionnaires are notoriously poor, and every unanswered request becomes either a gap in your filing or a supplier you have to chase by phone.

What separates teams that file on time is usually process, not chemistry expertise:

• Scope before you survey: filter to products manufactured on or after 1 July 2023 that actually reach Minnesota. Most companies discover the reportable set is far smaller than their full catalogue.
• Ask at the right level: request component-level composition in the structure PRISM expects, so responses arrive ready to file rather than needing translation.
• Make non-response expensive: route requests through procurement with a deadline and an escalation path, rather than sending a form from a sustainability inbox.
• Keep the audit trail: record who you asked, when, what they said, and what you did when they did not reply. If a filing is later questioned, documented diligence is the defence.

This is the same supplier data collection problem that shows up in digital product passports and in EU due diligence work: a structured request, sent to the right tier, tracked to closure. Companies that have already built their capacity for one regime tend to find the second one substantially cheaper.

If you are filing under time pressure

The one-time 90-day extension, which moved the due date to 14 December 2026, required a request postmarked by 16 August 2026. If you did not request one, that route is closed and 15 September stands.

When time is short, sequence the work by risk rather than trying to finish the catalogue:

1. Confirm whether you are a manufacturer under the definition at all, including as importer or brand owner
2. Filter the catalogue to in-scope products — post-1 July 2023, sold in Minnesota
3. Register in PRISM early; account setup and authorisation are not instant, particularly if a consultant files for you
4. Report what you know, using the 'present but unknown concentration' option where a supplier has not responded, rather than omitting the product
5. Log the outstanding supplier requests so the February update closes the gaps

A report with acknowledged uncertainty is a filed report. A product left out entirely because the data was incomplete is a missed disclosure, and those are treated differently.

After September: the annual cycle

This is not a one-off reporting exercise. Updated reports are due each 1st of February, and the obligation refreshes whenever you introduce a product, change a formulation, or add a supplier. Teams that treat September 2026 as a project rather than a process end up repeating the entire supplier chase five months later.

The durable answer is to capture PFAS composition at the point of supplier onboarding and at each specification change, so the February filing is an export rather than an investigation.

How Minnesota fits the wider state picture

Minnesota is the furthest ahead, but it is not alone . A growing group of states now regulate PFAS in specific product categories, and the reporting model Minnesota has built is the one others are most likely to copy. Minnesota also runs a separate packaging EPR programme on its own timetable, which catches many of the same companies.

For the full landscape, see our guide to US state environmental reporting requirements. If you sell consumer packaged goods, California's SB 54 packaging EPR regime raises a closely related question: the same producer definition, the same need for material-level data from suppliers, and the same pattern of registration, fees, and recurring disclosure.

Getting the data together

Minnesota PFAS reporting is not conceptually difficult. It is a supply chain data collection problem wearing a regulatory hat, and it recurs every February, alongside whatever the next state introduces.

Brightest helps manufacturers run structured supplier data collection at scale: sending component-level requests, tracking response rates, escalating non-responders, and keeping the audit trail that proves diligence. If you are working towards a Minnesota filing or building the process for the annual cycle, get in touch.