The Hidden Complexity of Returns
When a customer returns a product, it seems simple: refund the money, put the item back on the shelf, increment the count. But in practice, returns introduce multiple opportunities for inventory errors.
Where Returns Create Inventory Errors
1. Returned but Not Restocked
The most common error. The refund is processed in Clover, but the returned item sits in a bin behind the counter for days before anyone puts it back on the shelf. During that time, the POS shows it is in stock, but it is not on the sales floor where customers can find it.
2. Different Item Returned
Customer returns a "blue shirt, size L" but actually puts a "blue shirt, size M" in the bag. If no one checks, your L count goes up (incorrectly) and your M count stays the same (when it should go up). Both SKUs are now wrong.
3. Damaged Returns
A returned item that cannot be resold should not be added back to sellable inventory. If it is automatically re-added by the POS refund process, your counts are inflated. These items need to be categorized as damaged and written off separately.
4. Receipt-Free Returns
Returns without receipts are particularly risky. Without a receipt, it is harder to verify what was originally purchased, when, and at what price. Some merchants accept these returns as a customer service policy, but they need extra scrutiny.
Best Practices for Return Inventory Management
Inspect Every Return
Before processing the refund, physically verify the item matches what the customer says they are returning. Check the SKU, condition, and quantity.
Restock Immediately or Track Separately
Either restock the item on the shelf immediately after processing the return, or create a designated "returns to be restocked" area that is counted and cleared daily.
Separate Damaged Returns
Create a process for returned items that cannot be resold. These should be written off as damaged and removed from inventory, not put back in the sellable count.
Audit Return Patterns
Monitor return rates by product, by employee processing the return, and by time period. Unusual return patterns can indicate fraud (both customer and employee).
How This Connects to Auditing
Your regular inventory audits will naturally catch return-related discrepancies. But if you find recurring overages (more stock than expected) in certain products, look at your return process first. Overages from unverified returns can mask real shortages elsewhere.
Clean return processes keep your inventory accurate between audits. Sloppy return processes create noise that makes it harder to identify real problems.