Master Data Management

Master Data Management

One canonical Customer / Product / Location — built by match, merge and survivorship rules.

Why it matters

MDM resolves the 'which Acme Inc. is this?' problem at the source so 12 downstream dashboards don't each invent their own answer.

Going deeper

Four common MDM topologies, ordered by how invasive they are to source systems:

1. Registry — master record is read-only, just an index of cross-system IDs. Lowest blast radius, weakest enforcement.
2. Consolidation — cleansed master copy in a hub for analytics; sources keep writing their own truth.
3. Coexistence — hub holds the golden record and publishes back to sources, but sources may still write. Eventual consistency, lots of conflict-resolution.
4. Centralised / transactional hub — the hub is the system of record; sources read from it. Strongest data quality, hardest organisational lift.

Choosing one is mostly an org-design decision: pick the topology your business is willing to enforce, not the one with the prettiest architecture diagram.

MDM is the passport office for your business entities.

Before passports, you proved who you were with whatever document the local clerk would accept: a baptismal record, a sworn statement, a postman's recognition. Result: every border decided your identity from scratch.

A passport doesn't replace those documents — it consolidates them into one authoritative ID issued by a single agency, accepted everywhere. MDM does the same for Customer, Product and Location: every source system keeps its own record, but the master ID is the one downstream analytics, billing and ML join on. No more three 'Acme Inc.' rows in the warehouse.