EU Regulation 2025/40

Packaging Digital Passport

Preparing for the EU Packaging Regulation (PPWR)

The EU Packaging Regulation has applied since 12 August 2026 — is your packaging data ready?

What is PPWR?

The EU Regulation That Changes Everything

The Regulation has applied since 12 August 2026, but many of its requirements phase in later. Three that shape what packaging makers will need to document:

📦

Article 6

Recyclable packaging

All packaging placed on the EU market must be recyclable — a general requirement since 12 August 2026. Recyclability grades (A/B/C) apply from 2030 at the earliest, once the Commission sets the assessment method.

🔖

Article 7

Minimum recycled content in plastic packaging

Plastic parts of packaging must contain a minimum share of post-consumer recycled content, from 2030 at the earliest (with exemptions).

📱

Article 12

Labelling

Packaging must carry a harmonised pictogram label on its material composition, from 12 August 2028 at the earliest. Exceptions: transport packaging other than e-commerce packaging, and packaging under a deposit and return system. A QR code may be added in addition to the label.

How It Works

From Factory to Compliance in 3 Steps

  1. 1📋

    Submit Compliance Data

    Upload material composition, recyclability data, and certifications.

  2. 2🔗

    Generate GS1 Digital Link

    Your product gets a unique, verifiable URL.

  3. 3✅

    Print & Verify

    QR code printed on packaging. Anyone can verify compliance instantly.

Privacy-first Verification

Zero-Knowledge Proof: Verify Without Exposing

We use Midnight blockchain ZK proofs to let regulators verify compliance without exposing your supplier details or trade secrets.

  • Tamper-proof records

    Every passport version is anchored on-chain. Records cannot be silently rewritten after publication.

  • Privacy-preserving verification

    Zero-knowledge proofs let regulators check compliance without seeing supplier names or formulations.

  • Regulator-ready audit trail

    A continuous, time-stamped trail from factory data to consumer scan — exportable on request.

Anti-greenwashing

How we block greenwashing我們如何擋住漂綠

Three independent layers — each closing a specific path a brand could otherwise take to make a passport claim it can't back up.

Layer 1 · B3

Certificate file integrity

Every cert PDF's SHA-256 fingerprint is anchored on-chain.

If a brand swaps the certificate file after publication, auditors detect the tamper immediately — not just metadata, but the full content fingerprint. Pre-publish guard rejects any cert whose stored file or hash is missing.

schema_version 4 · hex CHECK constraint at DB layer · 14-item test matrix

Layer 2 · B2

Forensic / audit split

Failed anchoring attempts never enter the public audit trail.

Successful attestations and failed attempts live in separate tables. Brands cannot fake a clean record by hiding failures — every attempt is recorded for authorized auditors, while the public-facing chain shows only confirmed anchors.

Defense-in-depth status filter across 5 read paths · forensic admin endpoint

Layer 3 · B4

Preview = on-chain

What you preview is byte-for-byte what gets anchored.

The passport UUID is reserved at preview time and re-used at commit. There is no preview-vs-commit drift: if a single field changed between Step 4 and Step 5, the commit returns 422 and the brand re-previews.

Reserved UUID · 5-condition 422 guard · 30 min TTL · 7-day forensic GC

Verify it yourself

Auditors run the check offline.

Every audit token issues a ZIP containing the canonical passport bytes, a filename manifest, every cited certificate file, and a stdlib-only Python script. No dependency on our servers. No vendor lock-in. If we disappear tomorrow, the audit trail still verifies.

  • canonical.json — the exact bytes hashed on chain
  • manifest.json — cert_id → filename mapping
  • certs/*.pdf — actual certificate files, content-hashed
  • verify.py — stdlib only, no pip install required
$ unzip ppwr-audit-bundle-*.zip
$ cd ppwr-audit-bundle-*
$ python3 verify.py

Bytes read:  4392
Expected:    9f3c1abe...8d24
Actual:      9f3c1abe...8d24

OK: 3 cert file(s) match recorded hashes
RESULT: PASS - canonical.json matches the recorded content fingerprint.
NOTE: This checks content integrity only. To confirm the on-chain
anchor, verify the transaction on a public Midnight blockchain
explorer (www.midnightexplorer.com).

Pricing Model

Compliance-as-a-Service

Setup

API integration & certification onboarding.

One-time engagement to connect your ERP, validate test data, and pass first-article review.

Per-Unit

Pay only for passports generated.

Volume-based metering aligned with SKU launch cycles. No idle subscription fees.

Annual

Data hosting & regulatory updates included.

Continuous regulation tracking, schema upgrades, and long-term passport storage.

Pricing based on volume. Contact us for a quote.

Contact

Get Started

Be among the first packaging makers to document their PPWR data with ConformPass.