Scoping the backward flow with a provider

The return leg is rarely designed at the same time as the outbound one

Solution designs are built from forward volumes, because those are what the sales plan produces. Returns then appear as an operational reality with no agreed process, no agreed rate and no agreed space. The fix is unglamorous: estimate the backward flow as its own volume stream, decide where it is handled, and give it a line in the pricing schedule even when the assumed volume is modest.

Authorisation, and the consignment nobody expected

Unannounced arrivals are the costly case. A provider receiving goods with no reference cannot book them anywhere, so they sit as unidentified stock while someone investigates. Agreeing an authorisation mechanism, a reference that travels with the goods, and a defined holding process for unidentified arrivals turns a recurring investigation into a routine exception. It also decides who bears the cost of storing goods that should never have been sent.

Ownership of what comes back

Returned units may belong to the client, to a customer awaiting credit, or to a supplier under a recall. Each status implies different handling, different record keeping and a different answer on who absorbs the loss if the goods are unsellable. Where the provider is asked to scrap or donate stock, the authority to destroy someone else's property should be explicit, along with the evidence the provider must retain.

Cross-border returns need a separate answer

A unit going back across a customs frontier is an import into somewhere, and relief for goods being returned generally depends on procedure, evidence and timing rather than on intent. Whether a provider can act in that process, and under whose authorisation, is a customs question rather than a warehousing one. Establish the position with the customs authority for each corridor before promising customers a return route, and keep the paperwork obligations inside the scope you buy.

Frequently asked questions

Why does return handling cost more per unit than despatch?

Because the work is unpredictable and cannot be batched in the same way. Each unit needs identifying, inspecting and a decision made about it, arrivals come in irregular quantities, and packaging is often damaged. Effort per unit is high and the flow does not smooth.

Should returns be handled at the fulfilment site or somewhere else?

It depends on volume and on how quickly stock must be resold. Handling them where the stock lives shortens the path back to sale; handling them at a separate site protects despatch productivity from an unpredictable workload. Both arrangements are common and both should be priced explicitly.

Who pays for a return that was the provider's error?

Normally the provider, under the accuracy and error provisions of the agreement. That only works where errors are attributable, which means the record of what was picked, packed and despatched has to be reliable enough to settle the question without a debate.