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.
Previous
*GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally, and COOL VENDORS is a registered trademark of Gartner, Inc. and/or its affiliates and are used herein with permission. All rights reserved. Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.