> ## 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.

# Supplier Portal

> What your supplier sees and does after receiving a data request

## Overview

This page explains, from **your** perspective, what happens on the supplier side after you send a [data request](/en/ppwr/datenerfassung/datenanfragen) — so you can answer your suppliers' questions and gauge the process.

<Card title="Guide for your suppliers" icon="eye" href="/en/ppwr/lieferantenansicht">
  A step-by-step walkthrough addressed directly to the supplier — ready to forward.
</Card>

## Access: the link is enough, no account needed

The link in the request email takes the supplier straight to their reply view. **The link itself is the access** — your supplier needs neither an account nor a password. That keeps the barrier minimal: even a supplier who has never seen Polygon One can reply immediately.

Optionally, the supplier can additionally create a persistent **supplier workspace** (name, email, password). With it, they see all requests from their customers in one place under **Packaging data requests** — with sender, type, status, due date, and received date. The original link keeps working unchanged after registration; a signed-in supplier can reactivate expired links themselves from the overview.

<Frame caption="The supplier's entry point: request overview with progress per packaging unit">
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/polygonone/images/ppwr/datenerfassung/lieferantenportal-hub.png" />
</Frame>

## What the supplier sees

After a short welcome with context (who is asking, why, what the data is needed for) and a chance to check their own company details, the supplier lands in their working view: a list of the requested packaging units (or components) with a progress indicator **"{ready} of {total} ready"**.

Each item has a status: **Open** → **In progress** → **Ready**. The status is derived automatically from the completeness of the data — the supplier cannot "tick off" anything that is not actually complete.

For each unit, the supplier answers the guiding question **"How can you provide this data?"** with one of three options:

1. **I have a document** — upload existing documentation.
2. **I have component data** — enter the packaging component by component.
3. **I have neither – invite my sub-supplier** — delegate the request onward.

### Option 1: Upload a document

Per unit, the supplier uploads one primary document — depending on their relationship to the unit, a **supplier declaration / technical documentation** or a **Declaration of Conformity (DoC)**. Such a primary document is sufficient to set the unit to **Ready**. Optionally they add further evidence (test reports for heavy metals or PFAS, recycled-content proof, technical drawing, data sheets). Accepted formats are PDF, JPG, and PNG up to 10 MB; a bulk upload distributes multiple files onto the matching units.

### Option 2: Enter component data

The supplier enters the packaging's components in a guided form: name, material, mass (g), recycled content (%), heavy metals (mg/kg, sum of Pb+Cd+Hg+Cr VI), and for food-contact packaging the PFAS details.

<Frame caption="Component authoring in the supplier portal">
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/polygonone/images/ppwr/datenerfassung/lieferantenportal-komponenten.png" />
</Frame>

Two rules safeguard quality:

* **Substantiation duty for substance data**: every declared Art. 5 substance value (heavy metals, PFAS) must be backed by a test report or a supplier declaration, otherwise submitting is blocked.
* **Self-declaration**: before submitting, the supplier confirms via a mandatory checkbox: "I hereby confirm that the information I have provided is accurate and complete." This confirmation is stored for audit.

For many units there are convenience features: CSV/Excel import of components, multi-select (author a component once and copy it into several units), and "Continue to next unit".

### Option 3: Delegate to a sub-supplier

If the packaging (or part of it) comes from an upstream supplier, your supplier can **delegate the affected items to their own sub-supplier**: they select the items, enter the sub-supplier's name, email, and country, and send out a request of their own — via automatic email or as a copyable link. The sub-supplier's data flows back into the same request; in the cockpit you see the delegation in the **Delegated** column ("Delegated to {name}").

<Info>
  The supplier can choose to keep their sub-supplier's contact details confidential (**Hide sub-supplier details**) — you still see the delivered data.
</Info>

## Submitting and afterwards

Via **Review & submit** the supplier reaches a summary (ready units, components, documents) and sends the reply with **Submit reply**. After that, the request is read-only for them:

* Your request switches to **Submitted**; the data is on your units immediately.
* The **message thread** stays open for both sides — follow-up questions continue through the platform.
* If the supplier notices a mistake afterwards, they ask for a reopen via **Request a correction**. Only once **you** grant the correction ([Request correction](/en/ppwr/datenerfassung/datenanfragen)) can they rework their — prefilled — reply and resubmit.

<Info>
  Until submission, all of the supplier's entries stay local to their session; only **Submit reply** transfers the reply to you, completely and in a single step. The portal warns when leaving the page with unsubmitted work.
</Info>

## Next steps

<CardGroup cols={2}>
  <Card title="Supplier walkthrough (for your suppliers)" icon="eye" href="/en/ppwr/lieferantenansicht">
    The step-by-step guide from the supplier's perspective — ideal for forwarding.
  </Card>

  <Card title="Evidence documents" icon="file-shield" href="/en/ppwr/datenerfassung/nachweise">
    How the AI analyzes uploaded supplier documents and how you accept the values.
  </Card>
</CardGroup>