Three dates that don't move
PPWR is Regulation (EU) 2025/40. It's directly applicable across all 27 Member States — no national transposition, no carve-outs, no grace period. The dates below are written into the regulation itself.
PPWR replaced Directive 94/62/EC. The law has been on the books for 15 months. The transition window closes August.
Core obligations apply. Design, sustainability, labelling, documentation, market surveillance. Hard deadline. No grace period.
Binding reuse targets. 100% of intra-EU B2B transport packaging must run in a reuse system. Beverage 10%. Transport 40%. Structural mandate, not aspiration.
|Procimo TechFour obligations, three months out
PPWR's enforcement model rests on four pressures. Each one is a deadline-driven test. The system most operators have today fails each of them.
Market Surveillance Authorities can demand evidence of conformity from any operator, electronically, with a 10-day response window. From 12 August 2026.
Non-compliant packaging cannot be placed on the EU market. Already-shelved stock can be ordered withdrawn or recalled. "No compliance, no market."
100% of intra-EU B2B transport packaging must run in a reuse system. 40% of all transport packaging. 10% of beverage. From 1 January 2030.
PPWR mandates effective, proportionate, and dissuasive penalties. Each Member State sets its own scale. Fines, sales bans, withdrawals, recalls.
|Procimo TechMost of your industry isn't ready
PPWR is a data and documentation challenge before it's a sustainability challenge. The trade press, law firms, and consultancies all say the same thing: the buyers we talk to don't have the operational data PPWR demands. The numbers below are public.
Source: Greenberg Traurig PPWR readiness review, 2025
Source: Pacoon PPWR digital-readiness survey, DACH region
Source: FMCG manufacturer survey (n=220), 2025
|Procimo TechFour questions your ERP can't answer
When the authority asks about your IBCs, four questions land on the desk. The ERP record, the deposit ledger, the customer phone number — none of them produce per-asset cycle data.
The authority will ask for the chain of custody on a specific IBC. Where it filled, when it shipped, which customer site, when it returned. The ERP doesn't track motion.
Industrial reuse rates submitted to Member State authorities have to be backed by per-asset evidence. Estimates from sales flows won't pass.
Filled IBCs sit on customer sites long after the product is consumed. Without dwell data, you can't trigger collection or recover the asset.
|Procimo TechThe data layer PPWR was written for
Procimo RTLS produces the per-IBC, per-cycle, per-customer data PPWR demands. Hardware-independent, hazmat-tolerant, customer-site capable. Per route, per filling plant, per customer.
Every IBC and pallet. UWB at the fill plant, GPS through transport, BLE on customer sites where allowed, RFID at return reception.
Round-trip per asset, dwell per customer, write-off rate, peak vs. installed fleet. The KPIs that move B2B economics.
Industrial reuse rate, asset-level history per batch, customer-level return rate. Regulator-ready, billing-ready, audit-ready.
Per-asset chain of custody. Hazmat-grade audit trail. PPWR-ready and DPP-compatible data structure.
|Procimo TechYou're not losing IBCs. You're renting them.
The financial impact takes three numbers from your operation. Fleet size, write-off rate, replacement cost per unit. The structure runs in front of you, on your data.
Recovered with RTLS = the share of that loss tied to dormancy and missing returns, plus the pool reduction from cycle compression. The exact recovery rate depends on your operation.
Fleet × write-off × cost = the line item the business absorbs every year for IBCs sitting dormant on customer sites. Bring those three numbers to the next meeting and we run it live.
|Procimo TechAn ERP record isn't a location
Every chemicals and lubricants operator has an ERP record per IBC, a deposit ledger, and a phone number for the customer. None of those tell you where a specific IBC is sitting on a customer site, or for how long. The 58% of DACH companies admitting their data systems are unprepared know that already.
What real-time location adds that an ERP doesn't
- Per-IBC chain of custody — fill, dispatch, customer arrival, return
- Dwell visibility per customer, with auto-trigger collection routes
- Hazmat-grade audit trail, fillable into your existing QHSE process
- Working capital recovery: every dormant unit becomes a recoverable asset
- Hardware-independent: GPS, BLE, RFID, UWB — survives the filling plant and the road
|Procimo TechPPWR-data-ready before the deadline
Pick the product line with the worst return rate, instrument it end-to-end, prove the math on your data, then scale across the fleet.
One filling plant, one product line
Pick the line with the highest write-off or the longest customer dwell. Tag spec, protocol, KPI targets agreed up front.
Tags live at fill plant and return reception
RTLS infrastructure operational. Per-IBC cycle data flowing in week 4. First customer-dwell reading by week 6.
ERP, QHSE, customer SLAs
Data into the systems the operation already uses. Customer dashboards. Excess-dwell rules wired in.
Industrial reuse rate reportable
Reuse-rate export tested. Chain-of-custody documentation formatted for Member State submission. Ready for 12 August 2026.
|Procimo Tech