Skip to main content

​
Overview

When you ask a supplier for packaging data for PPWR compliance, they receive a packaging request. This page shows what the supplier sees and how they reply — so you can support them effectively. The supplier has two ways in, both leading to the same form:
  • Invite link — the supplier answers the request directly via a secure link from the email, without their own account.
  • Signed-in workspace — if the supplier has a portal account, they find all requests under Packaging data requests (/supplier/packaging-requests). This list is for overview; the reply still happens in the request form.
The supplier can complete the entire request with the invite link alone. The signed-in workspace is an optional convenience layer for tracking several requests in one place.
One link per customer. The supplier keeps one link per customer relationship; further requests from the same customer appear under that same link. If exactly one request is open, the link opens that request directly. If several are open, the supplier lands on the request list (see below).

​
1. The request list

In the signed-in portal, Packaging data requests lists all customer requests. The same list appears via the invite link whenever several requests are open. Above the list sits the guidance “Complete each request separately. Start with the requests under To do.” The list is split into two sections:
  • To do — everything that needs action, with a counter (“{n} requests need your action.”).
  • Completed — “Submitted and cancelled requests are kept here for reference.” This section only appears once such requests exist.
Each row shows:
  • whether Packaging units or Components are requested, next to the status badge
  • “{n} requested items” and the request type
  • From {company}, Due {date} (or No deadline) and Received {date}
  • exactly one button whose label depends on the status: Start request, Continue, Make corrections or View response. Cancelled requests have no button — they show No action needed.
When nothing is open under To do, the supplier sees You’re all caught up — “There are no packaging data requests that need your action.” Possible statuses: Open, In progress, Submitted, Cancelled and Changes requested.

​
2. Understanding the request

After opening it, the supplier sees who made the request, which packaging units or components are affected, by when it is requested, and the customer’s message. The welcome step explains the purpose:
Your data on materials, weight, recycled content and substances is the foundation. It lets the requester complete the technical documentation and EU Declaration of Conformity required from 12 August 2026.
Every new request is a data request: the supplier records the requested information and sends it back (see below).

​
3. The request overview

Your data request guides through all requested items. Per unit it shows a status — Open, In progress, Ready or Document provided — and progress (“{ready} of {total} ready · {n} covered by document”). Above one item there is also a search (“Search by name, reference or code…”) and the Filter by status control. Per unit the supplier finds:
  • the components expanded inside the row, each with its own status and the button Enter data or Add component;
  • the document upload, with no intermediate step;
  • Delegate as the third, subordinate option.
Below an unfinished row, in warning colour, stands what is missing — “Missing: Heavy metals” or “No component data entered yet.” That line is clickable and leads straight to where the entry belongs.

​
3a. Dropping documents and having them read

Automatic document analysis is not available in every workspace. Where it is not active, uploaded files are neither read nor used to prefill anything — your supplier uploads them and types the values into the fields themselves.
Above the list sits the drop zone “Drop your documents here”. The supplier drops their documents there, each file gets its own row with its terminal state, and where the placement on a unit is not certain the app asks instead of guessing. The full flow — file states, the placement question, newly detected components, and how values that were read are marked in the form — is described under Supplier portal. Under “Your documents”, every row is clickable and opens a guided window with the tabs “Document” and “Your details”, where the supplier works through file and form side by side and can change the assignment to a unit; once they have worked through a document, “Up next” marks the following one. This list and the window do not depend on automatic analysis — they appear as soon as a document has been uploaded for a unit.
A document does not replace the component data: “Documents do not replace the component data (e.g. heavy metals in mg/kg) — please enter it here as well.”

​
3b. Requested fields in the form

If you have asked about a single entry — by hand or automatically — your supplier sees the ask right next to the field concerned, as the marker “Requested by customer”. Clicking it opens the reason, the quoted document and, where available, the passage from it.

Field marker Requested by customer on the PFAS field

So your supplier answers in that same field and sends it back with the usual submit — there is no separate request to work through. The PPWR portal always shows them their open points; unlike the EUDR module there is deliberately no toggle for this.

​
4. Authoring components with material data

Via Enter data on the respective row, the supplier records the material data per component. Master data:
  • Component ID (optional) and Component (name)
  • Material (Plastic plastic, Paper / board paper_board, Glass glass, Metal metal, Wood wood, Composite composite, Other other) and optionally Polymer (PET pet, HDPE hdpe, LDPE ldpe, PP pp, PS ps, PVC pvc, Other other). The codes apply to the file import; in the form you pick the label.
Sustainability data — Required for 2026 (Art. 5):
  • Heavy metals (mg/kg) — sum of Pb+Cd+Hg+Cr VI, limit ≤ 100, with a basis of claim (Test report or Supplier declaration) and an optional measurement standard/method (heavy metals). For “Test report” the file is attached directly.
  • Product contact — the Contact-sensitive and Food-contact switches. For food contact the PFAS block appears: PFAS compliant, Measured PFAS (sum, ppb), Total fluorine (mg/kg), basis of claim and measurement method (PFAS/total fluorine).
Optional / supplementary: Mass (g), Recycled content (%) (with Source and Method once a value is entered), Notes and an optional Technical drawing.
The recyclability grade is not captured in the supplier form — it is a declared value at the packaging unit level. There is no grading engine.
Many components can be created at once via “Import components from a file” as CSV/Excel.

​
5. Uploading documents

The supplier attaches their documents through the drop zone or Upload document (PDF, JPG, PNG, max. 10 MB). Which main document carries the badge sufficient depends on the role you stored on the unit — for manufacturer, supplier and fulfilment service provider the supplier declaration / technical documentation, for importer, distributor and authorised representative the Declaration of Conformity (DoC); the detail is under Supplier portal. Optionally they add, under Further evidence (optional): Test report (heavy metals), Test report (PFAS), Recycled-content proof, Technical drawing and Data sheet / other evidence. In the Your documents panel the supplier sees everything they uploaded for this request — including the documents they filed under No specific unit, which sit there under Entire request. Before submitting they can remove any of them (“This uploaded document will be removed from your reply.”). After a reopen they track each file’s review status there — In review, Accepted or Rejected (with a Reason for rejection) — and can swap out rejected documents via Replace or Re-upload.
Documents are reviewed for content at the requesting company. The supplier sees no review verdict on their uploads — only that they were read and which values were taken into their fields.

​
6. Delegating to sub-suppliers

If the supplier sources parts of the packaging from their own sub-supplier, they pass those items on via “Delegate to a sub-supplier”: they choose the units or components, enter the Sub-supplier name and Sub-supplier email (the Country is optional), and pick either an invite link (“Create link”) or automatic delivery by email (“Send email”). The sub-supplier receives their own request under their own invitation link, which inherits the due date and your message from the original request; they submit it themselves, and their data flows back into this request. On your side they appear as a further supplier; unlike in the EUDR module, their identity cannot be hidden in PPWR, and the form does not offer your supplier that option either. Two limits that save questions: delegation is only possible while your supplier has not submitted their reply — not afterwards, and not even when you reopen the request for a correction. And each item goes out only once; items already delegated are no longer selectable and disappear from the list your supplier answers. If your supplier turns out to need an upstream supplier later, request those items from that company directly.

​
7. The message thread

Via Messages, the supplier and the requesting company communicate both ways. The supplier writes their message and sends it with Send; the channel stays open even after submission.

​
8. Submitting

In the Review & submit step, the supplier checks their entries and submits them. Before submitting:
  • At least one recorded component or one uploaded document exists.
  • The confirmation “I hereby confirm that the information I have provided is accurate and complete.” is ticked.
  • Every declared Art. 5 substance has a basis of claim (otherwise: “Submission blocked: missing basis for declared substances”).
Not blocking, but explicit: if the supplier submits without having answered a requested item, or with documents only and no filled-in data fields, a dialog appears first (“No requested data answered yet” or “Data fields not completely filled in”) with the option Submit anyway. With “Submit reply” the reply goes to the requesting company. The request moves through the statuses Open → In progress → Submitted. If the customer later asks for corrections, it is reopened (Changes requested), and the previous entries are pre-filled.
Submitting is the confirmation. Values the supplier typed in or explicitly adopted count as confirmed on submission and land directly on your components. A value that was only prefilled and never touched does not count as confirmed — it arrives with you as an open AI suggestion to review.
As long as you have not completed the request, “submitted” is not locked. The supplier does not have to ask you to reopen anything: they open the same invitation link, change their entries and send an update, which replaces their previous reply — and notifies you again. Only once the request is completed or cancelled can they no longer get in and do need you.“Request correction” is your row action on the supplier, not theirs — and it acts on all of that supplier’s currently submitted replies: each affected request then shows to them as Changes requested, with their previous entries pre-filled, and they are notified once per request. You write the optional reason once; it lands in the message thread of every request sent back. How many there were is in the confirmation.

​
9. Security codes and the email for security codes

A one-time code is required when the supplier changes data they have already submitted; a first-time fill is never interrupted. The code goes to a mailbox the supplier confirmed themselves — it is prefilled with the address you stored for them, and they cannot change it on their own, only by entering a code sent there. The audit trail shows you which mailbox a code went to. The full description is under One-time Code and Security Contact.