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

# Volume Reporting

> Capture the volumes placed on the market per material type and generate a validated XML file for the LUCID data report

## Overview

Under **Packaging → Volume reporting** (`/packaging/mengenmeldung`) you capture the **volumes placed on the market** per reporting year and market, and generate a **validated XML file for the LUCID data report** from them.

<Warning>
  This tool **generates** a validated XML file from your master data. It **submits nothing**: you upload the file yourself in the LUCID Packaging Register under "Datenmeldung". Filing the data report is legally non-delegable (VerpackDG §5(1) S.2).
</Warning>

<Info>
  Only the **Germany (LUCID)** market is currently supported for the XML export. Other markets are not yet selectable.
</Info>

## Capturing volumes

Capture is per reporting year (**Reporting year**) and **market**. In the **Volumes placed on the market** table, you enter, per packaging unit, the number of **units** placed on the market in the reporting year.

<Frame caption="Capturing the volumes placed on the market per packaging unit">
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/polygonone/images/ppwr/epr/mengenmeldung-mengen.png" />
</Frame>

<Info>
  **Blank does not mean 0.** An empty field means "un-entered" — the unit is not part of the report. An explicit **0** means "no volume placed" and counts with zero weight.
</Info>

Polygon One can derive a **suggestion** for the units from your linked order positions. A suggestion is never applied automatically — you apply it deliberately via **Apply** (or **Fill {count} empty rows**). Applied values are marked with the **derived** badge; a manual entry overrides this.

### What is computed and what is entered

| Entered (by you)                             | Computed (by the platform)                                                        |
| -------------------------------------------- | --------------------------------------------------------------------------------- |
| Units per packaging, year and market         | Mass per component = component weight × quantity in the bill of materials × units |
| Direct volumes per material type (overrides) | Aggregated mass per ZSVR material type                                            |
| System operator ID, report type              | Total volume and data-quality notes                                               |

In the **Preview per material type** you see how the reported volumes are computed; expand a row to see the per-unit derivation (`{grams} g × {quantity} × {units} = {kg}`).

### Direct volumes per material type (overrides)

Under **Direct volumes per material type** you enter a volume in **kilograms** directly for a ZSVR material type. Such a value **replaces** the derived volume for that material type (it never sums) and covers cases the model splits more coarsely (metal → ferrous/aluminium; composite → beverage carton/other composite packaging).

### ZSVR material types

Volumes are reported in eight ZSVR material types:

| Code  | Material type             |
| ----- | ------------------------- |
| 10000 | Glass                     |
| 20000 | Paper, cardboard, carton  |
| 30000 | Ferrous metals            |
| 40000 | Aluminium                 |
| 50000 | Plastics                  |
| 60000 | Beverage cartons          |
| 70000 | Other composite packaging |
| 80000 | Other materials           |

### Data quality

If a volume cannot be unambiguously assigned to a material type, Polygon One reports this under **Cannot report – data quality** — e.g. when a component has no mass, a material is not clearly derivable (metal/composite), or a component lists several materials. Mass is **never** silently dropped; every gram must land in exactly one material type or be entered directly.

## Completeness declaration — thresholds

Above certain annual volumes, an audited **completeness declaration** (Vollständigkeitserklärung) is additionally due via LUCID. Volume reporting evaluates your captured volumes and shows a notice banner as soon as a threshold is likely exceeded.

<Frame caption="Preview per material type with the completeness-declaration banner">
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/polygonone/images/ppwr/epr/mengenmeldung-vorschau.png" />
</Frame>

| Material group            | Threshold per year |
| ------------------------- | ------------------ |
| **Glass**                 | ≥ 80 t             |
| **Paper/cardboard**       | ≥ 50 t             |
| **Lightweight packaging** | ≥ 30 t             |

The banner **"Completeness declaration likely required"** lists the affected groups and points out the deadline: the audited completeness declaration is likely due via LUCID **by 15 May**.

<Info>
  The banner is a **heads-up, not a verdict** — verify against your actual placed-on-market volumes. The completeness declaration itself is **not** generated here.
</Info>

## Generating the validated XML file

<Steps>
  <Step title="Enter the system operator ID and report type">
    In the **Generate file** section, enter the **System operator ID (SystemOperatorID)** of the dual system (format: 2 letters + 13 digits, e.g. `DE0000000000000`) and the **report type**.
  </Step>

  <Step title="Generate the XML">
    Click **"Generate XML"**. The file is validated against the official ZSVR schema (XSD). Regenerating replaces the previous active version.

    <Frame caption="Generating the validated LUCID data report as XML">
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/polygonone/images/ppwr/epr/mengenmeldung-erzeugen.png" />
    </Frame>
  </Step>

  <Step title="Download and upload">
    Download the file under **Generated reports** via **"Download XML"** and upload it in the LUCID Packaging Register under "Datenmeldung". **"Open LUCID"** takes you straight there.
  </Step>
</Steps>

Under **Generated reports** you see all generated files with year, report type, status (**active** / **superseded**), version, system operator and generation date.

<Card title="EPR Registration" icon="id-card" href="/en/ppwr/epr/registrierung">
  Register first: determine which member states require producer registration.
</Card>