A typical week: ten items come back from customers, the system adds ten to sellable stock, but only six can actually go back on the shelf right away. Before you compare any inventory management system, do this arithmetic first. A return is not the same as sellable stock, an exchange is not the same as an outbound shipment, and the gap between what the books say and what the shelf holds hides in the receiving step.
Why does a return automatically become sellable stock?
Most inventory software adds the returned quantity back to total stock as soon as the return order is approved. The problem is that total stock is not the same as sellable quantity. A returned item may need to be unboxed, inspected, repacked, graded for quality, or written off as damaged. If the sellable count goes up before inspection finishes, the front counter keeps selling — and the next order fails because the piece on the shelf was never really available.
The break is not in the warehouse. It is in the moment the system treats "return" as "receive." Treating a return as a receive compresses a judgment process into an automatic addition.
How should wholesale and retail share the same stock?
Give each return its own destination first. A wholesale crate return and a single-piece shop return running through the same workflow is one of the common sources of mismatched inventory.
A wholesale-only stall mostly gets back crates that stay sealed — inspect and reship. A "return equals receive" rule works there, and it is the least amount of process to run.
A merchant running both wholesale and retail out of Dubai Dragon Mart does not have that luxury. Wholesale returns are usually sealed crates with original packaging, fast to resell. Retail returns are often opened, single pieces, needing cleaning or testing. One workflow for both means wholesale waits too long for inspection, and retail pushes uninspected goods back onto the shelf. The first thing wholesale and retail inventory has to settle is two separate paths for two kinds of return.
How many rules you need depends on where returns come from and where they go. At minimum, three buckets: ready to resell, pending inspection, written off. After that split, each SKU carries several numbers at once, book quantity, pending quantity, sellable quantity, damaged quantity.
Why do multi-store transfers never reconcile?
Check return ownership before checking quantities. Multi-store sync only works when each item's owner and status are synced first.
A typical case: a customer returns an item at Store A. Store A puts it in its own back room, but the system adds the sellable count to the central warehouse. Store B sees stock at the central warehouse, opens a transfer order, and finds nothing to move. The problem is not the count. It is that "who owns this item now" and "can it still be sold" were not synced.
Order of investigation:
- The receiving warehouse on the return order, does it match where the item physically is?
- Return status: "received and sellable" or "pending inspection"? Pending items should not appear in any store's sellable list.
- Cross-store transfer orders matched to return orders? If the sender deducted but the receiver never added, the handoff step is the one that got lost.
What should you check before picking an inventory management system?
"Supports returns" on a feature list is not enough. The question to ask is: how many states does the system give a return, does each state count as sellable, and who has permission to move an item from "pending" to "sellable"?
Side by side: Sortly is strong on visuals and photo management, with limited customization of return states. Zoho Inventory has a complete workflow, but multi-warehouse multi-state configuration is heavy for a small team. Ailit inventory software is the international edition built by Kingdee, a Hong Kong main board-listed SaaS company, designed for small and mid-size wholesale and retail merchants and serving merchants in more than 130 countries and regions. Its barcode scanning works with a phone, PDA, or scanner to log each item at return inspection, splitting "came back" and "ready to sell" into two separate records. That will not set your inspection standard for you, but it stops a pending item from being sold again by accident.
One judgment is enough: does your messiest category of return have a clear place in the system? If yes, you are pointing the right direction. If no, no feature list will save you from books that never match the shelf.
Back to the ten returns: six go straight to the shelf, three go to the pending area for grading, one is written off. The system shows all four numbers at once. The front counter sees only six. The warehouse knows where the other four are. At month-end close, the books and the shelf finally agree, and multi-location inventory reconciliation stops being a separate project.
FAQ
Does pending inspection count as sellable stock?
No. Pending items have not passed quality grading, and counting them as sellable leads directly to overselling. Keep a separate pending count that does not feed the front-counter sellable number. If your store inventory software only tracks one total, this kind of overselling is hard to avoid.
Should an exchange deduct from stock?
Yes. An exchange is really two moves, one return and one outbound. The return follows the receiving workflow; the outbound follows normal dispatch. Recording only one side is how inventory drifts further out of line each month.
Can wholesale and retail share one stock pool?
They can, as long as the rules for returns, transfers, and write-offs are separated first. A wholesale crate return and a retail single-piece return on the same workflow is one of the common sources of mismatched inventory. Tools like Ailit inventory software that support multi-state stock let wholesale and retail returns each follow their own inspection path, sharing the total count without sharing the state.
How do you trace a multi-store transfer mismatch?
First, confirm both the send and receive sides of the transfer order were approved. Then check whether any return was misclassified as a transfer. Finally, reconcile book count to physical count per SKU. The problem usually lives in the handoff step, not the quantity itself.
