By Rahul · 20 Sep 2026 · 4 min readAsk three departments how many active customers you have and you may get three different numbers. Sales counts one list, accounts counts another, and each branch keeps its own spreadsheet. None of them is wrong on its own terms - they are simply working from different copies of the truth. That is the problem enterprise data management (EDM) exists to solve.
What “master data” actually means
Master data is the core information your business runs on and refers to again and again: customers, products, vendors, locations, employees and the codes that tie them together. It changes slowly, but every transaction depends on it. An order is meaningless without the customer and product records behind it.
EDM is the combination of software, rules and ownership that keeps one trusted version of each of those records - and makes every other system use it.
Warning signs you have a master-data problem
- The same customer or product exists several times with slightly different names, codes or addresses.
- Monthly reports need hours of manual reconciliation before anyone trusts them.
- Branches or departments keep “their own” Excel files because the central system is out of date.
- Nobody can say who changed a record, or when.
- Importing data from a new partner, ERP or marketplace means days of copy-and-paste.
If two or more of these sound familiar, the cost is already landing somewhere - usually in staff time and in decisions made on numbers people quietly doubt.
What an EDM system does
1. Brings the data in
Bulk imports from Excel/CSV, existing databases and APIs, with field mapping so each source lands in the right place.
2. Cleans and de-duplicates it
Matching rules flag likely duplicates (same email, similar name, same tax ID) and merge rules decide which values win. Validation stops obviously bad data at the door.
3. Governs it
Role-based access controls who can view or edit which fields, approval steps protect sensitive changes, and an audit trail records every change with a user and a date.
4. Shares it
Other systems - CRM, e-commerce, accounts - read from the master record instead of keeping their own copy, and scheduled reports come from a single source.
How to start without a “big bang” project
- Pick one domain. Customers or products are usually where the pain is greatest. Leave the rest for later.
- Agree the definition. Decide which fields make up a “complete” record and who owns it. This conversation is often worth more than the software.
- Load and clean a real sample. Importing a few thousand real records early exposes the duplicates and gaps you will need rules for.
- Connect one consuming system. Point a single report or application at the master data and prove the value before widening the scope.
- Plan for care after go-live. Data rules evolve with the business. Budget for ongoing support rather than treating launch as the finish line.
Build, buy or tailor?
Large enterprise EDM suites are powerful but often heavy for small and mid-sized organisations. A tailored system built around your actual records, workflows and reports is frequently faster to adopt - especially when it starts from a proven core rather than a blank page.
At OASIS we build and support EDM platforms on that basis: your data model, your rules and your screens, with data migration and team training as part of the project. If you would like a second opinion on where your data problems really sit, tell us how your data flows today and we will suggest a sensible first step.
If you are a mid-sized business wondering whether you need one of the big enterprise suites, our guide to master data management for mid-sized businesses sets out the practical alternative.