ReturnFulfillment (Temu)

Uploads the return shipping label to Temu.

Only available when the return status is LABEL_PENDING (Temu status 8) and availableOperateList includes value 10.

Drop Off

The merchant generates a shipping label externally (e.g. via EasyPost, ShipStation) and provides its URL. Temu notifies the buyer, who prints the label, attaches it to the package, and drops it off at any carrier location. The label contains the warehouse address — the buyer does not need to know it separately.

{
  "returnFulfillment": {
    "tracking": { "number": "1Z999AA10123456784", "companyId": "12" },
    "fileUrl": "https://cdn.example.com/return-label.pdf",
    "locationId": "WH-001",
    "logisticMode": "dropOff"
  }
}

• tracking.companyId – Temu carrier ID. Use GET /api/v2/carriers to get valid IDs.
• fileUrl – Publicly accessible PDF of the shipping label.
• locationId – Optional. If omitted, the first available warehouse from Temu is used.

logisticMode is case-insensitive — dropOff, dropoff, DROPOFF are all accepted.

Pick Up

The carrier collects the package from the buyer's address. The pick-up time is resolved automatically by ecartAPI:

• If the buyer selected a preferred time slot → pickUpTimeScheduleMode: 1
• Otherwise → pickUpTimeScheduleMode: 3 (merchant's latest pick-up time)

{
  "returnFulfillment": {
    "tracking": { "number": "PICKUP-REF-001", "companyId": "12" },
    "fileUrl": "https://cdn.example.com/pickup-certificate.jpg",
    "logisticMode": "pickUp"
  }
}

• fileUrl – Pick-up certificate image (JPG/PNG).

Warehouse selection

ecartAPI calls temu.aftersales.returnlabel.prepare.get internally to retrieve the list of available return warehouses. The first warehouse is used unless locationId is specified.

Internal flow

1. temu.aftersales.returnlabel.prepare.get → fetch warehouses and pick-up times
2. temu.aftersales.upload.returnlabel → upload label
3. bg.aftersales.parentreturnorder.get → return updated logistics