Test reports, technical documentation, and declarations of conformity are the evidence behind your PPWR data. In Polygon One you upload these documents directly on the packaging unit or component; your suppliers also deliver documents via the supplier portal.What the AI does with a document depends on its type:
Technical documentation — the AI reads out the values and proposes them for your components.
Every other analysed type (heavy metals, PFAS, recycled content, technical drawing, declaration of conformity, marking evidence) — the AI only checks whether the document fits the evidence slot it was filed under. No values are read out of it.
Other — only collected, never analysed automatically.
As the app puts it: “It reads no values out of proof documents — the values on the component are the ones you or your supplier entered.”
Open the packaging unit or component and click Upload evidence.
Upload dialog for evidence documents with document-type selection
2
Choose the document type
Select the document type: heavy metals, PFAS, recycled content, technical documentation, declaration of conformity, other, technical drawing, or marking evidence. Technical documentation is preselected.
3
Select the file
Supported are PDF, JPG, and PNG up to 10 MB (one file per upload).
4
Upload
For technical documentation the button reads Upload & analyze and the dialog shows the hint “The AI will read this document and propose the values it contains.” — this is the only type whose values are read out. All other types upload with a plain Upload; they are still checked in the background, but only with the validity check (see below). The analysis runs in the background; you can keep working.
Every document belongs to exactly one packaging unit or one component — so it is always unambiguous which data it substantiates.
If your company’s monthly AI budget is reached, analysis pauses: “Monthly AI budget reached — AI analysis is paused. The document awaits manual review.”
The AI checks whether the chosen document type matches the content — but it never changes the type itself. If it recognizes a different type with high certainty, it only stores a suggestion: Suggested type: {type} with an Apply button, shown on the document card and in the document viewer.While the suggestion is open:
No extraction runs — a document the AI says is not a technical documentation never reaches the proposal machinery in the first place (the safety valve).
The validity check runs against the type you declared — the slot the document actually sits in.
Click Apply and the document is re-typed and a fresh analysis for the new type is queued automatically. A suggestion of Other cannot be applied: documents of type Other are never analysed, so the step could never be undone — the button is not offered for it.
The older Type corrected badge (“You selected: {type}”) only appears on documents an earlier version of the AI re-typed by itself. New analyses only ever produce suggestions.
For technical documentation the AI reads out the regulated values: heavy metals (mg/kg), PFAS compliance, recycled content with source and method, materials, polymer, and mass. It also summarizes the document and shows which aspects it covers and which are missing.
Heavy metals, PFAS, recycled content, technical drawing, declaration of conformity, and marking evidence go through a lightweight validity check instead. The AI reads the cover page and the file name and answers exactly one question: does this document fit the evidence slot it was filed under?
Verdict
Meaning
Fits this evidence slot
”The cover page reads as the kind of evidence this document was filed under.”
Does not fit this evidence slot
”The cover page reads as a different kind of document than the slot it was filed under. Please check it and re-file it if needed.”
Could not be confirmed
”The cover page did not say enough to tell. Nothing is necessarily wrong with the document — it simply could not be confirmed.”
No values are written to components from these documents. The values on the component stay the ones you or your supplier entered — the document substantiates them, it does not replace them.Documents of type Other are neither extracted nor checked: they carry the badge Collected — not analysed (“Stored and available here, but deliberately never analysed automatically — no values are read from it.”).
In the document viewer, under What is this?, the AI states in plain words what kind of document this is (technical documentation, test report (lab), certificate, declaration of conformity, or other document) and which Article 5 / Annex VII aspects it addresses: covers: and missing: list materials, heavy metals, PFAS, weight, and recyclability. Below it always sits the note “AI assessment, not a compliance verdict.” — it is an orientation, not a verdict.
From the values extracted out of a technical documentation, the AI generates proposals: new components or updates to existing components, each with the field, the current value, the proposed value, and a confidence percentage. Values the AI is not sure about carry the Uncertain marker (“check it against the document before accepting”). Evidence documents of every other type produce no proposals.
Reviewing proposals: auto-applied vs. held for review
This section applies to technical documentation uploads only — that is the only type that produces proposals. Polygon One distinguishes two paths:
Automatically applied (AI): values the AI is confident about are written directly to the component. These writes are fully transparent: the “Automatically applied by AI” card lists every automatically written value with its date, and any applied value can be removed again via Revert value — the field then returns to “not provided”.
Held for review: uncertain values are held back. They appear in the review panel “AI analysis: proposed data”, where you decide each proposal via Accept or Reject — you can also reject individual fields of a proposal. Only your acceptance writes the value to the component. One particularly important safety net: if the AI reads exactly 100 mg/kg for heavy metals (the legal limit), the value is always held for manual review — the likely explanation is that it accidentally read the limit instead of the measurement.
Review panel with AI proposals: current value, proposed value, confidence
Accepting a value only stores the measured value on the component’s record — whether the duty is met is derived separately from that value by the obligation checklist. An accepted heavy-metals value of 120 mg/kg therefore correctly results in Outstanding, not “Met”.
Via the Accept all AI suggestions ({count}) button in the documents view, you accept all open proposals across all documents and units in one pass; the confirmation dialog states how many of them are flagged as uncertain. Proposals missing required details stay open for review.
Via Reanalyze in the document viewer you re-run the analysis of an already-analyzed document — for instance after a model improvement, or when a document looks misfiled. A confirmation dialog explains what happens.
For technical documentation: open proposals are replaced; values already applied to components are kept (still undoable via Revert value).
For every other analysed type there are no proposals — the re-run refreshes the validity verdict and, where applicable, the type suggestion.
Under Documents (/packaging/documents) you find all packaging evidence in one place: “All packaging evidence — technical documentation, declarations of conformity, and substance attestations.”
Documents view: cards grouped by document type with analysis badges
Documents are still shown as cards grouped by document type, with a toolbar above them for narrowing down and working through the list:
Filters:Type (document type), Review (review status), AI analysis (Needs review, Analyzed, Analysis running, Never analyzed), Supplier, Component, and Packaging unit — each multi-select with search — plus the free-text search (“Search documents…”).
Sort: Newest first, Oldest first, Name (A–Z), Name (Z–A), or Type.
Header actions:Analyze not analyzed queues every document in the current filter that has never been analyzed — the confirmation dialog states that this uses your AI allowance. When open proposals exist, the bulk button for accepting all AI suggestions appears as well.
Every card shows the file name, upload date, the linked unit or component, the review status, and the AI badges: Analysis in progress…, Not analyzed yet (with an Analyze button), {n} values extracted, AI-checked, or Collected — not analysed. Alongside them sit the validity verdict, the proof badges Confirms your entry and Differs from your entry — and File missing when the stored file has passed the retention period (the document’s details and AI analysis are kept as a record).
A click opens the document viewer: the PDF preview on the left; type, review status, linkage, the AI analysis with its validity verdict or extracted values and open proposals, and download on the right.
Independently of the AI, you judge each document as a whole. Until you decide it shows as Pending review, afterwards as Approved or Rejected. How you reject depends on where the document came from:
Delivered by a supplier:Reject & request a new one — a reason is required so the supplier knows what to fix. The corresponding data request automatically goes back to the supplier with a “Documents to replace” note, and they are notified.
Uploaded by you:Reject document — the rejection is internal only, and the reason is optional (but useful for your team).
A rejected document no longer satisfies any duty.
Safety net: if the validity check comes back Does not fit this evidence slot, Polygon One puts an automatically approved document back to Pending review, so an obviously misfiled document does not silently count as checked. A decision a human has already made is never overridden.
The PPWR requires conformity records to be kept for 5 years — for reusable packaging 10 years (likewise the traceability records under Art. 22). Your documents uploaded to Polygon One remain stored centrally and can be retrieved and exported at any time, so you can meet these periods towards market surveillance.
