Getting a PFAS declaration out of an overseas supplier
What the states actually require you to file, why that is the only declaration form worth sending, and what to do when a supplier will not answer.
Most PFAS declaration forms we see were written by guessing at what a regulator might want. That's the wrong way round, and it's why they come back empty or unusable.
The states have already told you exactly which fields you will have to file. Ask for those fields, in those words, and a declaration stops being a favour you're asking for and becomes a list your supplier can actually complete. Everything below is quoted from the statute or rule and checked on 6 September 2026. Background: which states require what and what "intentionally added" means.
Ask for the fields you will have to file
Minnesota, §116.943 subd. 2(a), requires:
- A brief description of the product, including a UPC, SKU or other numeric code.
- The purpose for which PFAS are used in the product, including in any product components.
- The amount of each PFAS, identified by its CAS registry number — as an exact quantity by a commercially available analytical method, or within a range approved by the commissioner.
- The name and address of the manufacturer, and a named contact.
New Mexico's rule (20.13.2.12 NMAC) asks for the same four things, due 1 January 2027. Connecticut's notification adds percentage weight ranges and the PFAS function.
That's your form. Four questions, per product, per component — not "do you use PFAS?"
You probably don't need an exact number
This is the single biggest unlock, and almost nobody asks for it correctly.
A supplier who hears "tell me the exact PFAS concentration" hears "pay for an assay and disclose a formulation," and goes quiet. But New Mexico accepts a band, and publishes the six it will take (20.13.2.12 NMAC B(3)):
| Band |
|---|
| Less than 100 ppm (0.01%) |
| 100 – 500 ppm |
| 500 – 1,000 ppm |
| 1,000 – 5,000 ppm |
| 5,000 – 10,000 ppm |
| 10,000 ppm (1.0%) and above |
Minnesota likewise takes an exact quantity or a range approved by the commissioner.
So the ask becomes: "which of these six bands, and what is the CAS number?" That is a question a factory quality manager can answer from what they already know, without commissioning a test or handing over a recipe. Note that New Mexico requires documentation verifying analytical results where an exact figure is given — another reason a band is often the more honest answer.
There is no "my supplier wouldn't say" exemption
Worth being blunt about, because people assume otherwise: neither statute contains a provision excusing a manufacturer who could not get the information. We looked. Minnesota lets the commissioner waive part of the requirement where substantially equivalent information is already public (subd. 3(a)) and extend a deadline where more time is needed (subd. 3(d)) — but those are about publicity and timing, not about missing data.
And as covered in post one, if your overseas producer has no US presence, you are the manufacturer for these purposes. There is nobody upstream the obligation can be handed to.
The lever most importers don't know about
New Mexico lets the supply chain decide who files. From 20.13.2.12 NMAC (A):
All manufacturers must assume responsibility to report unless manufacturers in the same supply chain enter into an agreement to establish their respective reporting responsibilities.
A supplier — or a trade organisation acting for a group — can report on your behalf. The conditions are real and worth reading: the reporting party must notify the others that it has filed; everyone keeps documentation of the arrangement; everyone executes the agreement and produces it on request; and each manufacturer must verify that the data submitted on its behalf is accurate and complete.
For an importer buying from a large producer who already reports for other customers, that can be a much shorter path than extracting the data yourself. It is not a way to make the obligation disappear — you still verify the data — but it moves the work to whoever holds the information.
What actually gets an answer
Things that work, in rough order of effectiveness:
- Send the four fields, not a questionnaire. A supplier who can answer in five minutes usually does.
- Offer the bands. "Which of these six ranges" beats "what concentration."
- Name the law. Suppliers who ignore a buyer's form will often act on "Minnesota requires me to report this, and I am the filer."
- Ask per product, not per catalogue. A blanket request across 200 SKUs gets one blanket answer, which is worth nothing.
- Ask what it's for. The function question is required anyway, and it's the one a technical contact enjoys answering — it's about their product, not their liability.
- Put a date on it. An undated declaration cannot be re-checked, and material changes invalidate it.
The part that goes wrong six months later
A declaration is evidence about one moment. Suppliers change materials, substitute a coating, move a line to a second factory. Nothing tells you when that has happened — which is why the declaration needs to live on the product record with its date, so the question "is this still true?" has somewhere to land.
In Aleph, you upload the declaration against the product it covers, with its date and an expiry, and you get an alert before it lapses.
This article is general information, not legal advice. Every requirement above is linked to the state's own statute or rule — check those before acting, and talk to counsel about your specific catalogue.