来自 TikTok Shop 官方资料快照 ·
- 当前资料结构化阅读页
- 固定快照已留存，可追溯
- 官方原文可核对
资料正文
§1 For US Market: POD Customization Details Are Now Available
| Market | US |
|---|---|
| Audience | Apps that retrieve and manage order data for US sellers |
| Change type | Additive, non-breaking API enhancement |
§2 Overview
TikTok Shop has added POD customization identifiers to the Get Order Detail API and introduced the Get Pod Detail API. Together, these changes let your app detect a customized POD SKU and retrieve the customization JSON needed to display or process it. This change is additive. Existing apps that ignore unknown response fields can continue to process orders. Apps that support POD fulfillment, use strict response models, or maintain field allowlists should update their integration.
§3 What is changing
#§4 Identify customized POD line items
Identify customized POD line items
The Get Order Detail API now returns two fields in each object in data.orders[].line_items[].
| Field | Type | Description |
|---|---|---|
is_pod_customized | Boolean | Indicates whether the SKU contains print-on-demand customization. |
pod_info_id | String | Identifies the POD customization data associated with the order line item. |
§5 Retrieve POD customization details
Retrieve POD customization details
For each customized POD line item, call the Get Pod Detail API to retrieve its customization payload.
| API | Get Pod Detail |
|---|---|
| Endpoint | POST /fulfillment/202606/pod_details/get |
| Version | v202606 |
| Request | main_order_id and query_order_lines[], including order_line_id, product_id, sku_id, and pod_order_data_id. |
| Response | data.pod_details[], including order_line_id and pod_info_json, plus data.status_code. |
§6 How to integrate
#§7 Step 1: Update your order response model
Step 1: Update your order response model
- Continue calling
GET /order/202507/orders. - Add
is_pod_customizedandpod_info_idto your line-item response model. - Keep both fields optional so non-POD line items and historical orders remain compatible.
§8 Step 2: Detect line items that require POD data
Step 2: Detect line items that require POD data
| Condition | Meaning | Required action |
|---|---|---|
is_pod_customized = true | Customized POD line item | Collect its order, line-item, product, SKU, and POD data identifiers. |
is_pod_customized = false or absent | Standard line item | Continue your existing order flow. |
§9 Step 3: Request POD details
Step 3: Request POD details
Call Get Pod Detail at POST /fulfillment/202606/pod_details/get with the main order ID and customized line items. This endpoint requires the seller.redeem_info.write scope. Use the POD identifier returned for the line item as query_order_lines[].pod_order_data_id.
{
"main_order_id": "576461413038785752",
"query_order_lines": [
{
"order_line_id": "577086512123755123",
"product_id": "1732453831920750867",
"sku_id": "1732453830297817363",
"pod_order_data_id": "123456"
}
]
}
§10 Step 4: Match and parse the response
Step 4: Match and parse the response
- Match each object in
data.pod_details[]to your order line item byorder_line_id. - Parse the JSON string returned in
pod_info_jsonbefore using the customization data. - Do not start production or fulfillment when the required customization data is missing or cannot be parsed.
Request POD details only for line items where is_pod_customized is true. This keeps the standard order flow unchanged.
§11 FAQ
#§12 Does this change affect every US order?
Does this change affect every US order?
No. Use the new flow only for line items identified as customized POD items. Standard orders continue through the existing order and fulfillment flow.
§13 Can I ignore the new fields?
Can I ignore the new fields?
Yes, if your app does not support POD customization and can safely ignore unknown response fields. Apps with strict schemas should add the fields to prevent parsing failures.