Master data is the core reference information a business reuses across transactions, such as customers, vendors, products and locations.
Systems · Reviewed by Ray Rasouli
Ask about master data
Plain answers, with your setup in mind.
Ask anything about master data. For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
Transactions change every minute: orders, invoices, shipments. Master data changes slowly and gets reused by all of them. A retailer's product record, with its SKU, description, unit of measure and supplier, shows up on every purchase order, receipt and sale.
Because it is reused so often, one bad master record spreads fast. A wrong unit of measure on a single item can make every order for it ship the wrong quantity, and every invoice bill the wrong amount.
Good master data has a clear owner, a standard format and a simple process for adding or changing records.
In practice
Anyone can create a new record.
Without a request process, staff add near-duplicate customers and items when they cannot find the existing one.
Formats are not standard.
Addresses, units and product names get typed many ways, which breaks searches, reports and integrations.
Old records never retire.
Inactive vendors and discontinued items stay selectable, so people keep using them by mistake.
Each system keeps its own copy.
The ERP, CRM and ecommerce store each hold a version of the product list that slowly drifts apart.
Master data describes things that persist, like a customer or product. Transactional data records events that use them, like an order or a payment.
It is the set of processes, rules and sometimes tools used to keep master data accurate, consistent and shared across systems.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.