Why vendor returns quietly lose money
Picture a specialty store on a Thursday. A case arrives with six cracked items. The stock clerk sets them on a back shelf, writes "RETURN" on the box, and emails the sales rep from a personal inbox. Three weeks later the owner is reconciling the vendor statement and asks a simple question: did we ever get credit for that case? Nobody knows which purchase order it came from, whether the vendor issued a return authorization number, whether the box shipped, or whether the cracked items are still counted as sellable stock. That scene is an illustration, not a TwoQM client.
Most small retailers handle vendor returns. The weak spot is that the return lives on a shelf and in an email thread instead of on the purchase order line it came from.
TwoQM has already written about keeping online and in-store inventory numbers in sync. That piece is about counts across channels. This one is narrower: what happens when stock has to go back to the supplier, and how to make sure the credit actually comes back to you.
Here is an original example, not a measured result. A two-location store returns damaged, mis-shipped, or overstock goods to a dozen vendors. Each vendor has its own process: some want a return authorization (RA or RMA) number before anything ships, some want photos, some issue a credit memo, some send a replacement instead. Without one record per return, the common failures look like this:
No link to the PO. The return cannot be matched to what was ordered, received, and invoiced.
No RA number logged. The box ships without the vendor's reference, and the vendor cannot find it on their side.
Stock stays "sellable." Items waiting to go back still show as available, so counts and reorder points drift.
The return window passes. Vendor terms often set a deadline; nobody is watching it.
The credit never gets matched. A credit memo arrives, but nobody ties it to the original invoice, so the statement never balances.
Start every return from the purchase order line
The fix is to open a vendor return from the PO line, not from a sticky note. Every return record carries the same fields:
PO number and line. SKU or item, quantity received, unit cost on the PO.
Quantity returning and reason. Damaged, wrong item, overshipped, defective, or overstock, using reason codes your store defines.
Evidence. Photos of the damage and the packing slip, attached to the record.
Vendor RA number. Plus the date it was requested, the date it was issued, and who at the vendor issued it.
Return window. The deadline from that vendor's terms, entered by a person who read them.
Shipping. Carrier, tracking number, ship date, and who packed it.
Expected outcome. Credit memo, replacement, or refund, and the amount or quantity you expect.
Actual outcome. Credit memo reference and amount, or replacement received, plus any restocking fee the vendor applied.
Give each record a status your staff can read at a glance: flagged, RA requested, RA issued, packed, shipped, credit pending, credit matched, closed, or denied. Your store decides the labels; the software only enforces the structure you set.
Keep the stock honest while it waits
The moment a return is flagged, move those units to a non-sellable location such as "vendor return hold" in your inventory or POS system. They are still on your books, but they should not appear on the website or the shelf count. When the box ships, they leave inventory against the PO line. When a replacement arrives, it is received against the same PO so the trail stays in one place.
Match the credit to the original invoice
A return is not finished when the box leaves. It is finished when the credit or replacement is matched to the original PO and invoice. Someone on your team should own that match, and the record should show who confirmed it and when. How credits post in your accounting system is a decision for you and your bookkeeper; the return record simply makes the evidence easy to find.
Where connected systems and automation help
Purchase orders often live in one tool, stock counts in the POS, vendor emails in an inbox, and credits in accounting software. Connected systems can link those to one return record so nobody retypes the PO line or hunts for the RA email. Ordinary business automation can handle the reminders:
RA requested but not issued after the number of days your team sets.
Return window closing for anything still sitting on the hold shelf.
Shipped but no credit after the period you expect from that vendor.
Credit received but unmatched to its original invoice.
Where AI helps, and where it stops
AI can draft an RA request email from the PO line, reason code, and photos, summarize a long vendor reply into the next step, and prepare a Spanish version for bilingual staff. A person reviews every draft before it goes out. AI does not approve returns, decide whether a vendor owes a credit, mark a credit as received, or change inventory counts on its own.
Where to start this week
Walk to your back shelf and list every item waiting to go back to a vendor. For each one, try to write down the PO number, the RA number, the return deadline, and the credit you expect. If that list takes an afternoon of digging through email, start with one return record per PO line and a status everyone can see.
TwoQM builds connected systems, automation, and custom software for retail and ecommerce businesses. If vendor returns are costing you credits you never chase, TwoQM can scope a return workflow around the POS, inventory, and accounting tools you already use. Pricing explains how business apps, systems, and custom software are scoped.
Describe Your Vendor Return Workflow · Explore TwoQM connected systems