Fill in the scale weight information in the SKU level

Feature Summary

• Feature Name: SKU-level Dimensions & Weight (Package Size and Weight) Input
• Core Change: When creating or editing products, sellers can now enter package length, width, height, and weight at the SKU level. Different SKUs under the same product will display different shipping fees on the consumer side, enabling more accurate shipping fee calculation.
• Mandatory?: No. Sellers can choose whether to enable SKU-level dimensions and weight. If not selected, the original product (PID)-level logic remains unchanged and existing operations are not affected.
• Supported Entry Points: PC product creation / PC product editing / Excel bulk listing / POP cross-border distribution / API (ISVs need to integrate the new fields); APP does not support creating or editing SKU-level dimensions and weight in this phase.

---

Background and Value of the Feature

Under the original logic, package dimensions and weight could only be entered at the product (PID) level, meaning all SKUs under the same product shared one set of dimensions and weight data. In real operations, however, different variants of the same product (such as different colors, capacities, or bundle sizes) often correspond to different actual packaging dimensions and weights, which creates two major issues when using a single shared value:

• Inaccurate shipping fees: The shipping fee shown to users on the storefront may differ from the seller's actual logistics cost, affecting seller margin and pricing strategy.
• Logistics experience deviation: Inaccurate dimensions and weight can affect warehousing, fulfillment, customs clearance, and delivery-time estimation, which in turn impacts user experience.

With this feature launch, sellers can maintain dimensions and weight separately for each SKU. Based on the actual SKU dimensions and weight selected by the seller, the platform will display the accurate shipping fee for the corresponding SKU to consumers, delivering a true what-you-select-is-what-you-get shopping experience.

---

Change Details

Scope

SKU-level Dimensions & Weight vs. Product-level Dimensions & Weight

---

Feature Guide (by Entry Point)

Prerequisites: The product has at least 2 SKUs; it is not a virtual bundle product; and the current market has enabled SKU-level dimensions and weight.

Scenario 1: New Product Listing on PC (Create Product)

Path: Seller Center → Products → Add New Product → Fill in product information
Steps:

1. On the new product page, fill in the standard product basic information and SKU information first (at least 2 SKUs).
2. Check "Configure Weight & Dimensions by SKU" (unchecked by default).
   
3. After checking it:
   • The original product-level dimensions and weight input fields are automatically hidden;
   • The SKU list will add new columns for Weight / Length / Width / Height.
     
4. In the SKU list, fill in dimensions and weight at the SKU level using any of the following three methods:
   • Enter one by one: Input values directly on each SKU row;
   • Bulk apply: Use the Bulk Apply entry in the table header to populate all SKUs at once;
   • By dimension in batch: For example, fill in by color/size to improve efficiency.
5. After completing the inputs, click Submit.

Tips

• After SKU level is enabled, the product-level dimensions and weight fields will no longer be shown, and all dimensions/weight information will follow the SKU-level inputs.
• If the product has only 1 SKU, please continue to use the product (PID) level, which is consistent with the original experience.

Scenario 2: Edit Product on PC (Including Existing Listings)

Path: Seller Center → Products → Product List → Edit
Supported capabilities:

• PID → SKU: Existing products originally using product-level input can be switched to SKU-level input on the edit page by checking "Configure Weight & Dimensions by SKU" and then supplementing the dimensions and weight for each SKU.
• SKU → PID: For products already using SKU-level input, simply uncheck the option to revert to product (PID) level.
• Edits within SKU level: Directly adjust the dimensions and weight of any SKU in the SKU list and save.
• The entire chain (seller side → logistics → consumer-facing shipping fee) will be updated based on the latest data.

Before enabling (the Sales information section defaults to PID level, and the Shipping section below is used to fill in product-level dimensions and weight):After enabling (the Sales information section adds required SKU weight and dimension fields, while the Shipping section input is hidden):Bulk management: You can populate dimensions and weight for multiple SKUs in one operationMutually exclusive with Bundle (virtual bundle): once SKU-level dimensions and weight are enabled, the Bundle option is grayed outNote: When switching back from SKU level to PID level, the original SKU-level dimensions and weight data will be overwritten by one unified product-level set. Please confirm before saving.

Scenario 3: Excel Bulk Listing

Path: Seller Center → Products → Bulk Listing / Bulk Edit (Excel template)
Steps:

1. In the Excel template, enter the dimensions and weight fields separately for multiple SKUs under the same product.
2. Different SKUs under the same product should be entered in multiple rows, and different values are allowed in the dimensions/weight columns.
3. Upload the Excel file, and the data will be imported once the platform successfully recognizes it.
4. After import, you can see in the product details that each SKU has been bound with its own dimensions and weight data.

Excel template: One row per SKU, with different weight and dimension values entered by SKU rowOnline editor: Each SKU row can display and edit dimensions and weight independentlyField validation: Example of online validation errors for dimensions and weight fields

Scenario 4: APP (View Only, No Create/Edit Support)

• If a product has already been configured with SKU-level dimensions and weight on PC, the APP will prompt that the package dimensions and weight must be edited on PC, and no edit entry will be available on APP.
• If the product still uses PID level, the APP editing experience remains unchanged.

APP Shipping section: When the product has enabled SKU dimensions and weight on PC, the Weight and Dimension module is hidden. Only a guidance message is shown, directing sellers to edit the product in Seller Center on PC.

Scenario 5: API / ISV Integration (Open API Sellers)

• New SKU-level dimensions and weight fields are introduced in this release. If sellers upload products through self-built APIs or ISVs, the ISV must complete integration of the new fields before SKU-level dimensions and weight can be uploaded.
• If the ISV has not completed the upgrade, the API will continue to upload by product (PID) level, without affecting existing functionality.
• Interfaces involved: fields will be updated in product creation, product upload, product query, and other related APIs.
• API go-live timing: The fields will be published externally after the seller-side PC feature goes live, and sellers and ISVs can then begin integration.

API integration recommendation: Sellers using ISVs are advised to contact their ISV providers as early as possible to complete adaptation for the new fields. Sellers with self-built integrations should follow updates in the Open Platform documentation.

---

Consumer-side Experience Changes

• Product detail page / Cart / Checkout: When users switch between different SKUs, the shipping fee will be recalculated in real time based on that SKU's dimensions and weight, instead of displaying one unified value.
• User perception: what you select is what you get — shipping fees are transparent and strictly correspond to the selected SKU.
• The overall consumer-side UI remains unchanged; only the underlying shipping-fee calculation logic refreshes as users switch SKUs.

Seller-side shipping fee estimate change: When SKU-level dimensions and weight are not enabled, shipping fees/costs are shown as an estimated value. After SKU-level dimensions and weight are enabled, because different SKUs have different weight values, shipping fees/costs are shown as a range.
Consumer-side shipping fee estimate change: Shipping fees on the consumer side are displayed accurately for different SKUs based on SKU-level dimensions and weight.

---

Actions Required from Sellers

1. Assess your catalog: Identify products where packaging dimensions/weight vary significantly across SKUs, and prioritize enabling SKU-level dimensions and weight for those products.
2. Enable step by step: When creating or editing products on PC, actively turn on Configure Weight & Dimensions by SKU.
3. Validate data: After input, verify the shipping fee shown on the consumer-facing product detail page and ensure it aligns with actual logistics cost.
4. Update ISV integration: If you upload via an ISV, confirm the schedule for new-field integration with your ISV provider in advance.

---

Frequently Asked Questions (FAQ)

---