What's new in DPP.GS: Versioning, packaging DoCs, audit log & more
The last few weeks brought the biggest change to how a Digital Product Passport evolves over time — plus per-layer packaging declarations, a full activity log, simpler onboarding, and billing. Here's a tour of what you can use today.
Headline feature🔖 DPP Versioning — a passport that holds up over time
A Digital Product Passport is not a static web page — it's a legal record that a product met specific requirements at the time it was placed on the market. Regulations expect that record to be reproducible for years, even after you've improved the product and changed the data. That's temporal integrity, and it's now built into DPP.GS — for every product, in every sector, not just one industry.
Why it matters
- Reproducibility. A unit made in January should always resolve to the passport that was valid in January — not to whatever you edited last week.
- Proof, not claims. Each published version is cryptographically signed, so anyone can verify it is authentic and unchanged — without logging in, without trusting our server.
- Confidence to edit. Your working data stays editable; the public record only changes when you deliberately publish.
How it works
When your product data is ready, you click Publish version. DPP.GS freezes the complete passport into an immutable, signed snapshot with a validity date, and the public viewer serves that version from then on. Until you publish, the viewer shows your live data exactly as before — nothing changes for existing products until you opt in.
What you get with each version
- A tamper-proof record. Each published version is locked and digitally signed, so it can't be quietly changed later.
- Valid-from / valid-to dates. Every version knows the period it applied to, so a passport can always be seen exactly as it was on a given date.
- A version history anyone can browse. The public passport shows a discreet "Version history" — open an earlier version and jump back to the current one in a click.
- One-click authenticity check. A 🔏 badge confirms a version is genuine and unchanged — no login, no setup.
Built for real workflows
- Publish is a deliberate step. It lives on its own Version tab and a Publish button next to Save. Your edits are saved automatically before publishing, and you're asked to confirm before anything goes public.
- No accidental duplicates. If nothing changed since the last version, publishing is refused — you won't stack identical records.
- Draft vs published at a glance. While editing you can see whether the public passport matches your current data ("you have unpublished changes").
- See exactly what changed. A field-level diff between versions shows added, removed and changed values — including substances, materials and packaging.
📦 Packaging layers + a Declaration of Conformity per layer
Real packaging is layered — a primary wrapper, a secondary carton, a tertiary pallet — and under Regulation (EU) 2025/40 (PPWR, Art. 12) each layer carries its own obligations. DPP.GS now models packaging as individual layers (up to five), each with its material composition, weight, recyclability and recycled content.
- A DoC for each layer. Generate and archive an EU Declaration of Conformity per packaging layer — not just one blanket document for the product.
- Pull data from a linked DPP. If a packaging component already has its own passport, pull its data in by GTIN instead of retyping it.
- Shareable DoC links. Every archived DoC gets a stable link (
dpp.gs/doc/…) you can send to partners or authorities, grouped by carrier product vs. packaging layer.
🪪 Register without a GS1 Company Prefix
DPP.GS is identifier-agnostic — a passport can be keyed by a GS1 GTIN, but also by EPC, UUID, DID or an MA-DPP code. Requiring a GS1 Company Prefix at sign-up was an unnecessary barrier, so it's gone.
- No GS1 prefix needed to create an account or your first passport.
- If you do use GS1, you can still add it later; when provided, its format is validated.
- Faster path from sign-up to a live passport, whatever identifier scheme you use.
📝 Audit log — the "Activity" tab
Compliance data needs a paper trail. Every product now has an Activity tab that records who changed what, and when — down to the individual field.
- Field-level history — old value → new value, including sub-tables like substances, materials and packaging layers.
- Full coverage — product create/update/delete, DoC generation and document uploads are all captured.
- Readable — values shown cleanly (weights in grams, no raw JSON); a no-op save isn't logged as a change.
It's also the foundation the versioning feature above is built on — change capture first, then signed point-in-time records.
🧾 Billing details & invoices
Managing your subscription is now self-service inside the dashboard, under Billing.
- Billing details — company name, address and VAT ID in one place.
- Automatic VAT validation — EU VAT IDs are checked against VIES; checkout is gated until your billing details are complete.
- Invoices — your invoices are listed and downloadable, synced from Stripe.
Try it on your own products
Create a passport, publish a signed version, and share it — free to start.
Start free →