Returns management software is the system that records, checks and disposes of goods a customer sends back, so that the stock count and the refund both end up right. It covers the whole return, from the first request through to restock, refund or write-off. In the UK the rules for online returns come from the Consumer Contracts Regulations 2013, and GOV.UK summarises what a seller must do in its guidance on accepting returns and giving refunds. Most UK operations split this work between two tools: a customer-facing returns portal that handles the request, and a warehouse system that handles the physical goods. Knowing which of the two you need, and where they should connect, is the starting point for choosing.
What returns management software does
Returns management software controls the reverse flow of goods. It approves a return, links the returned item to the original order, records its condition, decides what happens to it next, and closes the order with a refund, credit or replacement.
Reverse logistics is the broader term for moving goods back from their usual endpoint, and returns are one part of it (our guide to the reverse logistics process covers the wider flow). The software has to keep every stage of a return traceable, because the question a customer or finance team asks later is always the same: what happened to this item?
Each stage of a return should leave a record behind, as the table below shows.
| Stage | What happens | What the software must record |
|---|---|---|
| Request | Customer asks to send an item back | Original order, item, reason, whether the return window is open |
| Authorisation | The return is approved or refused | Return reference, decision, who approved it |
| Transit | The parcel travels back by carrier or drop-off | Return label, carrier, tracking number |
| Receipt | The item is scanned in at the warehouse or returns site | Scan time, operator, match to the original order line |
| Inspection and grading | Condition is checked and recorded | Condition code, photos where needed, batch or serial number |
| Disposition and close | Restock, hold, supplier return or disposal; refund or credit | Destination, stock status, refund or credit value, close date |
How UK consumer rules set your returns timescales
For most online sales in the UK, a customer can usually cancel within 14 days of receiving the goods under the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013. GOV.UK’s guidance on accepting returns and giving refunds says a business must refund the customer within 14 days of receiving the item back. Faulty goods fall under a separate set of rights in the Consumer Rights Act 2015.
Those clocks are the reason a returns tool needs a timestamp on every step. A late refund becomes a complaint, and you cannot defend a timescale you did not record.
Customer-facing portals and warehouse-side processing do different jobs
Many buyers search for returns software expecting one product. In practice, a returns portal and a warehouse returns process solve different problems, and the best setup often uses both.
| Dimensjon | Customer-facing returns portal | Warehouse-side returns processing |
|---|---|---|
| Main users | Customers and customer service teams | Warehouse operatives and stock controllers |
| Starting point | A return request and its reason | A parcel or pallet arriving at the dock |
| Main output | Approved return, label and refund instruction | Verified stock record, condition and disposition |
| Typical risk if missing | Long email chains and manual approvals | Returned stock lost, sold as new, or stuck in limbo |
| Where it sits | In front of the order and the carrier | Inside the warehouse, next to stock and orders |
A portal answers the question “can this customer send this item back, and how?” A warehouse process answers “what exactly came back, can it be sold again, and where is it now?” If you buy only the portal, a person still has to check the parcel and update stock. If you buy only warehouse software, customers still email you about every return.
Clarus WMS does not include a customer-facing returns portal today. It is a warehouse management system, so the rest of this guide focuses on the warehouse side and on how the two halves should work together.
How a warehouse management system handles returns
A lagerstyringssystem (WMS) is the system of record for stock, so every returned item has to re-enter it correctly or the count drifts. A WMS does not decide whether a refund is due. It decides where the item goes, whether it can be sold again, and what the stock record says while it waits.
Mathew Buttar, Head of Solutions at Clarus, explains two behaviours that matter here. Stock placed on hold records the reason, who placed the hold and when, and a release is recorded in the same way. A storage unit reference can also come back into the system once its stock has been fully dispatched, so the history of a returned pallet or carton stays linked to what left the warehouse.
In practice, a returned item goes into a quarantine location or onto a hold status until someone has checked it. Clarus sets this up as an automation: stock put away into quarantine is placed on hold automatically, and held stock cannot be allocated to any task until it is released. The event triggers and automations feature is what makes that rule run without someone remembering to apply it.
Traceability depends on what you capture at receipt. Clarus can record serienumre on arrival, on dispatch or both, and batch control can be switched on product by product. That lets a returned item be matched to the batch it originally shipped in, which matters if a recall is raised later.
Scanner flows can also carry simple checks. Clarus lets you rename generic fields in the handheld flow as text, number or yes/no fields, and each entry is stamped with the date and time of the transaction. A yes/no field such as “undamaged” is a check, not a grading engine. It records the answer, but it does not decide the outcome for you.
Clarus does not have a dedicated returns module today. A returns workflow in the WMS is a process you design with us from these building blocks, rather than a setting you switch on. Ask any vendor, us included, to run that workflow on your own products before you commit.
Features your returns software should have
Use this list when you write requirements. Not every operation needs every item, but each one answers a question that will come up sooner or later.
- An RMA or return reference matched to the original order and line. A return that cannot be tied to an order line will be booked against the wrong stock.
- Return labels and tracking. Labels created from the return request, with the carrier and tracking number stored against the return. For the outbound side of the same process, see our programvare for fraktadministrasjon veiledning.
- Scan-based receipt. The item is scanned against its order before stock is updated, so the system checks what actually arrived.
- Condition codes and evidence. A standard set of condition codes, with photos where a dispute is likely.
- Disposition rules. Each product or return reason has a default outcome, such as restock, quarantine, supplier return or disposal. Stronger tools choose the outcome with the highest recovery value for each item, rather than applying the default every time.
- Restock only after checks. Only items that pass their checks return to pickable stock, so a damaged return never reaches a pick face.
- Quarantine and hold, with reasons. Held stock cannot be allocated to an order, and each hold records why it was placed and by whom.
- Lot and serial traceability. A returned item can be matched to the batch or serial number it shipped with, which matters in a product recall.
- Refund or credit triggers. A refund or credit is raised from a confirmed receipt, not from the customer’s claim alone.
- Client billing for 3PL returns handling. Returns work is charged to the client it belongs to, and the charge can be traced back to the activity.
- Reporting on return reasons. Return rates and reasons by product, carrier and client, so you fix the cause rather than the symptom.
Is there free returns management software?
Some vendors offer free trials or limited free tiers, but we have not verified a free option that covers a full warehouse returns process. Most returns tools do not publish list prices, so expect to ask for a written quote. When you talk to a vendor about a free tier, ask what it includes, how you export your data if you leave, and what the first paid tier costs.
Choosing returns software for ecommerce and 3PL operations
Ecommerce brands should start with the order. A return is only useful if it links back to the order and line that created it, so check how any returns tool receives orders and sends refund instructions back. For the order side of the picture, see our order management software veiledning.
On the platform side, Clarus connects to Shopify og WooCommerce, and to more than 70 shipping providers, including DHL, UPS, FedEx and Royal Mail.
If your stock is spread across several channels, the accuracy of what goes back on the shelf matters as much as the return itself. Our guide to programvare for lagerstyring for netthandel covers that side, and the best WMS for ecommerce page is the place to start if you are comparing full warehouse systems for online sales.
For 3PLs the picture changes. Each client may have its own rules for accepting returns, checking them, charging for the handling and reporting on them. Clarus was built for that: each client’s stock, reporting and billing are kept separate within one warehouse, and the selvbetjeningsportal for kunder lets clients see stock levels and order status without phoning the warehouse.
Where Clarus WMS fits for 3PLs, and where it does not
Clarus is a strong option when the warehouse side of returns is the problem: stock goes missing after goods come back, returned items reach pick faces before anyone has checked them, or several clients share one site and each needs its own rules. Our 3PL WMS page sets out the multi-client features in more detail. Clarus is also a member of the UK Warehousing Association.
JODA Freight, a 3PL, reached 99% stock accuracy by year two, after its stock takes went from weeks on Excel to a single day. Accurate stock is what makes a returned item trustworthy once it goes back into the count. The JODA Freight story sets out how that worked in practice.
Clarus is a poor fit if your main need is a consumer-facing returns portal, if your returns are single parcels with no warehouse handling step, or if you want a standalone returns tool without a WMS. Test the workflow against your own returns before you decide.
Snakk med en lageransvarlig
Hvis du vurderer ulike alternativer og ønsker å se hvordan et spesialutviklet lagerstyringssystem (WMS) fungerer i praksis, er Clarus verdt å ta en prat med. Vi samarbeider med 3PL-leverandører og distributører over hele Storbritannia for å implementere lagerstyringsprogramvare som tilpasses din driftsmodell – ikke omvendt.
Ta kontakt med teamet vårt å snakke gjennom dine krav.