---
content_id: tracking-status-usps-tendered-to-returns-agent
canonical_url: https://11tracking.com/tracking-status/usps-tendered-to-returns-agent/
title: "USPS Tendered to Returns Agent / Available for Returns Agent: What It Means"
meta_description: Learn what USPS Available for Returns Agent and Tendered to
  Returns Agent mean, when USPS still has the return, when it has handed it off,
  and what the status does not prove about merchant receipt or refunds.
language: en
published_at: 2026-08-20
last_reviewed: 2026-08-19
carrier_scope:
  - USPS package tracking
jurisdiction_scope:
  - United States
---


# USPS Tendered to Returns Agent / Available for Returns Agent: What It Means

If USPS tracking shows a **returns-agent event**, first determine whether it is a **pickup-readiness state** or a **handoff state**.

- **Available for Returns Agent** (event 16) and the facility-ready event 77 mean USPS is still holding a Parcel Return Service (PRS) item at a designated USPS location, ready for authorized returns pickup. They do **not** prove that the returns agent already has the parcel.
- **Tendered to Returns Agent** event 17 means USPS handed a PRS parcel to the Returns Logistics Agent. In a PRS context, event 42 can also represent a handoff under the public wording **Tendered to Returns Agent**.
- A handoff does **not** by itself prove that the merchant has matched the item to your order, inspected it, approved a refund, initiated payment, or posted money back to your account.

There is one important exception: the words **Tendered to Returns Agent** do not always prove that the shipment is a merchant return. USPS event 42 is typically associated with PRS, but USPS also allows that event in a **Global Express Guaranteed (GXG)** firm-book handoff. Use the return/service context and surrounding tracking history before treating the phrase as PRS.

## Which returns-agent event do you actually have?

USPS uses several related events, but they do not all prove the same possession state.

| USPS event or wording | Who has the item at this evidence level? | What it proves | What it does not prove |
|---|---|---|---|
| **16 — Available for Returns Agent** | USPS | A PRS return is ready for pickup by the Returns Logistics Agent at a designated USPS PRS location. | Agent possession, merchant intake, item/order match, or refund. |
| **77 — Available for RTN Agent Pickup at Facility** | USPS | A PRS return is ready for returns-agent pickup at a USPS processing facility. | Agent possession or any later merchant process. |
| **17 — Tendered to Returns Agent** | Authorized PRS return-logistics side | USPS handed the PRS package to the Returns Logistics Agent. | Merchant item/order match, inspection, refund approval, or refund posting. |
| **42 — USPS Hand Off to Shipping Partner** with public wording **Tendered to Returns Agent** | USPS has handed the item off | USPS says it no longer has the item after the handoff. The event is typically PRS, but it can also be used for GXG. | That the shipment is necessarily a merchant return, that the merchant completed intake, or that a refund is due. |

The practical rule is simple:

```text
ready for agent pickup
≠
picked up by the agent

USPS-to-agent handoff
≠
merchant return processing
```

## Available for Returns Agent: USPS still has the return

For **event 16**, USPS defines the parcel as ready for pickup by a Returns Logistics Agent at a Post Office or processing facility designated as a Parcel Return Service location.

That is a **readiness** state. The return has reached the USPS location where authorized pickup can occur, but the event does not establish that pickup has already happened.

Event 77 is a similar PRS readiness state at a USPS processing facility. It is also still on the USPS side of the handoff boundary.

If you already understand the status and the real problem is that the return has not progressed or the merchant still says it was not received, use [Return Package Not Updating or Seller Says It Was Not Received](/package-problems/return-package-not-updating-or-not-received/). This page does not create a universal number of days to wait.

## Tendered to Returns Agent: USPS has handed the item off

**Event 17** is stronger evidence than an available-for-pickup event. USPS defines it as a PRS package that USPS handed to the Returns Logistics Agent that processes returns for the shipping customer or merchant.

USPS tracking wording can vary across technical and customer-facing surfaces. In the current PTR2 scripting, event 17 can appear as **Picked Up by Shipping Agent** or **Picked up by Agent**. Those wording changes help identify the event family; they do not establish a different physical handoff rule.

A handoff proves a transition out of USPS possession at the level supported by the specific event. It does not prove that the merchant's internal return workflow is complete.

## Event 42: why “Tendered to Returns Agent” is not always PRS

Event 42 is the main reason the visible phrase should not be interpreted in isolation.

USPS defines event 42 as **USPS Hand Off to Shipping Partner**. Its public wording can be **Tendered to Returns Agent**, and USPS says it no longer has the item after that handoff.

For PRS, that can describe the same broad custody direction as a returns-agent handoff. But USPS explicitly says event 42 may also be used for a **GXG firm-book tender**.

Therefore:

```text
visible phrase “Tendered to Returns Agent”
≠
automatic proof of Parcel Return Service
```

If the surrounding history is clearly a merchant return, the PRS interpretation may fit. If the history instead looks like an ordinary outbound or GXG shipment, do not force the parcel into the return workflow. Use [Package Tracking Status Meanings](/tracking-status/) to classify the broader status family, or [Who Should I Contact About a Package?](/delivery-actions/who-to-contact-about-a-package/) if the remaining question is which actor controls the next step.

## Why “Available for Agent Pickup” can also be ambiguous

The shorter phrase **Available for Agent Pickup** is not an unconditional alias for PRS.

USPS event 14 can use that wording in a different **delivery-partner firm-book** context. That means the phrase alone is not enough to conclude that a package is waiting for a returns agent.

A full **Available for Returns Agent** event 16, event 77, or clear returns-specific history provides the safer PRS context. If the tracking history instead concerns an upstream shipping partner transferring an outbound parcel to USPS, use [USPS Shipping Partner Facility / USPS Awaiting Item](/tracking-status/usps-shipping-partner-awaiting-item/).

## Why the wording may look different in PTR2

USPS's PTR2 scripting changes preserve this family while changing some customer-facing labels:

- event 16: **Available For Returns Agent** → **Awaiting Returns Agent Pickup**;
- event 17: **Picked Up by Shipping Agent** → **Picked up by Agent**;
- event 42: **Tendered to Returns Agent** remains relevant;
- event 77: **Available for Pickup at Processing Facility** remains relevant.

These scripting changes help with recognition. They should not be treated as proof that the physical meaning changed.

## Stronger downstream PRS events: 84–87

USPS also defines later PRS-only events that can provide stronger evidence after the initial handoff:

| Event | USPS meaning | Evidence strength |
|---|---|---|
| **84 — Arrived Agent Facility** | The PRS item arrived at the return agent's facility. | Stronger evidence of downstream agent-network movement. |
| **85 — Departed Agent Facility** | The PRS item left the agent facility en route to the merchant. | Stronger evidence that movement continued beyond the agent facility. |
| **86 — Delivered by Agent to Merchant** | The return agent tendered the PRS item to the merchant. | Stronger transport-level evidence of merchant receipt. |
| **87 — Final Disposition by Agent** | USPS defines the PRS item as in the merchant's possession. | Stronger merchant-possession evidence. |

Do **not** read this table as a required sequence. USPS does not establish that every return must show 16 → 17 → 84 → 85 → 86 → 87, and this page does not promise that every consumer will see each milestone.

Even events 86 or 87 have an evidence ceiling:

```text
merchant transport-level possession
≠
item/order match
≠
inspection
≠
refund approval
≠
refund initiation
≠
refund posting
```

## Who is the “returns agent”?

The tracking phrase does not necessarily identify one universal third-party carrier.

Current USPS PRS rules allow bulk pickup by an authorized permit holder or its agent, and USPS's PRS guidance also describes permit holders, agents, and designees in the receipt process.

So the party on the other side of the USPS handoff may depend on the merchant's return program. The tracking line alone may not tell you whether the pickup party is:

- the merchant itself;
- a permit holder acting as an agent for receipt;
- an agent or designee;
- another authorized reverse-logistics participant.

Do not assume there is a public lookup that will always reveal the private returns provider from the status alone. If identifying the responsible actor is now the main problem, use [Who Should I Contact About a Package?](/delivery-actions/who-to-contact-about-a-package/).

## Will USPS tracking update again after Tendered to Returns Agent?

For event 42, USPS says **no further tracking updates are expected** after the handoff.

The safe interpretation is that further USPS updates are **not promised**. Do not strengthen that into “USPS tracking can never update again,” because the same current USPS event system defines later PRS agent and merchant milestones such as events 84–87.

At the same time, do not assume that those later events will appear for your return. The event family does not create a guaranteed downstream scan sequence.

## Will I get another tracking number?

Not necessarily.

Current USPS merchant-return architecture supports USPS return labels with an Intelligent Mail package barcode that can be tracked through USPS. The accepted evidence does **not** establish a universal rule that a consumer will receive a second UPS, FedEx, returns-agent, or other downstream tracking number after USPS hands off the parcel.

A merchant or platform may expose another identifier for a particular return program. Treat that as program-specific evidence, not as a promise created by the USPS status.

## Does Tendered to Returns Agent mean the merchant received my return?

Not by itself.

For event 17, USPS proves handoff to the Returns Logistics Agent. A PRS-context event 42 proves USPS handed the item off and no longer has it. Neither event alone proves that the merchant has completed its internal intake or associated the merchandise with your order.

Keep these states separate:

1. USPS holds the return ready for authorized pickup.
2. The authorized return-logistics side receives the item from USPS.
3. The item moves through the returns network.
4. The merchant receives the item at the transport level.
5. The merchant matches the item to the correct order or return authorization.
6. The merchant inspects or otherwise processes the return.
7. A refund is approved or initiated.
8. The refund posts to the payment destination.

If movement or merchant receipt is still uncertain after you understand the USPS status, use [Return Package Not Updating or Seller Says It Was Not Received](/package-problems/return-package-not-updating-or-not-received/).

If the merchant workflow has strong evidence of receipt and item/order matching and the unresolved problem is now the refund, use [Returned Package Received but Refund Has Not Arrived](/package-problems/returned-package-no-refund/).

## What should you do next?

Choose the next guide from the strongest fact you actually have:

| Current fact | Better owner |
|---|---|
| You have event 16 or 77 and need only to understand who has the item | Stay with this status guide: USPS still has the PRS item ready for authorized pickup. |
| You have event 17 or a confirmed PRS event 42 and later movement or merchant receipt is uncertain | [Return Package Not Updating or Seller Says It Was Not Received](/package-problems/return-package-not-updating-or-not-received/) |
| Merchant receipt and item/order matching are strongly established and the refund is now the problem | [Returned Package Received but Refund Has Not Arrived](/package-problems/returned-package-no-refund/) |
| The return label, QR code, authorized method, or return credential failed before tender | [Return Label or QR Code Not Working](/package-problems/return-label-or-qr-code-not-working/) |
| The original outbound shipment is being involuntarily sent back to the sender | [Return to Sender](/tracking-status/return-to-sender/) |
| The shipment is an upstream Shipping Partner → USPS handoff rather than reverse logistics | [USPS Shipping Partner Facility / USPS Awaiting Item](/tracking-status/usps-shipping-partner-awaiting-item/) |
| The status is understood and you only need to identify the actor who can act next | [Who Should I Contact About a Package?](/delivery-actions/who-to-contact-about-a-package/) |

There is no universal consumer deadline or “wait X days” rule established by these USPS event rows. Merchant return windows, marketplace protections, refund timelines, and other clocks belong to their own systems and should not be inferred from PTR clock fields.

## Privacy and 11Tracking limits

You do not need to provide 11Tracking with a full tracking number, return label, address, order number, merchant RMA number, invoice, or private screenshot to understand the status boundaries on this page.

11Tracking can explain what the USPS event means and route you to the better next owner. It cannot identify a private returns agent from non-public account data, contact USPS or the merchant on your behalf, recover a return, create scans, force merchant receipt, file a claim, or force or guarantee a refund.

## Official sources and actions

- [United States Postal Service / PostalPro: USPS Domestic Tracking Scan Events - April 2026](https://postalpro.usps.com/mnt/glusterfs/2026-04/PTR%20Event%20Descriptions_April%202026.pdf)
- [United States Postal Service / PostalPro: PTR2 Event Scripting Changes, Version 2](https://postalpro.usps.com/mnt/glusterfs/2025-12/PTR2_EventScriptingChanges_v2.pdf)
- [United States Postal Service / Postal Explorer: DMM 505 - Return Services](https://pe.usps.com/text/dmm300/505.htm)
- [United States Postal Service: Parcel Return Service (PRS)](https://faq.usps.com/articles/FAQ/Parcel-Return-Service-PRS)
- [United States Postal Service / PostalPro: Merchant Returns API](https://postalpro.usps.com/merchant-returns-api)

## Related 11Tracking guides

- [Package Tracking Status Meanings](https://11tracking.com/tracking-status/) — Choose the status guide that matches your tracking event family and evidence type.
- [Return Package Not Updating or Seller Says It Was Not Received](https://11tracking.com/package-problems/return-package-not-updating-or-not-received/) — Trace the last proven return handoff, identify the next missing transition, and protect return and dispute deadlines.
- [Returned Package Received but Refund Has Not Arrived](https://11tracking.com/package-problems/returned-package-no-refund/) — Separate return processing from payment posting, reconcile the amount and destination, and protect every live case deadline.
- [Return Label or QR Code Not Working or Expired Before Drop-Off Acceptance](https://11tracking.com/package-problems/return-label-or-qr-code-not-working/) — Fix a blocked return label, QR, method, or location before reliable return acceptance occurs.
- [What Does “Return to Sender” Mean?](https://11tracking.com/tracking-status/return-to-sender/) — Understand Return to Sender, why the package is going back, and whether it can still be stopped.
- [Who Should I Contact About a Package?](https://11tracking.com/delivery-actions/who-to-contact-about-a-package/) — Identify whether the seller, shipper, or carrier controls the next package action.

[Browse all Package Help guides](https://11tracking.com/package-help/)