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 order system can't answer
When the surveillance authority asks about your kegs, four questions land on your desk. The order system, the deposit ledger, the dock scans — none of them produce the data those questions need.
Authorities will ask for the cycle history of specific kegs. Where it filled, when it shipped, when it came back. Not aggregate flows. The actual record.
The reuse rate the brewery submits to its Member State has to be backed by asset-level evidence. Invoice-derived estimates don't survive an audit.
Empty kegs sit in cellars long after they should have come back. Without per-asset dwell data, you can't trigger collections, can't enforce SLAs, can't bill the cost back.
|Procimo TechThe data layer PPWR was written for
Procimo RTLS produces the per-keg, per-cycle, per-cellar data PPWR demands. Hardware-independent, brewery-tolerant, distribution-ready. Per route, per partner, per cycle.
Every keg and crate. UWB at the brewery, BLE through DCs, GPS on trucks, RFID at HoReCa returns. Whatever the route demands.
Round-trip per asset, dwell per cellar, dormancy by partner, peak vs. fleet size. The KPIs that drive returns and feed reporting.
Beverage reuse rate, placed-on-market by SKU, returned-vs-shipped per partner. Generated, not assembled at year-end.
Per-keg history. Each cycle, each cellar, each return event. Audit-grade documentation, queryable in minutes.
|Procimo TechYou're not losing kegs. You're renting them.
The financial impact takes three numbers from your operation. Fleet size, shrinkage rate, replacement cost. 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 × shrinkage × cost = the cheque the brewery writes every year for kegs that didn't come back. Bring those three numbers to the next meeting and we run it live.
|Procimo TechA deposit ledger isn't an audit trail
Every brewer has an order system, a deposit ledger, and a few dock scans. None of them tell you where a specific keg is right now, or how long it's been in cellar 23. The 58% of DACH companies admitting their data systems are unprepared know that already. RTLS is what fills the gap.
What real-time location adds that an order system doesn't
- Per-keg cycle history — fill, dispatch, cellar arrival, return
- Dwell visibility per HoReCa partner, with auto-trigger collection routes
- Beverage reuse rate generated from the data, not estimated
- Audit-grade chain of custody, PPWR-ready and DPP-compatible
- Hardware-independent: BLE, RFID, GPS, UWB — whatever the route demands
|Procimo TechPPWR-data-ready before the deadline
Pick the route with the worst loss rate or the highest HoReCa exposure. Tag a sub-pool. Prove the math on your data. Twelve weeks from kickoff to a defensible audit response.
One brewery, one DC, one HoReCa cluster
Pick the route that hurts most. Tag spec, protocol, KPI targets agreed up front. Loss-rate baseline locked.
Tag-write at fill, tag-read at return
RTLS at the brewery and DC. Per-keg cycle data flowing in week 4. First dwell-per-cellar reading by week 6.
Order system, billing, partner SLAs
Data into the systems the brewery already uses. Partner-level dashboards. Excess-dwell rules wired in.
Beverage reuse rate reportable
Reuse-rate export tested. Documentation formatted for Member State submission. Ready for 12 August 2026.
|Procimo Tech