24.09.2026 · 13 min read

This is part 2 of a live test we ran ourselves: 20 fashion shops selling online in Germany (global majors, footwear & outdoor, sustainable D2C, activewear/lingerie/workwear challengers), one real self-funded order each, everything returned through the normal customer flow.
As before: one order per brand is an incident, twenty side by side are a pattern. We name segments, never shops. Full methodology at the end.
Every shop in our test had a returns policy. Most looked excellent: 14 to 30 days, free return shipping, a clean FAQ. If you audited these 20 shops by reading their policy pages only, you'd conclude that returns in German fashion e-commerce are a solved problem.
Then you actually send a parcel back.

The German baseline is genuinely high:
This is the trap: because the basics are this good, German customers assume the whole process is this good. Every failure below detonates against that expectation.

An activewear order contained a bottle. At checkout: no warning, no flag, no asterisk. At return stage: the bottle cannot be returned, "for hygiene reasons." In a second case, a sustainable D2C brand's product turned out to be entirely non-returnable, again with nothing at purchase.
It is worth being precise about the law here, because "for hygiene reasons" is doing a lot of unearned work in this market:
So the two shops in our test have two different problems that arrive at the same customer. One may be applying an exclusion that does not cover the item at all. The other is applying a real exclusion in the wrong place.
There is also a structural cost neither of them priced. An exclusion discovered at return stage is the one situation in a returns flow with no self-service path. The customer cannot resolve it in a portal, because the portal is what just refused them. It escalates to email by definition, and both of these cases landed in the upper half of our email count.
The fix is cheap: state the exclusion on the product page, in the cart summary and in the order confirmation, and state the condition rather than the category. "Returnable only while the hygiene seal is intact" is information. "Some items cannot be returned" is a trap with a disclaimer on it.

A footwear brand delivered domestically, inside Germany. The return label pointed to another EU country. Nothing at checkout suggested it, nothing in the confirmation email. The customer finds out at the parcel shop, reading a foreign address off a label they just printed.
For the customer that is a longer wait for money. For the seller it is more expensive than it looks, because a cross-border return leg is not an exception you absorb on awkward cases. It is the default routing on every single unit that comes back.
The rough shape of it, on general market rates rather than anything we measured:
That is before counting what the items are worth after an extra week in transit instead of a week back on the shelf, in the season they were bought in.
That is what "the warehouse is in the cheaper country" costs once you price it per return instead of per pallet. It is also the one failure on this list that the customer notices least and the P&L notices most.

Only 4 of the 20 parcels arrived with a printed return label inside, the one route that works for every customer, including the one who checked out as a guest and never opens their account again. The other sixteen expected the customer to produce one: log into an account, open a portal, or carry a QR code to a counter.
Each route has a specific failure point, and they are not equally bad:
That is exactly what happened with one lingerie brand. The QR code had replaced the label entirely, and no printable alternative existed anywhere in the flow. The process stalled, and reaching a human about a failed automated flow turned out to be harder than the return itself. It was the longest single case in our dataset.
The problem is not the QR code. The problem is a QR code as the only path. Every digital return flow needs a printable label reachable in one click, from the order confirmation email, without logging in. If the only fallback is your inbox, your returns process is your support queue.

Worth knowing what the baseline rule looks like, because it is narrower than most shops assume. On withdrawal, the customer is refunded everything they paid, including the cost of standard delivery. The part a seller may keep is the surcharge: the difference where the customer expressly chose something faster or more expensive than the cheapest standard option on offer. Which means that in a shop with a single delivery option, there is no surcharge to retain.
We are not making a legal claim about any individual shop; we did not see their delivery configurations or their withdrawal information. What we can say is what we measured: money was deducted, and nothing told us in advance that it would be. Any shop can check its own position on this in an afternoon.
And the customer never runs that check anyway. Nobody disputes €4.90. They do the sum once. "I paid €44.90, I got back €40.00, and nobody told me why." Then they either order again or they don't. The shop books €4.90 against a lifetime-value question it will never see the answer to. The fix is three lines in the refund email: what came back, what didn't, why. Disclosing a deduction costs you nothing you were not already keeping.

Same country, same carrier, same product category, baskets between €10 and €50. One shop closed the case in four messages. Another needed eleven.
What generates emails five through eleven is not a mystery, and it is not the customer being difficult. In every long case in our dataset the trigger was one of the earlier failures arriving in an inbox:
Support volume is not a support problem. It is the invoice for the other four.
And eleven emails instead of four is not a service detail. On any realistic cost per contact, the labour on one badly built return can exceed the gross margin on the order that caused it.
The exchange gap sits in the same place on the balance sheet. Only one brand in four offered an exchange as an alternative to a refund. In a market where sizing is consistently reported as the leading driver of fashion returns, that is three quarters of these shops choosing a refund over retained revenue on every wrong-size order they get, answering "wrong size" with: send it back, take your money, start again, possibly with someone else.

One more time, because it's the number that matters: where the flow worked cleanly, money was back with the customer in 1-2 days. Best case: under 24 hours.
That is the bar. Not the legal 14 days, but the experienced 1-2 days. A customer refunded within 24 hours by one shop does not recalibrate their expectations for you. If your refund takes ten days because the parcel first has to cross a border to reach your warehouse, you are not slightly slower. You are, in the customer's arithmetic, five to ten times slower than the market that trained them.
Then run the same test on yourself: one real order, one real return, one deliberately awkward case: a partial return, a "non-returnable" item, a lost label. Our data shows the failures cluster exactly there.
Everything above was measured in the easiest possible configuration: a domestic order, a domestic return, one country, one carrier, no border. That's the version of this process that works best, and it still broke in five places.
Add distance and every failure on the list gets a multiplier:
None of these are new problems. They're the same five, measured over a longer distance.
Which is the real finding of this test: returns in Germany aren't broken by policy, they're broken by geography and by the details nobody audits. The shops that performed best weren't the ones with the best returns page. They were the ones where the parcel had the shortest way to travel and someone looked at it quickly. Every unnecessary kilometre a returned parcel travels is margin you will never get back.
The policy has been standardised. The experience has not, and your customers run this test on you every single day. They just don't publish the results. They churn instead.
If you want to know what your own flow costs per return, and where in those five steps it leaks, an operational review of one month of your returns is the place to start. That's the layer we build at ShopReturns.
This article is based on a live test we ran ourselves in March 2026: 20 fashion brands selling online in Germany (direct shops only, no marketplaces), spread across four segments (global majors, footwear & outdoor specialists, sustainable/organic D2C brands, and activewear/lingerie/accessories/workwear challengers), one real, self-funded order per brand (baskets of €10-50, delivered to a German consumer address). Of the 20 orders, 18 arrived and were sent back through each shop's standard customer return flow, with no special treatment and no contact identifying us as researchers. For every return we documented: return-label availability (printed, portal, QR), return shipping cost, carrier, tracking in both directions, refund speed and completeness, undisclosed deductions and exclusions, the physical routing of the return parcel, and the number of customer-service emails needed to close the case. Because one order per brand is an incident rather than a statistic, all results are reported as market- and segment-level patterns, and no individual brand is named.


