Courier Failure Rates & Returns

TL;DR: Measure courier failures with carrier or shipping-aggregator data, validate disputed attempts with customer reports, and compare partners by delivery success, RTO rate and cost per successful delivery. Forthroute manages the customer return request and merchant-controlled resolution after a failed delivery; it does not score or route outbound couriers.

Last updated: September 2026

When a courier's failed-delivery rate rises, separate the delivery problem from the return that follows. Your carrier or shipping aggregator is the source for delivery attempts, scans and RTO events. Customer reports can help you challenge disputed attempts. A returns app such as Forthroute becomes relevant after the customer starts a return; it is not a courier-performance or outbound-routing system.

Why Courier Failure Rates Differ

Failure rates can vary by region, service level, address quality, payment method, parcel type and the courier's local operating capacity. Do not assume one national average describes every route. Compare like with like: the same destination area, service level and time period.

Start with the status data you already receive from the carrier or shipping aggregator. Keep the original status, timestamp, tracking number and courier name. If customers dispute an attempt, record that separately instead of overwriting the carrier event. The difference between those two records is useful evidence when you review performance with the courier.

How to Validate Delivery-Attempt Claims

Ask only what you can verify. After an RTO event, a short message can ask whether the customer received a call, saw a delivery attempt or refused the parcel. Store the response against the order and tracking number.

A customer response does not prove why an attempt failed, but repeated discrepancies can justify a closer review. Check the timestamps and tracking events first, then raise a documented sample with the courier. Avoid labelling every disputed status as a fake attempt.

Measure Courier Performance at the Right Grain

Use a consistent reporting window and group results by courier, service and destination region. Useful measures include:

• RTO rate: returned-to-origin orders divided by dispatched orders.
• First-attempt delivery rate: orders delivered on the first recorded attempt divided by orders with a completed attempt.
• Disputed-attempt rate: customer-disputed attempts divided by the RTOs for which you collected a response.
• Median delivery time: the median time from dispatch to delivery for completed orders.
• Cost per successful delivery: outbound and return shipping costs divided by successfully delivered orders.

Keep the denominators visible. A courier with five failures from 20 orders should not be treated as equivalent evidence to five failures from 2,000 orders. Compare a meaningful volume and check whether the pattern persists before changing allocation.

Build a Courier Scorecard

Export order and tracking data from your carrier, shipping aggregator or order system. Add customer-reported discrepancies as a separate field. A weekly scorecard can show the order count, successful deliveries, RTOs, first-attempt deliveries, disputed attempts and shipping cost for each courier and region.

Use the scorecard to find where a review is warranted, not to invent a universal pass mark. The acceptable range depends on the service, geography, product and payment mix. Record any operational change so you can compare the period before and after it.

When to Reduce or Move Courier Volume

First confirm that the comparison is fair and that the data is complete. Share the affected tracking numbers and time window with the courier, ask for an explanation and agree on a review date. If the issue is concentrated in specific regions, test a second courier there instead of changing every route at once.

Run a bounded test and compare the same measures for both services. Keep enough volume with each option to make the comparison useful, and check cost per successful delivery rather than the headline shipment price alone. If you decide to move volume, follow the notice and service terms in your carrier agreement.

Once a courier has performed reliably at the same route-and-service grain, use that evidence in the commercial discussion. You can offer a larger share of volume in exchange for better rates or a dedicated contact. Record the agreed scope and review it against the same scorecard.

What Forthroute Does After a Failed Delivery

Forthroute does not rank couriers, recommend outbound carriers, blacklist providers or route new shipments. Those decisions should use data from your carrier or shipping system.

When a failed delivery becomes a customer return, Forthroute provides a branded return portal, merchant-controlled approvals, exchange options, merchant-initiated refunds and return-leg tracking. Refunds are not issued automatically. Merchants can use their own supported carrier connection or buy an optional prepaid label through Forthroute.

The software has no monthly subscription or monthly return limit. Optional platform prepaid labels are billed separately at the carrier cost plus a 1% handling markup, rounded up to the next US$0.10. See the current Forthroute pricing and label terms.

Reduce Preventable Delivery Failures

Check the delivery address at checkout and prompt the customer to correct incomplete or inconsistent fields before the order is confirmed. For COD orders or other higher-risk cases, consider phone or one-time-passcode verification when it is proportionate to the order and market. Explain the extra step instead of applying it silently to every customer.

Before delivery, send the courier name, tracking link and latest available delivery window. That gives the customer the information needed to recognise and follow the shipment without claiming that the window is guaranteed.

Set Clear Delivery Expectations

Show an estimated delivery date before the customer orders and keep it aligned with your real dispatch schedule and carrier service. SetuBridge's Estimated Delivery Date app lets Shopify merchants account for processing time, dispatch date, transit time, holidays, lead days and cut-off times. Its Shopify listing says estimates can appear on product pages, collections, cart, checkout and email notifications.

Present the date as an estimate rather than a guaranteed arrival date. If the carrier supports rescheduling, link to the carrier's own rescheduling flow.

Take Control of Courier Performance

Measure the failure at the source, keep the denominator visible and test changes at the same courier-and-region grain. Use carrier data for courier decisions and returns data for the customer return that follows.

If a failed delivery becomes a return, Forthroute can provide the customer-facing portal and merchant-controlled resolution. It does not replace your carrier or shipping aggregator.