03/11/2026 · Add pickup_code next to every warehouse id#
Every response that returns a warehouse id now also returns its warehouse code.¹ Also Add Order, Update Order and Cancel Order.Each code sits right after its id: pickup_id → pickup_code, vendor_pickup_id → vendor_pickup_code.PK + (id + 100000), the same code GET /pickup/list shows. null when the id is null.
{ "pickup_id": 21, "pickup_code": "PK100021" }
08/10/2026 · Add esku to inventory items#
¹ Also Add Order, Update Order and Cancel Order.| Field | Value |
|---|
esku | ERP SKU of the inventory product. "" when the product has no ERP code. |
unit_name | Stock unit, e.g. Thùng, Hộp. null when the product has no unit set. |
{ "inventory_sku": "SRM-100", "esku": "ERP-SRM-100", "unit_name": "Hộp" }
08/10/2026 · Add esku and unit_name to received SKU rows#
Both fields sit right after inventory_sku.| Field | Value |
|---|
esku | ERP SKU of the inventory product. "" when the product has no ERP code. |
unit_name | Stock unit, e.g. Thùng, Hộp. null when the product has no unit set. |
Both are null when the warehouse reported a SKU that is not linked to an inventory product.
{ "inventory_sku": "SRM-100", "esku": "ERP-SRM-100", "unit_name": "Hộp", "quantity": 2, "accepted": 1 }
02/10/2026 · Add unit_name to inventory items#
| API | New field | Value |
|---|
| Get Order Detail ¹ | parcels[].inventory_items[].unit_name | Stock unit, e.g. Thùng, Hộp. null when the product has no unit set. |
¹ Also Add Order, Update Order and Cancel Order.{ "inventory_sku": "SRM-100", "unit_name": "Hộp" }
01/10/2026 · Add order_item_id to catalogue and inventory items#
One order can carry the same catalogue_sku on several lines (e.g. a sold line and a gift line), so catalogue_sku alone cannot tell which line an inventory row belongs to.| API | New field | Meaning |
|---|
| Get Order Detail ¹ | parcels[].catalogue_items[].order_item_id | ID of the order line |
| Get Order Detail ¹ | parcels[].inventory_items[].order_item_id | The catalogue line this inventory row belongs to |
¹ Also Add Order, Update Order and Cancel Order.Match inventory_items to catalogue_items by order_item_id. catalogue_sku is kept unchanged.
"catalogue_items": [
{ "order_item_id": 987654321, "catalogue_sku": "COMBO-01", "is_gift": false },
{ "order_item_id": 987654322, "catalogue_sku": "COMBO-01", "is_gift": true }
],
"inventory_items": [
{ "order_item_id": 987654321, "inventory_sku": "SRM-100" },
{ "order_item_id": 987654321, "inventory_sku": "TONER-150" },
{ "order_item_id": 987654322, "inventory_sku": "SRM-100" }
]
21/09/2026 · Rename order status 600 and 900#
Display name Non-breaking| Status | Before | After | Vietnamese |
|---|
600 | Delivering | In-transit | Đang giao hàng → Đang vận chuyển |
900 | Deliveried | Completed | Giao hàng thành công → Hoàn thành |
Applies to status_name in Get Order List, Get Order Detail, Update Order and the order webhook, and status_display in Get Order Finance. See Status overview.Only the name changes. Match on status_id, which stays 600 / 900.
03/08/2026 · Rename order status 400 to "Processing"#
Display name Non-breaking| Status | Before | After | Vietnamese |
|---|
400 | Created shipment | Processing | Đã tạo vận đơn → Đang xử lý |
Applies to status_name in Get Order List, Get Order Detail, Update Order and the order webhook, and status_display in Get Order Finance. See Status overview.The status code 400, the status flow, transitions, filters and status groups are unchanged. The status and status_group query parameters behave exactly as before.{ "status_id": 400, "status_name": "Processing" }
If your integration matches the order status by name string ("Created shipment"), update it to "Processing".Match on status_id = 400 instead — the numeric code is stable and is not affected by label changes.
400 now reads "Đang xử lý", the same wording as the In Process status group. The status code 400 remains the only reliable identifier. 14/08/2025 · Add shipping_fee to parcels#
| API | New field | Note |
|---|
| Get Order Detail | parcels[].shipping_fee | Only for Lazada and Shopify |
"parcels": [ { "shipping_fee": 0 } ]
20/05/2025 · Add escrow_release_time#
{ "escrow_release_time": 0 }
04/11/2024 · New API "Cancel Order"#
04/10/2024 · Add seller_id; vendor_id is now the vendor's Seller ID#
| API | Change |
|---|
| Get Order Detail | New field seller_id |
| (same API) | parcels[].inventory_items[].vendor_id now holds the Seller ID of the vendor |
{ "seller_id": 0, "parcels": [ { "inventory_items": [ { "vendor_id": 0 } ] } ] }
27/06/2024 · New API "Update Document" for orders#
24/06/2024 · Add order type and vendor fields#
| API | New field |
|---|
| Get Order Detail | order_type |
| (same API) | parcels[].inventory_items[].vendor_name, vendor_id, vendor_pickup_id |
{ "order_type": "normal", "parcels": [ { "inventory_items": [ { "vendor_name": "string", "vendor_id": 0, "vendor_pickup_id": 0 } ] } ] }
{
"origin_shipping_fee": 100000,
"buyer_shipping_fee": 60000,
"seller_shipping_fee": 30000,
"seller_ship_rebate": 30000,
"platform_ship_rebate": 10000,
"wrong_weight_adjust": 15000
}
| Platform | Seller's shipping fee | Shipping invoice |
|---|
| Shopee / Lazada | seller_shipping_fee + wrong_weight_adjust | Seller's shipping fee + wrong_weight_adjust |
| TikTok / Brand.com | seller_shipping_fee + wrong_weight_adjust | origin_shipping_fee + wrong_weight_adjust |
Origin shipping fee: The shipping fee for a platform or an e-commerce marketplace is calculated based on the total item weight and the shipping fee policy set up within the system.Wrong Weight Adjust: The actual shipping fee charged by the shipping partner may differ from the estimated fee provided by Tiktokshop or set up on various brand websites.Shipping Invoice: Each month, you will receive shipping fee invoices from the platforms or shipping partners. There may be differences in the invoice amounts between the various sales platforms.Furthermore, you need to take note of recording the revenue from buyer's shipping fees for each order on the Tiktokshop/Brand.com platform.
