Resolve an MRO Vending Replenishment Complaint With Usage Evidence

When gloves, cutters, or other consumables vanish from an MRO vending machine on the floor, the plant contact wants two things at once, an explanation and a delivery time. A distributor representative who promises a refill before checking the transaction data is setting up a second complaint a few weeks later. The real fix is not a faster truck. It is a clear read of what the machine actually dispensed, who touched the reorder settings, and whether the missing item carries a safety requirement.

Why this conversation goes wrong

Most reps hear "why did your program remove supplies we use" and react to the tone instead of the claim. They apologize, promise a same day refill, and hang up feeling like they solved the problem. Then the machine runs low again the next week because nobody looked at why the reorder point changed in the first place. The customer heard urgency, not accuracy, and the next complaint lands harder than the first.

Another common failure is treating every missing item the same way. Cut resistant gloves used near a hazard and a box of shop rags do not carry the same risk if they run out overnight. A rep who does not separate the safety critical items from the routine ones either overreacts on low risk items or underreacts on the one that could stop a line or create a compliance gap.

The tone also turns adversarial fast because the customer suspects the distributor trimmed inventory to save money. SKU rationalization projects do remove or reclassify items, and if that change was never communicated to the plant floor, the suspicion is not unreasonable. A rep who gets defensive about the rationalization decision loses track of the one thing that is actually fixable, which is that current usage no longer matches the current reorder settings.

How to prepare

Before you answer the complaint, know what the machine and the paperwork can already tell you. Pull the vending transaction report for that item and machine going back several weeks, and check when withdrawals happen against which shift. Pull the item master to see whether the missing SKU was removed, substituted, or reclassified as part of a rationalization pass. Confirm the site's PPE list or check with the EHS coordinator if the missing item ties to a safety approval. Know who owns the vending configuration on the customer side and on yours, and check current stock with your storeroom manager so you never quote a delivery time you have not confirmed.

None of this takes long once you know where to look, and it changes the conversation from a debate about intent into a shared look at the data. If you handle other floor level issues for the same accounts, Manufacturing practice conversations covers more of these exchanges and the evidence each one needs.

What to say

Anita, the production manager, opens with frustration. "Why did your program remove supplies we use? Can you get this refilled before the night shift starts?"

Miles, the representative, does not answer the delivery question yet. "I want to give you an accurate answer, not a guess, so let me check current stock and the vending record first. Which items are affecting the line right now, and does any of them sit on your PPE list for safety use?"

Anita says the cut resistant gloves used on the night shift are the ones running out, and the machine has sat empty for two nights in a row.

Miles pulls up the transaction report while still on the call and tells her what he sees. "Your night shift pulls gloves at a steady rate, but the reorder setting for that SKU was lowered during a rationalization pass a few months back, and it never got reset to match the shift pattern. That is a configuration problem, not a demand problem. I will confirm safety approval status with your EHS coordinator and current stock with our storeroom manager today, and I can tell you within a few hours whether we can cover tonight's shift from existing stock or need an emergency pull. I will also assign an owner on our side to fix the reorder setting so this stops repeating."

Anita asks whether the item was intentionally cut from the program.

Miles answers directly instead of deflecting. "Some items were reclassified in the rationalization project, and if that removed something your line actually uses, that is on us to catch, not something I want to explain away. I will tell you today which one it was and how it happened."

Mistakes to avoid

1. Promising a refill time before checking stock and the transaction data.

2. Treating a SKU rationalization change as closed business instead of confirming it did not remove a safety item without a substitute.

3. Skipping the safety classification check on a missing item because it looks routine.

4. Letting the customer's suspicion about cost cutting derail the fact finding instead of addressing it head on once you have the facts.

5. Changing vending configuration on your own to fix the problem without the customer's sign off, even when the fix seems obvious.

Each of these turns a fixable configuration issue into a trust issue, and trust issues take a lot longer to repair than a reorder setting.

How to practice and score it

A manager coaching this conversation should hand the rep three missing items of different types and ask them to sort each one by urgency and by what evidence would close it out. A rep who can say which item needs an EHS call within the hour and which one can wait for the weekly storeroom review understands the actual skill here, not just the script.

When you review a rep's escalation note after a call like this, check for five things. Did they name the specific item and SKU. Did they capture the shift pattern that shows when it runs out. Did they name a safety owner if the item carries a PPE requirement. Did they cite an inventory source instead of a guess. Did they assign a configuration owner and a date for the fix.

Rehearsing this scenario against an AI counterpart, the kind used in DealSpeak, lets a rep hear an irritated production manager push back on a vague answer, then practice giving a factual update instead of an empty promise, before they try it on a live account. Score the rep who says they will confirm and report back by a specific time higher than the one who says they will make sure it gets fixed without naming who does what. The same discipline, verify before you propose a remedy, shows up in a different setting in Plan an Oven Temperature Survey Before Proposing a Remedyand the habit of checking what a number actually measures before you argue from it is covered in Align OEE Definitions Before Using the Number in an Evaluation.

Closing the loop

A vending complaint about missing gloves is rarely about the gloves. It is about whether your reorder settings still reflect how the plant actually runs, and whether you will tell the customer the truth about that before you promise a fix. Check the evidence first, and the delivery time you give will actually hold.