Key points at a glance
- Separate model, variant, batch and item levels.
- Store values with source, unit, language and validity.
- Publish immutable snapshots instead of live drafts.
Choose entities and relationships
Represent product families, models, variants, batches and individual items only where they add meaning, with clear inheritance and overrides.
Describe values properly
A field needs a stable code, type, unit, language, source, owner, validity, visibility and validation rules rather than just a label and text.
Version releases
Keep working data editable but create immutable approved snapshots for public access, audit and reproducible exports.
Frequently asked questions
Should every value be copied to every product?
No. Inheritance reduces duplication when overrides remain explicit and traceable.
Can the database schema remain flexible?
Yes. Versioned field schemas can add flexibility without sacrificing validation and stable field codes.
Official sources
Applicable legal acts and official publications govern legally relevant decisions.
As of: 17 August 2026. This guide provides general information and is not legal advice or a compliance guarantee.
Turn product data into a controlled product passport.
Import existing data, validate completeness and publish approved versions through a stable QR address.