CPG operations glossary

Master data management: keeping the product record consistent

Master data management, or MDM, is the practice of maintaining consistent, reusable information about the core things a business repeatedly references—such as products, suppliers, customers, and locations.

Plain-language definition

It is about the recurring record, not one event.

Master data describes the entities a business uses again and again across its work. Master data management is the discipline of keeping those shared records understandable and consistent when they appear across systems, teams, and processes.

For a food brand, a product’s name, pack size, version, identifier, and packaging hierarchy are examples of information that may be referenced repeatedly. The goal is not to make every record identical; it is to make clear which product information a team is referring to in a given context.

A useful distinction

The same product appears in two different kinds of records

One record helps a team recognize the item each time it comes up. Other records capture an event involving that item.

One 12-ounce snack pouchthe shared reference

Referenced again and again

The product record

It helps answer: Which pouch are we talking about?

  • Name and pack size
  • Product or version reference
  • Identifier or packaging context

Captured at one moment

The event record

It helps answer: What happened with that pouch?

  • A purchase order or invoice
  • A co-packer run or receipt
  • A particular sales order

Illustrative product record

One pouch can carry several reusable references

This is an example of a way to frame a product record. It is not a universal field list, a data model, or a required retailer, accounting, or regulatory record.

Identity

What is the item?

A product name, pack size, and a stated unit or format help a team distinguish one sellable item from another.

Version context

Which version is meant?

A product, formula, specification, or packaging revision reference provides context when a record changes over time.

Identifier context

How is it referenced?

An internal code or chosen product identifier can help a team connect the same item across documents and partners.

Relationship context

What is it connected to?

Supplier, co-packer, component, or packaging-hierarchy references can clarify how the item relates to surrounding records.

Related terms

TermHow it relates
Master data managementThe practice of managing reusable information about core entities such as products, suppliers, customers, or locations.
Product information managementA related focus on product information; the exact scope depends on how an organization designs its data and systems.
Transaction dataInformation about a particular business event, such as an invoice, order, receipt, or production run.
Data governanceThe policies, responsibilities, and practices an organization uses to manage data; it is broader than MDM alone.

What this definition does not decide

This overview does not prescribe a data model or field list, determine which records a brand must maintain, validate data quality, assign product identifiers, establish a system of record, or provide implementation, legal, regulatory, financial, accounting, or compliance advice. The right record design depends on the product, partner, channel, and systems a brand uses.

Source note

Where this terminology comes from

This overview summarizes professional data-management terminology and GS1 product-data context. The links are educational references, not a system-design recommendation.

Building commercial workflows with CPG design partners

Keep shared product references clear as the work around them changes.

A working prototype validated Guidance’s core operating model. The commercial rebuild is translating that proof into production-ready workflows with CPG design partners.

Apply as a Design Partner