Linkfox Temu Fulfillment Global

Temu 全球站 — 电商履行 / 发货（Fulfillment）

本 skill（linkfox-temu-fulfillment-global）覆盖 Partner Global Fulfillment 域 23 个已接入 type（与 US 版对齐但 不含 4 个 Scan Form 接口）。

未接入（相对 US）：temu.logistics.scanform.create、temu.logistics.scanform.get、temu.logistics.scanform.document.get、temu.logistics.candidate.scanform.list.get — 请用 `linkfox-temu-fulfillment-us`（site=us）。

详见 partner-global-catalog.md。美国站请用 `linkfox-temu-fulfillment-us`；欧洲站请用 `linkfox-temu-fulfillment-eu`。

网关：

相关 skill

默认参数

Scripts（按域）

Buy-Shipping（global_buy_shipping_*）

购标、面单、上门揽收等（不含 Scan Form）— 见 apis/README.md。

Co-Warehouse（global_co_warehouse_*）

bg.cooperativewarehouse.* — 合作仓授权、提交/取消履约。

Self-Fulfilled（global_self_fulfilled_*）

bg.logistics.shipment.v2.*、shippingtype.update 等 — 卖家自带运单号。

Tracking（global_tracking_*）

temu.track.trackinginfo.get

通用

薄封装统一调用 `_global_fulfillment_script.run_cli`。

示例

export LINKFOXAGENT_API_KEY="<key>"

# Buy-Shipping 购标
python scripts/global_buy_shipping_logistics_shipment_create.py '{
  "accessToken": "TOKEN",
  "site": "global",
  "tokenPurpose": "order-shipping",
  "request": { }
}'

# 卖家自发货更新跟踪号
python scripts/global_self_fulfilled_logistics_shipment_shippingtype_update.py '{
  "accessToken": "TOKEN",
  "site": "global",
  "tokenPurpose": "order-shipping",
  "request": { "editPackageRequestList": [{ "packageSn": "PKG-1", "trackingNumber": "1Z..." }] }
}'

Feedback： skillName：linkfox-temu-fulfillment-global

<!-- LF_LARGE_RESPONSE_BLOCK -->

Handling Large Responses

To avoid overflowing the agent context, persist the response to disk and extract only the fields you need:

python scripts/response_io.py run --script scripts/check_linkfox_token.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>"   # or --path "<JMESPath>"

Pick --out-dir outside any git working tree (e.g. /tmp/... on Unix, %TEMP%/... on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done.

This skill exposes multiple entry scripts: check_linkfox_token.py, get_temu_access_token.py, global_buy_shipping_logistics_label_list_get.py, global_buy_shipping_logistics_shiplogisticstype_get.py, global_buy_shipping_logistics_shipment_create.py, global_buy_shipping_logistics_shipment_document_get.py, global_buy_shipping_logistics_shipment_pickup_reservation_cancel.py, global_buy_shipping_logistics_shipment_pickup_reservation_create.py, global_buy_shipping_logistics_shipment_pickup_reservation_result_get.py, global_buy_shipping_logistics_shipment_result_get.py, global_buy_shipping_logistics_shipment_update.py, global_buy_shipping_logistics_shipped_package_confirm.py, global_buy_shipping_logistics_shippingservices_get.py, global_buy_shipping_logistics_warehouse_list_get.py, global_buy_shipping_order_unshipped_package_get.py, global_co_warehouse_cooperativewarehouse_fulfill_cancel.py, global_co_warehouse_cooperativewarehouse_fulfill_submit.py, global_co_warehouse_cooperativewarehouse_provider_list.py, global_co_warehouse_cooperativewarehouse_token_authorization.py, global_self_fulfilled_logistics_companies_get.py, global_self_fulfilled_logistics_shipment_shippingtype_update.py, global_self_fulfilled_logistics_shipment_sub_confirm.py, global_self_fulfilled_logistics_shipment_v2_confirm.py, global_self_fulfilled_logistics_shipment_v2_get.py, global_tracking_track_trackinginfo_get.py, list_temu_access_tokens.py, save_temu_access_token.py, temu_file_download.py, temu_global_file_download.py, temu_global_proxy.py, temu_proxy.py, temu_token_guide.py. Pass --script scripts/<name>.py to choose the one you need.

run writes the full response to a file and emits only a schema preview + file path. read projects specific fields, with --limit/--offset for slicing and --format json|jsonl|csv|table for output.

When to prefer this pattern — apply your judgment based on the response characteristics, e.g.:

• High field count per record, or fields you don't need
• Batch/paginated results (multiple items per call)
• Long-text fields (descriptions, reviews, HTML, time series)
• Output reused across later steps rather than consumed immediately

For small, single-use responses, calling the main script directly is fine.

⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via read. <!-- /LF_LARGE_RESPONSE_BLOCK -->

Temu accessToken 授权与获取

Temu 没有 LinkFox 侧自动 OAuth；accessToken 须在 Temu 卖家后台「服务市场 → 授权管理」手动复制。与 LINKFOXAGENT_API_KEY（LinkFox 用户鉴权）是两套令牌。

两种鉴权（勿混淆）

export LINKFOXAGENT_API_KEY="<your-key>"
python scripts/check_linkfox_token.py

tokenPurpose 与场景

1. 半托管 — 商品/库存 Token

1. 登录 seller.kuajingmaihuo.com 或 agentseller.temu.com 2. 系统管理 → 服务市场 → 授权管理 3. 获取授权 → 选择 「酷鸟卖家助手」 4. 全选常规和特殊授权 → 确认 → 复制 access_token 5. 调用 API：site=cn 或 partner，managementType=semi-managed

2. 半托管 — 订单/发货 Token

1. 登录 Temu 卖家后台 2. 右上角 Seller Central → 切换到目标区域（美区 / 欧区 / 全球） 3. 服务市场 → 授权管理 4. 获取授权 → 选择 「Cyber-ERP酷鸟助手」 5. 全选授权 → 确认 → 复制 token 6. 调用 API：site=global / global / eu，managementType=semi-managed

3. 全托管店铺

1. 登录 Temu 平台 2. 系统管理 → 服务市场 → 授权管理 3. 获取授权 → 「酷鸟卖家助手」 → 全选 → 复制 token 4. 调用 API：managementType=full-managed，site 通常 cn 或 partner

4. 本土店铺（美区、欧区主体）

1. 登录 Temu 2. Apps And Services → Manage Your Apps 3. Authorize a new app → 搜索 「Cyber-ERP」 4. 一般权限与敏感权限全选 → 确认 → 复制 token

站点与 OpenAPI 网关

本地保存 Token（推荐）

默认存储：~/.linkfox/temu-access-tokens.json（可用 TEMU_TOKEN_STORE_PATH 覆盖）。

# 查看授权步骤
python scripts/temu_token_guide.py '{"shopType":"semi-managed","tokenPurpose":"product-inventory","site":"cn"}'

# 保存 token
python scripts/save_temu_access_token.py '{
  "storeKey": "my-shop",
  "label": "中国半托管",
  "site": "cn",
  "managementType": "semi-managed",
  "tokenPurpose": "product-inventory",
  "accessToken": "PASTE_TOKEN"
}'

# 列出已保存（脱敏）
python scripts/list_temu_access_tokens.py

# 用 storeKey 调 API（无需每次粘贴 token）
python scripts/temu_proxy.py '{
  "storeKey": "my-shop",
  "site": "cn",
  "managementType": "semi-managed",
  "tokenPurpose": "product-inventory",
  "type": "bg.goods.category.mapping",
  "params": {"goodsName": "测试", "goodsNameEn": "Test"}
}'

注意事项

1. 子账号：可能无法进入服务市场，需主账号授权。 2. 多站点：全球站、英国站等需分别登录对应后台获取 Token。 3. 有效期：Token 会过期，过期后重新在后台复制并 save_temu_access_token.py。 4. IP 白名单：需联系紫鸟开放平台配置调用 IP。 5. 参数小写：site、managementType 必须小写。

脚本一览

linkfox-temu-fulfillment-global — API 参考

Temu 全球站电商履行/发货（Buy-Shipping + Co-Warehouse + Self-Fulfilled + Tracking），经 temu_global_proxy（POST /temu/proxy）转发。

网关与鉴权见 scripts/；tokenPurpose=order-shipping。

调用规范

网关请求 Body（/temu/proxy）

网关响应

解析顺序：网关 `code` → JSON.parse(body) → success / errorCode / errorMsg / result。

脚本调用

export LINKFOXAGENT_API_KEY="<key>"
python scripts/temu_global_proxy.py '{"accessToken":"TOKEN","tokenPurpose":"order-shipping","type":"<API_TYPE>","params":{"request":{}}}'

业务字段可放在顶层或嵌套 params；含 request 时通常整体作为 params 转发。

---

接口一览

完整 sub_menu_code 与 Partner 文档 URL 见 partner-global-catalog.md。

每个接口单独一份文档：apis/README.md（随接入递增）。

---

典型 Buy-Shipping 流程

1. linkfox-temu-order-global                    → 查待发货订单（注意 earliestTimeBuyShippingLabel 等字段）
2. bg.logistics.warehouse.list.get          → 仓库列表 / warehouseId（购标可用仓库）
3. temu.logistics.shiplogisticstype.get     → 在线发货物流类型 shipLogisticsType
4. bg.logistics.shippingservices.get        → 可用渠道 / channelId、估价
5. bg.logistics.shipment.create              → 购标，获得 packageSnList
6. temu.logistics.shipment.pickup.reservation.create（可选） → 需上门揽收渠道时预约时段
7. temu.logistics.shipment.pickup.reservation.result.get → 查询揽收预约结果
8. temu.logistics.shipment.pickup.reservation.cancel（可选） → 取消揽收预约
9. bg.logistics.shipment.result.get         → 轮询购标结果 / 面单状态
10. bg.logistics.shipment.update             → 调整 shipLaterLimitTime 或失败包裹重试
15. bg.logistics.shipment.document.get      → 面单 URL；temu_global_file_download 下载 PDF/PNG
16. temu.logistics.label.list.get            → 面单列表查询（状态/打印/时间窗筛选）
17. bg.order.unshipped.package.get          → 已购标、待发货确认包裹列表
18. bg.logistics.shipped.package.confirm    → 确认已发货（48h 内未确认可能自动转已发货）
19. linkfox-temu-order-global                   → 刷新订单发货状态

订单列表/详情/地址解密等请用 `linkfox-temu-order-global`。卖家自带运单号发货请用 `linkfox-temu-fulfillment-global`。

---

网关错误码

---

Feedback API

• POST https://skill-api.linkfox.com/api/v1/public/feedback
• skillName: `linkfox-temu-fulfillment-global`

典型 Co-Warehouse 流程

1. linkfox-temu-order-global                         → 查待履约订单（合作仓相关字段）
2. bg.cooperativewarehouse.provider.list         → 可选合作仓服务商、permitsStatus
3. bg.cooperativewarehouse.token.authorization   → 服务商 Token 授权
4. bg.cooperativewarehouse.fulfill.submit        → 提交合作仓履约
5. bg.cooperativewarehouse.fulfill.cancel        → 取消合作仓履约单
6. bg.cooperativewarehouse.fulfill.query         → 查询履约状态（待接入）
7. linkfox-temu-fulfillment-global          → 物流轨迹（如需要）
8. linkfox-temu-order-global                         → 刷新订单履约状态

---

典型自发货流程

1. linkfox-temu-order-global                    → 查待发货订单（fulfillmentType=fulfillBySeller）
2. bg.logistics.companies.get               → carrierId（= logisticsServiceProviderId）
3. linkfox-temu-fulfillment-global   → bg.logistics.warehouse.list.get（warehouseId）
4. bg.logistics.shipment.v2.confirm         → 确认发货（主流程）
5. bg.logistics.shipment.v2.get             → 核对运单/包裹/轨迹预警
6. bg.logistics.shipment.sub.confirm        → 拆包追加子包裹（可选）
7. bg.logistics.shipment.shippingtype.update → 更正跟踪号 / 集成改非集成（可选）
8. linkfox-temu-order-global                    → 刷新订单发货状态

订单列表/详情/地址解密等请用 `linkfox-temu-order-global`；商品与库存请用 `linkfox-temu-manage-product-global`。

---

物流跟踪

temu.track.trackinginfo.get（本 skill，global_tracking_track_trackinginfo_get.py）

取消合作仓履约单 — bg.cooperativewarehouse.fulfill.cancel

Description: cooperation warehouse ERP order

（取消已提交至合作仓（Cooperative Warehouse）的 ERP 履约单；按 `erpFulfillNo` 标识要取消的履约单。）

网关鉴权字段由本 skill 网关脚本处理；业务参数见下方 `request`。建议使用 `tokenPurpose=order-shipping`，且 `managementType=semi-managed`（本 skill 仅 Semi-managed）。

前置依赖：

- 须已完成 **`bg.cooperativewarehouse.token.authorization`** 绑定合作仓服务商。

- `erpFulfillNo` 通常来自 **`bg.cooperativewarehouse.fulfill.submit`** 提交成功后的返回，或 `bg.cooperativewarehouse.fulfill.query`（待接入）查询结果。

- 若履约单不存在，返回错误码 170020004。

---

Request 结构（官方顶层）

params
└── request (OBJECT, 选填)
    └── erpFulfillNo (STRING, 必填)

request 内字段

官方 Request 表将顶层 `request` 标为选填（False），但 `erpFulfillNo` 为必填（True）。Partner Request Example CURL 将 `erpFulfillNo` 写在顶层；经 LinkFox 网关时建议放在 `params.request.erpFulfillNo`。

网关 params 写法

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "managementType": "semi-managed",
  "request": {
    "erpFulfillNo": "ERP-FULFILL-20260101001"
  }
}

---

Response（Temu body 解析后）

Partner Response 表顶层为 `response` 对象；`result` 子行在导出 HTML 中为折叠状态，下列子层级按 Response 表 + Response Example 全部展开。

response（或解析后的根对象）
├── success
├── errorCode
├── errorMsg
└── result (OBJECT)
    ├── erpFulfillNo (STRING)
    └── cwFulfillNo (STRING)

顶层字段（response 内，或根级）

result 内字段

调用成功时先判断 `success === true`，再核对 `result.erpFulfillNo` 与请求一致。取消是否最终生效可能还须通过 `bg.cooperativewarehouse.fulfill.query`（待接入）或订单状态复核。

---

常见业务错误码（Partner Error Code）

<details> <summary>完整错误码列表（5 条，Partner 原文）</summary>

</details>

---

典型用法

1. bg.cooperativewarehouse.provider.list      → 选择 warehouseProviderCode
2. bg.cooperativewarehouse.token.authorization → 合作仓授权
3. bg.cooperativewarehouse.fulfill.submit      → 提交履约，获得 erpFulfillNo
4. bg.cooperativewarehouse.fulfill.cancel      → 本接口：按 erpFulfillNo 取消
5. bg.cooperativewarehouse.fulfill.query       → 查询取消后状态（待接入）

---

示例

export LINKFOXAGENT_API_KEY="<key>"

python scripts/global_co_warehouse_cooperativewarehouse_fulfill_cancel.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "erpFulfillNo": "ERP-FULFILL-20260101001"
  }
}'

python scripts/temu_global_proxy.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "type": "bg.cooperativewarehouse.fulfill.cancel",
  "params": {
    "request": {
      "erpFulfillNo": "ERP-FULFILL-20260101001"
    }
  }
}'

提交合作仓履约 — bg.cooperativewarehouse.fulfill.submit

Description: cooperativewarehouse_fulfill

（向合作仓服务商提交一笔合作仓履约单：指定合作仓、ERP 履约号、尾程发货方式及子订单 SKU/数量等；平台返回履约状态与合作仓履约号。）

网关鉴权字段由本 skill 网关脚本处理；业务参数见下方 `request`。建议使用 `tokenPurpose=order-shipping`，且 `managementType=semi-managed`（本 skill 仅 Semi-managed）。

前置依赖：

- `warehouseProviderCode` 来自 **`bg.cooperativewarehouse.provider.list`**。

- 若 `authorizeType=0`（默认），须已完成 **`bg.cooperativewarehouse.token.authorization`**，并填写 `cwCustomerCode`。

- 若 `authorizeType=1`，须填写 `authorizeToken`（及可选 `authorizeKey`）。

- `orderSn` / `parentOrderSn` 等通常来自 `linkfox-temu-order-global` 订单接口。

后续： 可用 `bg.cooperativewarehouse.fulfill.query` 查询履约结果（待接入）。

---

Request 结构（官方顶层）

params
└── request (OBJECT, 选填)
    ├── warehouseProviderCode (STRING, 必填)
    ├── authorizeType (INTEGER, 选填, 默认 0)
    ├── authorizeKey (STRING, 选填)
    ├── authorizeToken (STRING, 条件必填)
    ├── cwCustomerCode (STRING, 条件必填)
    ├── warehouseCode (STRING, 必填)
    ├── erpFulfillNo (STRING, 必填)
    ├── tailShippingMode (INTEGER, 选填)
    ├── logisticsProductCode (STRING, 条件必填)
    ├── packageSn (STRING, 条件必填)
    ├── shipCompanyId (LONG, 选填)
    ├── channelId (LONG, 选填)
    ├── channelVersionId (LONG, 选填)
    ├── shipCompanyName (STRING, 条件必填)
    ├── trackingNumber (STRING, 条件必填)
    ├── shippingLabelFileType (STRING, 条件必填)
    ├── shippingLabelFileBase64 (STRING, 条件必填)
    ├── shipLogisticsType (STRING, 条件必填)
    └── orderList[] (OBJECT[], 必填)
        ├── cwSkuCode (STRING, 必填)
        ├── productSkuId (LONG, 选填)
        ├── quantity (INTEGER, 必填)
        ├── orderSn (STRING, 必填)
        ├── parentOrderSn (STRING, 必填)
        └── skuId (LONG, 选填)

Partner Request 表在导出 HTML 中 `orderList` 子行未展开；上表 `orderList[]` 子字段按 Request Example 与 Error Code（170020024–170020027）补全。

request 内字段

authorizeType 与授权字段

tailShippingMode 与尾程字段

尾程模式非法见 170020006；当前承运商不支持面单见 170020010。

orderList[] 元素

网关 params 写法

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "managementType": "semi-managed",
  "request": {
    "warehouseProviderCode": "PROVIDER_CODE",
    "authorizeType": 0,
    "cwCustomerCode": "YOUR_CW_CUSTOMER_CODE",
    "warehouseCode": "WAREHOUSE_CODE",
    "erpFulfillNo": "ERP_FULFILL_NO_001",
    "tailShippingMode": 0,
    "logisticsProductCode": "LOGISTICS_PRODUCT_CODE",
    "orderList": [
      {
        "cwSkuCode": "CW_SKU_001",
        "productSkuId": 1,
        "quantity": 1,
        "orderSn": "ORDER_SN",
        "parentOrderSn": "PARENT_ORDER_SN",
        "skuId": 1
      }
    ]
  }
}

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "managementType": "semi-managed",
  "request": {
    "warehouseProviderCode": "PROVIDER_CODE",
    "authorizeType": 1,
    "authorizeKey": "AUTHORIZE_KEY",
    "authorizeToken": "AUTHORIZE_TOKEN",
    "warehouseCode": "WAREHOUSE_CODE",
    "erpFulfillNo": "ERP_FULFILL_NO_002",
    "tailShippingMode": 1,
    "packageSn": "PACKAGE_SN",
    "shipCompanyId": 1,
    "channelId": 1,
    "channelVersionId": 1,
    "shipCompanyName": "CARRIER_NAME",
    "trackingNumber": "TRACKING_NUMBER",
    "shippingLabelFileType": "PDF",
    "shippingLabelFileBase64": "BASE64_LABEL_CONTENT",
    "shipLogisticsType": "LOGISTICS_TYPE",
    "orderList": [
      {
        "cwSkuCode": "CW_SKU_001",
        "quantity": 1,
        "orderSn": "ORDER_SN",
        "parentOrderSn": "PARENT_ORDER_SN"
      }
    ]
  }
}

---

Response（Temu body 解析后）

Partner Response 表顶层为 `response` 对象；`result` 子行在导出 HTML 中为折叠状态，下列子层级按 Response 表 + Response Example 全部展开。

response（或解析后的根对象）
├── success
├── errorCode
├── errorMsg
└── result (OBJECT)
    ├── fulfillStatus (INTEGER)
    ├── erpFulfillNo (STRING)
    └── cwFulfillNo (STRING)

顶层字段（response 内，或根级）

result 内字段

调用成功时先判断 `success === true`，再读 `result.fulfillStatus`、`result.cwFulfillNo`。若需轮询或核对，使用 `bg.cooperativewarehouse.fulfill.query`（待接入）。

---

常见业务错误码（Partner Error Code）

<details> <summary>完整错误码列表（Partner 原文，含占位符项）</summary>

</details>

---

典型用法

1. bg.cooperativewarehouse.provider.list      → warehouseProviderCode、warehouseCode
2. bg.cooperativewarehouse.token.authorization → authorizeType=0 时绑定 cwCustomerCode
3. bg.cooperativewarehouse.fulfill.submit      → 本接口：提交履约
4. bg.cooperativewarehouse.fulfill.query         → 查询履约结果（待接入）

---

示例

export LINKFOXAGENT_API_KEY="<key>"

python scripts/global_co_warehouse_cooperativewarehouse_fulfill_submit.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "managementType": "semi-managed",
  "request": {
    "warehouseProviderCode": "PROVIDER_CODE",
    "cwCustomerCode": "YOUR_CW_CUSTOMER_CODE",
    "warehouseCode": "WAREHOUSE_CODE",
    "erpFulfillNo": "ERP_FULFILL_NO_001",
    "tailShippingMode": 0,
    "logisticsProductCode": "LOGISTICS_PRODUCT_CODE",
    "orderList": [
      {
        "cwSkuCode": "CW_SKU_001",
        "quantity": 1,
        "orderSn": "ORDER_SN",
        "parentOrderSn": "PARENT_ORDER_SN"
      }
    ]
  }
}'

python scripts/temu_global_proxy.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "type": "bg.cooperativewarehouse.fulfill.submit",
  "params": {
    "request": {
      "warehouseProviderCode": "PROVIDER_CODE",
      "warehouseCode": "WAREHOUSE_CODE",
      "erpFulfillNo": "ERP_FULFILL_NO_001",
      "orderList": []
    }
  }
}'

合作仓服务商列表 — bg.cooperativewarehouse.provider.list

Description: cooperate warehouse erp order（Partner 导出页 Description 原文；本接口用于查询合作仓（Cooperative Warehouse）服务商/ERP 列表及授权许可状态，供后续 **`bg.cooperativewarehouse.token.authorization`** 等合作仓履约流程使用。）

（查询当前店铺可用的合作仓服务商（Warehouse Provider）列表，包含服务商编码、品牌、支持的承运商、区域、客户编码及包裹配送类型等；`permitsStatus` 反映合作仓相关许可/授权状态。）

网关鉴权字段由本 skill 网关脚本处理；业务参数见下方 `request`。建议使用 `tokenPurpose=order-shipping`，且 `managementType=semi-managed`（本 skill 仅 Semi-managed）。

后续： 授权绑定见 **`bg.cooperativewarehouse.token.authorization`**；履约提交见 **`bg.cooperativewarehouse.fulfill.submit`**；查询见 `bg.cooperativewarehouse.fulfill.query`（待接入）。

---

Request 结构（官方顶层）

params
└── request (OBJECT, 选填)
    └── needAllPlatformProviders (BOOLEAN, 选填)

request 内字段

官方 Request 表将 `request` 与 `needAllPlatformProviders` 均标为选填（False）。Partner Request Example CURL 将 `needAllPlatformProviders` 写在顶层，经 LinkFox 网关时建议放在 `params.request.needAllPlatformProviders`。

网关 params 写法

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "managementType": "semi-managed",
  "request": {
    "needAllPlatformProviders": true
  }
}

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "managementType": "semi-managed",
  "request": {}
}

---

Response（Temu body 解析后）

Partner Response 表顶层为 `response` 对象；`result` 在导出 HTML 中为折叠状态，下列子层级按 Response 表 + Response Example 全部展开。

response（或解析后的根对象）
├── success
├── errorCode
├── errorMsg
└── result (OBJECT)
    ├── permitsStatus
    └── warehouseProviderList[] (OBJECT[])
        ├── warehouseProviderCode
        ├── warehouseProviderBrandName
        ├── supportNoCwCustomCode
        ├── cwCustomerCodeList[] (STRING[])
        ├── regionId[] (STRING[])
        ├── supportedPackageDeliveryType[] (INTEGER[])
        └── supportedShipCompany[] (OBJECT[])
            ├── shipCompanyName
            └── shipCompanyId

顶层字段（response 内，或根级）

result 内字段

warehouseProviderList[] 元素字段

Partner Response 表中 `result` 子行在导出 HTML 中为折叠状态；下列字段与类型来自 Response Example，说明结合 Co-Warehouse 履约语义整理。若 Partner 在线文档 Expand 后有更完整枚举，以在线表为准。

warehouseProviderList[].supportedShipCompany[] 元素字段

调用成功时先判断 `success === true`，再读 `result.permitsStatus` 与 `warehouseProviderList`。选定 `warehouseProviderCode` 后，通常继续调用 **`bg.cooperativewarehouse.token.authorization`** 完成授权，再使用 `bg.cooperativewarehouse.fulfill.submit` 等提交合作仓履约。

---

典型用法

1. bg.cooperativewarehouse.provider.list（本接口）  → 查询可选合作仓服务商、permitsStatus
2. bg.cooperativewarehouse.token.authorization      → 服务商 Token 授权（见 [文档](./bg-cooperativewarehouse-token-authorization.md)）
3. bg.cooperativewarehouse.fulfill.submit      → 提交合作仓履约
4. bg.cooperativewarehouse.fulfill.query       → 查询合作仓履约（待接入）
4. linkfox-temu-order-global                           → 订单状态刷新

---

示例

export LINKFOXAGENT_API_KEY="<key>"

python scripts/global_co_warehouse_cooperativewarehouse_provider_list.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "managementType": "semi-managed",
  "request": {
    "needAllPlatformProviders": true
  }
}'

python scripts/temu_global_proxy.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "managementType": "semi-managed",
  "type": "bg.cooperativewarehouse.provider.list",
  "params": {
    "request": {}
  }
}'

合作仓 Token 授权 — bg.cooperativewarehouse.token.authorization

Description: Cooperative warehouse token authorization

（将卖家在合作仓服务商（ERP/WMS）侧取得的访问凭证授权绑定到 Temu 店铺，使平台可代店铺调用该合作仓履约能力。）

网关鉴权字段由本 skill 网关脚本处理；业务参数见下方 `request`。建议使用 `tokenPurpose=order-shipping`，且 `managementType=semi-managed`（本 skill 仅 Semi-managed）。

前置依赖：

- `warehouseProviderCode` 通常来自 **`bg.cooperativewarehouse.provider.list`** 返回的 `warehouseProviderList[].warehouseProviderCode`。

- `cwAccessToken`、`cwCustomerCode` 由合作仓服务商侧颁发/分配，须与所选 `warehouseProviderCode` 对应。

- `cwAppKey` 为选填，部分 ERP 服务商要求与 `cwAccessToken` 一并提交。

后续： 授权成功后可用 **`bg.cooperativewarehouse.fulfill.submit`** 提交合作仓履约；查询见 `bg.cooperativewarehouse.fulfill.query`（待接入）。

---

Request 结构（官方顶层）

params
└── request (OBJECT, 选填)
    ├── cwAppKey (STRING, 选填)
    ├── cwAccessToken (STRING, 必填)
    ├── cwCustomerCode (STRING, 必填)
    └── warehouseProviderCode (STRING, 必填)

request 内字段

官方 Request 表将顶层 `request` 标为选填（False），但 `cwAccessToken`、`cwCustomerCode`、`warehouseProviderCode` 为必填。Partner Request Example CURL 将业务字段写在顶层；经 LinkFox 网关时建议放在 `params.request` 下（亦可由 extract_business_params 放在 params 顶层转发）。

网关 params 写法

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "managementType": "semi-managed",
  "request": {
    "cwAppKey": "YOUR_CW_APP_KEY",
    "cwAccessToken": "YOUR_CW_ACCESS_TOKEN",
    "cwCustomerCode": "YOUR_CW_CUSTOMER_CODE",
    "warehouseProviderCode": "PROVIDER_CODE_FROM_LIST"
  }
}

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "cwAccessToken": "YOUR_CW_ACCESS_TOKEN",
    "cwCustomerCode": "YOUR_CW_CUSTOMER_CODE",
    "warehouseProviderCode": "PROVIDER_CODE_FROM_LIST"
  }
}

---

Response（Temu body 解析后）

Partner Response 表顶层为 `response` 对象；`result` 子行在导出 HTML 中为折叠状态，下列子层级按 Response 表 + Response Example 全部展开。

response（或解析后的根对象）
├── success
├── errorCode
├── errorMsg
└── result (OBJECT)
    ├── authorizationSuccess (BOOLEAN)
    └── authorizationFailReason (STRING)

顶层字段（response 内，或根级）

result 内字段

调用成功时先判断 `success === true`，再读 `result.authorizationSuccess`。若为 `false`，根据 `authorizationFailReason` 与下方业务错误码修正 `cwAccessToken` / `cwCustomerCode` / `warehouseProviderCode`，或确认店铺已在服务商侧完成授权（170020002）。

---

常见业务错误码（Partner Error Code）

<details> <summary>完整错误码列表（5 条，Partner 原文）</summary>

</details>

---

典型用法

1. bg.cooperativewarehouse.provider.list      → 获取 warehouseProviderCode、permitsStatus
2. bg.cooperativewarehouse.token.authorization → 本接口：提交 cwAccessToken / cwCustomerCode 完成绑定
3. bg.cooperativewarehouse.fulfill.submit      → 提交合作仓履约
4. bg.cooperativewarehouse.fulfill.query         → 查询履约结果（待接入）

---

示例

export LINKFOXAGENT_API_KEY="<key>"

python scripts/global_co_warehouse_cooperativewarehouse_token_authorization.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "cwAppKey": "YOUR_CW_APP_KEY",
    "cwAccessToken": "YOUR_CW_ACCESS_TOKEN",
    "cwCustomerCode": "YOUR_CW_CUSTOMER_CODE",
    "warehouseProviderCode": "PROVIDER_CODE_FROM_LIST"
  }
}'

python scripts/temu_global_proxy.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "type": "bg.cooperativewarehouse.token.authorization",
  "params": {
    "request": {
      "cwAccessToken": "YOUR_CW_ACCESS_TOKEN",
      "cwCustomerCode": "YOUR_CW_CUSTOMER_CODE",
      "warehouseProviderCode": "PROVIDER_CODE_FROM_LIST"
    }
  }
}'

获取区域可用物流商 — bg.logistics.companies.get

Description: Obtain full logistics providers that support shipping at the corresponding region（获取指定区域下支持发货的全部物流服务商列表）。

网关鉴权字段由本 skill 网关脚本处理；业务参数见下方 request。建议使用 `tokenPurpose=order-shipping`。自发货确认物流、创建运单前，通常需先调用本接口取得 logisticsServiceProviderId 等。

---

Request 结构（官方顶层）

params
└── request (OBJECT, 选填)
    └── regionId              ← 必填

request 内字段

官方表将顶层 `request` 标为选填（False），但 `request.regionId` 为必填；实际调用时应始终传入 `request` 且包含 `regionId`，否则无法按区域筛选物流商。

网关 params 写法

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "regionId": 211
  }
}

---

Response（Temu body 解析后）

response
├── success          ← 请求级是否成功
├── errorCode
├── errorMsg
└── result[]         ← 物流服务商列表（OBJECT 数组）
    ├── logisticsServiceProviderId
    ├── logisticsServiceProviderName
    └── logisticsBrandName

顶层字段

result[] 元素字段

调用成功时先判断 `response.success === true`，再遍历 `result` 选用 logisticsServiceProviderId / logisticsServiceProviderName。errorCode / errorMsg 非空或 success === false 时以错误信息为准。

---

示例

export LINKFOXAGENT_API_KEY="<key>"

# 专用脚本（全球站 regionId=211）
python scripts/global_self_fulfilled_logistics_companies_get.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "regionId": 211
  }
}'

# 通用代理（等价）
python scripts/temu_global_proxy.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "type": "bg.logistics.companies.get",
  "params": {
    "request": {
      "regionId": 211
    }
  }
}'

---

典型用法

1. 从订单接口（如 bg.order.detail.v2.get）或业务上下文确认 `regionId`（全球站多为 211）。 2. 调用本接口获取该区域可用 `logisticsServiceProviderId` 列表。 3. 用户或后续脚本选择承运商后，再调用自发货相关创建运单 / 确认发货等接口（待接入）。

在线下单购标 — bg.logistics.shipment.create

Description: The bg.logistics.shipment.create interface is for sellers to place online logistics orders and receive package numbers, which enables sellers to effortlessly place logistics orders with selected carriers online.（卖家在线向 Temu 集成承运商下单购标，创建包裹并获取 packageSn；是 Buy-Shipping 购标核心接口。）

网关鉴权字段由本 skill 网关脚本处理；业务参数见下方 request。建议使用 `tokenPurpose=order-shipping`。

前置依赖： warehouseId 来自 `bg.logistics.warehouse.list.get`；channelId / shipCompanyId / shipLogisticsType / signServiceId 等来自 `bg.logistics.shippingservices.get` 或 `temu.logistics.shiplogisticstype.get`；parentOrderSn / orderSn / quantity 来自 `linkfox-temu-order-global`。

异步说明： 部分场景下单为异步处理；若返回成功但无运单，请用 **`bg.logistics.shipment.result.get`** 按 `packageSnList` 查询结果（错误码 120012013）。

---

Request 结构（官方顶层）

params
└── request (OBJECT, 选填)
    ├── sendType                    ← 必填
    ├── sendRequestList[]           ← 选填（Package List Information；实际购标须传）
    │   ├── warehouseId
    │   ├── weight / weightUnit / extendWeight / extendWeightUnit
    │   ├── length / width / height / dimensionUnit
    │   ├── shipCompanyId
    │   ├── channelId               ← 与 shipLogisticsType 二选一履约方式
    │   ├── shipLogisticsType       ← 与 channelId 二选一履约方式
    │   ├── signServiceId
    │   ├── pickupStartTime / pickupEndTime
    │   ├── orderSendInfoList[]
    │   │   ├── parentOrderSn
    │   │   ├── orderSn
    │   │   ├── goodsId
    │   │   ├── skuId
    │   │   └── quantity
    │   ├── confirmAcceptance[]
    │   ├── splitSubPackage
    │   ├── sendSubRequestList[]    ← splitSubPackage=true 时必填
    │   │   └── （附属包裹：尺寸/重量/渠道/仓库等，结构见下）
    │   ├── interlineShipCompanyList[]  ← 联运/分段渠道时必填
    │   │   ├── shipStageType
    │   │   ├── shipLogisticsType
    │   │   ├── shipCompanyId
    │   │   └── channelId
    │   ├── cooperativeWarehouseShipment
    │   ├── uspsMailingDateOffset
    │   └── autoConfirmAfterPickup
    ├── shipLater                   ← 选填
    └── shipLaterLimitTime          ← 选填（shipLater=true 时按订单标签传）

request 内字段

\ Partner Request 表将 `sendRequestList` 标为选填（False），但购标业务必须*传入有效包裹明细。

sendType

shipLater

shipLaterLimitTime

无效枚举将报错 120015532。与 `shipLater=true` 配合使用，表示稍后发货的截止时间。

sendRequestList[] 元素字段

Partner Request 表中 sendRequestList 子行在导出 HTML 中为折叠状态；下列字段、类型与说明来自 Request 表（顶层）、Request Example、Response Example 关联字段及 Partner Error Code 表。

orderSendInfoList[] 元素字段

confirmAcceptance[] 枚举值

仅当订单存在对应待处理事项且商家选择继续发货时传入。

sendSubRequestList[] 元素字段

单件 SKU 拆多包裹时，主包裹 + 附属包裹共同完成发货；附属包裹不含 orderSendInfoList（商品行在主包裹 `sendRequestList` 元素上）。

interlineShipCompanyList[] 元素字段

网关 params 写法（sendType=0 单包裹购标示例）

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "sendType": 0,
    "shipLater": false,
    "sendRequestList": [
      {
        "warehouseId": "WH-001",
        "length": "12.00",
        "width": "8.00",
        "height": "4.00",
        "dimensionUnit": "in",
        "weight": "2",
        "weightUnit": "lb",
        "extendWeight": "8",
        "extendWeightUnit": "oz",
        "shipCompanyId": 314439762,
        "channelId": 19409681780736,
        "orderSendInfoList": [
          {
            "parentOrderSn": "PO-20260101001",
            "orderSn": "O-20260101001-1",
            "goodsId": 6017592186252451,
            "skuId": 281474976920151,
            "quantity": 1
          }
        ]
      }
    ]
  }
}

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "sendType": 0,
    "shipLater": true,
    "shipLaterLimitTime": "48",
    "sendRequestList": [
      {
        "warehouseId": "WH-001",
        "shipLogisticsType": "USPS_GROUND_ADVANTAGE",
        "length": "12.00",
        "width": "8.00",
        "height": "4.00",
        "dimensionUnit": "in",
        "weight": "2",
        "weightUnit": "lb",
        "shipCompanyId": 314439762,
        "signServiceId": 1001,
        "pickupStartTime": 1717200000,
        "pickupEndTime": 1717203600,
        "orderSendInfoList": [
          {
            "parentOrderSn": "PO-20260101001",
            "orderSn": "O-20260101001-1",
            "goodsId": 6017592186252451,
            "skuId": 281474976920151,
            "quantity": 1
          }
        ],
        "confirmAcceptance": ["DENY_CANCELLATION"]
      }
    ]
  }
}

---

Response（Temu body 解析后）

response
├── success
├── errorCode
├── errorMsg
└── result (OBJECT)
    ├── packageSnList[] (STRING[])
    ├── warningMessage[] (STRING[])
    └── shipLaterLimitTime (STRING)

顶层字段

result 内字段

Partner Response 表中 result 子行在导出 HTML 中为折叠状态；下列字段来自 Response Example 与购标后续流程约定。

调用成功时先判断 `response.success === true`，再使用 `result.packageSnList` 走结果查询与面单下载。若 `warningMessage` 非空，建议记录并人工确认是否影响发货。

---

常见业务错误码（Partner Error Code）

完整错误码以 Partner 文档 Error Code 表为准（导出 HTML 含 70+ 条）。

---

典型用法

1. bg.logistics.warehouse.list.get          → warehouseId
2. linkfox-temu-order-global                    → parentOrderSn、orderSn、quantity、earliestTimeBuyShippingLabel
3. bg.logistics.shippingservices.get        → channelId / shipCompanyId / signServiceId / pickup 时段
   （或 temu.logistics.shiplogisticstype.get → shipLogisticsType）
4. bg.logistics.shipment.create              → packageSnList（本接口）
5. [bg.logistics.shipment.result.get](./bg-logistics-shipment-result-get.md) → 确认异步下单结果
6. [bg.logistics.shipment.document.get](./bg-logistics-shipment-document-get.md) → 面单 URL
7. [bg.order.unshipped.package.get](./bg-order-unshipped-package-get.md) → 未发货包裹列表
7. bg.logistics.shipped.package.confirm      → 确认已发货（待接入）

---

示例

export LINKFOXAGENT_API_KEY="<key>"

python scripts/global_buy_shipping_logistics_shipment_create.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "sendType": 0,
    "shipLater": false,
    "sendRequestList": [
      {
        "warehouseId": "WH-001",
        "length": "12.00",
        "width": "8.00",
        "height": "4.00",
        "dimensionUnit": "in",
        "weight": "2",
        "weightUnit": "lb",
        "shipCompanyId": 314439762,
        "channelId": 19409681780736,
        "orderSendInfoList": [
          {
            "parentOrderSn": "PO-20260101001",
            "orderSn": "O-20260101001-1",
            "goodsId": 6017592186252451,
            "skuId": 281474976920151,
            "quantity": 1
          }
        ]
      }
    ]
  }
}'

python scripts/temu_global_proxy.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "type": "bg.logistics.shipment.create",
  "params": {
    "request": {
      "sendType": 0,
      "shipLater": false,
      "sendRequestList": [
        {
          "warehouseId": "WH-001",
          "length": "12.00",
          "width": "8.00",
          "height": "4.00",
          "dimensionUnit": "in",
          "weight": "2",
          "weightUnit": "lb",
          "shipCompanyId": 314439762,
          "channelId": 19409681780736,
          "orderSendInfoList": [
            {
              "parentOrderSn": "PO-20260101001",
              "orderSn": "O-20260101001-1",
              "quantity": 1
            }
          ]
        }
      ]
    }
  }
}'

获取面单/运单文档 — bg.logistics.shipment.document.get

Description: The bg.logistics.shipment.document.get interface is for sellers to obtain the express delivery waybill which has been fulfilled successfully by Temu-integrated channel so as to facilitate the printing of the express delivery waybill and the package out of the warehouse.

（卖家获取已通过 Temu 集成物流渠道 成功履约包裹的快递面单/运单文档 URL，用于打印面单、包裹出库。）

网关鉴权字段由本 skill 网关脚本处理；业务参数见下方 `request`。建议使用 `tokenPurpose=order-shipping`。

前置依赖：

- `packageSnList` 来自 `bg.logistics.shipment.create` 或 `bg.logistics.shipment.result.get`（购标成功 `shippingLabelStatus=1`）。

- 须在订单 `earliestTimeGetShippingDocument` 之后调用（错误码 120012038）。

返回的 `url` 若为加签链接，可用本 skill 的 `temu_global_file_download.py`（POST /temu/fileDownload）下载 PDF/PNG 文件。

---

Request 结构（官方顶层）

params
└── request (OBJECT, 选填)
    ├── documentType (STRING, 选填)
    └── packageSnList[] (STRING[], 选填)

request 内字段

documentType

官方 Request 表将 `request`、`documentType`、`packageSnList` 均标为选填（False）；实际调用须传入有效 `packageSnList`（错误码 120018027）。Partner Request Example CURL 将字段写在顶层，经 LinkFox 网关时建议放在 `params.request` 下。

网关 params 写法

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "documentType": "SHIPPING_LABEL_PDF",
    "packageSnList": ["PKG-001", "PKG-002"]
  }
}

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "packageSnList": ["PKG-001"]
  }
}

---

Response（Temu body 解析后）

Partner Response 表顶层为 `response` 对象；网关解析后通常直接见到 success / errorCode / errorMsg / result。`result` 在导出 HTML 中为折叠状态，下列子层级按 Response 表 + Response Example 全部展开。

response
├── success
├── errorCode
├── errorMsg
└── result (OBJECT)
    ├── shippingLabelUrlList[] (OBJECT[])
    │   ├── packageSn
    │   ├── documentType
    │   └── url
    └── warningMessage[] (STRING[])

顶层字段

result 内字段

shippingLabelUrlList[] 元素字段

warningMessage[] 元素

调用成功时先判断 `response.success === true`，再遍历 `result.shippingLabelUrlList` 取 `url` 打印或下载。若 `warningMessage` 非空，须阅读警告内容（可能部分包裹未返回 URL 或需额外操作）。

---

常见业务错误码（Partner Error Code）

---

典型用法

1. bg.logistics.shipment.create              → packageSnList
2. bg.logistics.shipment.result.get          → shippingLabelStatus=1，确认可打印时间
3. bg.logistics.shipment.document.get        → shippingLabelUrlList[].url
4. temu_global_file_download.py（可选）         → 下载加签 PDF/PNG
5. 打印面单 / 出库

---

示例

export LINKFOXAGENT_API_KEY="<key>"

python scripts/global_buy_shipping_logistics_shipment_document_get.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "documentType": "SHIPPING_LABEL_PDF",
    "packageSnList": ["PKG-001", "PKG-002"]
  }
}'

# 下载面单（若 url 需网关加签下载）
python scripts/temu_global_file_download.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "url": "<shippingLabelUrlList[].url>"
}'

python scripts/temu_global_proxy.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "type": "bg.logistics.shipment.document.get",
  "params": {
    "request": {
      "packageSnList": ["PKG-001"]
    }
  }
}'

查询购标/在线下单结果 — bg.logistics.shipment.result.get

Description: The bg.logistics.shipment.result.get interface is for sellers to query the result of placing online logistics orders, with the shipping label status including in-progress{0}, successful{1}, and failed{2}.

（卖家查询在线物流下单/购标结果；`shippingLabelStatus` 表示面单状态：0=进行中、1=成功、2=失败。）

网关鉴权字段由本 skill 网关脚本处理；业务参数见下方 `request`。建议使用 `tokenPurpose=order-shipping`。

前置依赖： `packageSnList` 中的包裹号通常来自 `bg.logistics.shipment.create` 或订单/包裹相关接口返回的 `packageSn`。

---

Request 结构（官方顶层）

params
└── request (OBJECT, 选填)
    └── packageSnList[] (STRING[], 选填)

request 内字段

官方 Request 表将 `request` 与 `packageSnList` 均标为选填（False）；实际查询须传入有效 `packageSn`（错误码 120018027）。Partner Request Example CURL 将 `packageSnList` 写在顶层，经 LinkFox 网关时建议放在 `params.request.packageSnList`（与 Partner Request 表一致）。

网关 params 写法

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "packageSnList": ["PKG-001", "PKG-002"]
  }
}

---

Response（Temu body 解析后）

Partner Response 表顶层为 `response` 对象；网关解析后通常直接见到 success / errorCode / errorMsg / result。`result` 在导出 HTML 中为折叠状态，下列子层级按 Response 表 + Response Example 全部展开。

response（或解析后的根对象）
├── success
├── errorCode
├── errorMsg
└── result (OBJECT)
    └── packageInfoResultList[] (OBJECT[])
        ├── packageSn
        ├── shippingLabelStatus
        ├── failReasonText
        ├── trackingNumber
        ├── channelId
        ├── shipLogisticsType
        ├── shipCompanyId
        ├── shippingCompanyName
        ├── warehouseId
        ├── warehouseName
        ├── mainPackageSn
        ├── subPackageSnList[]
        ├── subPackageType
        ├── cwFulfillNo
        ├── reservationSn
        ├── estimatedText
        ├── estimatedAmount
        ├── estimatedCurrencyCode
        ├── solutionText
        ├── packageDeliveryType
        ├── dimensionUnit
        ├── length
        ├── width
        ├── height
        ├── weight
        ├── weightUnit
        ├── extendWeight
        ├── extendWeightUnit
        ├── pickupStartTime
        ├── pickupEndTime
        ├── shipLabelPrintableTime
        ├── isConfirmAfterPickup
        ├── canChangeToManualSend
        ├── signServiceId
        ├── uspsMailingDateOffset
        ├── warningMessage[]
        ├── interlineShipCompanyList[] (OBJECT[])
        │   ├── shipLogisticsType
        │   ├── shipStageType
        │   ├── shippingCompanyName
        │   ├── channelId
        │   └── shipCompanyId
        ├── shippingInfoList[] (OBJECT[])
        │   ├── shipLogisticsType
        │   ├── shipStageType
        │   ├── shippingCompanyName
        │   ├── trackingNumber
        │   └── shipCompanyId
        └── orderSendInfoList[] (OBJECT[])
            ├── semiUniqueId
            ├── quantity
            ├── orderSn
            ├── parentOrderSn
            ├── goodsId
            ├── mallId
            └── skuId

顶层字段（response 内，或根级）

result 内字段

packageInfoResultList[] 元素字段

Partner Response 表中 `result` 子行在导出 HTML 中为折叠状态；下列字段与类型来自 Response Example，说明结合接口 Description 与 Buy-Shipping 流程整理。若 Partner 在线文档 Expand 后有更完整枚举，以在线表为准。

interlineShipCompanyList[] 元素字段

shippingInfoList[] 元素字段

orderSendInfoList[] 元素字段

调用成功时先判断 `success === true`，再按 `packageSn` 在 `result.packageInfoResultList` 中查看 `shippingLabelStatus`：1 表示购标成功，可继续取面单；0 可轮询本接口；2 查看 `failReasonText`。

---

Error Code（Partner 摘录）

---

典型用法

1. bg.logistics.shippingservices.get     → 选渠道
2. [bg.logistics.shipment.create](./bg-logistics-shipment-create.md) → 购标，获得 packageSnList
3. bg.logistics.shipment.result.get      → 本接口：轮询购标结果 / shippingLabelStatus
4. bg.logistics.shipment.document.get    → 下载面单（待接入）

---

示例

export LINKFOXAGENT_API_KEY="<key>"

python scripts/global_buy_shipping_logistics_shipment_result_get.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "packageSnList": ["PKG-001"]
  }
}'

python scripts/temu_global_proxy.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "type": "bg.logistics.shipment.result.get",
  "params": {
    "request": {
      "packageSnList": ["PKG-001", "PKG-002"]
    }
  }
}'

更新物流跟踪号 / 发货方式 — bg.logistics.shipment.shippingtype.update

Description: The bg.logistics.shipment.shippingtype.update interface is used by sellers to update logistics tracking numbers, supporting the following scenarios（卖家更新物流跟踪号，支持以下场景）：

1. Non-integrated logistics updating logistics tracking numbers — 非集成物流更新物流跟踪号 2. Temu-integrated logistics has been changed to non-integrated logistics — Temu 集成物流已改为非集成物流

网关鉴权字段由本 skill 网关脚本处理；业务参数见下方 request。建议使用 `tokenPurpose=order-shipping`。

- packageSn 通常来自 `bg.logistics.shipment.v2.get` 或 `bg.logistics.shipment.get`

- shipCompanyId 与 bg-logistics-companies-get.md 返回的 `logisticsServiceProviderId` 相同

- selfShippingWarehouseId 来自 `linkfox-temu-fulfillment-global` 的 `bg.logistics.warehouse.list.get`

---

Request 结构（官方业务参数）

params
└── request (OBJECT, 选填)
    └── editPackageRequestList[] (OBJECT[], 否)
        ├── packageSn (STRING, 是)
        ├── trackingNumber (STRING, 是)
        ├── shipCompanyId (LONG, 是)
        └── selfShippingWarehouseId (STRING, 是)

request

editPackageRequestList[]

网关 params 写法

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "editPackageRequestList": [
      {
        "packageSn": "PKG-123456789",
        "trackingNumber": "1Z999AA10123456784",
        "shipCompanyId": 123456789,
        "selfShippingWarehouseId": "WH-001"
      }
    ]
  }
}

---

Response（Temu body 解析后）

response
├── success
├── errorCode
├── errorMsg
└── result (BOOLEAN)

response 顶层字段

---

示例

python scripts/global_self_fulfilled_logistics_shipment_shippingtype_update.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "editPackageRequestList": [
      {
        "packageSn": "PKG-123456789",
        "trackingNumber": "1Z999AA10123456784",
        "shipCompanyId": 123456789,
        "selfShippingWarehouseId": "WH-001"
      }
    ]
  }
}'

典型流程：已发货包裹需更正跟踪号，或 Temu 集成物流改为非集成物流 → bg.logistics.companies.get 取 shipCompanyId → 本接口批量更新 editPackageRequestList → 可用 bg.logistics.shipment.v2.get 核对。

确认子包裹发货 — bg.logistics.shipment.sub.confirm

Description: The bg.logistics.shipment.sub.confirm interface should only be used in scenarios where the smallest sku needs to be shipped as split packages, and can append the sub-parcel information to the main parcel（仅在最小 SKU 需拆分为多个包裹发货时使用；向主包裹追加子包裹信息）。

网关鉴权字段由本 skill 网关脚本处理；业务参数见下方 request。建议使用 `tokenPurpose=order-shipping`。

- mainPackageSn 来自 `bg.logistics.shipment.get`（待接入时可先用 temu_global_proxy.py）

- selfShippingWarehouseId 来自 `linkfox-temu-fulfillment-global` 的 `bg.logistics.warehouse.list.get`（warehouseId）

- carrierId 可与 bg-logistics-companies-get.md 返回的物流商 ID 对应

---

Request 结构（官方业务参数）

params
└── request (OBJECT, 选填)
    ├── mainPackageSn (STRING, 是)
    └── sendSubRequestList[] (OBJECT[], 否)
        ├── carrierId (LONG, 是)
        ├── trackingNumber (STRING, 是)
        └── selfShippingWarehouseId (STRING, 是)

request

sendSubRequestList[]

网关 params 写法

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "mainPackageSn": "PKG-MAIN-123456789",
    "sendSubRequestList": [
      {
        "carrierId": 123456789,
        "trackingNumber": "1Z999AA10123456784",
        "selfShippingWarehouseId": "WH-001"
      }
    ]
  }
}

---

Response（Temu body 解析后）

response
├── success
├── errorCode
├── errorMsg
└── result (BOOLEAN)

response 顶层字段

---

示例

python scripts/global_self_fulfilled_logistics_shipment_sub_confirm.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "mainPackageSn": "PKG-MAIN-123456789",
    "sendSubRequestList": [
      {
        "carrierId": 123456789,
        "trackingNumber": "1Z999AA10123456784",
        "selfShippingWarehouseId": "WH-001"
      }
    ]
  }
}'

典型流程：主包裹已发货并取得 mainPackageSn（bg.logistics.shipment.get）→ 同一最小 SKU 需拆分子包裹时 → 本接口追加 sendSubRequestList 子包裹物流信息。

确认发货 V2 — bg.logistics.shipment.v2.confirm

Description: The bg.logistics.shipment.v2.confirm interface is designed to synchronize and return order fulfillment information through this interface. Switch the order status from pending shipment to shipped（同步并回传订单履约/发货信息，将订单状态从待发货切换为已发货）。

网关鉴权字段由本 skill 网关脚本处理；业务参数见下方 request。建议使用 `tokenPurpose=order-shipping`。

前置依赖： carrierId 与 bg.logistics.companies.get 返回的 `logisticsServiceProviderId` 相同；selfShippingWarehouseId 来自 `linkfox-temu-fulfillment-global` 的 `bg.logistics.warehouse.list.get`（warehouseId）。订单号来自 `linkfox-temu-order-global`（如 bg.order.detail.v2.get）。

---

Request 结构（官方顶层）

params
└── request (OBJECT, 选填)
    ├── sendType                    ← 必填
    └── sendRequestList[]           ← 必填（Shipment package details）
        ├── carrierId               ← 必填
        ├── trackingNumber          ← 必填
        ├── selfShippingWarehouseId ← 必填
        ├── orderSendInfoList[]     ← 必填（本包裹内商品行）
        │   ├── parentOrderSn       ← 必填
        │   ├── orderSn             ← 必填
        │   ├── goodsId             ← 选填
        │   ├── skuId               ← 选填
        │   └── quantity            ← 必填
        ├── confirmAcceptance[]     ← 选填
        └── subSendRequests[]       ← 选填（子包裹/子运单）
            ├── carrierId           ← 必填（当使用 subSendRequests 时）
            ├── trackingNumber      ← 必填
            └── selfShippingWarehouseId ← 必填

request 内字段

sendType

sendRequestList[] 元素字段

orderSendInfoList[] 元素字段

confirmAcceptance[] 枚举值

仅当订单存在对应待处理事项且商家选择「拒绝申请并继续发货」等场景时传入；无此类事项可省略。

subSendRequests[] 元素字段

使用 `subSendRequests` 时，父级 `sendRequestList` 元素仍须填写 `orderSendInfoList` 等；子项用于补充额外运单/仓库组合，具体与 `sendType=1` 等多包裹场景配合，以 Partner 文档与订单详情约束为准。

网关 params 写法（sendType=0 单包裹示例）

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "sendType": 0,
    "sendRequestList": [
      {
        "carrierId": 123456789,
        "trackingNumber": "1Z999AA10123456784",
        "selfShippingWarehouseId": "WH-001",
        "orderSendInfoList": [
          {
            "parentOrderSn": "PO-xxx",
            "orderSn": "O-xxx",
            "goodsId": 987654321,
            "skuId": 111222333,
            "quantity": 1
          }
        ]
      }
    ]
  }
}

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "sendType": 1,
    "sendRequestList": [
      {
        "carrierId": 123456789,
        "trackingNumber": "TRACK-A",
        "selfShippingWarehouseId": "WH-001",
        "orderSendInfoList": [
          {
            "parentOrderSn": "PO-xxx",
            "orderSn": "O-xxx-a",
            "quantity": 1
          }
        ],
        "confirmAcceptance": ["DENY_CANCELLATION"],
        "subSendRequests": [
          {
            "carrierId": 123456789,
            "trackingNumber": "TRACK-B",
            "selfShippingWarehouseId": "WH-001"
          }
        ]
      }
    ]
  }
}

官方表将顶层 `request` 标为选填（False），但 `sendType`、`sendRequestList` 及其子字段多为必填；实际调用时应传入完整 `request` 对象。

---

Response（Temu body 解析后）

response
├── success
├── errorCode
├── errorMsg
└── result (OBJECT)
    ├── assistantAgreementText
    └── warningMessage[]

顶层字段

result 内字段

调用成功时先判断 `response.success === true`，再查看 `result.warningMessage` 是否有需向用户展示的警告；发货是否最终在平台侧生效，建议再调 `linkfox-temu-order-global` 的 bg.order.detail.v2.get 核对订单状态。

---

典型流程

1. linkfox-temu-order-global          → 待发货订单 / 订单详情（parentOrderSn、orderSn、数量）
2. bg.logistics.companies.get    → carrierId（= logisticsServiceProviderId）
3. linkfox-temu-fulfillment-global → bg.logistics.warehouse.list.get → warehouseId / selfShippingWarehouseId
4. bg.logistics.shipment.v2.confirm（本接口）→ 提交运单并确认发货
5. linkfox-temu-order-global          → 刷新订单状态（parentOrderStatus 等）

---

示例

export LINKFOXAGENT_API_KEY="<key>"

python scripts/global_self_fulfilled_logistics_shipment_v2_confirm.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "sendType": 0,
    "sendRequestList": [
      {
        "carrierId": 123456789,
        "trackingNumber": "9400111899223344556677",
        "selfShippingWarehouseId": "YOUR_WAREHOUSE_ID",
        "orderSendInfoList": [
          {
            "parentOrderSn": "PO-20260101001",
            "orderSn": "O-20260101001-1",
            "skuId": 58224724203874,
            "quantity": 2
          }
        ]
      }
    ]
  }
}'

python scripts/temu_global_proxy.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "type": "bg.logistics.shipment.v2.confirm",
  "params": {
    "request": {
      "sendType": 0,
      "sendRequestList": []
    }
  }
}'

查询发货信息 V2 — bg.logistics.shipment.v2.get

Description: The bg.logistics.shipment.v2.get interface is for sellers to verify shipped info after self-fulfillment（卖家自发货后，按订单查询并核对已提交的发货/物流信息）。

网关鉴权字段由本 skill 网关脚本处理；业务参数见下方 request。建议使用 `tokenPurpose=order-shipping`。

通常在 `bg.logistics.shipment.v2.confirm` 确认发货之后调用，用于核对运单号、包裹号、承运商及子包裹信息；parentOrderSn / orderSn 来自 `linkfox-temu-order-global`。

---

Request 结构（官方顶层）

params
└── request (OBJECT, 选填)
    ├── parentOrderSn    ← 必填
    └── orderSn          ← 必填

request 内字段

官方表将顶层 `request` 标为选填（False），但 `parentOrderSn`、`orderSn` 均为必填；实际调用时应传入完整 `request` 对象。

网关 params 写法

{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "parentOrderSn": "PO-20260101001",
    "orderSn": "O-20260101001-1"
  }
}

---

Response（Temu body 解析后）

response
├── success
├── errorCode
├── errorMsg
└── result (OBJECT)
    └── shipmentInfoDTO[]              ← shipment result（发货结果列表）
        ├── carrierId
        ├── carrierName
        ├── trackingNumber
        ├── skuId
        ├── quantity
        ├── packageSn
        ├── packageDeliveryType
        ├── trackingWarningLabel
        ├── cooperativeWarehouseDTO (OBJECT)   ← 合作仓履约时可能有值；卖家自发货时可能为空
        │   ├── warehouseProviderCode
        │   ├── warehouseProviderBrandName
        │   ├── warehouseCode
        │   └── warehouseName
        └── subPackageShipmentInfoList[]     ← subPackage Shipment result（子包裹发货结果）
            ├── carrierId
            ├── carrierName
            ├── packageSn
            ├── packageDeliveryType
            └── trackingNumber

顶层字段

result 内字段

shipmentInfoDTO[] 元素字段

packageDeliveryType（主包裹与子包裹共用）

trackingWarningLabel

cooperativeWarehouseDTO 内字段

卖家自发货（Self-Fulfilled）场景下，该对象常为 空或不返回；合作仓履约订单才需关注。

subPackageShipmentInfoList[] 元素字段

调用成功时先判断 `response.success === true`，再解析 `result.shipmentInfoDTO`。若需核对平台侧订单状态，可配合 `linkfox-temu-order-global` 的 bg.order.detail.v2.get。

---

典型用法

1. bg.logistics.shipment.v2.confirm   → 确认发货
2. bg.logistics.shipment.v2.get       → 按 parentOrderSn + orderSn 核对运单、包裹号、预警标签
3. （拆包场景）subPackageShipmentInfoList → 获取各子包裹 packageSn / trackingNumber，供 sub.confirm 等后续操作

---

示例

export LINKFOXAGENT_API_KEY="<key>"

python scripts/global_self_fulfilled_logistics_shipment_v2_get.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "request": {
    "parentOrderSn": "PO-20260101001",
    "orderSn": "O-20260101001-1"
  }
}'

python scripts/temu_global_proxy.py '{
  "accessToken": "TOKEN",
  "tokenPurpose": "order-shipping",
  "type": "bg.logistics.shipment.v2.get",
  "params": {
    "request": {
      "parentOrderSn": "PO-20260101001",
      "orderSn": "O-20260101001-1"
    }
  }
}'