Education
An emerging return model routes returns directly from one customer to the next without warehouse processing. This article explains the mechanism, where it fits, where it does not, and how to evaluate it as one option among several.
Übersetzung folgt. Wir zeigen die englische Version.
Peer-to-peer return forwarding is a return-routing model that has emerged in European fashion e-commerce over the last few years. Instead of a returned item travelling back to a central warehouse, getting inspected, and shipping out again to the next buyer, the item ships directly from the returning customer to the next customer who is buying the same product. The retailer remains the seller of record. The consumer experience on both sides is designed to feel like a normal return and a normal purchase. The warehouse is bypassed entirely.
This article explains how the model actually works, the economics that determine where it fits, the consumer experience implications, the structural limits where peer-to-peer returns do not work, and how the category sits within a broader landscape of return-management options that include recommerce, branded resale, and conventional warehouse routing. It is written for retailers researching what the category is and whether it might fit, not for any specific provider.
The note worth making upfront: peer-to-peer returns are not the right model for every retailer. They are an option, with specific conditions for fit and specific limits where they do not work. The article tries to lay out both honestly.
The canonical peer-to-peer return flow has the following steps:
The key technical components: the matching algorithm (which decides whether to attempt a forward or fall back to warehouse routing), the shipping-label generation (which has to work with the carriers the retailer already uses), and the rating-based release of the refund (which substitutes for warehouse inspection).
The retailer remains the seller of record throughout. Both customers see the retailer's brand, not any third party. The matching software typically runs as a hosted service that integrates with the retailer's order-management system and return portal.
The economic case for peer-to-peer routing is straightforward in principle: warehouse handling, inspection, repackaging, and the second outbound shipment all cost money. If the return can match an incoming order without those steps, the cost of the return falls. Per-Forward savings reported in production deployments run €5 to €12, depending on the original handling cost and the retailer's logistics setup.
The practical conditions for fit:
High return volume. The matching algorithm needs incoming demand to find a match for an outgoing return. A retailer handling fewer than 50 returns per month, especially across a long-tail catalogue, will rarely find matches and the model produces little benefit. A retailer handling thousands of returns monthly across SKUs with predictable demand has the opposite problem: matches are easy to find.
Resaleable condition expectation. The model relies on the buyer's rating substituting for warehouse inspection. This works for items where condition can be reliably self-attested by a returning customer (the item was not used, the tags are still attached, the packaging is intact). It works less well for items where condition is harder to assess from the outside (technical equipment, fragrance, intimate apparel).
Standardised products. The same SKU has to be returnable and re-purchasable. Custom products, unique items, or made-to-order pieces do not match because there is no incoming demand for the exact item.
Fashion-aligned demographic. Customer comfort with shipping packages, having a delivery come from another consumer, and engaging with a slightly less-traditional return flow varies by demographic and category. The model adopts faster among customers who are already comfortable with peer-to-peer commerce in adjacent categories (Vinted, Depop, eBay).
Where these conditions all hold, the economics are clear-cut. Where they do not, peer-to-peer routing is one of several options the retailer is considering, not the obvious answer.
From the returning customer's perspective, the flow looks like a normal return with one extra step. They initiate the return, they are offered the forward option (typically alongside the conventional warehouse-return option), they choose, and the rest is automatic. They ship the item using a label that arrives by email. They receive their refund when the next customer rates the item.
From the buying customer's perspective, the flow looks like a normal purchase. They place an order. They receive an item. They rate the condition. The sender being another customer rather than a warehouse is typically disclosed but does not change the core experience: the item arrives in the retailer's branded packaging, the order confirmation comes from the retailer, and the customer service relationship is with the retailer.
The critical design choice that determines adoption: the customer-facing flow must remain simple and recognisable. Implementations that introduce extra forms, additional steps, or unfamiliar branding kill adoption. The implementations that work well make the forward feel like an option within a familiar return process, not a separate transaction.
Reported adoption rates across production deployments vary widely with implementation quality. Well-designed flows reach 30 to 50% sender-side adoption (the share of customers who choose forwarding when offered) and similar buyer-side adoption (the share who select forwarded items when shown). Poorly-designed flows reach much lower numbers and produce limited operational benefit.
Peer-to-peer routing has structural limits that are worth being honest about, because retailers evaluating the option will run into them.
Volume threshold. Below roughly 50 returns per month, matching becomes too sparse. The algorithm has to wait for an incoming order on the same SKU within the matching window, and when both volumes are low, the wait time exceeds the patience threshold and the return falls back to the warehouse. Smaller retailers can pilot the approach, but the operational benefit is constrained until volume grows.
Condition verification. The model substitutes a buyer rating for warehouse inspection. This works well in practice for the bulk of fashion items, but it does require a feedback loop and trust mechanisms (typically including the option to fall back to warehouse handling if the buyer rates poorly). Categories where condition certification is critical (luxury goods, fine jewellery, certain technical products) often retain warehouse inspection regardless of the cost.
Category fit. Peer-to-peer works best for standardised consumer goods with predictable demand. Items that are highly personal (fitted intimate apparel, fragrance), highly variable (custom, made-to-order), or where appearance is critical and easily damaged in transit may not be appropriate.
Brand-control preferences. Some brands prefer warehouse inspection regardless of cost, because the inspection step provides visibility and quality control that direct routing does not. This is a legitimate position. The trade-off is between operational efficiency and inspection visibility.
Geographic fit. Cross-border peer-to-peer routing introduces customs, carrier-handoff, and timing complications that domestic routing does not. The model works best within unified shipping zones (within a single country, or within an integrated trade area like the EU) and adds complexity at borders.
Customer demographic. Adoption rates vary by customer base. Customers comfortable with peer-to-peer commerce in adjacent categories adopt faster. Customer bases skewed older, more affluent, or more brand-traditional adopt slower. This is solvable through good UX, but it is a real factor in whether a particular retailer's customer base will engage.
The honest position is that peer-to-peer routing is well-suited to a specific (and expanding) subset of fashion e-commerce, not all of it. Retailers evaluating should pilot, measure adoption and satisfaction, and decide based on their own data rather than category-level claims.
The category is small but real. The companies operating in this specific space, focused on direct customer-to-customer return routing rather than recommerce or branded resale:
The broader category around return management includes:
These are not necessarily competitors. Many retailers combine several approaches: peer-to-peer for items where it fits, recommerce for items past full-price window, returnless for low-value items, and conventional warehouse processing for everything else. The right strategy is per-item, not per-retailer.
The point worth making is that peer-to-peer specifically is a small category with a few dedicated players. Retailers evaluating should consider both the providers active today and how the space might evolve. The underlying mechanism (algorithmic matching of returns to incoming orders) is generalisable, and adoption is likely to grow as more retailers gain operational experience with it.
Peer-to-peer return routing intersects with several elements of the EU sustainability framework. The intersections are mostly favourable:
For full coverage of how the regulatory framework applies to fashion retailers more broadly, see our comprehensive guide to EU sustainability regulations for fashion retailers.
For retailers researching peer-to-peer returns as part of a broader return-management decision, a practical evaluation framework:
The technical integration question, which is the one most enterprise IT and finance teams raise first in scoping, is solvable across all the major ERP systems used by fashion retailers. For a detailed treatment of the integration patterns (virtual warehouse, non-inventory item with month-end correction, ignore-in-ERP with adjustment) and ERP-specific notes for Microsoft Dynamics 365, SAP, NetSuite, Acumatica, and others, see our guide to ERP integration for peer-to-peer return forwarding.
For the broader operational picture of how returns processing is evolving and what operations teams should be thinking about, see our guide to preparing operations teams for the new returns reality.
Whether peer-to-peer routing is the right answer for any specific retailer depends on volume, category, customer base, and brand control preferences. The honest framing is that it is one option worth evaluating, not a universal answer.
Return-related emissions are a substantial part of fashion's environmental footprint. The reduction levers are: cut return volume, route returns more efficiently when they happen, minimise packaging waste, and report what is actually measurable rather than what sounds impressive.
Zuletzt aktualisiert:
Most retailers undercount what a return actually costs. Once depreciation, opportunity cost, write-off, and customer-service overhead are properly attributed, returns are typically 2 to 3 times more expensive than spreadsheet defaults suggest.
Zuletzt aktualisiert:
The make-or-break technical question in any peer-to-peer routing evaluation: how does it actually integrate with the ERP? Three patterns work in practice across the major systems, none requiring custom development. A reference for IT directors and controllers.
Zuletzt aktualisiert:
