Written by Senior Solutions Engineer, Tim Hay-Edie
Whenever I workshop the launch of a dropship programme, one question is always high on the agenda: what happens when the customer wants to send it back?
Returns are the part of dropship that keeps retail teams up at night. Get it wrong, and you confuse customers, frustrate colleagues, and haemorrhage profitability. Get it right, and dropship becomes indistinguishable to your customer from your core stocked-in proposition; and scales with your ambition.
Here is how I talk retailers through the reverse logistics piece, and the principles that tend to separate the programmes that scale smoothly from the ones that get stuck.
Start from the returns process you already have
The single most important design principle is consistency. A customer should never need to learn a new process because the item they bought is fulfilled by a supplier rather than picked from your own warehouse. Wherever possible, dropship needs to plug into the same returns channels you already offer for stocked-in products, whether that is bringing an item back to store, using a pre-printed label, or a third-party returns platform. The moment a customer has to behave differently because of how the product was sourced, you create friction and confusion that has nothing to do with the product itself. And if it is a Click & Collect order, the customer will expect to be able to return to store – whatever you or your systems have to say about it. (That’s customers for you!)
To accommodate this, the returns journey must be defined at the product level, not bolted on as an afterthought. Every dropship SKU needs a clear answer to two questions: is this item returnable at all, and if so, through which of your existing channels? Some categories (for example batteries and bikinis) cannot be returned for obvious reasons, and your systems and your colleagues need to know that from the outset.
Customer Service needs the same information at their fingertips. A dropship item will not be one of the core products your colleagues know inside out, so they need instant access to product detail, warranty status, and the specific returns journey for that item; alongside the standard order details and customer information they already work with. Without this, every dropship query becomes a slow, manual investigation, and the customer experience suffers.
Returns to store: empower the colleague, then reconcile in bulk
If you allow customers to return stocked-in items to store, the same option should be available for dropship, and that means putting a business decision in the hands of your store colleagues rather than the supplier. The colleague needs to access the customer’s order, recognise that it was sold by the retailer, identify that it is a dropship line, and make a quick, confident call on whether to give a refund. Giving colleagues the information and authority to make that call, rather than routinely waiting for supplier approval, is what makes returns to store fast and low-friction for the customer.
Once the item has been accepted in store, our recommendation is not to have the supplier or a carrier collect from the store. Instead, consolidate. Returned dropship items should go into a cage alongside the rest of a store's returns, and that cage is then sent through the same logistics network you already use to move stocked-in returns back to your central returns warehouse or hub.
The important shift here is that once those items reach the returns warehouse, you should stop thinking about them at the individual customer or order level. Tracking whether one specific item made it back to its related supplier is far more operational overhead than a returns hub can realistically absorb. Instead, this becomes a numbers game: bulk consolidation by supplier. Each item's original packaging carries a barcode that the warehouse team can scan to identify which supplier it belongs to, so items from a cage full of assorted returns can be batched together quickly by supplier. That barcode-to-supplier mapping must be set up at the product level from day one, alongside the retailer’s product code and supplier reference, so the returns warehouse can act on it the moment items arrive. Once batched, the supplier collects their consolidated returns from the hub, and issues a credit note against that batch.
This is also where your return recovery rate (RRR%) becomes a critical metric. It is the percentage of customer returns for which the retailer successfully recovers the corresponding credit from the supplier. You should target one hundred percent, even if you do not consistently hit it. What is important is that you track the gap, understand why it exists and work to improve it. The reason it matters is straightforward: you refund the customer as soon as you accept the return, but you only get a credit from the supplier once the item physically reaches them. If the mechanics of getting items back to suppliers are weak, you will be refunding customers out of your own margin with no corresponding credit. And, how many hard-earned sales are needed to make up for one lost return? Whatever channel you use, the operational discipline of getting returned stock back to source must be bulletproof.
Returns direct to supplier: label generation and order-level tracking
The other major returns channel is where a return goes straight back to the supplier rather than through a store or a returns warehouse.
Here, the customer typically finds their order on the retailer's website, indicates they want to return it, and downloads a returns label. Many retailers use third-party returns platforms like ZigZag, Narvar, ReBound or AfterShip to handle this. The customer prints the label, attaches it to the package, and either has it collected or leaves it at a drop-off point.
The critical requirement is that dropship products are fully integrated into whichever returns platform you use, in exactly the same way stocked-in products are managed. When a customer enters their order number, the platform needs to pull the correct product and returns data regardless of fulfilment method, so the right label and instructions are generated every time.
In this case, because a direct-to-supplier return is tied to a specific order, it opens up a different level of visibility. Rather than reconciling in bulk, you can track the reverse logistics journey item by item and get credit notes at the order level. This only works if the supplier is able to update the status of the return as it progresses, and if you are recording key timestamps, like when the label is used and the item is scanned into the carrier network (meaning it is in flight and no longer with the customer) and when it is delivered to, and finally processed by the supplier.
That timeline also raises one of the harder policy questions in dropship returns: at what point do you refund the customer? Some retailers refund as soon as the item is confirmed in flight, on the basis that the customer has done their part and the item is demonstrably no longer in their possession. Others wait until the goods have been received, particularly where there is a greater risk of the wrong item being returned or components being missing. Whichever trigger you use, it needs to balance customer experience, fraud risk and operational control, while remaining consistent with the customer’s statutory rights.
If a supplier does reject a return, this will need a clear offline process, with the supplier providing documentary or photographic evidence and the retailer's Customer Service team taking that evidence back to the customer.
Whichever refund timing policy you choose, the guiding principle is the same one we started with. You must mirror what you already do for stocked-in returns. If a stocked-in customer is refunded once their item is scanned, and is in transit back to your warehouse, a dropship customer should be refunded on the same basis, even though the item is heading to a supplier rather than your own facility. The processing party changes; the customer's experience of how long it takes and what to expect should not.
Not every return fits in a box
It is also worth remembering that some larger dropship categories (e.g. furniture, white goods, etc.) cannot simply be dropped off by the customer or collected via a standard parcel carrier. These require a two-person collection service. Your Customer Service team needs to be equipped to recognise when an item falls into this category and to book the appropriate collection, rather than defaulting to a standard label-based process that will not work for the item in question.
The common thread
Both scenarios, whether returns are consolidated through store and warehouse, or routed directly back to the supplier, come back to two things. First, the customer experience has to feel identical regardless of how the product was fulfilled (e.g. same channels, same expectations, same timelines). Second, the operational plumbing behind the scenes must be robust enough that returned items make their way back to the supplier efficiently; and the RRR% can be reliably measured. Retailers that treat dropship returns as a variant of their existing process, rather than a separate one, are the ones that scale without creating a support headache for themselves or their customers – or lose hard-earned margin through returns that never make it home.