> ## 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.
# Digital packaging record (QR)
> Publish the Declaration of Conformity, technical documentation and supporting evidence behind a QR code, share it by email, update it and revoke it
## Overview
A **digital packaging record** is a public page about **one** packaging unit or **one** packaging component. It is reached through a **stable link** and a **QR code**, and it shows exactly what you released: the manufacturer identity, the Declaration of Conformity, the technical documentation and selected supporting evidence.
This is how you meet **Art. 15(6) PPWR**: the **manufacturer's** name, registered trade name or registered trademark, together with the postal address and — where available — an electronic contact, may be provided on the packaging **or through a QR code or other data carrier**.
A digital packaging record is a **way of providing information**, not proof of conformity. The **Current** status on the public page means that everything published can currently be delivered — it does not say the packaging is PPWR-compliant. Nor does the page on its own satisfy the Art. 15(5) marking duty (type, batch, serial number or other identifying element).
On the public page the Art. 15 role is called **Manufacturer** (in German: **Erzeuger**). This is a different role from the **producer** under EPR, which drives volume reporting.
## What gets published
| Section | Contents | Applies to |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- |
| **Provided by** | Your company logo and company name as the publisher of the page | unit and component |
| Header | Name of the unit or component, **Reference** (internal reference or code), **Type** (Packaging unit / Packaging component), status and the date of the last change to the release | unit and component |
| **Manufacturer** | **Legal name**, **Postal address** and — if recorded — **Electronic contact** | packaging units in the manufacturer role only |
| **Documents** | **Declaration of Conformity** and **Technical documentation**, each with **View** and **Download** | packaging units only |
| **Supporting evidence** | The individual evidence documents you selected; the number per record is capped and the dialog states the limit | unit and component |
**Components have no core documents.** For a packaging component you publish selected **supporting evidence** only — there is no Declaration of Conformity and no technical documentation at component level: "Components have no default core document. Select the exact supporting evidence for each component."
**Nothing is frozen.** The page resolves the documents and the manufacturer identity **on every request**. Change the manufacturer details under **Settings → PPWR** and the public page is immediately up to date — the link does not change.
### The manufacturer identity appears only when it is complete and applicable
The **Manufacturer** section is **omitted entirely** unless all three of the following hold:
* The unit carries the **manufacturer role** — either directly, or under Art. 21, because an **importer** or **distributor** places the packaging **under its own brand** or **modifies it in a way that affects conformity**. In those Art. 21 cases the manufacturer block does appear. Supplier and fulfilment service provider never get it, and neither do components.
* The Art. 15 duty does not sit with the supplier (the micro-enterprise shift under Art. 15(12)).
* **Legal name and address are both recorded** (under **Settings → PPWR**).
If one of them is missing, no half identity is shown — the section is omitted and the record counts as out of date.
## Status
The packaging-units and components tables carry a **Status** column (with a filter) with five values:
| Status | Meaning |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Not published** | There is no active record. |
| **Ready to publish** | There is no record yet, but publishable content exists. |
| **Active** | A record is published and everything released can be delivered. |
| **Needs attention** | A record is published, but something released is no longer current or no longer reachable. Visitors then see **Out of date** and the note "Some published information or documents are no longer current." |
| **Blocked** | There is nothing to publish — no current core document and no eligible evidence. |
There is **no draft status**. A record is either published (active) or revoked. What gets published is decided in the dialog before you first click **Publish digital record**.
## Publishing a record
The entry point is the same in four places:
* On the **detail page of a packaging unit** or **component**: the **Publish digital record** button in the header, or the **Digital packaging record** card on the **Documents** tab.
* In the **row menu** of the packaging-units and components tables.
* As a **bulk action** from the selection in those same tables.
* From the **Documents** area via **Add to public record**.
The **Publish digital record** dialog asks you to "Choose what people with the link can see." Tick **Declaration of Conformity**, **Technical documentation** and the **supporting evidence** you want — at least one item is required ("Select at least one item.") — then publish with **Publish digital record**. The card then shows the **Canonical link**, the QR code and the status **Active**.
The dialog states it plainly: **"Anyone with this link can view the selected information."** The link is the only access control — there is no sign-in.
The card then offers:
* **Copy** — put the canonical link on the clipboard.
* **Preview** — see the public page the way a visitor sees it.
* **Download QR SVG** — the QR code as an SVG file for print artwork.
* **Email** — send the link to one address.
* **Manage** — change the selection.
* **Revoke** — switch the record off.
The QR code encodes the canonical link in the form `https://your-domain/r/…`. On a custom (white-label) domain the link carries your own domain.
## Bulk publishing and the QR package
From the selection in the packaging-units or components table, start **Publish digital records**. The dialog first checks publication readiness and shows the split **Total**, **Ready**, **Already active** and **Blocked**; blocked targets are named with a reason (**"No current core document"**, **"No eligible current evidence"** or **"Already active; needs attention"**). For components you pick the evidence per component (**Show evidence**, **Select all eligible evidence**). The run reports progress as **"Processed 12 of 40"** with **Published: …** and **Failed: …**.
Once finished, **Download QR package** becomes available: a ZIP archive with one SVG per record under `qr/` and a `records.csv` with the columns `kind`, `name`, `reference`, `public_record_link`, `qr_file` — the input for label printing or artwork.
The QR package is **re-resolved at download time**. A record revoked after the run, or one whose target was deleted, is not in the ZIP.
## Adding evidence later
From the Documents area you can attach selected evidence to **several** records at once: **Add to public record** → "Choose the packaging units or components that should receive the selected evidence".
Where an active record already exists, the evidence is **appended** ("This will append the evidence to the active record."); where none exists yet, one is **created** ("This will create a public record containing the selected evidence."). If the evidence is already included, Polygon One reports "No changes were made because the selected evidence is already included." Documents in your selection that cannot be published are reported up front ("3 of them can't be published.").
## Sharing by email
**Email** opens **Email the public record**. Enter a recipient address and send with **Send email**. There is no bulk email.
The email contains **only the canonical link** — **"Only the canonical link will be sent."** No documents are attached. The recipient needs no account; whoever forwards the link forwards the access.
## Updating, revoking, republishing
**Updating.** Use **Manage** to change the selection and save with **Update record**. The **link and QR code stay the same** — printed labels keep working. The evidence selection is set to exactly the new state: anything you untick stops being retrievable immediately.
**Revoking.** **Revoke** asks "Revoke this public record?" — "The link will stop working immediately." After that, visitors only see **Record unavailable** with the text "This record is no longer available."; the document endpoints answer with 404.
**Revoking is permanent, and republishing creates a NEW link with a NEW QR code.** The old QR code on packaging already printed is dead for good. If you only want to change **what** is visible, use **Manage** — not revoke-and-republish.
Deleting the packaging unit or component also switches the public page off.
## Security and privacy
* **The page is reachable without signing in.** The link is the access control; whoever holds it sees the released contents.
* **Search engines are excluded** (`noindex`, `nofollow`), and the page passes on no referrer information.
* **The page shows only** the company logo and company name, the target's name/reference/type, the date of the last release change, the currency status, the manufacturer identity (where applicable and complete), and the links to the released documents and evidence.
* **The display language follows the visitor**, not you. The **documents themselves** stay in the language they were generated or uploaded in.
## Permissions
Publishing, updating, revoking and sending the email require the permission to **manage packaging**; downloading the QR package needs read access only. The public page itself needs no permission.
The document the record publishes — including the manufacturer identity from the PPWR settings.