Supplymo
Toy API field studyEvidence v1 · non-random sample

61 of 120 1688 toy product-detail API responses omitted shippingTimeGuarantee

We sampled 120 first-page toy results through 1688's English cross-border keyword API, then requested a product-detail response for each result. 59 responses returned productShippingInfo.shippingTimeGuarantee and 61 omitted it. The omission count varied across the twelve search terms.

The one-line version, free to quote with attribution: In a Supplymo non-random sample of 120 first-page toy results from 1688's English cross-border keyword API, 61 product-detail API responses omitted productShippingInfo.shippingTimeGuarantee; the water gun and slime kit searches each had nine omissions among ten sampled responses.

Liam Cai

Liam Cai · Founder, Supplymo

Published 18 August 2026 · Collected 2026-08-12 · Yiwu, China

shippingTimeGuarantee field return across 120 sampled 1688 toy product-detail API responses
shippingTimeGuarantee omitted
61
Returned shipIn48Hours
54
Returned shipIn24Hours
5

n = 120 product-detail API responses. Collected 2026-08-12. Non-random sample: 12 toy keyword searches, 10 first-page results and product-detail API responses each. API field omission says nothing about other surfaces or supplier conduct.

61/120

API responses omitted shippingTimeGuarantee

This is key presence in the product-detail response—not a reading of any other 1688 surface.

9 of 10

omissions for both water gun and slime kit

Each keyword split contains ten responses and is descriptive of this draw only.

59/120

API responses returned the field

Returned values were shipIn48Hours or shipIn24Hours in this sample.

54/59

returned shipIn48Hours

5 of 59 responses returned shipIn24Hours.

Omission varied by search term

water gun and slime kit each had nine omissions among ten product-detail API responses. building blocks and magnetic toys had at most two omissions among ten. The calls used the same API family, collection day and per-keyword denominator.

That contrast is a useful description of this sample, not an estimate for the whole toy category. The keywords were chosen deliberately and each split contains only ten responses, so the data cannot establish why the difference appeared or whether it persists over time.

Returned values used two documented strings

Among the 59 product-detail API responses that contained shippingTimeGuarantee, 54 returned shipIn48Hours and 5 returned shipIn24Hours. No other value appeared in this sample.

The official 1688 response schema places shippingTimeGuarantee under productShippingInfo. This study records the returned key and value only. It does not test production completion, international transit, customs, destination delivery or performance on an actual order.

How a buyer can use a response-level gap

When the sampled API response omitted shippingTimeGuarantee, that data source could not answer the dispatch-timing question. A buyer can close the gap by requesting a current written production and dispatch date tied to the exact product, variant, quantity and order terms before payment.

Keep the API observation and the supplier confirmation as separate evidence. One records what this response contained on 2026-08-12; the other records the commercial term agreed for a specific order. Neither should be substituted for the other.

What this study cannot tell you

Putting this before the method rather than after it is deliberate. A number without its boundary travels further than the boundary does.

  • It cannot establish what a rendered 1688 website, app, product description, other API surface or supplier conversation contained. The study queried one product-detail API response per sampled result.
  • It cannot establish seller intent, policy or performance. A missing key is an API-response observation, not a conclusion about a supplier or an actual order.
  • It is not a toy-safety assessment. The sample did not inspect materials, test reports, standards, age grading or destination-market requirements.
  • The per-keyword figures use ten product-detail API responses each. Nine out of ten describes this non-random draw; it is not a category-wide prevalence estimate.
  • The 120 rows are sampled product results and responses, not 120 distinct suppliers. Seller identity is not published, so the sample cannot be de-duplicated by shop.
  • The 40 refund-rate values returned as numeric zero are not interpreted as zero actual refunds. The direction check was inconclusive, and the field's unit, denominator and missing-data convention were not independently verified.

How the sample was collected

Source
com.alibaba.fenxiao.crossborder:product.search.keywordQuery + product.search.queryProductDetail (read-only)
Sampling frame
12 English toy keyword searches on the cross-border distribution channel, first API results page only, 10 platform-ranked product results per keyword. A product-detail API response was then requested for each result. The keyword list deliberately mixes safety-sensitive subcategories (water gun, toy gun, slime kit, magnetic toys, baby rattle) with ordinary ones (plush toy, building blocks, toy car, doll, puzzle toy, rc car, educational toy).
Collection window
Single day, 2026-08-12 in China
Write operations
None. No order, payment, enquiry, messaging or logistics endpoint was called.

The readings we tested before publishing

Each of these is a way the data could have been misread. We checked, and the check is published with its result, including where it came back inconclusive.

What does omission of shippingTimeGuarantee establish?

Method. Record hasOwnProperty for productShippingInfo.shippingTimeGuarantee on every product-detail API response instead of converting an omitted key into a real-world commercial term.

Result. The product-detail API response returned shippingTimeGuarantee on 59 of 120 sampled rows and omitted it on 61.

Conclusion. Omission establishes only that this product-detail API response did not contain the key. It does not establish what a rendered 1688 page, another API surface or a supplier conversation showed.

Does an API-returned refund-rate value of exactly 0.0 mean no refunds, or does it mean no data?

Method. Compare the after-sales experience-score distributions for rows returning numeric zero and rows returning a value above zero as a descriptive ambiguity check. The direction cannot authenticate the platform field's definition, denominator, scope or missing-data convention.

Result. In this toy sample the direction test is inconclusive: API-response rows returning zero have a median after-sales score of 3.8, below the 4 of rows returning a value above zero — the opposite direction from the general-shelf sample.

Conclusion. Unlike the general-shelf study, we cannot rule out the missing-data reading here. The count is therefore published only as 'API responses returning a numeric zero', and no claim is made about actual refunds.

Can repeated refund-rate values establish whether the field is product- or merchant-scoped?

Method. Group the observed non-zero API-returned values and measure the largest repeated cluster.

Result. The largest repeated non-zero value covers 3 of 79 non-zero rows.

Conclusion. No. The public sample contains no seller identity, so repetition cannot resolve product-versus-merchant scope. The values are reported only as values returned for each sampled product-detail response.

The stated limits, in full

All 11 of them travel inside the evidence file, so they stay attached to the data after it leaves this page.

  1. 1.This is not a random sample. Rows correspond to first-page English keyword API results ranked by the platform, so they cannot estimate field-return rates across all 1688 products, categories, dates or buyer interfaces.
  2. 2.This study measures whether named keys and values were present in one product-detail API response. It does not establish what a rendered website, app, description, other API surface or supplier conversation contained.
  3. 3.Per-keyword splits rest on 10 product-detail API responses each. Figures like 'nine out of ten' are descriptive of this draw only; no statistical test is applied and none would be meaningful at that size.
  4. 4.The zero-refund-rate count is a count of API responses returning a numeric zero. The descriptive score comparison cannot establish the field's definition, denominator, scope or missing-data convention, so no claim is made about actual refunds. See the ambiguity checks.
  5. 5.We did not audit the formula, unit, denominator, missing-data convention or product-versus-merchant scope of qualityRefundWithin30Day.
  6. 6.shippingTimeGuarantee is an API field under productShippingInfo. Its presence or omission does not establish production completion, international transit, customs, destination delivery, safety compliance or performance on an actual order.
  7. 7.The keyword list was chosen deliberately, not sampled: it over-represents safety-sensitive toy subcategories on purpose. Shelf-wide averages in this file should not be read as an estimate for the whole toy category.
  8. 8.Single day of collection. Platform fields can change, and no trend is claimed from one observation.
  9. 9.All figures describe responses from the English cross-border distribution APIs. Other 1688 surfaces may return or present different information.
  10. 10.Nothing here says a platform or seller has done anything wrong, and the result does not establish seller intent, policy or performance.
  11. 11.The 120 rows are 120 sampled product results and product-detail API responses, not 120 distinct suppliers. We deliberately do not publish seller identity, so the sample cannot be de-duplicated by shop and one seller may appear more than once.

Use this data

Everything below is free to reuse with attribution. If you are writing about this and 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 toy results from 1688's English cross-border keyword API, 61 product-detail API responses omitted productShippingInfo.shippingTimeGuarantee; the water gun and slime kit searches each had nine omissions among ten sampled responses.

How to cite this study

Liam Cai. "shippingTimeGuarantee field return across 1688 toy API responses." Supplymo, 18 August 2026, https://supplymo.com/research/1688-toy-listings.

The underlying data

One row per sampled product-detail API response. No supplier identity is published, and the sample was not de-duplicated by shop. 11 stated limits travel inside the file. Free to reuse with attribution under CC BY 4.0.

Questions we get asked

What is the one-line finding?

In a Supplymo non-random sample of 120 first-page toy results from 1688's English cross-border keyword API, 61 product-detail API responses omitted productShippingInfo.shippingTimeGuarantee; the water gun and slime kit searches each had nine omissions among ten sampled responses. This is a response-level field-presence result collected on 2026-08-12, not a claim about any other 1688 surface or supplier conversation.

What does an omitted shippingTimeGuarantee key prove?

Only that productShippingInfo in the sampled product-detail API response did not contain shippingTimeGuarantee. We did not treat omission as evidence about a rendered website, app, description, other API surface, supplier terms or actual order performance.

Why did water gun and slime kit stand out?

Each search had nine omissions among ten sampled product-detail API responses, compared with at most two among ten for building blocks and magnetic toys. These are descriptive splits from one non-random draw; the sample does not establish a cause or estimate category-wide prevalence.

Does this result say anything about toy safety?

No. The sample did not inspect materials, test reports, standards, age grading or destination-market requirements. API-field presence and product safety are separate questions.

Can I reuse the figures?

Yes, with attribution to Supplymo and a link to this page. The sanitized row-level CSV and evidence JSON are published under CC BY 4.0, together with the method and every stated limit.

Research accountability

Author and figure check

Author: Liam Cai. Collected 2026-08-12; published 2026-08-18.

Figure verification: every published count is automatically recomputed from the 120 sanitized rows and checked against repository-tracked raw-sample hashes. No independent human reviewer is claimed.

Check the exact product

Turn the sample-level gap into an order-level checklist

Submit the exact toy, variant and destination. Product Check helps organize the specification, supplier evidence, compliance questions and written order terms to verify before payment.

Check a product before payment