15of115
At least one numeric-zero SKU across multi-SKU rows.
15 of 115 multi-SKU rows included at least one zero-stock variant
115 of 120 first-page result/detail pairs returned multiple complete SKU records. 15 included at least one SKU whose amountOnSale value was zero, while only 13 placed at least half of returned stock in one SKU. The study measures API-returned values, not physical or reserved inventory.
Liam Cai · Founder, SupplymoYiwu, ChinaWhat we measured
Numeric-zero variant presence across 115 comparable multi-SKU result/detail rows
amountOnSale is not audited physical inventory. Numeric-zero values do not establish persistent stockouts, supplier capacity or checkout acceptance.
amountOnSale is not audited physical inventory, factory capacity, reserved stock, replenishment ability or a purchase guarantee.
Study reading
A product-level total does not answer the target-SKU question
All 120 sampled detail responses returned productSkuInfos. 115 rows contained multiple complete SKU records and 5 contained one. The multi-SKU rows held 4213 SKU records in total.
Among the 115 comparable multi-SKU rows, 15 contained at least one numeric-zero amountOnSale value, covering 61 SKU records. Missing or non-numeric values were excluded rather than converted to zero.
The returned value does not explain why a SKU was zero, how long it remained zero or whether a supplier could produce or replenish it after contact.
Study reading
Most rows did not show extreme one-SKU concentration
The largest SKU held at least half of returned stock in 13 rows and at least 80% in 5. The median largest-SKU share was 12.51%.
Product-level amountOnSale matched the sum of SKU-level values in 115 of 115 comparable rows. That supports internal arithmetic consistency in this draw, not the accuracy of the underlying inventory.
A SKU row can represent color, size, pack quantity, material or combinations of attributes. A large row count is not automatically a large number of substantially different products.
Study reading
How a buyer can use the result
Specify the exact SKU before comparing price, MOQ or availability. Put color, size, model, material, pack and quantity into the request instead of sending only the listing link.
Ask the supplier to confirm current availability, production status and written dispatch terms for that exact variant. Keep the API snapshot and supplier confirmation as separate evidence.
Use the same SKU identity for samples, photos, labels, packaging and order documents. This prevents a broad product total from standing in for the variation the buyer will actually receive.
Use this data
Everything here is free to reuse with attribution under CC BY 4.0. If you need a cut of the data we have not published, ask and we will run it.
Quote it, or take the whole file
One line, free to quote with attribution
In a Supplymo non-random sample of 120 first-page result/detail API pairs across 12 selected English searches on 1688, 15 of the 115 pairs with multiple complete SKU rows included at least one numeric-zero amountOnSale value, and 13 showed at least half of their API-reported visible inventory in a single SKU.
How to cite this study
Liam Cai. "Numeric-zero variants in 1688 SKU stock fields." Supplymo, 29 September 2026, https://supplymo.com/research/1688-sku-stock-structure.
The internal source contains 120 distinct offer IDs, but no seller identity. Rows are not 120 distinct suppliers, and amountOnSale is not audited physical inventory. 11 stated limits travel inside the file. Free to reuse with attribution under CC BY 4.0.
Method
How the sample was collected
Everything here is reproducible from the evidence file and the sampling script.
Source
com.alibaba.fenxiao.crossborder:product.search.keywordQuery + product.search.queryProductDetail (read-only)
Sampling frame
12 English keyword searches, default first results page only, 10 platform-ranked result positions per keyword. Each keyword-position is one observation.
Collection window
Single day, 2026-08-12 in China
Write operations
None. No order, payment, enquiry, messaging, refund or logistics endpoint was called.
Check the figures yourself
The internal source contains 120 distinct offer IDs, but no seller identity. Rows are not 120 distinct suppliers, and amountOnSale is not audited physical inventory.
- Rows
- 120
- Collected
- 2026-08-12
- Stated limits
- 11
Readings tested before publication+
Is numeric zero being confused with a missing SKU stock field?
Method. Record SKU row count, amountOnSale field count and null count separately; count zero only after numeric parsing succeeds.
Result. 115 multi-SKU listings had complete numeric SKU stock rows; zero-stock variants were counted only inside that set.
Conclusion. Missing or non-numeric values are excluded, not converted to zero.
Are product-level total stock and the sum of SKU stock on the same observed scale?
Method. Compare productSaleInfo.amountOnSale with the sum of productSkuInfos[].amountOnSale for every complete multi-SKU listing.
Result. 115 of 115 comparable listings matched exactly; 0 differed.
Conclusion. The two returned levels were internally consistent in this draw, but neither is treated as audited physical inventory.
Does one listing with one SKU distort concentration?
Method. Exclude no-SKU and one-SKU listings from all largest-SKU-share thresholds.
Result. 5 listings had one SKU and 115 had multiple complete SKU rows.
Conclusion. Concentration denominators refer only to genuinely multi-SKU listings.
Does a zero stock number prove the buyer cannot buy that variation at checkout?
Method. Treat amountOnSale as an API-exposed snapshot and avoid any checkout or warehouse claim.
Result. No order-preview, cart, supplier message or physical inventory endpoint was called.
Conclusion. The result measures visible listing data, not reserved stock, factory capacity or a purchase guarantee.
Limits
The 11 limits of this sample
All 11 stated limitations, in the order the evidence file lists them. A number travels further than the caveat attached to it.
- 1This is not a random sample. It covers the default first page returned for 12 selected English keywords and does not represent all 1688 listings or categories.
- 2API-reported amountOnSale is not audited physical inventory. It does not prove factory capacity, warehouse stock, reserved stock, replenishment ability or what checkout will accept later.
- 3The 120 rows are result positions rather than distinct suppliers. The same seller can appear more than once, and this study does not make a supplier-level claim.
- 4A zero-stock SKU row means the API returned zero for that variation at collection time. It does not show why the value was zero, how long it remained zero or whether a supplier could make more after contact.
Show the other 7 limits+
- 5SKU rows can be combinations of colour, size, pack quantity, material and other attributes. A listing with 400 rows is not necessarily 400 substantially different products.
- 6Only listings with at least two complete numeric SKU rows and a positive SKU-stock total enter concentration thresholds. No-SKU, one-SKU, incomplete and zero-total rows are not silently converted into the denominator.
- 7The product total matched the sum of SKU rows in this draw, but that internal consistency does not validate the underlying stock numbers.
- 8The snapshot used one API client, default ranking and no buyer-specific filters. Login state, geography, filters and later listing changes may produce different results.
- 9The study is a single-day snapshot and does not measure stock persistence, sales velocity, restocking or seasonal availability.
- 10The findings do not accuse a seller or platform of misrepresentation. They support checking the exact target SKU before payment instead of relying on an aggregate listing total.
- 11Nothing here says a platform or seller has done anything wrong. The finding concerns values returned by one product-detail API response and does not establish what a rendered page, warehouse system or checkout would show.
Research boundary
What this study cannot tell you
- amountOnSale is not audited physical inventory, factory capacity, reserved stock, replenishment ability or a purchase guarantee.
- A numeric-zero SKU row does not establish why the value was zero or whether the supplier could make more after contact.
- The 120 rows map to distinct internal offer IDs but not necessarily distinct sellers; seller identity was not retained.
What this means for a buyer
A sample of this kind is a starting point for questions, not a verdict on any one supplier. Check the exact product and supplier you are about to pay.
Supplier verification
A free check before you commit. We run supplier checks from Yiwu, and we do not promise a lowest price.
Check a supplier →Questions a reader should ask about this
What is the one-line finding?
In a Supplymo non-random sample of 120 first-page result/detail API pairs across 12 selected English searches on 1688, 15 of the 115 pairs with multiple complete SKU rows included at least one numeric-zero amountOnSale value, and 13 showed at least half of their API-reported visible inventory in a single SKU. amountOnSale is API-reported visible inventory, not audited physical stock or checkout acceptance.
How many sampled rows returned multiple SKU records?
115 of 120 rows returned multiple complete SKU records; the median count among those rows was 12.
Does a zero amountOnSale prove the variant cannot be bought?
No. It means the API returned numeric zero for that SKU at collection time. The study did not test inventory persistence, supplier replenishment or checkout acceptance.
Was visible stock usually concentrated in one SKU?
No broad concentration claim is supported. Only 13 of 115 comparable multi-SKU rows placed at least half of returned stock in one SKU; the median largest-SKU share was 12.51%.
Were these 120 different suppliers?
No. The internal sample contained 120 distinct offer IDs, but seller identity was not retained, so the sample cannot be de-duplicated by shop.