Table of Contents >> Show >> Hide
- What happened, in plain English
- Quick glossary: PFAS, MPCA, and why cookware is in the spotlight
- Amara’s Law: what Minnesota actually restricted (and when)
- Inside the CSA lawsuit: what CSA argued and what stayed on the table
- Why the court dismissed the dormant Commerce Clause claims
- So what does this mean for businesses selling cookware (or anything) into Minnesota?
- What could happen next?
- Practical takeaways (not legal advice, just survival tips)
- Field Notes: of Real-World “Been There” Experiences
- 1) The “we don’t use PFAS” moment… followed by the spreadsheet
- 2) Engineers learn that “alternative coating” is a whole personality
- 3) Retailers ask one question that contains ten questions
- 4) Legal teams see the bigger pattern: state programs as market signals
- 5) The calmest teams are the ones who treat compliance like product quality
- Conclusion
Some lawsuits start with a bang. This one starts with a frying pan.
In a case that managed to mix constitutional law, “forever chemicals,” and the daily heroics of scrambled eggs,
a federal court in Minnesota (within the Eighth Circuit) granted the Minnesota Pollution Control Agency’s (MPCA)
motion to dismiss key claims brought by the Cookware Sustainability Alliance (CSA).
The headline takeaway: CSA’s dormant Commerce Clause challenge to Minnesota’s PFAS-in-cookware ban didn’t survive the motion-to-dismiss stage.
The court dismissed the Commerce Clause counts with prejudice, while CSA’s First Amendment and Supremacy Clause claims were dismissed
without prejudice after CSA voluntarily dropped them in response to the dismissal motion.
Translation: the constitutional “interstate commerce” attack is effectively over in this case, and the fight (if any) shifts elsewhere.
What happened, in plain English
Minnesota passed a lawoften referred to as Amara’s Lawthat restricts products with intentionally added PFAS.
Among the product categories affected is cookware, including common nonstick items that rely on PFAS-based coatings.
CSA (a trade group representing major cookware manufacturers) sued MPCA Commissioner Katrina Kessler in her official capacity,
seeking to block enforcement and arguing the law was unconstitutional.
Early in the case, CSA asked for a preliminary injunction to pause enforcement. The court denied that request.
Later, MPCA moved to dismiss the complaint. In the August 11, 2025 order, the court granted that motion,
dismissing CSA’s dormant Commerce Clause claims with prejudice and disposing of the other claims without prejudice.
Quick glossary: PFAS, MPCA, and why cookware is in the spotlight
PFAS: “forever chemicals” with a real-world footprint
PFAS (per- and polyfluoroalkyl substances) are a large family of chemicals valued for their resistance to heat, oil, and water.
That same chemistry also makes many PFAS persistent in the environment. Federal agencies have emphasized that
research links exposure to certain PFAS with a range of potential health concernsand that the science is still evolving,
in part because there are thousands of PFAS and exposure pathways vary widely.
MPCA: the agency charged with implementing Minnesota’s PFAS-in-products program
The MPCA is Minnesota’s environmental agency and, under the statute, plays a central role in enforcement and implementation.
That includes issuing guidance, coordinating rulemaking for reporting fees and “currently unavoidable use” determinations,
and enforcing prohibitions that roll out in phases.
Why cookware, specifically?
For decades, PFAS chemistry has been tied to some nonstick coatings. Minnesota’s guidance calls out that
Teflon™ (a brand name) is associated with PTFE, which falls within the PFAS family under Minnesota’s framework.
In other words: if your nonstick performance depends on certain fluoropolymers, Minnesota’s 2025-era rules are not just “interesting.”
They’re operational.
Amara’s Law: what Minnesota actually restricted (and when)
Minnesota’s PFAS restrictions aren’t a single on/off switch. They’re a timeline with multiple gears:
specific product-category prohibitions beginning in 2025, reporting requirements (with agency rulemaking details),
and a broader 2032 prohibition on products with intentionally added PFAS unless the use is deemed “currently unavoidable.”
The 2025 product-category prohibition
Beginning January 1, 2025, Minnesota law prohibits the sale, offer for sale, or distribution for sale of certain product categories
if the product contains intentionally added PFAS. Cookware is explicitly listed among those categories.
The statute also includes an exemption for products where intentionally added PFAS appear only in electronic components or internal components.
The 2032 “broader ban” and the “currently unavoidable use” concept
Beginning in 2032, the law generally prohibits sale of products containing intentionally added PFAS unless the commissioner determines by rule
that PFAS in that product is a “currently unavoidable use.” This creates a regulatory pressure cooker:
businesses aren’t just redesigning for Minnesota’s 2025 listthey’re also planning for a much wider 2032 horizon.
Reporting, testing, and enforcement pressure
The statute empowers the commissioner to request testing results in certain circumstances, requires manufacturer reporting in specified contexts,
and includes enforcement tools that can involve civil penalties. Meanwhile, MPCA’s public materials emphasize that implementation details
are shaped through rulemaking and guidance, which matters because “compliance” is rarely just a yes/no questionit’s usually a paperwork question, too.
Inside the CSA lawsuit: what CSA argued and what stayed on the table
CSA’s complaint originally raised multiple constitutional theories, but the case ultimately narrowed.
In response to the MPCA’s motion to dismiss, CSA voluntarily dismissed (without prejudice) its First Amendment and Supremacy Clause counts,
leaving the dormant Commerce Clause claims as the centerpiece.
The dormant Commerce Clause is essentially the principle that states generally can’t discriminate againstor unduly burdeninterstate commerce.
CSA’s pitch (in simplified form) was that Minnesota’s PFAS cookware restrictions functioned like a barrier affecting out-of-state manufacturers.
The court was not persuaded, and that’s where the motion-to-dismiss ruling becomes the big headline:
if your facts don’t plausibly establish discrimination or a substantial burden on interstate commerce, the case doesn’t proceed to discovery.
It ends earlybefore anyone’s inbox fills with 2,000 emails labeled “NONSTICK_ISSUE_FINAL_v17_REALLYFINAL.msg.”
Why the court dismissed the dormant Commerce Clause claims
The court’s analysis follows a familiar structure for Commerce Clause challenges:
is the law discriminatory (favoring in-state over out-of-state economic interests),
or is it evenhanded but allegedly places an undue burden on interstate commerce?
1) No plausible claim of overt discrimination
The court concluded CSA did not plausibly plead that Minnesota’s law discriminated against out-of-state businesses in the way the doctrine requires.
That’s important because “this impacts us” is not the same as “this is protectionist.” A state can regulate products sold within its borders
for health and environmental reasons, even if the regulation affects companies headquartered elsewhere.
2) No substantial burden pleaded (and the scale matters)
Even if a law is not discriminatory, it can still be challenged if it imposes a substantial burden on interstate commerce that clearly outweighs
local benefits. Here, the court concluded CSA had not alleged a substantial burden on interstate commerce sufficient to state a claim.
The court also noted thateven accepting CSA’s framing about the risksCSA’s allegations didn’t clear the high hurdle required for an undue-burden theory.
3) Dismissal “with prejudice” is a loud procedural message
The dormant Commerce Clause counts were dismissed with prejudice.
Practically speaking, that means CSA can’t simply re-file the same Commerce Clause theory in the same case and hope for a different outcome.
It’s the legal equivalent of being told, “No, and also please don’t ask again in this exact format.”
So what does this mean for businesses selling cookware (or anything) into Minnesota?
If you manufacture, import, distribute, or sell cookware in the United States, Minnesota’s PFAS program is a reminder that
state chemical restrictions can move faster than federal uniformity.
And because retail supply chains don’t love state-by-state fragmentation, one state’s rule can influence national product strategy.
Product design and materials strategy
Companies that historically relied on PFAS-based coatings may need alternatives (such as sol-gel ceramic-type coatings, silicone-based nonstick,
stainless, cast iron, or other surface technologies). But switching isn’t just “swap coating, ship pan.”
It can involve new performance testing, durability validation, supplier qualification, and marketing claim review.
Inventory, retailers, and the “Minnesota carve-out” problem
Minnesota compliance can force hard decisions: Do you create a Minnesota-specific SKU set, or do you transition broader product lines?
Retailers may also react early by canceling orders or limiting Minnesota distribution, especially when enforcement risk and public scrutiny are high.
Documentation: the unglamorous hero
Statutes like this tend to reward boring excellence:
knowing which products contain intentionally added PFAS, having supplier attestations,
keeping test results where needed, and maintaining a defensible basis for “PFAS-free” claims.
In compliance, the paperwork is the product.
What could happen next?
This dismissal doesn’t erase Minnesota’s lawit reinforces it. Future developments are more likely to focus on:
(1) the state’s continuing rulemaking and guidance (especially around “currently unavoidable use” and reporting mechanics),
(2) how other states adopt similar restrictions, and
(3) whether future challengers pursue different legal theories with different factual records.
Also, because Minnesota’s federal district court sits within the Eighth Circuit, it’s not unusual for business and legal communities
to shorthand this as an “Eighth Circuit” storyeven though the decision at issue was issued by a district judge, not the appellate court.
If an appeal were pursued in a future posture, the Eighth Circuit would be the next stop.
Practical takeaways (not legal advice, just survival tips)
- Map your PFAS touchpoints: coatings, gaskets, inks, packaging, and “small components” that suppliers swear are “nothing.”
- Get supplier documentation early: a confident email is nice; a signed, specific attestation is nicer.
- Read the definitions: “intentionally added” is doing a lot of workand it’s not the same as trace contamination.
- Don’t wing marketing claims: “PFAS-free” and “non-toxic” language can create its own headache if unsupported.
- Plan for 2032 now: a redesign cycle measured in years will not be comforted by a deadline measured in months.
- Watch guidance updates: exemptions and interpretations can change how a product category is treated.
- Assume Minnesota isn’t the last stop: state-level chemical regulation is trending toward more, not less.
Field Notes: of Real-World “Been There” Experiences
Because this topic sounds abstract until it lands on someone’s desk at 4:57 p.m., here are experiences that compliance teams,
product engineers, and in-house counsel often describe when PFAS restrictions collide with real commerce. These are not one company’s story
they’re the recurring patterns people report across the market.
1) The “we don’t use PFAS” moment… followed by the spreadsheet
A common first reaction is confidence: “We don’t use PFAS.” Then someone asks a second question:
“Do we use any fluoropolymers, fluorinated surfactants, or coatings that include PTFE-family materials?”
Suddenly, the conversation becomes a cross-functional meeting with procurement, R&D, and a supplier who replies,
“We’ll get back to you,” which is corporate for “we’re opening a drawer we hoped would stay closed.”
The practical lesson: most PFAS surprises come from components and sub-suppliers, not from the main bill of materials.
2) Engineers learn that “alternative coating” is a whole personality
Teams evaluating non-PFAS alternatives often describe a predictable tradeoff triangle:
nonstick performance, durability, and cost rarely improve all at once.
A prototype might test beautifully in ideal conditions but disappoint when exposed to real kitchens, real utensils,
and real people who preheat pans like they’re forging swords.
The experience many product teams report is that the successful transition isn’t a single material swap
it’s a design refresh that may include substrate changes, surface prep adjustments, and updated care instructions.
3) Retailers ask one question that contains ten questions
Retailers often start with a simple request: “Can you certify this product is compliant in Minnesota?”
That question quietly includes: compliant as of what date, under which guidance, for which components,
based on what definition, and supported by what documentation.
Companies that move fastest typically build a repeatable packet: product list, compliance basis,
supplier statements, and a plain-language explanation that a merchandising team can understand without a chemistry degree.
4) Legal teams see the bigger pattern: state programs as market signals
When a court dismisses a dormant Commerce Clause challenge like this, lawyers and policy teams often read it as a signal:
states have room to regulate product chemistry within their borders when the law is framed as health-and-environment protection
rather than economic protectionism. That doesn’t mean every statute is bulletproof, but it does mean
“we’ll sue it away” is not a business plan.
The experience many organizations take from cases like this is that litigation risk exists on both sides:
suing can be costly and uncertain, while noncompliance can disrupt distribution and brand trust.
5) The calmest teams are the ones who treat compliance like product quality
The most useful mindset shift people describe is treating PFAS compliance like quality control:
define the requirement, test or document against it, track change control, and keep records.
It’s not glamorous. It is, however, the difference between “We think we’re compliant” and
“Here is the support for our compliance position,” which tends to play much betterwhether you’re talking to a regulator,
a retailer, or a very detail-oriented customer with a long memory and a short temper.
Conclusion
The MPCA motion-to-dismiss win in the CSA cookware case is more than a procedural footnote. It’s a practical reminder that
state PFAS-in-products laws can endure early constitutional attacksespecially when plaintiffs can’t plausibly plead
discrimination or a substantial burden on interstate commerce. For manufacturers and sellers, the safest bet isn’t hoping
the rules disappear. It’s building products, documentation, and supply chains that can live in a world where “PFAS compliance”
is simply part of doing business.
