> ## Documentation Index > Fetch the complete documentation index at: https://help.polygon-one.com/llms.txt > Use this file to discover all available pages before exploring further. # Data Collection Overview > Why collecting data from suppliers is the heart of PPWR compliance ## Why data collection? The PPWR demands evidence about things you usually **do not know yourself**: material composition, heavy-metal and PFAS values, recycled content, weights. That data sits with whoever actually makes the packaging — your **supplier**. Without their input you can complete neither the technical documentation (Annex VII) nor the EU Declaration of Conformity (Annex VIII). This is exactly why Art. 16 PPWR obliges the supplier to provide the manufacturer with all information and evidence needed to demonstrate conformity. Polygon One turns this exchange into a structured workflow: you send a request, the supplier delivers directly into the platform, and the data lands on the right packaging unit without retyping. Data collection closes the open items from the [obligation checklist](/en/ppwr/rollen-pflichten/pflichtenkatalog): every delivered component and every delivered document directly feeds the status of your units. ## The two collection grains A data request always targets exactly one of two grains: ### 1. Supplier on the packaging unit (recommended default) You assign a supplier to a whole **packaging unit** and request the data for the unit. The supplier **authors the components themselves** in the portal — they know best what their packaging is made of, with which materials, weights, and substance values. Alternatively, they upload their existing technical documentation or Declaration of Conformity. This is the primary way of working: you do not need to know the packaging's bill of materials yourself; the supplier builds it for you. ### 2. Supplier on the individual component If you have already created a unit's components yourself, you can assign a supplier to individual **components** and request the data for exactly that component (e.g. only the heavy-metals test report for the lid). The supplier then fills in the values of the existing component instead of creating new ones. A request always targets either units **or** components — never a mix of both. You assign the supplier directly in the request dialog, in the packaging unit's form, or in the supplier dialog. ## The collection cockpit: Suppliers The **Suppliers** menu item (`/packaging/suppliers`) is your control cockpit for the entire collection: **"Track which suppliers have been asked for packaging data, who has replied, and what's blocking."**

At the top, four key figures summarize the state: **Suppliers**, **Complete**, **Awaiting data**, and **Overdue**. The table shows each supplier's journey through the collection: | Column | Content | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | **Supplier** / **Country** | The supplier's master data. | | **Collection status** | The derived status: **Not yet requested** → **Awaiting data** → possibly **Partially provided** → **Complete**; missed due dates show **Overdue**. | | **Packaging units** | Which units are assigned to the supplier (expandable). | | **Delegated** | If the supplier passed parts of the request on to a sub-supplier: "Delegated to {name}". | | **Data provided** | Progress "{provided} of {total}", plus committed dates ("Committed by {date}") and notes from the supplier. | | **Messages** | Direct entry into the message thread with the supplier. | | **Reminders** | How often the supplier was reminded automatically and when last; muted requests are marked. | | **Assignee** | Optional: which team member owns the supplier. | From every row you launch the key actions: **Request data**, **Request correction** (once data has been provided), mute or resume reminders, assign ownership. Multi-select lets you request data from many suppliers at once — **Request data ({count})**. By default the cockpit shows all of your company's suppliers. The **PPWR-relevant only** filter narrows the list to suppliers with assigned packaging units or components. ## The flow at a glance Assign the responsible supplier to the packaging unit (or to individual components) — directly in the request dialog or in the unit's form. Create a [data request](/en/ppwr/datenerfassung/datenanfragen) — as an email from the platform or as a copyable link. The supplier authors components, uploads documents, or delegates to their sub-supplier — all in the [supplier portal](/en/ppwr/datenerfassung/lieferantenportal), with no account required. The cockpit shows who has delivered and what's blocking. Automatic reminders chase late suppliers. The AI analyzes uploaded documents and proposes the values they contain — details under [Evidence documents](/en/ppwr/datenerfassung/nachweise). ## Further pages Create, send, chase requests and review replies. What your supplier sees and does after receiving the request. Uploading documents, AI analysis, the document library. Where the collected data feeds in.