How to automate returns in wholesale without re-booking anything by hand

A return at a wholesaler passes through four departments, and each one types in something another department already typed. Customer service takes the email, the warehouse books the receipt, accounting issues the credit note and clears the open item, purchasing files a claim with the supplier for anything defective. If you want to automate returns, you can speed up each of those desks on its own. The bigger saving comes from removing the handovers between them, because that is where data gets re-entered and cases stall. A chain of agents that pass the case along to each other does exactly that.

The example below is constructed. It shows how we would build such a chain and does not describe a client project.

Automating returns: an electrical wholesaler as the example

Say an electrical wholesaler supplies around 400 installation contractors from one central warehouse. Orders, delivery notes, invoices and open items live in the ERP, and the books are kept in DATEV. Returns arrive by email in the customer service inbox, rarely with a form.

On Monday morning an electrician writes: "Two boxes of cable trunking from last week's delivery are coming back, we ordered too much. Also one of the RCDs is faulty, trips the second you switch it on. Please arrange collection." No invoice number, no item numbers, no quantities in units.

That email holds two returns heading in different directions. The trunking is new stock and goes back on the shelf after a visual check. The RCD is a defect the wholesaler passes on to its own supplier, who will refund it, provided somebody actually files the claim.

By hand: the same data, entered five times

Without automation, customer service looks up the delivery and finds two deliveries to this customer the week before. They phone to find out which one, open a return case and copy items and quantities from the delivery note. They book a pickup with the parcel carrier. The warehouse receives the parcel into blocked stock and writes its findings on a slip. Customer service uses the slip to write the credit note. Accounting matches the credit note to the invoice and discovers on the way whether that invoice was already paid. At some point the warehouse moves the trunking from blocked to available stock. And if anyone tells purchasing, they file a claim for the RCD.

Customer, item, quantity and price get typed or looked up five times, and every desk waits for the one before it. The tail end is what slips most often: releasing the blocked stock, clearing the invoice, claiming from the supplier. Nobody feels responsible for those steps, because the customer already has their credit.

With an agent chain: five links

The chain has five agents. Each one reads from a fixed input, does one job and writes to a fixed output. Whatever it cannot decide with certainty goes to a person.

1. Registration: read the email, find the delivery

The first agent recognises the customer by the sender address and pulls their deliveries from the last 30 days. Only one delivery note contains both trunking and RCDs, so the match is clear. It takes item numbers, delivered quantity and packing unit from that note. "Two boxes" becomes 40 pieces because the delivery note lists 20 pieces per box.

It splits the case into two lines with separate reasons, over-ordered and defective. It books a pickup through the carrier's API and drafts a reply to the customer with the return number, the pickup day and a request for a photo of the RCD's rating plate. The reply goes out once customer service approves it.

The wholesaler decides once on the return window, the restocking deduction and whether credit is issued before or after inspection. The agent applies those rules and notes which ones it used. A return outside the window lands on the review list.

2. Goods receipt: compare instead of retyping

When the parcel arrives, the warehouse scans the return number. At the packing bench the second agent shows what is expected: 40 pieces of trunking, one RCD, a reason for each. The warehouse worker confirms the quantity and picks a condition such as "as new", "damaged" or "supplier claim". Whether goods can be resold is the call of the person at the bench, and the agent makes sure that call is recorded in the case.

If the box holds 30 pieces instead of 40, the difference shows up in the case right away, not three days later on a credit note that doesn't match the goods.

3. Credit note: price from the original invoice

The third agent creates the credit note in the ERP as a draft. It takes the price from the invoice for that delivery. The current price list would be wrong the moment the list price has changed since then. If the customer had a special price or a line discount, it is on the invoice and carries over. For the trunking it subtracts the agreed restocking deduction, if the wholesaler charges one. For the faulty RCD it doesn't.

Every line carries a note saying where the value came from. Customer service reviews the draft and approves it.

4. The follow-up bookings: stock and open items

After approval, the fourth agent does the work that normally sits on someone's desk. It moves the trunking from blocked to available stock so it can be sold again. It checks the invoice in open items. If the invoice is still open, it clears it against the credit note. If it has been paid, it proposes to accounting either offsetting against the next invoice or paying out, depending on what was agreed with the customer. If the customer took an early payment discount, the agent factors that into the refund, so the customer doesn't get back more than they paid.

The postings go to DATEV with the usual batch export. Nobody has to chase returns at month end.

5. Claim against the supplier

The fifth agent takes the RCD. It finds the purchase order through which the wholesaler bought the unit and uses that supplier's claim channel, whether that is an API, a form in the supplier portal or an email to the claims address. It attaches the customer's fault description, the photo and the purchase document, opens the return to the supplier as its own case and tracks whether a credit or a replacement comes back. If nothing arrives, it reminds purchasing after the agreed period.

By hand, this is the step that gets skipped most. Nobody enjoys spending half an hour on a form for a 60 euro switch. Across a year and every customer, that adds up to money the wholesaler is owed and never collects.

What is left for your team

Customer service approves two things, the reply to the customer and the credit note. The warehouse picks a condition at the bench. Accounting only sees cases where a paid invoice needs a refund or an offset. The customer gets the return number and the credit note by email and has no reason to call and ask.

The review list collects returns without a matching delivery, goods nobody registered and returns past the deadline. Who decides those, we agree with you before building. The groundwork questions behind it, such as which price belongs on the credit note, are covered in our article on returns automation.

How we build the chain

We don't build all five links at once. The first one, registration tied to a delivery, pays off most because every later step works from a clean case. An agent takes one to two days to build, and testing with real return emails happens in the same week. The other links follow in stages, each measured in days.

Sophera Consulting builds agent chains like this at a fixed price and without a subscription, and you own the result. Beforehand we walk through real returns with customer service, the warehouse and accounting and write down which deadlines, deductions and responsibilities apply. Every chain comes with a maintenance agent that watches the interfaces to the ERP, the carrier and the supplier portals and tests any change against past cases. It is included in the fixed price, and the only running cost is usage of the AI models. Whether it pays off for your return volume is something we work out in the free automation check.

Our recommendation

Take ten returns from last month and follow each one to the end. Was the stock released? Was the credit note cleared against the invoice? Was faulty stock claimed from the supplier? Wherever the answer is "no idea", that is where your money is. If supplier claims are what's mostly missing, start with link five. Otherwise start with registration, since everything else builds on it.