# Send a customer a return label

> Send a customer a return label: 3 companies fully do it, 7 with a limit, 10 carry the tag. Every listing in Shipping & fulfilment with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/shipping.return-label/
- Markdown: https://www.anchorterminal.com/niches/shipping.return-label/index.md (~1,050 tokens)
- Slim: https://www.anchorterminal.com/niches/shipping.return-label/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/shipping.return-label/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 3 | 7 | 10 | 6 | 2 |

## What counts as done

A return label PDF or QR code and tracking number sent or returned in one call, with the region and carrier valid for the lane.

How agents ask for it: send them a return label; create a prepaid return for order 1042

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Easyship (Easyship Inc.)**: Create a Return Shipment reuses the original easyship_shipment_id, and with buy_label true the reference example returns both a QR code and a label in shipping_documents.
- **Shippo (Shippo)**: is_return true in extra on a new shipment makes a scan-based return label for USPS, FedEx and UPS that is charged only when used.
- **ShipStation API (Auctane LLC d/b/a ShipStation)**: POST /v2/labels/{label_id}/return creates a return label from the original label in one call.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **atoship (atoship LLC)**: POST /v1/returns creates a return label from the original label id, with a generate-label call; the docs don't say whether it is charged on creation or on scan.
- **EasyPost (Simpler Postage, Inc. (d/b/a EasyPost))**: is_return on a new shipment swaps the addresses and buys a return label in the normal flow, but it is charged on creation; scan-based USPS returns need contacting EasyPost above 10,000 a year.
- **Envia (Envia Shipping)**: reverse_pickup: 1 on the label call makes a return shipment, but there is no return-from-original call, charge timing isn't stated, and acc-25 shows Mexican state codes going wrong on return labels.
- **Karrio (Karrio, Inc.)**: Rate and shipment requests take is_return and a return_shipment field, but support is per carrier connector and the docs give no charge-timing note.
- **Sendcloud (Sendcloud B.V.)**: The Returns API creates returns synchronously or not, with a validate-only call; acc-31 shows the label PDF fetched in a later GET, and charge timing isn't stated.
- **ShipBob (ShipBob, Inc.)**: POST /2026-07/return creates a return order at a fulfilment centre with a reference_id, but the API guide covers receiving the return; customer return labels sit in the separate ShipBob Returns product.
- **ShippyPro (Italian Valley S.r.l.)**: Ship with IsReturn true makes a return label, including a return label in the box with a different carrier. Charge timing isn't stated, and returns ride on the Enterprise-only API.

- not this job: Ship24 (Ship24 Limited): No label or returns endpoint.
- not this job: TrackingMore (CHANNELWILL CO., LIMITED): No label or returns endpoint.

## What stops agents finishing

- returns need a paid plan or a separate returns product
- return label charged on creation rather than on use

## Around it

Before: support.read-ticket, commerce.read-order. After: email.send, shipping.track-parcel.

## Where this comes from

Weight 6 of 100 in Shipping & fulfilment: 2 of 33 accounts (Envia, Sendcloud)

As data: https://www.anchorterminal.com/api/v1/use-cases/shipping.return-label.json, or the MCP tool get_use_case with id shipping.return-label. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
