Carrier Scorecards for the Return Leg
Every merchant has a view on carrier performance, and almost all of it is about outbound. On-time delivery, damage rate, first-attempt success. The return leg runs on the same contracts, produces the same kind of failures, and is measured by almost nobody, which is why it is where the unexamined cost sits.
The reason is partly structural: on the way out you know when the parcel was handed over. On the way back you often do not know a return exists until the customer tells you, or until a scan appears days later.
What to Measure on the Way Back
The outbound metric set does not transfer cleanly. Time to first scan matters far more than transit time, because it tells you whether the network actually accepted the parcel. Lost-in-transit rate matters more than damage rate, because returns travel in customer-sourced packaging and go missing more often than outbound goods do.
And drop-off availability becomes a real metric rather than a footnote, because a network with sparse coverage in a region silently converts into abandoned returns and support contacts. Carrier documentation such as the USPS returns overview describes the service constructs, but only your own data tells you how they perform on your volume.
| Metric | Why it matters on the return leg | Typical blind spot |
|---|---|---|
| Time to first scan | Proves the network accepted the parcel | Not tracked at all |
| Scan-to-receipt time | The part you can actually chase | Blended into total time |
| Lost rate | Higher than outbound | Absorbed as write-off |
| Drop-off density by region | Drives abandonment | Assumed uniform |
| Label-free acceptance | Determines flow choice | Varies by location, not just carrier |
| Claims outcome rate | Recovers real money | Nobody owns the process |
Time to First Scan Is the Core Signal
The interval between a customer telling you they are returning something and the first carrier scan is the most diagnostic number in the whole return leg. A long tail here means one of three things: customers are not actually posting, the drop-off network is inconvenient, or the carrier is not scanning at acceptance.
Each cause has a different fix and they are distinguishable by shape. Customers not posting shows as a flat distribution with a large never-arrives tail. Inconvenient networks show as a regional pattern. Scanning failures show as a step change at one location or after a process change at the carrier. Merchants already capturing first-scan events can build this analysis without new instrumentation.
Regional Breakdown Beats a National Average
Carrier performance is not uniform across a country, and a national average hides the regions where your customers are actually struggling. A carrier that performs excellently in metropolitan areas and poorly in rural ones will look fine in aggregate while quietly generating a disproportionate share of your complaints.
Break the scorecard by region and, where volume allows, by drop-off point. The pattern that emerges is usually actionable in a way the average never is, and it is the basis for a genuine carrier-agnostic returns strategy where you route by geography rather than by a single national contract.
- Measure time to first scan as the primary return-leg metric.
- Break every metric by region before you draw any conclusion.
- Track never-arrived separately from delayed; they have different causes.
- Record which drop-off point was used, not only which carrier.
- Own the claims process; unclaimed losses are pure margin leakage.
Outbound you measure how fast the parcel arrived. Inbound you first have to measure whether it was ever accepted.
Claims Are Money Left on the Table
Returns go missing at a higher rate than outbound shipments, and most merchants write those losses off rather than claiming them. The reason is usually that nobody owns the process and the individual amounts are small enough to feel not worth chasing.
In aggregate they are rarely small. A structured claims process with evidence attached at the point of dispatch recovers a meaningful share, and the discipline required is the same documentation habit that supports everything else in the scorecard. The mechanics are covered in carrier claims on lost returns.
Using the Scorecard Commercially
A carrier scorecard for the return leg changes two conversations. In contract negotiation it moves you from arguing about headline rates to arguing about service levels that actually affect your cost, which is a much stronger position. And in routing decisions it lets you split volume by geography instead of awarding a whole country to one provider.
The second is where most of the value is realised. Very few merchants need a single national returns carrier; most need the best network per region, which is only visible once you measure regionally. This is also what makes it possible to offer drop-off density as a customer-facing promise rather than a hope, connecting directly to the choice architecture in drop-off return networks.
Share the scorecard with the carrier. Account managers respond to specific, evidenced regional data far better than to general complaints, and the ones who cannot improve a region will usually tell you so, which is itself useful information for routing.
What is the single most useful return-leg metric?
Time to first scan, measured from when the customer told you they were returning. It is the number that reveals whether the network actually accepted the parcel, and its distribution shape distinguishes between customers not posting, an inconvenient drop-off network, and a carrier not scanning at acceptance. Transit time matters much less because you cannot act on it.
Why break carrier metrics down by region?
Because carrier performance is not uniform and a national average hides where your customers actually struggle. A carrier that is excellent in cities and poor in rural areas looks acceptable in aggregate while generating a disproportionate share of complaints. Regional breakdown is also what enables routing by geography rather than awarding a whole country to one provider.
Are returns really lost more often than outbound parcels?
Generally yes. Returns travel in customer-sourced packaging, often without the labelling discipline of an outbound shipment, and frequently enter the network at a counter rather than through a scheduled collection. Most merchants absorb these losses as write-offs rather than claiming them, which turns a recoverable cost into permanent margin leakage.
Should I share the scorecard with my carrier?
Yes. Account managers respond far better to specific, evidenced regional data than to general complaints, and the exercise usually surfaces which regions the carrier can realistically improve. Where they tell you a region cannot be fixed, that is itself valuable routing information rather than a failed conversation.
See it on your own returns.
Start freeKeep reading
Fee vs Free Returns: Run the Math First
Should returns be free or carry a fee? Run the conversion-versus-margin math with our model before you set a restocking fee or absorb return shipping cost.
Migrating Off Native Shopify Returns
Outgrown native Shopify returns? Learn what native returns lack, how to migrate to a full returns portal, and how to move Shopify returns data without loss.
