Parts Inventory Blind Spots: When the DMS, Warehouse and Distributor Portal Disagree

Ask a parts manager how many front brake pad sets the group has in stock, and you will get a confident answer. Ask the DMS, the warehouse team, the distributor portal and finance the same question, and you may get four different ones. Nobody is lying. Each system reports what it was last told, and nobody has made sure they were all told the same thing at the same time.

The cost rarely shows up as a line item. It shows up as a service advisor promising a part that is not on the shelf, and a car sitting on a lift for two days. It shows up as an emergency order, paid at a premium, for something already sitting in the next branch. And it shows up as a customer who has stopped messaging the advisor and started messaging the general manager.

This article looks at the four systems that usually hold a version of the truth, and at how they drift apart. It then looks at what that drift does on an ordinary working day in a multi-location group, and what it takes to bring the systems back into line without replacing any of them.

Four systems, four meanings of "in stock"

Most dealer groups and distributors run some combination of the systems below. Each answers the stock question differently, and each answer is reasonable on its own terms.

The DMS parts module is where counter staff and service advisors spend their day. It holds the part master, pricing, on-hand quantities by branch, reservations against repair orders and sales history. Its stock figure is only as good as the last transaction posted: a receipt, an issue, a return or an adjustment. If a movement happens physically but is not posted, the DMS does not know.

The OEM or distributor parts portal is where you check availability and place stock, daily and urgent orders. It tells you what the distributor can supply, what is back-ordered and what has shipped. It often carries superseded part numbers and alternates that differ from what is in your DMS. Its view of your own stock is essentially zero. Its view of your orders is only as current as the last status update.

Warehouse management is the physical reality: bin locations, goods receipt, picking, packing and cycle counts. In a group with a central warehouse feeding several branches, this is where you learn what is on which shelf and what is in transit between sites. Some groups run a proper WMS. Others run a mix of barcodes, spreadsheets and one very important storekeeper.

The ERP is finance's view: purchase orders, supplier invoices, stock valuation, intercompany transfers and VAT or sales tax. Where regional e-invoicing mandates apply, such as Peppol-based schemes, the quality of invoice data becomes a compliance matter. Elsewhere, correct tax treatment and clean documentation matter just as much at audit time. The ERP's stock value is the number owners and auditors see.

None of these is wrong. They answer different questions: can I sell it, can I get it, where is it, and what is it worth? Trouble starts when one question is asked of all four and people reconcile the answers by hand.

A Tuesday at the parts counter

Consider a dealer group with three service branches and a central warehouse. A customer who prefers to be served in their own language messages one branch on WhatsApp about a squealing brake. The advisor inspects the car, and the DMS shows four rear pad sets on hand. She quotes the job, promises same-day delivery, and the technician puts the car on a lift and strips the wheel.

The storeman walks to the bin and finds it empty. The last four sets were fitted to another car two days ago. That job card was closed on paper, and the issue was never posted. The advisor checks the distributor portal and sees stock available. She places an urgent order, pays the urgent freight rate, and tells the customer "tomorrow".

At 3 p.m. someone at the central warehouse notices a pallet from the distributor, received on Sunday. The goods receipt was never posted in the warehouse system because the supplier invoice had not arrived. The ERP still shows the purchase order as open. The pads were twelve kilometres away the whole time.

Count what that morning produced:

• A bay blocked for a full day, with another booking pushed back.
• A duplicate order at a premium freight cost.
• A broken promise to a customer who will remember it.
• A second purchase order to close and reconcile at month-end.
• A parts team that spent the afternoon chasing the explanation, not serving the next customer.

Nothing dramatic happened. Everybody did their job. The systems simply disagreed, and a person had to find out the hard way.

Where the numbers drift

The drift has a small number of repeat causes. Most groups will recognise several of them.

• Late receipts. Goods arrive but are not posted until the invoice or paperwork turns up, so physical stock runs ahead of every system.
• Supersessions and alternate numbers. The portal says one part number, the DMS another, and stock splits across two codes that nobody realises are the same part.
• Inter-branch transfers. One branch dispatches, the other has not yet received, and stock in transit belongs to nobody.
• Reservations that never release. Parts are allocated to quotes or job cards that were cancelled, converted late or never closed.
• Unposted counter sales and issues. A part leaves the shelf on a busy afternoon and the transaction is entered later, or not at all.
• Returns and warranty. Defective parts, returns to the distributor and credit notes land in the ERP weeks after the physical movement.
• Re-keying. Orders placed on the portal are retyped into the DMS or ERP, and every retyping is a chance for a wrong quantity or code.
• Adjustments made in one place. A cycle count corrects the warehouse figure, but the DMS and ERP are never told.

Each of these is a small gap between two systems, and the gap is usually closed by a person with a phone or a WhatsApp group.

What it costs, in the ways teams actually feel it

Delays. A part that exists but cannot be found, or cannot be trusted, is a delayed part. The car waits, the bay waits and the next customer waits. Where a group runs several branches, a one-day delay at one site ripples into booking schedules at the others.

Exhausted teams. Parts staff end up as human middleware. They check three screens before answering a simple question, post catch-up transactions at the end of the day, and field "does anyone have this?" messages from other branches. Month-end becomes a reconciliation exercise instead of a review.

Mistakes. When nobody trusts the figures, people order defensively. They place duplicate orders, miss a supersession, or hold excess stock of slow movers while fast movers run out. Wrong-part orders and returns follow, and so do the credit notes and corrected invoices that finance has to clean up.

Frustrated customers. Customers are often multilingual, messaging-first and used to fast answers. They do not care which system was wrong. They care that the promise made on Monday was not kept on Tuesday. Fleet and corporate accounts care even more, because a vehicle off the road is a cost to their own operation, and they will compare you with the next workshop.

Leaking money. The leaks are many and individually modest: urgent freight on parts you already own, bays idle while a car waits, lost sales when the system says zero but the shelf says four, dead stock that was ordered twice, and write-offs found at the annual count. Added up across branches, they are a real margin problem in the part of the business that usually drives most of the revenue.

Peak seasons make it worse. Think of the weeks before a long holiday, when customers rush to service cars before travelling, the pre-summer air-conditioning season, or the return to work after a extended break. Volumes rise, staff are stretched, and a small discrepancy at normal volume turns into a queue. Late postings pile up exactly when you can least afford to untangle them.

Why another report or another system will not fix it

The usual responses are understandable. One is a stock reconciliation report, built weekly in a spreadsheet by the person who knows how. It works until that person is on leave or the volume doubles. The other is a new DMS or ERP, in the hope that one platform will remove the problem.

Neither addresses the cause. A new platform still needs to talk to the OEM portal, the warehouse and the finance system, and every system you add becomes one more place where stock can be wrong. The problem is not any single product. It is that no one has decided which system owns which fact and how a change in one is passed to the others.

Questions that are rarely written down include these. Which system is the master for part numbers and supersessions? When does a purchase order become an expected receipt in the warehouse? When goods are received, what updates the DMS, and how fast? Who releases a reservation, and when? Until these have clear answers, a system will always be a little out of date.

This is also a RevOps question, not only a parts question. Aftersales revenue depends on the handoff between the counter, the workshop, the warehouse and finance, and when those handoffs rely on people, leadership sees the result weeks late, if at all.

How The Ninjaz Group approaches it

The Ninjaz Group is a managed-services partner. We design the change, wire your existing systems into one operating backbone, and stay on to run it. We sell the outcome, which here is stock figures you can trust, and not another piece of software. The work runs in three phases, and you can stop after any one of them.

Blueprint. We map the parts operation end to end, from the portal order and the goods receipt through bin, DMS reservation, counter sale or job card, and on to the ERP invoice and tax treatment. We look for every place where work is done twice, where a figure is retyped, and where a movement can happen without a posting. We also agree, in writing, which system owns which fact across every branch and warehouse.

Connect. We link the DMS, the warehouse system, the distributor portal and the ERP so that a receipt, an issue, a transfer or a count is posted once and passed on to the others. Supersessions and reservations follow the same rules at every site. Your existing platforms stay in place, and we build the connections between them.

Run. We operate the integrations, monitor them and fix drift before it reaches the counter. We also provide a single command center view for operations and finance leaders, showing stock by site, items in transit, open reservations and exceptions waiting for a decision. It does not replace the systems your teams already use. It gives leadership one place to see how the whole group is performing.

None of this removes the need for good habits at the counter. It does mean that when a part is on the shelf, the people who need to know can see it.

If your parts teams spend more time reconciling stock than selling it, book a consultation and we will start with a look at where your four systems disagree.