A maintenance engineer needs a bearing today. A search of the system by description returns nothing useful, so a purchase request is raised. Three aisles away, twelve of the same bearing sit under another code. Nobody was careless. The system gave no way to know.
The fix is not more discipline. It is a check that runs at the moment the request is made.
01Why the stock is invisible
- The same item exists under several codes, so stock is split and no single search finds it.
- Descriptions are free text, and the requester's wording differs from the storekeeper's.
- Stock at another site is in another system or another plant code.
- A substitute that would serve is not linked to the item requested.
02What it costs
The purchase itself, the carrying cost of two stocks of one item, and eventually the write-off of whichever one is forgotten. There is also a quieter cost: people stop searching, because searching never works, and every request becomes a new purchase.
03The check that prevents it
- When a request is raised, read what is being asked for and work out its class and specifications.
- Search every code, at every site, for items with the same critical specifications.
- Look for acceptable substitutes as well as exact matches.
- Show the requester what was found: where it is, how many, and how close the match is.
- Let the requester use the stock, or proceed with the purchase and record the reason.
The check advises; it does not block someone who has a real reason to buy. What it removes is the purchase made only because nobody could see the stock.
04What makes it work
- Matching on specifications, not on words
- One view across sites and systems
- Clear verdicts: identical, usable substitute, similar but different
- A result in seconds, inside the screen the requester already uses
05How it connects to the rest
The same understanding of items that powers this check also cleans the material master, compares prices between suppliers and shows where stock is idle. Starting with the check at the point of request is a practical first step, because the saving is immediate and easy to count.
In short
- Stock goes unseen because one item has several codes, descriptions differ and sites are separate.
- A check at the moment of request finds identical items and usable substitutes everywhere.
- It informs the requester and records the decision; it does not take the decision away.
- It is a small, countable first step toward wider procurement and inventory intelligence.
Questions
Will this slow down urgent purchases?
No. The check takes seconds and advises. An urgent purchase can still go ahead, with the reason recorded.
Does it need our material master to be clean first?
It works better on clean data and still helps on messy data, because it matches on specifications rather than on codes. It also shows which items most need cleaning.
Can it see stock at other plants?
Yes, where it is connected to those systems. Seeing across sites is where much of the value lies.
What does Quantum Beetle offer here?
A Pre-Procurement Check that can be added to an existing system on its own, and ATLAS, which is built to compare suppliers, prices and stock across sites.
Sounds like your problem?
Tell us about it. We'll say honestly whether the swarm can help, and what it would take.
Read next
- How to find duplicate material codes in your SAP material masterMaterial master data
- What sovereign AI means, and when on-premise AI is the right callOn-premise AI
- Duplicate payments: how they happen and how to stop them before the money leavesFinance controls
- What master data management is, in plain words, and why it decides whether AI worksMaster data
- How to clean a material master: a plan that survives contact with a real plantMaterial master data
- On-premise language models or a cloud AI service: how to choose for company dataOn-premise AI