Return to Sender: How Carriers Process Undeliverable Shipments

A shipment sent back to the shipper after it cannot be delivered or is refused.

Return to Sender is a shipment sent back to the shipper after it cannot be delivered or is refused. This article explains how common carriers handle those undeliverable shipments, the operational steps they follow, and the service-level differences that affect time, cost, and liability.

Carriers maintain standard procedures for shipments flagged as undeliverable. Reasons range from incorrect addresses, recipient refusal, lack of required documentation, damage in transit, or regulatory holds. The practical handling combines automated scanning, exception workflows in carrier systems, and physical routing to origin or to a designated return hub.

Typical Carrier Workflow For Undeliverable Packages

Each carrier’s network differs, but the high-level sequence is consistent. First, a delivery attempt is made (or the carrier immediately identifies an issue). If delivery fails, the package is scanned into an exceptions queue. The carrier attempts alternate delivery methods — leaving a notice, contacting the recipient, or holding at a local facility. If none succeed or the recipient refuses, the package becomes a candidate for return to shipper.

• Initial Scan: The package is scanned as undeliverable and assigned an exception code (incorrect address, refused, unknown recipient, hazardous material, etc.).
• Local Resolution Attempt: The carrier may re-attempt delivery, contact the recipient, or hold the parcel for pickup at a local service point.
• Return Routing: When no resolution is possible within the carrier’s policy window, the item is routed back through the network to the origin or a specified return location.
• Final Disposition: On arrival, the shipper can inspect, restock, repair, or dispose of the item per contract terms and local regulations.

How Service Types Affect Returns

Service level matters. Express and expedited services typically have stricter delivery attempts and faster return routing; some include automated attempts to contact recipients before returning. Ground or economy services may hold parcels longer at the local facility before initiating return routing to reduce network cost. International returns involve customs paperwork and may be delayed by import/export clearance.

Documentation And Tracking

Accurate scans and exception codes are essential. Carriers update tracking with the reason for non-delivery and the return status — in transit to shipper, returned to sender, or undeliverable as addressed. For international returns, a return customs declaration or CN22/CN23 may be required; carriers typically append return documentation during processing but may require the shipper to provide commercial invoices.

When Carriers May Not Return A Shipment

There are scenarios where carriers will not route an item back. Perishable goods, hazardous materials, and regulated items may require special handling that leads to destruction or regulatory seizure instead of return. Similarly, if the shipper’s contract disallows returns or if the return would contradict local import restrictions, the carrier will follow legal and contractual obligations and notify the shipper.

Practical Example From A Delivery Network

Consider a retail SKU shipped nationwide. The carrier attempts delivery twice. The second attempt shows the recipient refused the package. The driver scans the refusal code and the item routes back to the local hub. At the hub, staff repackage a damaged label, send a return manifest to the regional sorting center, and the parcel moves back toward the shipper’s return address. The shipper receives updated tracking, inspects the carton, and issues a credit or creates a replacement shipment.

Tips For Shippers To Reduce Return-To-Sender Incidents

• Validate Addresses: Integrate address verification at checkout to catch typos and undeliverable addresses before shipping.
• Clear Recipient Instructions: Use delivery notes, alternate address options, and preferred time windows to reduce failed attempts.
• Communicate Proactively: Send tracking and delivery alerts; many delivery refusals result from missed communications.
• Understand Carrier Policies: Review your carrier agreements for exception handling, return routing timelines, and liability limits.

In short, the Return to Sender process is a standard carrier workflow driven by exception codes, delivery attempts, and contractual rules. Understanding each carrier’s return policies and ensuring accurate documentation reduces delay, cost, and customer friction when an undeliverable shipment needs to be sent back to the shipper.