Five master data domains cover what most organizations actually need to master: customer (or party), product (or material), supplier / vendor, location / site, and employee / workforce. Each domain spans multiple systems (CRM, ERP, ecommerce, billing, HR), each produces its own business pain when unmanaged (duplicate billing, mis-shipped orders, partner conflicts), and each can be the first domain a program masters - though customer is most common as a starting point.
The Five Domains
|
Domain |
Typical systems |
Pain when unmanaged |
|
Customer |
CRM, ERP, ecommerce, billing, support |
Duplicate / fragmented customer view |
|
Product |
ERP, PIM, ecommerce, catalog |
Inconsistent SKUs, pricing, descriptions |
|
Supplier |
ERP, procurement, AP |
Duplicate vendor records, terms inconsistencies |
|
Location |
ERP, logistics, retail systems |
Site mismatches, shipping errors |
|
Employee |
HRIS, payroll, IT, security |
IAM gaps; reporting inaccuracy |
Customer
The most-mastered domain in B2C and B2B. Customer MDM produces a single identity per buyer / household / account across CRM, ERP, ecommerce, billing, and support. Pain when unmanaged: duplicate marketing, missed cross-sell, fragmented service history, compliance risk.
Product
Product MDM (sometimes called PIM-adjacent) standardizes SKU, description, attributes, pricing rules, and category hierarchy across ERP, ecommerce, catalog, and partner channels. Pain when unmanaged: channel-specific descriptions that diverge, pricing inconsistencies, and SEO leak from duplicate product pages.
Supplier / Vendor
Supplier MDM produces one trusted vendor record across ERP, procurement, accounts payable, and partner systems. Pain when unmanaged: duplicate vendor accounts at different terms, missed spend consolidation, partner conflicts, audit complications.
Location / Site
Location MDM standardizes site / store / facility identifiers across ERP, logistics, retail, and reporting systems. Pain when unmanaged: mis-shipped orders, store-data inconsistency, retail / wholesale channel mismatches.
Employee / Workforce
Employee MDM produces one trusted person record across HRIS, payroll, IT, security, and IAM. Pain when unmanaged: provisioning errors, security gaps, reporting inaccuracy. (Often run separately as identity management; the MDM discipline is the same.)
Which to Master First
Most programs start with customer (highest immediate value across marketing, sales, and service); some start with product (if SKU inconsistency is costly); some start with supplier (if procurement spend or compliance is the driver). Start where the business pain is most acute; expand from there.
Centric delivers MDM across all five domains through its master data management service.
Frequently Asked Questions
What are the main types of master data?
Five domains - customer, product, supplier, location, employee. Some organizations add reference data (codes, hierarchies) as a sixth.
Which domain should we master first?
Most common start: customer. Pick the domain with the most acute business pain; expand from there.
Can we master multiple domains at once?
Possible but harder. Most programs sequence domains to manage scope and absorb operating-model changes.
What about reference data?
Reference data (codes, hierarchies, classifications) is often managed inside or alongside MDM. Some teams treat it as a sixth domain.
Conclusion
Knowing your five master data domains is the first step toward managing them. Most organizations have all five spread across multiple systems; the question is which one is hurting most today and which should be the first to consolidate. Start with one; sequence the rest; avoid the temptation to do all five at once.
