快工助手跨境电商知识与商机助手
快工云仓服务介绍

US/MX/SEA Market：Support product weight and dimensions at the SKU level

TikTok Shop 官方资料 · TikTok Shop Partner Center 开发者文档 · 适合开发者

stable本次发布有变化全部展示

来自 TikTok Shop 官方资料快照 ·

打开官方原文 ↗
  1. 当前资料结构化阅读页
  2. 固定快照已留存，可追溯
  3. 官方原文可核对
查看技术与溯源信息
平台 / profile
TikTok Shop / profile.tiktok.docs_api
语言
en-US
发布版本
cn-20260909-2
标签
zhuge/sourceplatform/tiktok_shopaudience/developercategory/api_doctopic/compliancetopic/developer

资料正文

§1 What is changing?

TikTok Shop is introducing SKU-level dimension and weight support in Partner APIs. This update allows product weight and dimensions to be maintained and synchronized at the SKU level, which improves shipping-related accuracy for products with multiple variants. Previously, weight and dimension data were mainly handled at the product level. With this release, APIs now support dedicated SKU-level fields so partners can send and retrieve more precise package information for each SKU. Two areas of the API are affected:

  1. Product query APIs — new response fieldsThe following fields are now returned in product query responses:
  2. sku_weight
  3. sku_dimensions

Applicable APIs:

  • Get Product
  • Check Product Listing
  • Product creates and updates APIs. —The new request fields following fields are now supported in product write requests:
  • sku_weight
  • sku_dimensions

Applicable APIs:

  • Create Product
  • Edit Product
  • Partial Edit Product
#

§2 Field details

Field details

#

§3 `sku_weight`

sku_weight

FieldTypeRequiredExampleDescription
sku_weightStructNo-Weight information for a SKU package.
valueStringYes1.32Package weight. Must be a positive number. Formatting depends on the selected unit.
unitStringYesKILOGRAMAllowed values vary by region. For example,the US supports KILOGRAM and POUND, while other regions may support KILOGRAM or GRAM depending on market rules.

Additional notes:

  • Package weight is generally required except for virtual product categories.
  • Weight should reflect the packaged item.
  • If the fee calculated by weight is higher than the fee calculated by dimensions, weight takes precedence in fee calculation.
#

§4 `sku_dimensions`

sku_dimensions

FieldTypeRequiredExampleDescription
sku_dimensionsStructNo-Dimension information for a SKU package, including length, width, height, and unit.
lengthStringYes10Package length.
widthStringYes10Package width.
heightStringYes10Package height.
unitStringYesCENTIMETERAllowed values vary by region. For example, US supports CENTIMETER and INCH, while other regions support CENTIMETER.

Additional notes:

  • Dimensions should reflect the packaged item.
  • sku_weight.unit and sku_dimensions.unit must use the same measurement system.
#

§5 How does product logic work?

How does product logic work?

When SKU-level data is available, the system reads SKU-level values first. When SKU-level data is not available, the system falls back to product-level values. If a product-level value is requested while only SKU-level data exists, the system uses the maximum SKU value as the fallback. If SKU-level data is requested while only product-level data exists, each SKU inherits the product-level value by default.

#

§6 Which markets are affected?

Which markets are affected?

This capability is currently aligned with the existing launch scope described in the reference GTM materials, with priority support for:

  • US、MX、SEA
#

§7 Who is affected?

Who is affected?

This change affects developers and integration partners whose applications are used for:

  • Product creation and editing
  • Product data synchronization
  • Shipping-related attribute management
  • Product query and listing validation

It is also relevant to internal Partner Product, Engineering, Ops, PSO, and Support teams.

#

§8 What action is required?

What action is required?

  1. Update product query handlingRead and parse the new response fields:
  2. sku_weight
  3. sku_dimensions
  4. Update product create and edit logic Support sending the new request fields for each SKU:
  5. sku_weight
  6. sku_dimensions
  7. Validate unit and data rulesEnsure:
  8. Weight and dimension units follow regional rules
  9. Weight and dimension units use the same measurement system
  10. Values reflect packaged items instead of unpackaged products
  11. Align seller-facing and support messagingPrepare guidance for cases where:
  12. Shipping estimation may be shown as a range for multi-SKU products
  13. SKU-level values override product-level values
  14. Product-level fallback still applies when SKU-level data is not provided
#