On 12 August 2026, Regulation (EU) 2025/40 on packaging and packaging waste applies directly in every member state (European Commission). In integration projects this date rarely arrives as a legal question. It arrives as a data question: whoever first makes packaging available in a member state has to know what material it consists of, how much each material fraction weighs, which packaging level it belongs to and how many units actually left the warehouse during the reporting period. Those fields are missing from most item master records. What is there instead is a gross weight, a net weight and, with luck, a box size in a free-text field. This article therefore treats the regulation consistently as a modelling task: how a packaging master record is created alongside the item, where the volumes really come from, and how a reporting output is built from shipment and returns data instead of being estimated once a year.
What actually applies on 12 August 2026
The regulation was adopted on 19 December 2024 and published in the Official Journal of the European Union on 22 January 2025 (Regulation (EU) 2025/40, EUR-Lex). It entered into force on 11 February 2025 and applies from 12 August 2026 (European Commission). It replaces the Packaging Directive 94/62/EC (Regulation (EU) 2025/40, EUR-Lex). The change of legal instrument is the real difference: a directive had to be translated into national law by each member state, a regulation takes effect directly. In Germany, the Packaging Act is being replaced by a packaging law implementation act that is currently going through the legislative process (Zentrale Stelle Verpackungsregister).
For planning a data project, one sentence from the German packaging register authority matters most: there is no transition period, and without system participation adjusted in time, affected packaged products face a distribution ban from 12 August 2026 (Zentrale Stelle Verpackungsregister). A data model that is only finished in autumn 2026 is therefore not a late project, it is a distribution risk. Anyone planning today still has roughly twelve months for modelling, data collection, migration and a test run covering at least one full quarter.
The scale of the topic can be quantified. In 2022, 186.5 kg of packaging waste was generated per person in the EU, and around 40 percent of the plastics used in the EU go into packaging (European Commission). In Germany, 17.9 million tonnes of packaging waste arose in 2023, of which 69.4 percent was recycled and 97.1 percent recovered (German Environment Agency). 47.0 percent of all packaging waste came from private end consumption (German Environment Agency) -- precisely the segment an online shop serves. That explains why the regulation addresses the data path from item master to shipping box so closely.
| Date | What takes effect | Data consequence |
|---|---|---|
| 11 Feb 2025 | Regulation (EU) 2025/40 enters into force | Lead time for modelling and data collection |
| 12 Aug 2026 | Date of application in all member states | Packaging master data and volume logic must be in production |
| 15 May, annually | Declaration of completeness for the previous year, audited by a registered auditor | Volumes must be derived and evidenced in an auditable way |
| by 2029 | Deposit return schemes for single-use beverage packaging in member states | Additional per-item attributes per target market |
| from 2030 | Empty space ratio capped at 50 percent for grouped, transport and e-commerce packaging | Box dimensions and fill levels become reportable master data |
| from 2030 | 70 percent recycling rate for packaging waste overall | Material fractions must be reported cleanly separated |
| 2030 to 2040 | Reuse targets, among them 40 percent for transport packaging by 2030 and 70 percent by 2040 | Reusable cycles need their own stock accounting |
The regulation's calendar is not the calendar for your data model
Two roles, two data obligations
The regulation introduces a separation of roles that the German wording renders as Erzeuger and Hersteller. Under Art. 3(1)(13) PPWR, the manufacturer is any natural or legal person that produces packaging or a packaged product itself, or has it designed or produced under its own name or brand (Zentrale Stelle Verpackungsregister). Under Art. 3(1)(15) PPWR, the producer is whoever -- as manufacturer, importer or distributor -- first makes packaging available in the member state where it becomes waste (Zentrale Stelle Verpackungsregister). The manufacturer is responsible for product conformity and packaging design; the producer is responsible for registration in the LUCID packaging register, for financing disposal through extended producer responsibility, for the system participation contract and for data reporting (Zentrale Stelle Verpackungsregister).
Manufacturer: product compliance
Responsible for composition and design of the packaging. The information needed for this -- material type, layer structure, weight per fraction -- originates in development and purchasing and has to flow from there into the master data process.
Producer: registration and reporting
Registers in the LUCID packaging register, signs the system participation contract and reports volumes. This role needs no design data, but reliable consumption volumes per material fraction and period.
Labelling: the second stage
The harmonised labelling requirements are being specified by the Commission through secondary legal acts, subject to deadlines of 18 to 24 months (Zentrale Stelle Verpackungsregister). Data obligation and label design are therefore decoupled.
This split has consequences for retailers. With private labels, the brand establishes that the retail company is the manufacturer of the packaged products; with imports without a domestic intermediary, extended producer responsibility likewise sits with the domestic retail company (Zentrale Stelle Verpackungsregister). Service packaging shifts too: the option of discharging the obligations by buying pre-participated service packaging largely disappears. An exception applies where the supplier is based in the same member state and the purchasing company has fewer than 10 employees and at most 2 million euros in annual turnover (Zentrale Stelle Verpackungsregister).
The first concrete task is a supplier enquiry
The packaging master record as its own entity
The most common modelling mistake is to attach packaging attributes to the item as extra fields. That works for the grouped packaging of a single item and breaks for everything else. Packaging is an object in its own right with its own lifecycle: a size M shipping box is used for hundreds of items, one item ships in different boxes depending on order quantity, and the same folding carton can serve as the sales packaging of one item and as the grouped packaging of a bundle. The packaging master record therefore belongs next to the item as a separate entity, with an n:m relationship between the two.
- Packaging ID and a meaningful description, independent of the item number
- Packaging level: sales, grouped or transport packaging -- a mandatory field, not a comment
- Material fractions as line items: material type and weight in grams per fraction, not one total weight
- Target market and legal jurisdiction, so the same box can be reported differently per country
- Manufacturer details: who designs or commissions the packaging, including the brand reference
- Reusable flag with a cycle counter, kept separate from single-use packaging
- Validity period per packaging version, so a material change does not overwrite history
- Source and verification date of the data, so supplier statements and own measurements stay distinguishable
Two objects are regularly forgotten in practice. First, the shipping box itself: it is not an attribute of an order but a consumable item with its own item number, its own purchasing, its own stock and its own packaging master record. If it is not managed as an item, its consumption cannot be posted and has to be estimated later. Second, the filling material: paper cushioning, air pillows and tape cannot sensibly be weighed per shipment, but they can be modelled through a flat rate per box type -- for example as a stored grammage per box size, verified once a year through a sample. The same approach applies to pallet film and strapping in drop-shipping.
Gross weight is not a packaging figure
Where the volumes come from: shipping, not purchasing
The second typical mistake concerns volume logic. Volumes subject to system participation do not arise when boxes are purchased, but when packaging is first made available -- in practice, at shipping. Anyone reporting the purchase volume from the box supplier is reporting a stock receipt, not consumption. With a single annual purchase in December, that shifts the entire volume into the wrong period. The reliable source is therefore the combination of order and delivery note data: the shop supplies the order structure, the ERP or shipping software supplies the box size actually used and the shipping date.
That puts the packing process at the centre. If the packing station does not capture the chosen box type, the single most important figure in the whole model does not exist. Three routes lead to the goal: the packing software writes the box type back into the delivery note record, a box selection algorithm in the ERP derives it deterministically from volume and weight, or the shipping method determines it through a fixed assignment. The first route is the most accurate, the second the easiest to maintain. What counts in every case: the assignment has to be stored with the shipping document, not merely exist at runtime. How shipping data flows cleanly back into the ERP is described in the article on shipping and logistics interfaces.
- Delivery note or shipping document supplies date, destination country and consignment number
- Shipment lines supply items and quantities, resolved down to individual items
- Packaging assignment supplies sales and grouped packaging per line, and the shipping box per consignment
- Packaging master record supplies the material fractions with weights per packaging
- Filling material flat rates add the volumes that are not measured per shipment
- Returns reduce the volume in the correct period, provided the packaging actually comes back
- Aggregation per material fraction, target market and quarter produces the reporting output
The question in a project is rarely: which packaging do we use? It is: how often did we use which packaging in the third quarter -- and how do we know?
The middleware pattern for the reporting output
Architecturally the task is pleasantly well bounded, because it does not have to run in real time. The packaging master record is kept where master data ownership sits -- in the inventory management system or the product information system. The middleware reads it, joins it with transaction data from shop and shipping, and derives periodic aggregates. Unlike stock levels or prices, there is no reason for second-by-second synchronisation: a nightly run with a restart point is sufficient, as long as it is traceable and can be repeated any number of times. What role a middleware plays compared with direct point-to-point coupling is set out on our middleware page.
Own the master data, do not copy it
The packaging master record gets exactly one leading system. Everything else reads. If shop, shipping software and spreadsheet each maintain their own weights, there are three truths and no defensible report. The ground rules are in the article on master data synchronisation.
Aggregate periodically, recalculate idempotently
Every run writes one aggregate per material fraction, target market and period -- reproducible from the raw data. If a shipping document is corrected afterwards, the period is recalculated rather than adjusted by hand.
Store evidence in an audit-proof way
Every reported value needs a storable record with timestamp, data status and calculation logic. That makes a report reconstructable years later -- the same requirement that GoBD process documentation places on accounting data.
Make the report visible before reporting
The quarterly report belongs in the back office, not in an export directory. Anyone who can see deviations from the previous quarter finds data gaps before the report goes out, not afterwards.
The bridge to accounting is not an afterthought here. The declaration of completeness has to be submitted annually by 15 May for the previous year and audited by an auditor registered with the German packaging register authority (Zentrale Stelle Verpackungsregister). An auditor will not read the source code of the aggregation but will want to follow how delivery notes and packaging master data turned into a number. That is exactly why the report needs the same documentation quality as an accounting flow: defined data source, defined cut-off date, defined rounding, traceable corrections. Anyone building those blocks for an inventory system shop integration anyway gets the reporting output as a by-product.
Typical pitfalls in the volume model
Most deviations between reported and actual volumes are not caused by wrong weights but by wrongly delimited cases. Six of them show up in almost every project.
| Pitfall | Why the figure tips over | Data-side solution |
|---|---|---|
| Marketplace sales | Depending on the constellation, the marketplace operator or the merchant carries the producer obligation -- the assignment decides the reported volume | Sales channel as a mandatory field on the order, reporting logic parameterisable per channel |
| Cross-border shipping | Reporting happens in the member state where the packaging becomes waste -- the destination country, not the dispatch location | Derive the destination country from the delivery address and aggregate separately per country |
| Sets and bundles | A set has its own grouped packaging, and the individual items bring their own sales packaging | Resolve the set bill of materials down to individual items and total packaging per level |
| Returns | Returned goods only reduce the volume if the packaging actually comes back and is reused | Return as a negative volume with its own flag, kept separate from new shipments |
| Drop-shipping | The supplier packs and the goods do not pass through your own warehouse at all -- yet the obligation can still sit with the merchant | Flag drop-ship orders separately and request packaging data from the supplier |
| Cut-off logic | Invoice date and shipping date diverge, particularly around the turn of the year | Fix the shipping date as the cut-off and document it in the process description |
Cross-border shipping deserves particular attention because it multiplies the effort. The competent authorities and organisations formed the European National Registers network in September 2024, currently comprising bodies from 16 European member states (Zentrale Stelle Verpackungsregister). The network works towards a consistent interpretation of extended producer responsibility -- but the registers remain national for now. A shop delivering to six countries needs six registrations, six reporting logics and six deadline calendars. The data model therefore has to carry the target market as a dimension from the start, not as a later add-on. How a middleware cleanly separates channels and jurisdictions is shown in the article on marketplace integration via middleware.
Returns are the most popular calculation error
Data quality in the item creation workflow
A packaging master record ages faster than it is maintained. The reason is mundane: new items are created every day, packaging data is rarely fully available at creation time, and without a mandatory-field check the item goes into the shop anyway. Two years later, exactly the information the reporting output needs is missing for a relevant share of the assortment. What works is therefore only a check at the point where the record is created -- not a clean-up run in spring.
- Mandatory-field check in the creation workflow: no release status without an assigned packaging carrying at least one material fraction
- Weight plausibility check: the sum of packaging fractions must be smaller than the difference between gross and net weight, otherwise a warning
- Range check per material type: catch unrealistic grammages before they flow into a report
- Mandatory packaging level, so sales, grouped and transport packaging do not get mixed up
- Report of incomplete packaging master records, sorted by sales volume of the last period
- Due date per supplier statement, so figures are re-confirmed after a material change
- Change log per packaging version with user, timestamp and previous value
The report of incomplete packaging master records is the single most effective instrument here, provided it sorts by sales volume. A gap on an item with three sales a year is a footnote; the same gap on a bestseller distorts the entire report. The same prioritisation logic is advisable for the supplier enquiry: rather than requesting the full assortment at once, order items by volume contribution and clear the top percentiles first. Building such a data pipeline differs little technically from a PIM integration for product data -- except that the consumer here is not a product page but a reporting output.
Packaging data is the second run at the same problem
From estimate to defensible report
The path there is plannable in four steps. First the packaging master record is modelled in the inventory management or ERP system, including material fractions, packaging level and target market. Then the missing fields are added through the existing interface instead of opening a second data store -- the shop supplies order structure and destination country, the ERP the packaging assignment. Next comes the periodic aggregation from shipment and returns data, with a stored record per reported value. Finally the quality checks go into the creation workflow so the model does not drift apart again. For the integration itself we use the existing routes: inventory system shop integration, JTL ERP integration, or dedicated API development where the leading system brings no suitable interface.
Two neighbouring obligations are worth planning together, because they touch the same document data. The customs data obligations arising from the EU customs reform also draw on order and shipment lines -- the article on the 2026 customs reform and customs data from the ERP describes the overlapping fields. And the technical foundation has to hold: when TLS certificate lifetimes shrink, every automated reporting route is affected, as the article on TLS certificates with 200-day lifetimes shows. An overview of the building blocks we use is given by our integration services; for multi-channel scenarios, marketplace integration adds the channel separation.
The difference between a spreadsheet estimate in spring and an automated quarterly report is not primarily the effort. It is whether you can explain a reported figure afterwards. If you would like to know how far your current data situation is from a defensible packaging report, we will look at item master, shipping process and interfaces together in a personal conversation.
Sources and studies