Category definition
A packaging attribute register is a system of record for packaging components — what they are, the attribute values that describe them, and how they compose into a bill of materials. Each value can carry evidence, and every change stays traceable.
Everything in the register is built from these — nothing more, nothing hidden behind it.
Named, typed fields — text, number, choice, or yes/no, each with its own unit where it applies. You decide which attributes exist; nothing is baked into the product.
Item types are grouped into categories (a bottle and a pallet ask different questions) and each carries the set of attributes that apply to it.
One row per real packaging component — a bottle, a cap, a box — holding a value for every attribute its item type asks for.
An item can be composed of other items, with quantities: a finished packaging built from the components that go inside it.
A value in the register is worth what its evidence is worth. Attach a spec sheet or a declaration to the value it backs, and the change stays traceable — who changed it, when, and via which source (a person in the UI, a sector-package import, or the sync API). Requirement profiles then let you define which attributes a given item type must carry, and see per item which of those are still missing — the register shows the gap, you decide what "complete" means.
A short, factual boundary — worth stating plainly rather than leaving implicit.
No scanners, no IoT tags, no physical asset tracking. A register holds data about a component — it does not follow the physical item around a supply chain.
Requirement profiles let you define which attributes are mandatory for a given item type, and show which items are missing them — a gap check against a profile you define, not a ruling on compliance with any specific regulation.
A value has one current state. There is an audit trail of who changed what, when, and via which source — but no draft/publish cycle, no releases, no baselines, and no querying an item as it stood on a past date.
What it is: one place for packaging attributes, evidence and bills of materials — built to enrich the ERP and DWH you already run, not replace them.