All Market：Adjust product dimensions to two decimal places

To support a more consistent product publishing experience across all markets, TikTok Shop will standardize product dimension values to two decimal places. This update is a data-format standardization for dimension fields only. It does not affect weight fields, does not introduce a new business rule, and does not change the data type of the related Product API fields. According to the current Product API design, the affected dimension fields are already defined as string values. This means requests and responses at the API protocol level remain compatible with decimal-formatted values.

What Is Changing Starting on June 17, 2026, TikTok Shop will support and return product dimension values in a standardized decimal format with up to two decimal places across all markets. Weight fields are not affected by this change.

Examples:

• 10 remains 10
• 10.5 remains 10.5
• 10.55 remains 10.55
• Values with more than two decimal places will be normalized according to the platform rule before downstream use

Impacted APIs and Fields This change applies to product-related dimension fields used in TikTok Shop Product APIs. Based on the current technical design, these fields are already defined as string types.

Typical impacted fields include:

• Dimension fields such as package_length, package_width, and package_height
• Related product and SKU dimension fields in create, edit, query, and calculation flows

Note: package_weight and other weight-related fields are not impacted by this change.

Compatibility Note Because the related Product API fields are already string typed, this update does not require an API schema change and does not create a protocol-level breaking change.

What Developers Need to Do Although the TikTok Shop API schema remains compatible, ISVs should review their own downstream implementations carefully for dimension fields.

Some developers may have interpreted previous marketplace rules in their own systems and stored dimension values as integers in ERP, PIM, OMS, or other internal systems. After this change takes effect, those assumptions may cause issues such as:

1. Decimal values being truncated or rounded unexpectedly
2. Validation logic rejecting decimal-formatted inputs
3. Synchronization failures between TikTok Shop and internal systems
4. Incorrect value display in merchant-facing or operator-facing tools

To ensure compatibility, developers should review and update the following if needed:

1. Parsing logic: confirm your application accepts decimal-formatted strings for dimension fields
2. Validation logic: remove any integer-only assumptions for dimension fields
3. Storage schema: ensure your database or ERP model can store decimal dimension values without precision loss
4. Transformation logic: check any conversion logic between TikTok Shop dimension data and internal data models
5. Display logic: verify that front-end or reporting systems can correctly present decimal dimension values

Recommended Action Timeline