> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://tieback.io/docs/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://tieback.io/docs/_mcp/server. # Product Master Data > The stable, shared core data that identifies and describes a product across the systems that use it, as distinct from transactional or event data about individual movements and orders. ## Definition The relatively stable core data that identifies and describes a product and is shared across business functions: its identifiers, classification, specification, composition, packaging and key commercial and technical attributes. It is distinguished from transactional data, which records individual orders and movements, and from event data, which records what happened to specific items over time. ## Expanded Explanation The distinction is one of role rather than storage. A batch number recorded against a shipment is transactional; the definition of the product that batch belongs to is master data. Master data is referenced repeatedly by many processes, changes comparatively rarely, and causes disproportionate damage when it is wrong, because the error is inherited everywhere it is used. In practice product master data is spread across several systems. Engineering specification and composition typically originate in a lifecycle management system, commercial and logistics attributes in an enterprise resource planning system, marketing descriptions and media in a product information system, and declared sustainability attributes from suppliers. Treating these as one logical set of product master data, governed consistently, is what separates a managed estate from a collection of overlapping databases. Passport work extends the scope of product master data. Attributes that were previously held informally, such as substance declarations, recycled content or durability characteristics, become part of the shared core because they are published externally and must be maintained to the same standard as any other master attribute. ## Why It Matters A Digital Product Passport is anchored to a product identity and populated largely from product master data. If the same physical product exists three times under different codes, or if its composition is only described in an attachment, no publication layer can compensate. Most passport readiness work is, in substance, product master data work. ## Common Misconceptions #### Master data is whatever sits in the product information system Product information systems usually hold the commercial subset. Specification, composition and conformity attributes commonly originate elsewhere and are equally part of product master data. #### Master data never changes It changes slowly rather than never. Specifications are revised and suppliers are replaced, which is precisely why change control and versioning matter for published passports. ## Related Terms * [Master Data Management](/docs/knowledge-base/glossary/master-data-management) * [Product Data](/docs/knowledge-base/glossary/product-data) * [Golden Record](/docs/knowledge-base/glossary/golden-record) * [System of Record](/docs/knowledge-base/glossary/system-of-record) * [Product Identifier](/docs/knowledge-base/glossary/product-identifier) ## Related Knowledge Base Articles * [What is Product Master Data?](/docs/knowledge-base/enterprise-systems-and-data-architecture/what-is-product-master-data) * [ERP vs PIM vs PLM: What's the Difference?](/docs/knowledge-base/enterprise-systems-and-data-architecture/erp-vs-pim-vs-plm) * [What is Master Data Management (MDM)?](/docs/knowledge-base/enterprise-systems-and-data-architecture/what-is-master-data-management) ## Related Articles * [Golden Record](/docs/knowledge-base/glossary/golden-record) * [Master Data Management](/docs/knowledge-base/glossary/master-data-management) * [Authoritative Source](/docs/knowledge-base/glossary/authoritative-source) * [Data Architecture](/docs/knowledge-base/glossary/data-architecture) * [Product Data Governance](/docs/knowledge-base/glossary/data-governance) * [Product Data Quality](/docs/knowledge-base/glossary/data-quality) * [Product Data Stewardship](/docs/knowledge-base/glossary/data-stewardship) * [Source of Truth](/docs/knowledge-base/glossary/source-of-truth) ## See Also * [Enterprise Systems and Data Architecture](/docs/knowledge-base/enterprise-systems-and-data-architecture/overview) * [Implementation](/docs/knowledge-base/implementation/overview) ## References * ISO 8000, data quality: [https://www.iso.org/standard/81745.html](https://www.iso.org/standard/81745.html) * Regulation (EU) 2024/1781, Official Journal of the European Union: [https://eur-lex.europa.eu/eli/reg/2024/1781/oj](https://eur-lex.europa.eu/eli/reg/2024/1781/oj) ## About This Article About This Article
Last Reviewed
2026-08-09
Next Scheduled Review
2027-08-09
Article Version
1.0
tieback Knowledge is a continuously maintained reference library covering Digital Product Passports, product traceability, product compliance and related regulations. Articles are reviewed regularly as legislation, standards and implementation guidance evolve. ## Related Docs * [Enterprise Systems and Data Architecture](/docs/knowledge-base/enterprise-systems-and-data-architecture/overview) * [Implementation](/docs/knowledge-base/implementation/overview) * [Digital Product Passports](/docs/knowledge-base/digital-product-passports/overview) * [Glossary](/docs/knowledge-base/glossary/overview)