Reference & Master Data (KA 8)

Reference & Master Data (KA 8)

Customer, Product, Location — one canonical truth, governed by match/merge/survivorship.

Why it matters

If three dashboards disagree on ‘active customer’ counts, the difference is almost never a quality bug — it's a master-data gap. MDM is the discipline that makes the disagreement impossible at the source.

Going deeper

The four MDM topologies, ordered by invasiveness:

1. Registry — read-only index of cross-system IDs.
2. Consolidation — cleansed hub for analytics; sources unchanged.
3. Coexistence — hub publishes back to sources; eventual consistency.
4. Transactional hub — hub is the system of record; sources read from it.

Reference data (countries, currencies, ISO codes) is the easy sibling — small, stable, low political cost. Start there to build the muscle before tackling Customer MDM, which is mostly an org-design challenge.

Master data is the passport office for your business entities.

Before passports, identity was decided per-border from whichever document the local clerk would accept — and three borders meant three identities. A passport doesn't replace the source documents; it consolidates them into one authoritative ID issued by a single agency, accepted everywhere downstream.

MDM does the same for Customer, Product, Location: every source system keeps its own record, but the master ID is the one downstream analytics, billing and ML join on. Without it, you'll always have three ‘Acme Inc.’ rows in the warehouse.