Leak 26 · Inventory & Working Capital - Returns sitting unresolved
A pallet of returns in the corner of the warehouse. Some restockable, some for the supplier, some scrap. All of it counted as nothing, or as full value, depending on the day.
Diagnostic note. Symptoms, required records, an initial check, and possible fixes. This shorter note does not include a full worked example.
What is it?
Customer returns arrive, get set aside for inspection, and wait. Meanwhile the customer is waiting for a credit, the restockable items are not available to sell, the supplier return window is closing, and the inventory record is wrong in one direction or the other. The leak is the value stuck in the queue and the customer friction caused by slow credits.
- Family
- Inventory & Working Capital
- Primary owner
- Warehouse Manager
- Secondary owners
- Customer Service Manager, Controller
- Primary impact
- Working capital
- Typical data source
- Return authorizations, receiving records, credit memos
- Detection difficulty
- 30-day measurability
Ask yourself
How many customer returns are physically in the building but not yet inspected, restocked, credited, or sent back to the supplier?
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.
- A returns area that is never empty.
- Customers calling about credits weeks after returning goods.
- RAs open for more than 30 days.
- Returned goods restocked without inspection, or scrapped that could have gone back to the supplier.
What data do I need?
The minimum viable set. Most of it is already in your ERP.
| Field |
|---|
| Open RAs with issue date, received date, and status |
| Value of returned goods by disposition |
| Credit memo dates versus receipt dates |
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 RAs open for more than 30 days and total their value.
- 2Walk the returns area and estimate the value on the floor by disposition: restock, supplier return, scrap.
- 3Check the average days from receipt to credit memo for last month.
Stuck value = Σ open RA value > 30 days; credit lag = average days from receipt to credit
Then ask one question: Who owns a return from the moment it arrives until it is resolved?
How much could it be costing us?
A conservative range, not a headline. The goal is a number management can trust enough to investigate.
Value stuck in returns × carrying cost rate, plus supplier returns missed because windows closed, plus customer friction (not quantified)
Common root causes
Fixes fall into three layers. Not every problem needs software, and almost none needs AI first.
- Process
- No owner for returns and no service standard for resolution.
- Data
- Return status is not tracked beyond “RA issued.”
- Technology
- Returns are processed outside the system until the credit memo, so the queue is invisible.
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
Visibility
A weekly open-returns report by age and disposition.
Level 2
Process
A five-day standard from receipt to disposition, with a named owner.
Level 3
Workflow
Return receipt, inspection, disposition, and credit tracked as one workflow with status visible to customer service.
Where AI helps
- Drafting customer credit communications and matching returned items to the original order when paperwork is missing.
Where AI probably doesn’t
A weekly report and an owner clear most return backlogs.
Before you call it a leak
- Fast credits without inspection create a different leak. Keep the inspection, shorten the queue.
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 16 · SuppliersUnclaimed vendor returnsMany suppliers allow an annual return of slow stock, often a percentage of purchases. The window passes. The stock stays on the shelf.
- Leak 36 · OperationsPreventable order errors and creditsWrong item, wrong quantity, wrong price, wrong address. Each error costs a credit, a return, a reship, and a customer’s patience. The reason codes, if they exist, tell you exactly where.
- Leak 21 · InventoryDead and obsolete inventoryInventory with no demand and no prospect of demand. It is on the balance sheet at cost, and it will never be worth that again.
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.