Minnesota PFAS reporting has pulled thousands of companies into a question they never expected to face: are we even required to file? If you only import, only put your brand on a product someone else makes, or sell into Minnesota through an online marketplace, your obligation under Amara's Law is not obvious. This guide works through the actual scope test so you can decide whether you are a reporting party before you spend weeks collecting supplier data.

The question of who must report Minnesota PFAS is answered by statutory definitions, not by how your company describes itself. A business that has never called itself a manufacturer can still be one under Minnesota's PFAS law. Below is the decision framework, the exemptions that genuinely apply, and the traps that cause companies to wrongly self-exclude.

If you are unsure whether your products contain reportable forever chemicals, the practical starting point is to map your bill of materials against Minnesota's reportable PFAS before the deadline. You can request a compliance review to pressure-test your scope determination.

What Is Amara's Law, in One Paragraph

Minnesota's PFAS reporting requirement lives in Amara's Law, codified at Minn. Stat. § 116.943 and enacted in May 2023. It is named after Amara Strande, a Minnesota teenager whose death was linked to PFAS contamination. The Minnesota PFAS law does two things in sequence: it bans intentionally added PFAS in specific product categories, and it requires manufacturers to report every product containing intentionally added PFAS that is sold in the state. This article addresses the second obligation, the reporting requirement, and specifically the question of who is in scope.

The Three-Part Test: Are You In Scope?

A product triggers the Minnesota PFAS reporting requirement only when all three of the following are true at the same time. Under Minn. Stat. § 116.943, subd. 2, a report is required if the product or product component:

1. Was manufactured after July 1, 2023;

2. Is sold, offered for sale, or distributed in Minnesota, including through online sales into the state; and

3. Contains intentionally added PFAS.

Miss any one of the three and the reporting obligation does not attach. This is the most useful filter for companies weighing Minnesota PFAS applicability. Before you analyze definitions, confirm whether all three conditions can even be met for the products you place into Minnesota commerce. Certivo's overview of the Minnesota reporting requirement under Amara's Law breaks down each condition in more detail.

Three-part test decision flow for who must report Minnesota PFAS

Click on image to view full

What "Manufacturer" Actually Means (Importers, Brand Owners, Distributors)

The word manufacturer in this law is broad, and this is where most scope confusion under Amara's Law begins. Under Minn. Stat. § 116.943, manufacturer means the person that creates or produces a product, or whose brand name is affixed to the product. For a product imported into the United States, manufacturer includes the importer or first domestic distributor if the party that made or assembled the product, or whose brand name is affixed to it, has no presence in the United States.

Read that against your own role:

The practical point: obligated parties can sit inside or outside Minnesota and can include entities not usually thought of as manufacturers, such as retailers whose brand or private-label name is on a product. Out-of-state and foreign-origin sellers routinely underestimate this. If your brand is on the box, or you are the first US party bringing a foreign-made good into commerce, do not assume you are downstream of the obligation.

What Counts as "Intentionally Added" PFAS

The third condition, intentionally added PFAS, is a functional test, not a contamination test. PFAS are intentionally added when the chemicals are deliberately used to serve a specific function, such as water resistance, grease resistance, or chemical stability. Incidental contamination, such as trace PFAS introduced through water or shared equipment, is not intentionally added.

That distinction is hard to apply across a complex product. A moisture-resistant coating on a circuit board may contain intentionally added PFAS, while a trace amount in an adhesive may not. The determination has to be made component by component, which is why this obligation becomes a bill-of-materials and supplier-data problem rather than a single yes-or-no answer.

Two points matter for scope:

• If your products contain no intentionally added PFAS, formal reporting is not required, but you should retain the supplier evidence and documentation supporting that determination.

• The chemistry scope is wide. Minnesota reaches a broad range of PFAS, including fluoropolymers such as PTFE, so "we only use PTFE" is not a reason to assume you are out of scope. Certivo's guide to tracking PFAS materials across the supply chain covers how to structure that determination.

The July 1, 2023 Manufacture Date: The Exclusion That Narrows Scope

The most important recent change to scope is the manufacture-date exclusion. In the 2026 legislative session, Minnesota amended Amara's Law to exclude products manufactured before July 1, 2023 from the reporting requirement. The change reflects feedback from manufacturers, particularly those responsible for replacement and service parts produced before the law was enacted, for whom sourcing PFAS data on older products was often impossible.

This is genuine relief for companies with long-lived products, legacy inventory, and spare parts. If a specific SKU was manufactured before July 1, 2023, it falls outside the reporting requirement even if it is still sold in Minnesota today. Depending on your production and inventory records, this can meaningfully reduce the population of products you need to assess. The date is not cosmetic. It is now the first gate in the three-part test.

Who Is Exempt: The Statutory Carve-Outs

Beyond the manufacture-date exclusion, the statute lists specific exemptions. Under Minn. Stat. § 116.943, subd. 8, the section does not apply to a product for which federal law governs the presence of PFAS in a manner that preempts state authority; a product regulated under section 325F.072 or 325F.075; or the sale or resale of a used product. Sections 325F.072 and 325F.075 are Minnesota's separate rules on firefighting foam and food packaging, so those categories are handled under their own regimes rather than through this reporting requirement.

There is also a medical carve-out, and its scope must be read precisely. The sales prohibitions in subdivisions 4 and 5 do not apply to a prosthetic or orthotic device, or to a medical device, drug, or product used in a medical setting or application regulated by the FDA. That exemption is written against the prohibition provisions. Manufacturers of FDA-regulated medical products should confirm their reporting position directly against the statute and MPCA guidance rather than assume a blanket reporting exemption.

The Trap: "Exempt from the Ban" Is Not "Exempt from Reporting"

This distinction catches even sophisticated manufacturers. Minnesota treats internal and electronic components differently under the two halves of the law. Intentionally added PFAS in internal and electronic components is exempt from Minnesota's PFAS sales prohibitions, and those uses are instead slated for prohibition in 2032 unless designated a currently unavoidable use.

That exemption applies to the sale ban, not to disclosure. Internal and electronic components containing PFAS are not exempt from the reporting requirement. A product whose only PFAS sits inside an electronic component may still be fully reportable even though it is not subject to the current Minnesota PFAS ban.

If your scope analysis stopped at "our PFAS is only in internal components, so we are fine," revisit it. You may be exempt from the Phase 1 ban and still owe a report. Certivo's breakdown of PRISM deadlines and CUU exemptions addresses this point, and it is one of the most common reasons companies mistakenly self-exclude.

Comparison of Minnesota PFAS reporting scope versus the sales ban scope

Click on image to view full

A Quick Word on the PFAS Ban (Phase 1) and Your Category

Scope also depends on which product categories you make. Since January 1, 2025, Minnesota has banned the sale of intentionally added PFAS in eleven categories, including cookware, cosmetics, carpets and rugs, cleaning products, dental floss, fabric treatments, juvenile products, menstruation products, textile furnishings, ski wax, and upholstered furniture. The Minnesota PFAS cookware ban and cosmetics restrictions are the most searched of these, and companies in those categories often face both a sales prohibition and a reporting obligation for other products they sell into the state.

By January 1, 2032, the framework expands to a broad ban on all intentionally added PFAS in products sold in Minnesota unless a use qualifies as a currently unavoidable use. Being in a banned category does not remove your reporting duty for other qualifying products. Certivo's summary of 2026 state PFAS regulations shows how Minnesota compares to other state PFAS regulations.

If You Are In Scope: Deadlines, Fees, and What to File

Once you confirm scope, the operational requirements are clear. Reports are filed through the MPCA's PFAS Reporting Information System for Manufacturers (PRISM). Under Minn. Stat. § 116.943, subd. 2 and Minn. R. 7026, each report must include, for every covered product or component: a product description; the identity of each PFAS by name and CAS number where known; the amount or an approved concentration range of each PFAS; the function or purpose the PFAS serves; and manufacturer contact information.

One legal nuance worth understanding: the codified statutory deadline still reads on or before January 1, 2026, but MPCA used its extension authority to set the operative initial deadline, most recently to September 15, 2026. The current, administratively set timeline is time sensitive:

The fee is a one-time flat $800 per manufacturer, regardless of how many products you report, which rewards comprehensive, well-organized filing. The rule also allows grouping of similar products, reporting by a group of manufacturers together, and concentration ranges instead of exact amounts. For this first cycle, MPCA will consider companies compliant if they provide all available information and document their efforts to obtain missing data from suppliers. Verify these details against the MPCA's reporting PFAS in products page and the text of Minn. Stat. § 116.943.

Why the Scope Question Is Really a Data Question

For most enterprises, "are we in scope?" cannot be answered from a policy document. It is answered from the bill of materials, because the intentionally-added determination happens at the component level and depends on supplier disclosures you may not currently hold. That is the operational core of Minnesota PFAS reporting: identifying, across every SKU sold into the state, which components carry reportable PFAS and which suppliers can substantiate it.

This is where a centralized approach matters. A materials and environmental compliance system lets you map substances against your BOM, run supplier data collection at scale, and hold time-stamped evidence for the determinations you make. Certivo pairs BOM-level substance mapping with automated supplier outreach so the in-scope question is answered against real product data, and the automated supplier data collection built for article importers targets exactly the multi-tier gaps that make scope hard to confirm.

CORA-powered regulatory intelligence keeps the reportable-substance list and applicable deadlines current, so a determination made today does not silently go stale as lists and thresholds evolve. Certivo scans your bill of materials against Minnesota's reportable PFAS and flags where supplier data is missing. To confirm your exposure before the September 15 deadline, request a compliance review.

What This Means for Executive Teams

For the board and CEO, the exposure is direct: PRISM filings become publicly accessible after a review period, so a scope error that leads to a missed report carries reputational as well as regulatory consequences under Minnesota's forever chemicals law. For the CFO, the fee is modest at $800 per manufacturer, but the real cost is supplier data collection and the internal effort to reach a defensible determination across the portfolio.

For compliance, quality, and supply-chain leaders, the action is to resolve scope now rather than at the deadline. Confirm which SKUs were manufactured after July 1, 2023, establish obligated-party status across your import and brand relationships, and document the basis for any product you treat as out of scope. Companies that treat this as a one-time filing rather than an ongoing PFAS identification program will struggle with the February 1 annual update cycle and with the broader wave of state PFAS regulations following Minnesota's model.