Leak 41 · Data & Product Information - Incomplete product and customer master data
Items with no weight, no product class, no supplier part number. Customers with no segment, no terms, no default ship-to. Every automated decision downstream falls back to a guess or a person.
Diagnostic note. Symptoms, the records to bring, and a practical first check with your team.
What is it?
Master data is the foundation every other process stands on. When it is incomplete, pricing matrices cannot apply, freight cannot be estimated, replenishment cannot classify, and reports cannot segment. The leak shows up everywhere else as manual work and exceptions, which is why it is last on this list and first in most fixes.
- Family
- Data & Product Information
- Primary owner
- IT / Operations Manager
- Secondary owners
- Product Managers, Customer Service Manager, Controller
- Primary impact
- System-wide
- Typical data source
- ERP customer master, item master
- Detection difficulty
- 30-day measurability
Ask yourself
For your active items and customers, what share have the fields your pricing, replenishment, and reporting actually depend on filled in?
Yes, partially, no, or don’t know. “Don’t know” is the most useful answer, because it points at the test below.
What does it look like?
Look for these patterns, then use the check below to trace the issue in your own records.
- Exceptions caused by missing fields: no weight for freight, no class for pricing.
- Reports with large “unclassified” or “other” groups.
- Staff who know which records to distrust.
What data do I need?
The minimum viable set. Most of it is already in your ERP.
| Field |
|---|
| List of the fields your pricing, freight, replenishment, and reporting depend on |
| Fill rate of each field for active records |
The initial check
Start with a small sample. Ask the person who owns the records to gather the exports and agreements, then work through these steps together.
- 1Write down the ten item fields and ten customer fields your business actually uses in rules and reports.
- 2Export active records and count the fill rate for each.
- 3For the emptiest field, trace one downstream exception it causes.
Fill rate = records with the field populated ÷ active records, per field
Then ask one question: Which single empty field causes the most manual work downstream?
How much could it be costing us?
A conservative range, not a headline. The goal is a number management can trust enough to investigate.
Not directly quantified. Estimate through the leaks it causes: exception handling, freight estimation, pricing overrides, and reporting rework.
Common root causes
Fixes fall into three layers. Not every problem needs software, and almost none needs AI first.
- Process
- No creation standard and no owner for completeness.
- Data
- Required fields are optional in the ERP.
- Technology
- No completeness reporting, so gaps are invisible until they cause an exception.
What should we do?
Start with the simplest intervention that could solve it. Move down the list only if the one above is not enough.
Level 1
Measurement
A monthly fill-rate report for the fields that matter.
Level 2
Standard
Required fields enforced at creation, with an owner for each master.
Level 3
Enrichment
Fill the gaps on active records from supplier data, past transactions, and review, starting with the fields that cause the most exceptions.
Where AI helps
- Proposing values for missing fields from supplier catalogs, descriptions, and transaction history, for a person to confirm.
Where AI probably doesn’t
Deciding which fields matter and making them required is a management and configuration task.
Before you call it a leak
- Filling fields with guesses is worse than leaving them empty. Confirm, then fill.
Think this might be happening in your business?
Turn the finding into a next step.
If the numbers say there is something there, send us what you found and we will help you decide whether it is worth a full investigation. No transaction files needed for that conversation.
Related leaks
- Leak 39 · DataDuplicate customer and product recordsAcme Mfg, ACME Manufacturing, and Acme Manufacturing Inc. Three records, three price files, three credit limits, and a sales report that shows none of them as your biggest customer.
- Leak 40 · DataPoor substitute and cross-reference dataThe customer asks for a competitor’s part number. The rep asks the product manager, who checks a catalog, who calls the supplier. Two days later the customer has bought it elsewhere.
- Leak 38 · OperationsExcessive manual exception handlingHalf the day goes to exceptions: the address that does not validate, the item that needs a substitute, the credit hold that needs a call. Most of them are the same exception, repeated.
- Leak 22 · InventoryExcess safety stockSafety stock set once, by feel, for every item. It protects against a stockout that stopped being likely years ago and ties up cash doing it.
Let’s start with one thing.
Give your team more time for the work that needs them.
Show us the quoting, order-entry, or follow-up work that keeps piling up. We’ll map it with you and find a practical place to start.
Start with a free workflow conversation with Alex.