A customer in Berlin sends back a jacket to your Stockholm warehouse. The parcel crawls across a border, sits in a customs queue, and lands on a shelf three weeks later. You paid to ship it out, paid to ship it back, ate a duty you could have reclaimed, and refunded before the item was ever resaleable. That is the quiet math of international returns, and this post shows you the operating model that fixes it.
What "broken international returns" actually means
International returns break when a brand runs one global return flow for markets that are not the same. A return from France, a return from the US, and a return from Norway each carry different shipping economics, customs paperwork, refund rules, and restock timing. Force them through a single generic process and every one of them leaks margin somewhere you cannot see on the order screen.
Here is the short version. Broken international returns are cross-border return flows that ignore country-level differences, so the cost hides in duplicate shipping, customs friction, and slow restocking instead of showing up as a line item.
Where the money actually leaks
The refund is the number everyone watches. It is rarely the number that hurts.
Duplicate shipping. You paid to send the order across a border. Now you pay again to bring it home, often at a worse consumer rate than your outbound contract. Two international legs for one sale.
Customs and duties. A return crossing a border is a customs event. Without the right paperwork and the right value declarations, you can pay import charges on your own returned goods or lose duty you were owed back. This is the cost that almost never makes it into a returns dashboard.
Slow restocking. Every extra day a returned item spends in transit or in a customs queue is a day it cannot be resold. In apparel and seasonal goods, that delay is the difference between reselling at full price and marking it down.
Refund timing mismatch. Many flows refund on scan or on receipt at a central hub. If that hub is in another country, the customer waits longer, messages your support team, and the whole thing costs you twice.
Add those up and the return that looked like a simple refund quietly carried three or four other charges.
The model that fixes it: handle each market locally
The fix is not a better return label. It is a return process that knows which country it is in and behaves accordingly.
Think about it market by market:
| Decision | One global flow | Per-country model |
|---|---|---|
| Return destination | Everything ships to one hub | Route to the nearest sensible destination, sometimes in-country |
| Customs docs | Generic or missing | Correct declaration per lane, duties reclaimed where possible |
| Refund logic | One rule for the world | Rules that respect local law and local timing |
| Restock speed | Gated by the slowest lane | Faster because the item travels less far |
The principle is simple. A return generated in a market should be reasoned about with that market's shipping, customs, and refund reality, not the reality of wherever your head office happens to sit.
That means per-country routing so parcels do not always cross a border to come home. It means customs and cross-border documents generated correctly for each lane. And it means refund logic that can differ by country, because a partial refund rule or a duty adjustment that is right in one market is wrong in another.
Our point of view
Most returns tools treat cross-border as a checkbox. You get a label and a portal, and the assumption is that a return from Madrid and a return from Manchester are the same event with a different flag on them. They are not.
We think the return should adapt to the market, not the other way around. The reason so many brands accept the hidden costs is that their tooling gives them one fixed box and one fixed flow. When the only lever you have is "generate a label", every country gets the same label and the margin leak is invisible until you go looking for it at the end of the quarter.
The brands that get this right stop asking "how do we process a return" and start asking "how does a return from this country work". That is a different question, and it is the one worth building around.
How Pango fits
Pango runs returns, exchanges, and claims as natural-language return and exchange rules compiled into per-merchant workflows. That includes labels, customs and cross-border documents, and refund logic set per merchant and per country. So the France flow and the Norway flow can genuinely differ instead of sharing one compromise.
On the tracking side, Pango treats a shipment status as an operational trigger, not a passive update. A cross-border handover scan or a delay can fire an apology email, a support alert, or a workflow before the customer messages you. Pango also normalizes the many different statuses carriers return, which matters most on cross-border lanes where the data is messiest.
Now the honest part. The more complex logic, like proportional refunds, country-specific rules, and per-customer or per-country refund decisions, is built to fit your operation through Pango's harness. It is not a fixed feature you toggle on. Pango reads your data and policies and builds the workflow your markets actually need. If your returns picture is simple, you will not use it. If you sell into several countries with real differences between them, that is exactly where it earns its place.
If you want the fuller picture, this post sits under our guide to return management for cross-border DTC brands, which covers the whole post-purchase returns layer, not just the international slice.
