Return rate is one of the cleanest-looking numbers in an e-commerce QoE pack. Low returns reads as product-market fit, accurate sizing and descriptions, satisfied customers. It’s also one of the easiest numbers to manufacture, and manufacturing it doesn’t require touching the product at all. It only requires pricing the return itself high enough that most customers decide it isn’t worth doing.
The Mechanism
Set the return-shipping fee at or above the resale or replacement value of a lower-priced item — the fast-fashion accessory, the small home good, the impulse-tier SKU that makes up a large share of many catalogues — and add a restocking fee or a store-credit-only refund on top for good measure. A customer holding a €12 item facing a €9 return fee has a rational response: keep it, give it away, or throw it away. Not return it. The reported return rate reflects the fee schedule the target built, not the product it sold.
Where This Sits in EU Law — Consumer Rights Directive, Article 14
By default under the CRD, a consumer bears only the direct cost of returning goods — unless the trader failed to clearly inform the consumer, before the contract was concluded, that the consumer would bear that cost. Fail the disclosure and the trader owes the return cost anyway, across every affected transaction, not just going forward. That makes this a two-layer exposure rather than one: a fee that was never validly disclosed pre-purchase is a retroactive liability sitting on the balance sheet right now, not a policy choice.
That disclosure rule is confirmed, primary-source text — Article 14(1) of the Consumer Rights Directive. A second, narrower question was researched for this piece and remains genuinely open rather than settled: whether a fee that is properly disclosed but set well above the actual cost of return, specifically to deter use, is independently policed as its own violation. No clear operative Commission guidance or case law surfaced confirming a “must reflect actual cost” ceiling distinct from the disclosure requirement — treat this as an arguable position, not a citable rule, until a lawyer has checked current national-authority enforcement practice specifically.
Even where the fee is disclosed, a schedule set well above genuine carrier cost specifically to discourage returns arguably lands in the same territory as the companion piece in this GP2 series on customer-service obstruction — a disproportionate barrier to exercising a contractual right, just built into price instead of process.
The Fake GM2 Problem
Two things move together and get read as one improvement. Reverse-logistics cost falls, because there are fewer physical returns to process. Revenue realization improves, because fewer refunds get issued. Both flow straight into a stronger-looking GM2. Neither is durable. If the fee wasn’t validly disclosed, the trader is sitting on a receivables liability the moment it’s examined. And even where it was disclosed, the target is holding a repeat-purchase cost that never appears in a GP waterfall at all: a customer forced to eat a bad purchase rarely comes back as a customer.
There’s a directional policy point worth naming precisely rather than stretching: ESPR — the same regulation underpinning the DPP piece — banned large companies from destroying unsold clothing, accessories, and footwear, a prohibition that formally entered into application on 19 July 2026. That ban reaches company-side destruction of unsold inventory. It does not reach what a consumer does with an item they already bought and own — that’s a genuinely different legal question, and this piece isn’t claiming otherwise. What the parallel does establish is direction of travel: a target whose margin depends on customers quietly discarding purchases rather than returning them is building its numbers against the exact policy current the EU is now actively legislating, not incidental to it.
What Outside-In Analysis Can Detect
- Reading the actual returns policy for the fee schedule and comparing it against typical price points across the catalogue — is the fee a meaningful fraction of item value for the bulk of what’s sold?
- Checking whether the fee is disclosed at the point of sale — product page, cart, checkout — versus only reachable in a policy page a customer finds after buying. The CRD test turns on pre-contract disclosure, not on whether a policy exists somewhere.
- Reviews filtered for “not worth returning,” “return fee,” “just threw it away,” “kept it because,” “wasn’t worth sending back”
- Comparing the target’s reported return rate against category benchmarks — a rate meaningfully below category norms, on a catalogue with fee-heavy return terms, is a specific and testable pattern, not a generic quality signal
The Pre-LOI Question Every PE Fund Should Ask
Not “what is the return rate” — a low return rate can be genuinely earned or engineered to look that way, and the number alone doesn’t say which. The question is: is the return fee disclosed compliantly before purchase, and would the return rate survive if it were priced to reflect actual cost rather than to deter use?
A target with a disclosed, cost-reflective return policy has a real number. A target with an underpriced compliance risk dressed up as a low return rate has a GM2 that resets the moment the fee gets fixed — whether that fix is the acquirer’s choice or a regulator’s.
This analysis is part of Tronvik’s GP2 Fulfilment & Service Margin pillar. Nothing in this article constitutes legal advice. To initiate an outside-in return-fee compliance screen on a specific acquisition target, contact info@tronvik.com.