{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/shipping.return-label/",
    "json": "https://www.anchorterminal.com/niches/shipping.return-label/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/shipping.return-label/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/shipping.return-label/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 3 | 7 | 10 | 6 | 2 |\n\n## What counts as done\n\nA return label PDF or QR code and tracking number sent or returned in one call, with the region and carrier valid for the lane.\n\nHow agents ask for it: send them a return label; create a prepaid return for order 1042\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **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.\n- **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.\n- **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.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n\n- not this job: Ship24 (Ship24 Limited): No label or returns endpoint.\n- not this job: TrackingMore (CHANNELWILL CO., LIMITED): No label or returns endpoint.\n\n## What stops agents finishing\n\n- returns need a paid plan or a separate returns product\n- return label charged on creation rather than on use\n\n## Around it\n\nBefore: support.read-ticket, commerce.read-order. After: email.send, shipping.track-parcel.\n\n## Where this comes from\n\nWeight 6 of 100 in Shipping \u0026 fulfilment: 2 of 33 accounts (Envia, Sendcloud)\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Send a customer a return label",
        "url": ""
      }
    ],
    "description": "Send a customer a return label: 3 companies fully do it, 7 with a limit, 10 carry the tag. Every listing in Shipping \u0026 fulfilment with the reason and a source.",
    "facts": null,
    "h1": "Send a customer a return label",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/shipping.return-label/",
    "published": "",
    "section": "agents",
    "title": "Send a customer a return label: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/shipping.return-label/"
  },
  "tokens": {
    "markdown": 1050,
    "slim": 280
  },
  "version": 1
}
