Leak 40 · Data & Product Information - Poor substitute and cross-reference data
The 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.
Diagnostic note. Symptoms, required records, an initial check, and possible fixes. This shorter note does not include a full worked example.
What is it?
Cross-references (this competitor number equals this item) and substitutes (this item can replace that one) are the knowledge that turns an RFQ into a quote and a stockout into a sale. In most distributors that knowledge lives in a few experienced heads and a pile of supplier catalogs. When it is not in the system, every lookup is slow and every stockout is a lost sale.
- Family
- Data & Product Information
- Primary owner
- Product Managers
- Secondary owners
- Inside Sales Lead, Purchasing Manager
- Primary impact
- Revenue / labor
- Typical data source
- Item master cross-references, quote and lost-sale records
- Detection difficulty
- 30-day measurability
Ask yourself
Can a salesperson find an approved substitute for an out-of-stock item, or a match for a competitor’s part number, without asking someone?
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?
Warning signs. None of these proves the leak exists. They tell you where to look.
- Cross-reference lookups done by phone or from memory.
- Lost sales on stockouts when a substitute was on the shelf.
- Quote delays traced to “finding the equivalent.”
- One or two people everyone asks.
What data do I need?
The minimum viable set. Most of it is already in your ERP.
| Field |
|---|
| Item master cross-reference and substitute fields, populated or not |
| Quote lines that required a manual lookup |
| Stockout events where a substitute existed |
The initial check
Start with a small sample. Gathering the exports, agreements, or observations is separate from running the check; agree that work with the person who owns the records.
- 1Count the share of your top 500 items with at least one cross-reference and one substitute recorded.
- 2Ask the quote desk how many lookups they did yesterday and how long each took.
- 3For last month’s ten most-backordered items, check whether a substitute was in stock and whether it was offered.
Coverage = items with cross-references ÷ top items; lookup labor = lookups per day × minutes × loaded rate
Then ask one question: If the two people who know the equivalents left, what would happen to quote speed?
How much could it be costing us?
A conservative range, not a headline. The goal is a number management can trust enough to investigate.
Lookup labor per year + lost gross profit on stockouts where a substitute existed × share recoverable with data in the system
Common root causes
Fixes fall into three layers. Not every problem needs software, and almost none needs AI first.
- Process
- No one owns cross-reference and substitute maintenance.
- Data
- Fields exist in the ERP but are empty.
- Technology
- No tool to capture cross-references at the moment a lookup happens, so knowledge stays in heads.
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
Ownership
A product manager owns the data; every manual lookup gets recorded.
Level 2
Load
Load supplier cross-reference files for the top lines and populate substitutes for A items.
Level 3
Workflow
Suggest cross-references and substitutes at quote and order entry, with confirmation captured back to the item master.
Where AI helps
- Reading supplier catalogs and interchange guides to propose cross-references for review.
- Matching competitor part numbers from RFQs to your items with a confidence score.
Where AI probably doesn’t
Approved substitutes are a product-management judgment. A model can propose. A person approves.
Before you call it a leak
- A wrong substitute can be a safety or warranty problem. Keep approval with a qualified person.
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 28 · SalesSlow quote responseThe RFQ arrives at 9 a.m. The quote goes out two days later, after a supplier price check and a cross-reference hunt. The customer decided yesterday.
- Leak 23 · InventoryStockouts on high-value SKUsThe fast, high-margin item is out again. The customer buys elsewhere, and the sale is never recorded because it never happened.
- Leak 41 · DataIncomplete product and customer master dataItems 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.
- Leak 34 · OperationsManual order-entry reworkA customer PO arrives as a PDF. Someone types it into the ERP, checks it against the quote, fixes the part numbers, and emails an acknowledgement. Fifteen minutes, forty times a day.
Let’s start with one thing.
What would better performance look like?
Bring a result you want to improve, a symptom, or a workflow you already understand. You do not need to know the bottleneck yet. We’ll help choose what to investigate first.
No transaction files needed for the first conversation.