Short answer
Master data management (MDM) is the discipline and system for keeping core business entities such as products, customers and suppliers consistent across systems. MDM governs the master records that PIM and DAM reference, such as the product identifier a DAM uses to link images. A DAM selection needs MDM input whenever 2 or more systems create or change those records.
How MDM works with a DAM
MDM creates one trusted master record per entity and distributes its identifiers and core values to every connected system. The DAM rarely owns master data. The DAM consumes it to tag, link and govern assets.
MDM touches a DAM through five kinds of master data:
- Products: identifiers such as SKU and GTIN that link assets to products.
- Brands and product lines: the hierarchy behind brand facets and permissions.
- Suppliers and agencies: the parties that deliver assets and hold licences.
- People: talent and photographers named in model releases and credits.
- Locations and markets: the regions used in usage rights and portals.
MDM programmes also define data stewardship: named owners who approve changes to master values. A DAM that copies master lists by hand drifts away from the master after the first unsynchronised change.
Example of MDM in a DAM context
Worked example: a manufacturer's MDM hub issues an internal SKU and a GS1 GTIN for every product. ERP, PIM and DAM all use those keys.
When a product is replaced by a successor, MDM publishes the mapping from old to new SKU. The DAM receives the event, links the existing images to the new SKU and marks the old product's assets for archive review.
MDM in a DAM selection
MDM belongs at checkpoint 1, Map, where the buyer records which system masters each entity. The stakeholder map adds the data owners to the selection team.
Test these four behaviours at checkpoint 5, Test:
- Load a brand and product list from an external source into DAM controlled vocabularies by API.
- Rename a brand in the source and show the DAM update every tagged asset.
- Merge two product records and show what happens to the linked assets.
- Show that the DAM stores external identifiers as key fields, separate from file names.
DAMSelection assessment: data first, then process, then people, then tooling. Settle master data ownership before scoring any DAM. The metadata model builder records which fields come from master sources.
Common mistakes with MDM
DAM projects mishandle master data through four common mistakes.
- Keeping a DAM-local brand list that drifts from the master.
- Using file names as product keys.
- Running an MDM programme inside the DAM project and delaying both.
- Leaving master data changes without a steward, so nobody approves merges or renames.
Related terms: PIM.
Frequently asked
Does a DAM need MDM?
A DAM needs master data, but it does not always need a separate MDM system. Smaller organisations often take product and brand masters from ERP or PIM. An MDM system becomes relevant when several systems create the same entities and conflicts appear.
What is the difference between MDM and PIM?
MDM keeps core entities such as products, customers and suppliers consistent across all systems. PIM enriches product data for channels with copy, attributes and translations. MDM governs the product key, and PIM builds the sellable product content on top of it.