Niches · Shipping & fulfilment

Send a customer a return label

Two or three companies' docs show a full fit.

3companies, full fit
7companies, fit with a limit
10companies carry the tag
6share of the category's work
2first-hand accounts

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 3

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

ListingWhy
Easyship BB
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. source
Shippo B
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. source
ShipStation API D
Auctane LLC d/b/a ShipStation
POST /v2/labels/{label_id}/return creates a return label from the original label in one call. source

Does the job, with a limit 7

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.

ListingWhy
atoship E
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. source
EasyPost C
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. source
Envia F
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. source
Karrio D
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. source
Sendcloud B
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. source
ShipBob B
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. source
ShippyPro F
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. source

Doesn't do this job 2

Listings in the category that do something else, with the reason.

ListingWhy
Ship24 C
Ship24 Limited
No label or returns endpoint. source
TrackingMore E
CHANNELWILL CO., LIMITED
No label or returns endpoint. source

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)

The same as data: /api/v1/use-cases/shipping.return-label.json, or the MCP tool get_use_case with id shipping.return-label. Other jobs in this category: /api/v1/niches?category=shipping.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.