Packaging register
Packregister keeps packaging components, attributes and bills of materials in one place — and syncs straight into the ERP and DWH you already run, without taking over your trade data.
CMP-0042
The data exists — it is just spread across places that were never meant to hold it, disagreeing with itself along the way.
Bottle 500 ml · Recycled content
3 answersSpreadsheets
Every department keeps its own Excel truth. Versions drift apart, and the evidence behind a value gets lost in mail threads.
ERP
Fields added to the ERP item master serve finance first. Packaging detail does not fit, so it ends up living somewhere else.
External registers
Every customer request and industry register wants its own format. The same component gets re-entered by hand, every time.
Data warehouse
Packaging facts stay in packaging tools. The BI report and the compliance dashboard run on a dataset that never heard of them.
Four steps, in order. Each one builds on the previous.
Upsert items and BOMs from your ERP or PIM by your own reference, or point an agent at it. No Packregister ids to look up first.
Add the attributes, certificates and evidence your reports need, once, against the reference you already have.
See what's missing and what's already covered, before a customer or auditor asks.
Pull it all back out through the same API, on your schedule, into Power BI, Fabric, or wherever you already report.
VRS packaging already defined the attributes, item types and which of them are mandatory. Import it once to set up your workspace in a click, and re-import when VRS publishes an update — anything you've customized by hand stays untouched.
VRS — Verpakkingsindicatoren · 2026.09.05
Click through the sidebar below the way you would in the app itself — five screens, the same data underneath.
128
Items
94%
Compliant
3
Open issues
Compliance trend
Write to enrich, read to sync downstream — incremental, no full re-export.
All of these point to the same component in Packregister.
Your systems each have their own code for the same bottle. Packregister keeps the references side by side — correct once, enrich everywhere. No re-import needed.
Your ERP or PIM stays the source of truth for the item. Link it to Packregister once by its own external reference, then create and update it — including its compliance attributes — through the same API. No Packregister ids to look up, no migration project.
Invite a supplier or customer workspace once, and shared items stay live — no more re-keying a spec sheet you were emailed. Sharing a sector package like VRS gives both sides the same attribute schema, so values map onto yours automatically instead of landing as text to reinterpret by hand.
Untouched fields follow your supplier automatically. Edit one yourself and it's yours — later supplier changes show up as an update to accept or ignore, never applied behind your back.
Mark an item public and it gets a page anyone can open — no login — showing the attributes you chose to publish, always the last confirmed version. It's a lightweight way to support Digital Product Passport (DPP) and PPWR-style disclosure needs: publish the item once, point people at the page, and keep it current from the same place you already manage the item. DPP and PPWR carry their own mandated data models and registries beyond a public attribute page, so treat this as a head start on that disclosure, not a substitute for full regulatory compliance.
Requirement profiles check the item's actual attribute values, live — not a spreadsheet someone updates once a quarter. Checklists track the physical tasks attribute values can't capture. Try it: fill in the missing value below.
Bottle 500 ml · EU PPWR — packaging
1 open requirementAssembly checklist
2 of 3 doneIf this bottle sits inside a bill of materials, its parent item's compliance depends on it too.
A value in the register is worth what its evidence is worth. Claims are made per requirement profile, never in general, and every change stays traceable.
Bottle 500 ml · Recycled content · 35 %
Packregister stores no order lines, customers, prices or volumes. Those remain in the ERP and DWH of your own organisation.
Packregister does one thing: keep packaging components, their attributes and their structures straight. Synced in through the API or entered by hand, every value carries the same evidence rules. Everything else stays where it already works.
More sectors to follow — imported the same way, alongside what you already have.
Claude, or any MCP-capable tool, reads and writes your register in minutes — run npx @packregister/mcp-server, no custom API client to write. Every item it creates lands as a draft for your review; adding a new attribute always asks you first.
Scan it. No app, no login, no account. Download the QR code and print it on the packaging, the spec sheet or the pallet label — anyone with a phone camera lands straight on the page. It's the one channel that still reaches whoever is standing in front of the physical product, not just whoever has the link.
The same structured, API-accessible attribute data can also feed broader sustainability reporting — for example the resource-use and circular-economy disclosures under CSRD's ESRS E5. That's the packaging slice of CSRD; the rest of it — emissions, workforce, governance, supply-chain due diligence — is outside what a packaging register does.