Why Do Spare Parts Stock Counts Disagree Between the CMMS, ERP and Site Storerooms?

Ask three people how many of a particular bearing the company holds and you will get three answers. The CMMS says four. The ERP says nine. The storeroom technician, who just looked at the shelf, says two. Nobody is lying, and nobody is necessarily careless. Each system is reporting what it was last told, and each was told something different.

This is the CMMS ERP inventory mismatch, and it is one of the most common reasons spare parts inventory accuracy erodes across multi-site operations. It shows up as a planner who cannot trust a work-order reservation, a buyer who reorders parts already sitting at another site, and a finance team writing off stock that "disappeared."

This article explains why the figures diverge, how to diagnose the problem in your own estate, what it costs, and what you can do about it. The later sections cover how The Ninjaz Group approaches it with one synchronised inventory view, without replacing the systems you already run.

Three systems, three versions of the truth

Each system holding a stock figure was built for a different job.

The CMMS exists to keep assets running. Its inventory module links parts to equipment, bills of materials and work orders. Its question is "can I do this repair?"

The ERP exists to account for money and buy things. Its inventory module holds valuation, purchase orders, goods receipts and ledger postings. Its question is "what do we own, what is it worth, and what should we order?"

The storeroom holds the physical parts, plus the informal arrangements that keep a site running: a bin of "just in case" fittings, a cage of returned items, a shelf of parts borrowed from a neighbouring site.

Each has a fair claim to being the record, but one physical event has to be captured in all three. A part is received, issued, returned or moved, and that event is usually recorded in one place and passed along later, partially, or not at all. Every gap leaves the numbers a little further apart.

The usual causes of storeroom stock discrepancies

Storeroom stock discrepancies rarely come from one dramatic failure. They accumulate from small, repeated ones. These are the five we see most often in MRO inventory management:

• Manual issue transactions. A technician takes a part at night when the storeroom is unattended. The slip goes on a clipboard and is keyed in the next day, or the following week, or never. If the CMMS records the work-order consumption but the ERP never sees the issue (or the reverse), the two balances split permanently.
• Duplicate item masters. The same part exists as "BRG-6205-2RS," "6205 2RS BEARING," and a free-text entry created by a site that could not find the first two. Each record carries its own balance, its own supplier and its own reorder point. This duplicate item master problem is often the largest single source of confusion, because no count of one record can ever match a count of the physical part.
• Receiving gaps. Goods are receipted in the ERP at a central dock, while the physical parts reach a remote site days later. Partial deliveries, substitutions with an alternative part and returns to supplier add further timing differences.
• Fragile interfaces. A nightly file transfer fails silently, a unit of measure changes between systems (each versus a box of ten), or a field is mapped incorrectly after an upgrade. Nobody notices until a count is run.
• Informal transfers and hoarding. Parts move between sites on a truck, sit in a van as kitted stock, or get stashed because a planner once waited three weeks for something and swore never to again. None of this is visible to any system.

None of these is a training failure alone. They are what happens when the process for recording physical movements depends on memory and goodwill, and when two systems each keep their own copy of a quantity.

What the mismatch really costs

The cost is spread across departments, so it is rarely added up in one place. Here is how it plays out in practice.

Consider a group with twelve sites, each with its own storeroom. A planner at one site reserves a pump seal for a scheduled repair. The CMMS shows three on hand. The shelf is empty because two were issued on paper last week and one was lent to a neighbouring site. The job slips, the asset stays down longer than planned, and a technician and a contractor are both waiting on a part that "exists."

At the same time, the buyer's view comes from the ERP, which shows nine seals across the network, mostly because issues have not been posted. The buyer sees nothing alarming. In a different scenario the figures run the other way. The ERP shows zero because a receipt was posted to the wrong record, an expedited order goes out, and the seals later turn up at another site, idle.

Those two failures, the stock-out and the over-order, have the same root cause. The costs fall into familiar categories:

• Time. Planners check shelves before trusting the system. Storeroom staff reconcile slips. Buyers phone sites to confirm availability.
• Inventory. Cash is tied up in duplicates and in "safety" stock that only exists because nobody trusts the numbers.
• Downtime and delay. A missing part turns a short repair into a long one, which means a delayed return to service and, for field operations, a delayed response to customers.
• Mistakes. Wrong-part substitutions, double orders and emergency freight are all downstream of uncertain data.
• Finance. Stock valuation drifts from reality, and period-end counts produce adjustments that nobody can fully explain.
• Burnout. Skilled people spend their days chasing and re-keying data rather than doing the work they were hired for.

How to diagnose it in your own operation

You do not need a major project to find out how bad it is. A focused two-week exercise will show where the numbers split and why.

1. Choose a sample of parts. Pick a few dozen items across categories: critical spares, fast movers and high-value components. Include some that you suspect are duplicated.
2. Count them physically at two or three sites. Count in the storeroom, and also check any satellite locations such as vans, cages and lineside bins.
3. Pull balances from the CMMS and ERP on the same day. Make sure the unit of measure is consistent so you compare like with like.
4. Classify every variance. Is it a duplicate record, an unposted issue, a receipt timing difference, a unit-of-measure error, or a genuine loss? The mix tells you where to focus.
5. Trace a handful of parts end to end. Follow one item from purchase order to receipt to shelf to work-order issue. Note every manual step and every point where a figure is re-typed.
6. Review the interfaces. Document what moves between the CMMS and ERP, how often, who owns it and what happens when it fails.
7. Search for duplicates. Compare item masters using manufacturer part numbers and normalised descriptions, not just internal codes.

When you finish, you will have a ranked list of causes. In most estates a few of them account for most of the variance, and that is where effort pays back first.

Fixes you can make before touching any software

Several improvements cost little and make everything that follows easier.

Govern the item master. Assign one owner for part creation. Require a manufacturer part number and a naming standard, and make a search-before-create step mandatory. Merge confirmed duplicates, and retire the extra records rather than leaving them active.

Decide the system of record for each data type. For example, the ERP might own valuation and purchasing, while the CMMS owns reservations against work orders. What matters is that quantity on hand is not independently maintained in two places.

Capture transactions at the point of movement. Barcode scanners at the storeroom counter, and on bins where practical, let a technician scan the part and the work order in seconds. This replaces clipboard slips and delayed keying, and it reduces wrong-part selection. Apply the same discipline to receiving, so the physical arrival is recorded when it happens.

Count by criticality. Cycle-count critical and high-movement parts more often than slow, low-value ones. Investigate each variance for its cause instead of just adjusting the balance.

Put availability checks into procurement. Before a requisition becomes a purchase order, the buyer should see stock at other sites and open orders. Even a manual check will catch avoidable orders.

Reconcile with finance on a schedule. Compare the inventory subledger to the ledger every period, and treat unexplained differences as process defects to fix.

These steps will improve accuracy. They will not keep it there on their own, because the underlying structure is still two or three systems holding copies of the same quantity.

Why one synchronised inventory view changes the picture

Discipline reduces errors, but it does not remove the structural problem. As long as each system maintains its own balance and passes updates on a schedule, drift will reappear. The durable fix is a synchronised inventory view.

In practice this means one record per part, with quantities shown by site and by bin. On-hand stock, reserved stock, stock on order and stock in transit are all visible together, and a change made in one system is reflected everywhere that needs it. The planner, the buyer, the storeroom lead and the finance analyst are all looking at the same figure, even if they reach it from different tools.

This addresses the earlier scenarios directly. A planner reserving the pump seal sees real availability, including stock at the nearest site and whether a transfer is feasible before the job is scheduled. A buyer sees network-wide stock and open orders before raising a requisition, so duplicate purchases get caught before they are placed. Finance sees issues and receipts posted consistently, so valuation and counts reconcile with far less manual effort.

One view does not mean every system must be replaced. The CMMS keeps doing maintenance work and the ERP keeps doing accounting and purchasing. The shared layer between them ensures they agree.

How The Ninjaz Group approaches it

The Ninjaz Group is a managed-services partner for multi-location enterprises, including energy and industrial companies with field sites. Our approach to a stock-count problem follows the same path as any engagement: Blueprint, then Build & Link, then Operate.

Blueprint maps the operation as it actually runs. For inventory, that means finding where parts transactions are done twice, where data goes stale and where money leaks, such as the unposted issues, duplicate records and failed interfaces described above. You keep the map whether or not you continue with us.

Build & Link connects what you already have. There is no rip-and-replace, and software you have already paid for stays. Through our Managed Link layer, we build, own and maintain the integration between your CMMS, ERP, inventory or warehouse systems and finance. The Ninjaz Operating Platform provides the connectors and a unified data layer with one record per asset and order, along with inventory and asset views across sites. Workflow automations can route transfers or flag a reservation that cannot be filled, and the Command Center shows live KPIs and alerts across locations. Roles and an audit trail show who changed what, and when.

Operate is handled through Managed Business Operations: managed IT and day-to-day running after go-live, so the integration does not quietly decay as systems are upgraded.

A platform will not fix everything on its own. Unlabelled shelves, missing scan habits and an item master nobody owns still need decisions from your people. What the platform does is make those problems visible, and ensure that once a transaction is recorded, every system sees it.

Start with one storeroom and one honest count

If your CMMS, ERP and storerooms disagree, you do not need to start with a transformation programme. Start with the sample count above and see which causes dominate. Then decide whether disciplined process changes will be enough, or whether the number of sites and systems means a synchronised layer is the more reliable answer.

If you would like help with that, we can map where your stock figures split and what it would take to bring them together. Book a consultation to talk through your storerooms and systems, or see the platform demo to view how inventory and asset information can be brought together across sites.