Every distributor gets stock back — a wrong pick, damage in transit, a customer who over-ordered, or short-dated stock they won't accept. It's rarely the volume that causes the problem; it's that returns sit outside the normal order flow, so they get handled however whoever's on the loading dock that day decides to handle them. The stock goes somewhere, a credit gets promised, and a week later nobody can say for certain whether the customer's account, the stock count, or the driver's memory is the one that's right.
Why ad hoc returns quietly cost money
A return that isn't recorded against the original order creates three separate risks at once. The stock might sit in limbo — not on the shelf, not written off, just missing from the count until the next stocktake turns up a variance nobody can explain. The credit might get promised verbally and never actually raised, which the customer notices on their next statement even if you don't. Or the stock gets put straight back into stock on hand without anyone checking whether it's actually still resalable, which just delays the write-off to whoever orders it next.
What a proper returns process actually needs
Whatever your specific policy, the mechanics underneath a return are the same:
- A record that ties the return back to the original invoice and order line, not a fresh line item nobody can trace
- A resalable / not-resalable decision made before stock is adjusted — not assumed
- A credit note raised against the terms you actually run — full credit, restocking fee, exchange only, whatever the case requires
- A stock adjustment that reflects the real outcome — back on the shelf, quarantined, or written off — logged the same way as any other stock movement
Run this way, a return isn't a separate process bolted onto the side of the business — it's the same order and stock data everything else runs on, just moving in the other direction.
Where it gets harder: short shelf-life stock
For food and beverage distributors, a return isn't just a resalable/not-resalable call — it's a resalable-by-when call. Stock that's genuinely undamaged can still be too close to expiry to put back into general circulation, and putting it back on the shelf under normal FEFO rotation only works if the system actually knows which batch it came from. That's the same traceability that matters for a recall — see our guide on batch and lot traceability — applied in reverse, on the way back in rather than the way out.
Returns still have to reach your accounts
A credit note that only exists in your ERP isn't finished — it needs to reach the customer's account and your books the same way a normal invoice does. Cognit sends invoices, credit notes, customers and products to Xero as you trade, which covers credit notes raised against returns the same as any other credit note — see do I still need Xero if I have an ERP? It's a one-way push from Cognit to Xero, so the return shows up correctly without anyone re-entering it, and it still counts against the customer's credit limit and trade terms the way it should.
Built around the returns policy you actually run
Restocking fees, who authorises a credit, whether damaged stock needs a photo before it's accepted back — every distributor's returns policy is a little different, and a generic "process a return" button rarely matches what a business actually requires. Rather than force your team into someone else's workflow, we build the returns and credit note process your business runs into your Cognit system, tied to the same stock, orders and accounts as everything else. Tell us how returns work today and we build it properly around that.
Stop reconstructing returns after the fact
If returns in your business currently mean a driver's note, a verbal promise of credit, and a stocktake variance nobody can fully explain, it's worth working out what the process should actually look like before it costs you a customer relationship or a write-off you didn't see coming. See pricing or get in touch to talk through how returns run in your business today.
Frequently asked questions
What counts as a "return" for a wholesale distributor, and why does it need its own process?
Wrong item picked, damaged on delivery, short-dated stock a customer won't take, or a straightforward over-order — each is a return, and each needs the same three things sorted out correctly: whether the stock is resalable, what the customer is owed, and a record that ties both back to the original order. Treated as one-off admin instead of a defined process, distributors end up with credit notes that don't match what physically came back, and stock that's neither properly on the shelf nor properly written off.
Does Cognit generate credit notes automatically for returns?
The trigger and the terms are specific to your business — some distributors credit on collection, some on inspection, some only above a certain value. Rather than force one fixed returns workflow, we build the credit note process into your Cognit system around the rules you actually use, tied to the original invoice so there's no separate reconciliation step to get wrong.
Does returned stock go straight back into stock on hand?
Not automatically, and it shouldn't. A return needs a resalable/not-resalable decision before it affects stock on hand — putting damaged or compromised stock straight back on the shelf just moves the problem to the next customer who orders it. Cognit's stock adjustments record that decision explicitly, so what's actually sellable is what the system — and your online store — shows.
What about short shelf-life or food stock — can it always go back into stock?
Only if it genuinely still has saleable shelf life left, and only if you can trust the batch or lot it came from. That's where returns depend on the same traceability as the rest of the warehouse — see our guide on batch and lot traceability. Stock that's too close to expiry to sell on needs to be written off, not quietly returned to the same shelf under FEFO rotation.
Does a returned-stock credit note flow through to Xero automatically?
Yes, in the same direction as everything else. Cognit sends invoices, credit notes, customers and products to Xero as you trade — that includes credit notes raised against returns. It's a one-way push from Cognit to Xero, so your books reflect the return without anyone re-keying it.
