Master data management (MDM)
Master data management (MDM) is the governance, processes, and tooling that maintain a single authoritative record (a golden record) for core entities like suppliers, items, and materials across ERP, procurement, and quality systems. MDM defines who can create and change records, the standards those records must follow, and how systems stay synchronized, preventing the duplicates and drift that one-time cleanup projects cannot.
Examples
Creation workflow: A manufacturer routes all new vendor requests through a form that fuzzy-matches against existing records. Of 90 monthly requests, about 22 match an existing supplier and are redirected, holding duplicate creation near zero after a one-time merge of 1,400 legacy duplicates.
Two ERPs, one golden record: After an acquisition, a company keeps both ERP instances but designates an MDM hub as the supplier master. Each supplier carries one golden ID mapped to local IDs in both systems, so consolidated spend reporting works without forcing a five-year migration first.
Survivorship rule: When merging duplicates, the company keeps the legal name from the tax record, the address from the most recent verified invoice, and the payment terms from the active contract, documented so merges are repeatable rather than judgment calls.
Definition
Duplicates and drift are not random; they are the predictable output of unmanaged record creation. A plant onboards a supplier that already exists in the vendor master under a slightly different name because search did not find it. An acquisition brings a second ERP instance with its own item numbers. One engineer creates "Aluminum 6061-T6" while another creates "AL6061T6." Each event is small; after five years the company has 9,000 vendor records for 6,000 actual suppliers.
MDM is the standing countermeasure. In practice it means one designated source of truth per domain, a request-and-approve workflow with duplicate matching at creation, naming and unit standards (including the category taxonomy), survivorship rules for merging conflicting records, and sync jobs that push the golden record to every consuming system.
The hard part is rarely tooling. It is convincing plants and business units to give up local control of record creation, which is why MDM programs without executive backing decay into suggestions.
The relationship to data cleansing is one of tense: cleansing fixes the past, MDM governs the future. Fund a cleanup project without the governance and you are buying the same project again in three years.
Frequently asked questions
What is master data management in simple terms?
Master data management (MDM) is the governance, processes, and tooling that maintain a single authoritative record, often called a golden record, for core entities like suppliers, items, and materials across ERP, procurement, and quality systems. MDM defines who can create and change records, the standards those records must follow, and how systems stay synchronized.
What is the difference between master data management and data cleansing?
Data cleansing fixes the past while master data management governs the future. A cleanup project merges the duplicates that already exist, and MDM prevents new ones through creation workflows, duplicate matching, and naming standards. Funding a cleanup without the governance usually means buying the same project again in about three years.
Why do duplicate supplier and item records keep appearing?
Duplicates are the predictable output of unmanaged record creation. A plant onboards a supplier that already exists under a slightly different name, an acquisition brings a second ERP with its own item numbers, or two engineers key the same material with different spellings. Each event is small, and after five years a company can hold 9,000 vendor records for 6,000 actual suppliers.
What does master data management look like in practice?
In practice, master data management means one designated source of truth per domain, a request-and-approve workflow with duplicate matching at creation, naming and unit standards, survivorship rules for merging conflicting records, and sync jobs that push the golden record to every consuming system. One manufacturer's creation workflow redirects about 22 of 90 monthly vendor requests to existing records, holding duplicate creation near zero.
What is the hardest part of an MDM program?
The hard part of master data management is rarely tooling. Convincing plants and business units to give up local control of record creation is the real obstacle, which is why MDM programs without executive backing decay into suggestions.
Previous