EU PACKAGING · EPR DATA
PPWR Packaging.
Figures you can defend.
- Who it helps
- Merchants who register and report packaging in the EU.
- What changes
- Packaging data moves from spreadsheets into Magento, with a ledger that produces figures a person can file.
- Versioned packaging records with an approval workflow
- Bitemporal product assignments with CSV import
- Parcels captured per shipment, exceptions in a queue
Keep packaging data, shipped weights and claim evidence in Magento, in a ledger that produces figures a person can file. It does not file returns for you.
8.1–8.5
PHP
2.4.8
Magento Open Source
2.2.x
Mage-OS
1.3+
Hyvä
v 1.0.0 — RELEASED 1 month ago
composer require qoliber/ppwr
Product details
Move packaging data out of spreadsheets and into Magento.
Packaging reporting needs weights per material for what you actually shipped, and evidence behind every claim. In a spreadsheet, that record is hard to reconstruct months later. Regulation (EU) 2025/40, the Packaging and Packaging Waste Regulation, has applied since 12 August 2026.
This extension keeps your packaging data in Magento: what each pack is made of, which products use it, what went out with every parcel, and the evidence behind each claim. Every shipment appends to a ledger that is never edited or deleted, so a person can file a figure and defend it later.
Please read this first. This extension does not file your EPR return. It has no connection to any national scheme and ships no verified country adapter. It is a system of record, not a conformity implementation of the regulation, and no claim of legal compliance is made. Whether you are an importer or a distributor, and what a scheme requires of you, are questions for you and your adviser.
Who it is for
- EU merchants who register and report packaging in one or more Member States and need the weights per material an EPR return asks for.
- Non-EU sellers shipping into the EU who need the same figures.
- Merchants who also sell outside Magento, through ERP orders, offline sales, samples or replacements, since packaging placed through any channel counts toward the same filing.
- Stores making recyclability or compostability claims on product pages, which from 27 September 2026 must be substantiated under Directive (EU) 2024/825.
From a pack to a figure you can file
- Set up the company that files. Complete the legal entity, its roles per jurisdiction and its market scopes.
- Record your packaging. Quick Create takes a name, level, format and a row per component. Revisions are immutable, and approval refuses incomplete records.
- Assign it to products. Use CSV import, which reports every failed row instead of aborting the file, or SKU assignments over REST.
- Capture what shipped. Record parcels and packaging on the shipment. A shipment whose packaging cannot be resolved becomes a visible compliance exception, never a zero-weight row.
- Generate a report run. For a market and period you get a CSV with kilograms per material, and its header records how it was produced. Every total links through to the ledger entries behind it.
- File it yourself. A person transcribes the figures into the scheme's own portal.
Also included
- A product-page block on Luma and Hyvä showing composition and mass by material.
- Claims that render only when their declaration is on file. Remove the evidence and the claim disappears.
- Declarations stored outside the web root, behind their own permission.
- Ingestion of external movements, so packaging placed outside Magento reaches the same ledger.
- 27 REST endpoints, each behind its own ACL resource.
Requirements
| PHP | 8.1 to 8.5 |
|---|---|
| Platform | Magento Open Source 2.4.8 or Mage-OS 2.2.x (magento/framework ^103.0) |
| Cron | Required for ledger recognition. No message queue, MSI or specific WMS is needed. |
| Hyvä (optional) | qoliber/ppwr-hyva, on Hyvä 1.3 (Tailwind 3) or 1.4+ (Tailwind 4) |
Limitations
- It does not file anything. There is no connection to any national scheme or registry.
- No verified country adapter ships, only a generic CSV export. Its
material_categorycodes are this extension's own taxonomy, and the shipped regulatory code lists are marked provisional. - Article 12 marks belong on the physical packaging. The product-page block is supplementary information.
- It will not decide your obligations.
FAQ
Does this make my store PPWR compliant?
No extension can promise that, and this one makes no such claim. It gives you a versioned record and reproducible figures that a person files by hand.
Which countries does it report for?
It ships a generic CSV export and no verified country adapter. You work with the figures per market and period, and transcribe them into the scheme's own portal.
Can a reported figure change later?
The ledger is never edited or deleted, and a report run is reproducible from its recorded cutoff, so last quarter's number still reconstructs as it was.
What if a shipment has no packaging assigned?
It becomes a compliance exception on a queue for a person to work. It is never recorded as a zero-weight row.
Does my packaging data leave the store?
No. Everything runs inside your Magento installation, and the extension connects to no external service.
WHAT IT FIXES
Packaging data, out of spreadsheets.
What each pack is made of, which products use it, what went out with every parcel and the evidence behind each claim stay versioned in Magento. Every shipment appends to a ledger that is never edited, so a person can file a figure and defend it later.
- Versioned packaging records with an approval workflow ● records
- Bitemporal product assignments with CSV import ● catalog
- Parcels captured per shipment, exceptions in a queue ● fulfillment
- Append-only placed-on-market ledger ● ledger
- Report runs reproducible from their recorded cutoff ● reporting
- Generic CSV only: a person files the return ● limit
INSTALL · COMPOSER
One metapackage, five modules.
No message queue, MSI or specific WMS is required, but cron is: it drives ledger recognition. The Hyvä package is separate, so Luma stores never carry it.
# Once per project: add your private qoliber repository # (the exact command is in your account → Composer & keys) composer require qoliber/ppwr # Hyvä storefronts: composer require qoliber/ppwr-hyva php bin/magento setup:upgrade ✓ Start by completing the declarant on Legal Entities.
FROM THE COMMUNITY
Customer reviews
Write a review
Write Your Own Review