Returns management software: controlling the flow back

Authorisation defines the funnel

An authorisation records what the customer intends to send back, against which original order, for what reason, and under which policy. It generates the reference the receiving site will use to identify goods that would otherwise be anonymous. Systems differ in how strictly they enforce it: strict authorisation improves receiving accuracy but frustrates customers, while accepting anything creates a receiving area full of unidentifiable items. Most retailers land somewhere between, with automatic approval inside policy and review outside it.

Routeing: not everything should come back to the warehouse

Disposition can be decided before the goods move. Low-value items may be better written off than transported; items needing testing should go to a repair partner; sealed goods in resaleable packaging can return to the main stock location; regulated items may have a mandated route. Encoding these rules cuts transport and handling cost more than any efficiency gained in the returns bay. It also prevents the common pattern where every return arrives at the central site and is then shipped onwards to where it should have gone directly.

Grading, and separating credit from stock re-entry

On arrival, goods are identified, inspected and graded into dispositions such as return to sellable stock, refurbish, discount channel, return to supplier, or destruction. Grading rules should be explicit enough that two operators reach the same conclusion, because grading determines recovered value. Crucially, the credit decision and the stock decision are independent: many businesses credit on receipt for service reasons while grading later, and the system must support that without treating an ungraded item as available inventory.

Cross-border returns carry duty and tax consequences

Goods returning across a customs frontier are a customs event, not merely a transport movement. Relief mechanisms exist in many territories for goods returned in an unaltered state within defined conditions, and there are separate procedures where goods were exported under a specific regime or are being sent for repair. Eligibility, evidence and time limits are set nationally, so the process must capture the original export details and the returns system must retain them. Confirm the treatment with the relevant customs administration before designing an automated flow.

The analytics that pay for the system

Return reasons collected at authorisation, joined to grading outcomes, product data and recovered value, show which products, suppliers, size ranges or descriptions generate avoidable returns. That analysis funds itself in merchandising and content changes rather than in logistics savings. It only works if reason codes are meaningful to the customer, few enough to be chosen honestly, and mapped consistently to what inspection actually found, since a reason recorded as not as described and graded as unused tells a different story from one graded as worn.

Frequently asked questions

Should returns be handled in the warehouse system or separately?

Receiving and grading belong in the warehouse system, since that is where stock states live. Authorisation, customer communication and disposition policy often sit in a returns or order layer, with a clean handover of the authorisation reference.

When should the customer be credited?

That is a commercial policy with a cost, not a system default. Crediting on despatch or on receipt improves customer experience and increases exposure to items that never arrive or arrive unusable, so whichever is chosen should be measured against actual grading outcomes.

How are returns of goods sold through several channels kept straight?

By tying every authorisation to the original order and its channel, and by keeping channel-specific policies as configuration rather than as separate processes. Otherwise the same item returns under different rules depending on who received it.