EU Declaration of Conformity for Packaging under PPWR What it is – who signs – what evidence belongs in the technical file – and how to operationalise it across SKUs and suppliers

1- What is the EU Declaration of Conformity under PPWR?

The EU Declaration of Conformity (DoC) is the manufacturer’s formal statement that the packaging complies with applicable PPWR requirements, including requirements laid down in or pursuant to Articles 5 to 12.

Think of it like this:

• The DoC is the declaration
• The technical file is the proof behind the declaration
• The conformity assessment procedure is the method that links the two

A DoC without the underlying technical file is fragile. A technical file without clear scope and version control becomes unusable at portfolio scale.

2- Where the DoC sits inside PPWR?

PPWR has two broad compliance “lanes” that many companies mix up:

• EPR and reporting lane – producer responsibility registration, reporting, fees, PROs
• Product conformity lane – packaging requirements and the proof that packaging meets them

The DoC belongs to the product conformity lane under Chapter VII.

The core chain is explicitly built into PPWR:

• Manufacturer obligations – PPWR Article 15
• Conformity assessment – PPWR Article 38 and Annex VII
• EU declaration of conformity – PPWR Article 39 and Annex VIII

Why this matters. If the DoC or technical documentation is missing, incomplete, or inconsistent with what is actually being placed on the market, you are exposed to formal non-compliance and corrective action expectations under PPWR enforcement provisions (commonly referenced under formal non-compliance concepts, including Article 62).

3- Who signs the DoC and who supports the evidence?

Who signs?

• The manufacturer draws up and signs the DoC and assumes responsibility – PPWR Article 15 and Article 39

Who must feed the manufacturer?

• Suppliers of packaging or packaging materials must provide the manufacturer with information and documentation needed to demonstrate conformity – PPWR Article 16

Importers and distributors – where accountability shifts?

• Importers must ensure that the manufacturer has carried out the conformity assessment and has the technical documentation and DoC available before placing packaging on the market – PPWR Article 18
• Distributors must act with due care and can become treated as a manufacturer if they place packaging on the market under their own name or trademark or modify it in a way that could affect compliance – PPWR Article 19

A relatable scenario

You are a brand owner selling a shampoo across 10 EU countries. Your packaging is made of:

• PET bottle from Supplier A
• PP cap from Supplier B
• Label and adhesive from Supplier C
• Carton from Supplier D for some markets
• Multipack shrink film for promotional packs

Even if your suppliers say “we are compliant,” your DoC will only be defensible if you can link each packaging type and version to:

• A controlled packaging BOM and material-weight dataset
• Evidence per component and per version
• A clear statement of what the DoC covers and where it applies

4- What must be in the DoC?

PPWR requires the DoC to follow a model structure in Annex VIII and be continuously updated – PPWR Article 39 and Annex VIII.

In practical terms, your DoC should clearly include:

• Unique identification of the packaging type covered (your packaging type ID and version)
• Manufacturer name and address (and authorised representative details if applicable)
• Statement issued under the manufacturer’s sole responsibility
• Description of the packaging object so it is traceable
• The legal reference to PPWR and any other relevant Union acts (if you combine declarations)
• References to harmonised standards, common specifications, or other technical specifications used
• Place, date, and authorised signatory details (name, function, signature)

The biggest practical question – what is a “packaging type”?

PPWR frames DoC creation at the packaging type level. To scale, you must define “type” in a way that is consistent and audit-friendly.

A workable definition:

• Packaging type = a stable combination of packaging format + component structure + material composition + compliance-relevant features
• New type or new version is triggered when a change could affect conformity

Examples of changes that should trigger a new type version:

• Material grade change (example: PET resin grade change)
• Supplier change that changes composition or evidence scope
• Weight change beyond your control tolerance
• Label, ink, adhesive change that affects recyclability assumptions
• Any claim change that requires new substantiation (recycled content, recyclability statement)

5- What evidence belongs in the technical documentation (technical file)?

The technical documentation requirements sit in Annex VII (Module A – internal production control) linked via PPWR Article 38.

At minimum, your technical file should include:

• General description of the packaging and intended use
• Design and manufacturing information, including drawings or schematics where relevant
• Explanations needed to understand design and how requirements are met
• List of standards or specifications applied
• Where standards are not applied, description of solutions used to meet requirements
• Description of assessments and results required by applicable PPWR articles
• Test reports and calculations where relevant

A practical technical file index that works at portfolio scale

Use a consistent index per packaging type:

• TF-00 Packaging type summary sheet – type ID, version, photos or renders, intended use, markets
• TF-01 Packaging BOM and specification – component hierarchy, materials, weights, suppliers, part numbers
• TF-02 PPWR applicability matrix – which Articles 5–12 apply to this packaging type and why
• TF-03 Minimisation evidence pack – Article 10 – design constraints, reduction rationale, tests or studies where relevant
• TF-04 Recyclability evidence pack – assessment method, assumptions, component constraints, evidence
• TF-05 Recycled content evidence pack (if you claim it) – supplier declarations, calculation notes
• TF-06 Labelling and information evidence pack – artwork proofs, language variants, placement rules, data carrier logic if relevant
• TF-07 Supplier evidence register – Article 16 operating proof – who provided what, date, scope, expiry, gaps, follow-ups
• TF-08 Change log and approval trail – what changed, why it matters, who approved, date
• TF-09 Tests and calculations – raw reports mapped to requirements and components

Retention rules you must design into operations

PPWR expects retention of technical documentation and DoC:

• Single-use packaging – 5 years
• Reusable packaging – 10 years

Do not treat this as “store PDFs somewhere.” Treat it as “store indexed, searchable, version-linked evidence for the retention window.”

6- How to operationalise DoC and technical files across SKUs and suppliers?

This is the section that decides whether your programme works or collapses.

Control 1- Build a canonical packaging data model

Stop managing packaging as “a few columns in an Excel sheet.” A workable model:

• SKU → Packaging assembly (versioned)
• Packaging assembly → Components (bottle, cap, label, carton, film, adhesive, inks where relevant)
• Each component → Attributes (material, weight, supplier, grade, compliance-relevant properties)
• Evidence attached at the right level (component or packaging type version)

Control 2- Use packaging type IDs and strict version triggers

Define rules that automatically trigger DoC and technical file updates:

• Material change
• Supplier change
• Weight or thickness change beyond tolerance
• Packaging format change
• Claim or label change that affects compliance positioning

This is how you meet the “continuously updated” expectation in PPWR Article 39 without chaos.

Control 3- Treat supplier evidence collection as a process, not emails

Because PPWR Article 16 makes supplier information flow a structural dependency.

Implement:

• Standard supplier request packs per component category
  • Bottle request pack
  • Cap request pack
  • Label and adhesive request pack
  • Carton request pack
  • Film request pack
• Minimum acceptance criteria
  • Issuer identity
  • Scope and applicability
  • Material grade linkage
  • Validity or expiry date
• SLA tracking, follow-ups, escalation

Control 4- Language and market variants

PPWR Article 39 expects the DoC to be drawn up in or translated into language(s) required by the Member State where it is made available.

Operationally you need:

• Master DoC controlled version
• Approved translations per market
• Mapping of market → correct DoC version
• Change process so translations update when the master updates

Control 5- Retrieval speed and authority response readiness

A portfolio-scale system must be able to answer quickly:

• Which packaging type version applies to this SKU in this market
• Where is the DoC
• Where is the technical file index
• What evidence supports key claims and assessments

If you cannot retrieve this within days, you do not have an operational conformity system.

7- Examples your team will recognise

Example 1- FMCG bottle with constant supplier churn

SKU family – Shampoo 250 ml sold in 12 EU markets.

Packaging:

• PET bottle 28 g
• PP cap 4 g
• Label 1.2 g plus adhesive
• Multipack shrink for promotions in some markets

What breaks in real life:

• Procurement switches bottle supplier or resin grade
• Marketing changes label artwork and ink coverage
• Multipack shrink thickness changes by season

What “good” looks like:

• Packaging type ID for base assembly (bottle + cap + label)
• Separate variant ID for multipack configuration
• Evidence linked to resin grade and supplier plant scope
• Change log showing what changed and whether assessments remain valid or were updated

Example 2- E-commerce fulfilment packaging controlled by a 3PL

You ship D2C with:

• Corrugated box
• Tape
• Void fill
• Inserts and return label

What breaks:

• Your 3PL changes box supplier based on cost
• You only track box size, not board grade or weight
• You cannot show minimisation rationale if challenged

What “good” looks like:

• Standard pack-out rules documented as part of minimisation evidence
• Controlled box spec per size with board grade and weight
• Supplier evidence pack and change trigger when the 3PL changes suppliers

Example 3- Reusable transport packaging for B2B supply

You use reusable crates or totes.

What’s different:

• Longer retention – 10 years
• More exposure to change over time
• Reuse performance evidence becomes more relevant operationally

What “good” looks like:

• Robust version control and long-term evidence storage
• Reuse system documentation that survives staff turnover and supplier changes

Example 4- Importer relabelling or rebranding

You import packaged products and add your brand or modify packaging.

What breaks:

• If your action makes you treated as the manufacturer for PPWR purposes, you inherit DoC and technical file expectations
• Teams still assume the non-EU manufacturer “owns it”

What “good” looks like:

• A clear rule in your system that flags “manufacturer shift events”
• Automatic triggers to create a new packaging type version and update the DoC and technical file scope

8- What goes wrong and why it matters

The most common failure modes are:

• DoC exists but does not clearly identify the packaging type and version
• Technical file is incomplete or not mapped to PPWR requirement-by-requirement evidence
• Evidence is unmanaged PDFs with no linkage to the exact packaging version
• Packaging changes happen without a version update and DoC refresh
• Supplier documents are out of scope or not applicable to your packaging component

These scenarios are exactly what formal non-compliance frameworks are designed to catch. Even if intent is good, the system must be precise.

9- How RegSurance can help?

RegSurance B.V. supports PPWR conformity readiness by building the operational backbone behind DoC and technical documentation.

1- DoC and technical file readiness sprint

• Define packaging type ID rules and version triggers
• Build a PPWR requirement-to-evidence matrix (Article mapping)
• Select pilot packaging families and set an implementation cadence

2- PaxHub as your packaging compliance data backbone

Using PaxHub, we help you implement:

• SKU → packaging assembly → component mapping
• Component-level attributes (materials, weights, supplier, grade)
• Evidence packs linked to components and packaging type versions
• Versioned exports and technical file indexes

3- Supplier evidence operations aligned to PPWR Article 16

• Supplier request templates per component type
• Acceptance criteria and validation checks
• Evidence register with SLAs, follow-ups, and escalation
• Audit-ready retrieval

4- DoC production and maintenance model

• DoC templates aligned to PPWR Article 39 and Annex VIII
• Controlled translation workflow per market language expectations
• Change control rules that automatically trigger updates

5- Authority response playbook

• Fast retrieval structure for DoC + technical file index
• “Which SKUs are impacted” mapping when a supplier or material changes
• Response readiness processes so you do not scramble under pressure