A Folder of Supplier Declarations Is Not a Compliance File by VerdLynx

On 12 August 2026, the EU's Packaging and Packaging Waste Regulation, Regulation (EU)2025/40, better known as PPWR, begins to apply. There is no transition period. For every brand placing packaged products on the EU market, packaging compliance stops being a future projection on that date and becomes a present-tense obligation.

Most companies have prepared intuitively: they wrote to their packaging suppliers and asked for declarations.

Confirm this laminate is PFAS-free. Confirm this carton is recyclable. Confirm this ink is fine.

The replies were filed, the box was ticked, everyone moved on.

Here is the uncomfortable part: a folder of supplier declarations is not a compliance file. It is a folder of promises. The difference matters, because PPWR is built around demonstrable conformity, and when someone asks you to demonstrate it, “our supplier said so” is where the conversation starts, not where it ends.

A Declaration Asserts: Evidence Demonstrates

Under PPWR, the manufacturer draws up an EU Declaration of Conformity following Annex VIII of the regulation and holds technical documentation supporting it, and importers must verify that declaration exists before the packaging reaches the EU market. That structure tells you what regulators actually expect. The DoC is a legal self-declaration; the technical documentation is what makes it more than a signature.

A market-surveillance authority does not ask, “Did your supplier say this complies?” It asks, “Show me the documentation that demonstrates it complies.” A supplier statement can be one input into that file, but on its own it has three chronic weaknesses:

1. No measured data: "Compliant with EU requirements” is an opinion about a conclusion. It contains no numbers to check against any threshold.

2. Unclear scope: Which component, which material grade, which formulation year? Supplier reformulations are common, and a 2024 statement about a since-changed laminate evidences nothing.

3. No expiry: Declarations are treated as evergreen. Evidence isn't. Materials, suppliers, and rules all change.

None of this means supplier declarations are useless. It means they are the cover letter, not the file.

The PFAS Rules are Where Declarations Break First

The clearest illustration arrives on the same 12 August date, when PPWR's restriction on PFAS infood-contact packaging applies. The thresholds are specific: 25 ppb for any single targeted PFAS, 250 ppb for the sum of targeted PFAS, and 50 ppm for total fluorine.

Numbers that specific cannot be evidenced by a “PFAS-free” statement. “PFAS-free” is a marketing phrase; the regulation deals in measured concentrations. The document that actually supports a conclusion here is a lab test report, a Certificate of Analysis, and not every CoA does the job. A usable one:

• identifies the actual material or component you use, not a generic product family;

• states the test method and detection limits, with limits low enough to be meaningful against a 25 ppb threshold;

• reports measured values in units you can compare; ppb-versus-ppm confusion is a real failure mode (50 ppm is 50,000 ppb; misread the unit and you can be off by three orders of magnitude);

• comes from a competent, ideally accredited, laboratory; and

• is recent; a sensible working practice is to treat test certificates older than twelve months as expired and due for renewal; packaging supply chains change too quickly for older paper to stay meaningful.

If you run that checklist against a typical “PFAS statement” from a supplier, you see the gap between declared and demonstrated very quickly.

The Annex VIII DoC is a Signature, Not a Formality

The Declaration of Conformity deserves more respect than it usually gets. Someone in your organisation signs it, and that signature asserts that the packaging conforms, with the technical documentation standing behind it. Two practical consequences follow.

Generate the DoC last, not first. The declaration should be the output of your evidence file, produced after the artwork has been checked, the test reports reviewed, and the thresholds compared. A DoC produced before the evidence exists is exposure with a letterhead. (Also mind

the languages: the declaration needs to be available in the languages required by the member states where the packaging is placed on the market.)

Make a named human own it. Whatever tools you use to prepare the file, sign-off is a human act. The signer should be able to open the file behind the declaration and see why each conclusion was reached. (For a deeper walkthrough of the declaration itself, see this plain-English DoC guide.)

A Practical Sequence That Works

For a brand starting from a folder of declarations, the path to an evidence-based file looks like this:

1. Inventory first: List SKUs, break each into packaging components, and map components to materials and suppliers. Every later step keys off this.

2. Request measured data, not reassurance: Ask suppliers for test reports and CoAs, and name the thresholds and methods in the request. Suppliers answer the question you ask; ask a better question.

3. Check the numbers yourself: Compare measured values against the applicable limits, with the units double-checked. This is tedious, careful work, which is precisely why it is usually skipped.

4. Check what the pack itself says: The printed artwork, i.e., markings, labels, claims, is what a customer or inspector actually sees. Verify it against requirements before it goes to print, not after.

5. Treat the file as living: Track certificate dates, gate expired evidence out, and keep an audit trail of who reviewed what. Then, and only then, generate the Declaration of Conformity from it.

Where Software Fits and Where It Doesn't

Full disclosure: this article comes from the team behind VerdLynx, a packaging-compliance platform, so weigh what follows accordingly. The honest version of the pitch, for any tool in this category, not just ours, is this: software is useful exactly where the evidence work is repetitive and error-prone. Parsing lab reports against thresholds, checking artwork against requirements, tracking certificate expiry, keeping the audit trail, assembling the DoC from the underlying file. That is automation territory, and doing it in a structured way is dramatically less painful than spreadsheets and inbox archaeology.

What software does not do is make you compliant. No tool can. What structured evidence review does is make your compliance demonstrable, and demonstrable is the standard that matters after 12 August. Keep the human sign-off; automate the paper-chase underneath it.

The Next Three Weeks

If you are reading this in late July, sequence matters: prioritise food-contact SKUs (the PFAS thresholds bite there first), send your CoA requests now, accredited labs are busy in the run-up to the deadline, and do not sign Declarations of Conformity ahead of the evidence that supports them. A useful first step is simply reading the regulation's requirements in plain language (plain-English PPWR guide) and estimating what your packaging portfolio will owe under EPR (freeEPR fee estimator).

Declarations still have a place, as the conclusion of a file full of evidence. Just not as a substitute for one.

This article is general information about regulatory requirements, not legal advice. Verify obligations foryour specific products with qualified counsel.

*This article contains sponsored content.