49 of 118 1688 baby-product detail API responses omitted shippingTimeGuarantee
We ran the same twelve baby-product searches twice through 1688's English cross-border API. The later after-sales snapshot produced 118 successful product-detail responses: 69 returned productShippingInfo.shippingTimeGuarantee and 49 omitted it. The earlier 120-row title-and-video snapshot remains a separate cohort.
The one-line version, free to quote with attribution: In a Supplymo sample of 118 successful product-detail API responses from 12 baby-product searches on 1688, 49 responses omitted productShippingInfo.shippingTimeGuarantee; 7 of 10 baby bottle responses omitted it, compared with 2 of 10 responses in each of the teether and baby car seat searches.
Liam Cai · Founder, Supplymo
Published 24 August 2026 · Collected 2026-08-13 · Yiwu, China
- shippingTimeGuarantee omitted
- 49
- Returned shipIn48Hours
- 67
- Returned shipIn24Hours
- 2
n = 118 product-detail API responses. Collected 2026-08-13. Non-random after-sales cohort: 12 deliberately selected baby-product searches with 118 successful product-detail API responses.
49/118
product-detail API responses omitted shippingTimeGuarantee
This is key presence in one API response, not a reading of any rendered 1688 surface.
7/10
baby bottle responses omitted the key
Teether and baby car seat each had 2 omissions among 10 responses.
69/118
product-detail API responses returned the field
Returned values were shipIn48Hours or shipIn24Hours in this draw.
120/118
rows in two separate snapshots
The cohorts are not joined and must not be treated as one product set.
Field omission varied across the selected searches
The baby bottle search had 7 omissions among 10 successful product-detail responses. Teether and baby car seat each had 2 omissions among 10. These small splits describe this non-random draw only; they do not estimate the wider baby-goods market.
Among the 69 responses that contained the field, 67 returned shipIn48Hours and 2 returned shipIn24Hours. Those strings describe the returned API field, not international transit, customs clearance or delivery to the buyer.
The two snapshots stay separate
The listing-quality snapshot produced 120 rows. The later after-sales snapshot produced 118 successful responses after 2 detail-call failures. Only 107 internal keyword-offer pairs overlapped, so title repetition and video observations cannot be attached to the later after-sales rows.
The public evidence labels every row by cohort and removes offer identifiers. Its 238 rows are not 238 distinct products or suppliers, and the study does not deduplicate by shop.
How a buyer can close the response-level gap
When a sampled response omitted shippingTimeGuarantee, that data source could not answer the dispatch-timing question. Before payment, request a current written production and dispatch date tied to the exact product, variant, quantity and order terms.
Keep the API observation and the supplier confirmation as separate evidence. For baby products, also request product-specific material, age-use, test and destination-market documents where relevant. This study does not decide safety or compliance.
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, other API surface or supplier conversation contained. The study queried one product-detail API response per sampled result.
- It cannot establish seller intent or performance. An omitted key is an API-response observation, not evidence of a missed dispatch deadline or poor service.
- The 120-row listing-quality snapshot and 118-response after-sales snapshot are separate. Their measures must not be combined as if they describe one joined product set.
- The 46 numeric-zero refund-rate values are not interpreted as zero actual refunds. The direction check was inconclusive.
- It is not a baby-product safety or legal-compliance assessment. Materials, reports, standards, age grading and destination-market requirements were not inspected.
How the sample was collected
- Source
- com.alibaba.fenxiao.crossborder:product.search.keywordQuery + product.search.queryProductDetail (read-only)
- Sampling frame
- The same 12 English baby-product keyword searches were run twice on one day, each requesting the first 10 platform-ranked results. The listing-quality snapshot produced 120 usable rows. The later after-sales snapshot produced 118 usable rows after two detail failures. Because first-page membership changed between runs, the cohorts are analysed separately.
- Collection window
- Two snapshots 226.668 seconds apart on 2026-08-13 in China
- Write operations
- None. No order, payment, enquiry, messaging, refund 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.
Can the title/video rows and after-sales rows be treated as the same listings?
Method. Compare the internal kw+offerId keys between the two raw samples without publishing the identifiers.
Result. Only 107 rows overlapped; 13 appeared only in the listing-quality snapshot and 11 only in the later after-sales snapshot.
Conclusion. No. The public evidence keeps two explicitly labelled cohorts. Cross-cohort totals are never presented as one joined set of products.
What does an absent shippingTimeGuarantee key establish?
Method. Record hasOwnProperty for shippingTimeGuarantee on every successful detail row and publish the field-return denominator.
Result. The field was present on 69 of 118 successful product-detail API responses and absent on 49.
Conclusion. Only that the sampled product-detail API response omitted the key. It does not establish rendered-page content, supplier terms, dispatch speed or service quality.
Does a displayed refund rate of exactly zero prove there were no refunds?
Method. Separate missing, zero and positive values, convert the API string only after a null check, then compare after-sales scores for zero and positive groups.
Result. The zero-display group had a median after-sales score of 3.6, below 4 for the positive-rate group. The direction test is inconclusive and cannot rule out missing-data semantics.
Conclusion. The evidence says only 'showing a rate of zero'. It does not claim that the listings had no refunds.
Do repeated refund-rate values prove independent listing-level measurements?
Method. Measure the largest repeated positive-value cluster, while retaining no seller identity in public data.
Result. The largest repeated positive rate covered 5 of 68 positive rows.
Conclusion. The values are treated as fields displayed on listing rows, not as independent supplier observations. This test cannot prove how the platform computes or copies them.
The stated limits, in full
All 13 of them travel inside the evidence file, so they stay attached to the data after it leaves this page.
- 1.This is not a random sample. Both cohorts use the first platform-ranked page for 12 deliberately selected English baby-product searches.
- 2.This study measures fields returned by two read-only 1688 API snapshots. It does not establish what any rendered website, app, other API surface or supplier conversation contained, and it does not assess physical safety or legal compliance.
- 3.The listing-quality and after-sales rows come from separate snapshots. Only 107 internal keyword-offer pairs overlapped, so the 238 public rows must not be read as 238 unique products or as one joined sample.
- 4.Two after-sales detail calls failed and the failed rows were excluded rather than converted into missing promises. That cohort therefore has 118 successful rows; stroller and baby clothes have nine observed rows each.
- 5.Per-keyword splits rest on nine or ten observed rows. Counts such as seven of ten are descriptive of this draw only, with no statistical inference.
- 6.A refund-rate value displayed as zero is not proven to mean no refunds. The direction check was inconclusive, so the evidence does not make a no-refunds claim.
- 7.Refund rates and after-sales scores are platform-displayed values. Supplymo did not audit their formula, denominator, update timing or whether values can be copied across listings.
- 8.A returned shippingTimeGuarantee value is an API field about leaving the seller side. It is not an international delivery estimate, customs promise, product-safety check or compliance certificate.
- 9.The keywords deliberately mix feeding, mobility, sleep, monitoring, clothing and bathing products. Their combined average is not an estimate for every baby-product listing on 1688.
- 10.This is a single-day observation and does not measure persistence, seasonality or later listing changes.
- 11.The English cross-border API channel may not match what a buyer sees on the domestic site, under a different login state or with other filters.
- 12.Nothing in this evidence says a platform or seller has done anything wrong. The buyer action is to verify the exact product, target variant, dispatch terms and evidence before payment.
- 13.Rows were not deduplicated by seller and do not represent distinct suppliers. One seller may appear more than once, and public evidence deliberately contains no seller identity.
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 sample of 118 successful product-detail API responses from 12 baby-product searches on 1688, 49 responses omitted productShippingInfo.shippingTimeGuarantee; 7 of 10 baby bottle responses omitted it, compared with 2 of 10 responses in each of the teether and baby car seat searches.
How to cite this study
Liam Cai. "shippingTimeGuarantee field returns in 1688 baby-product API responses." Supplymo, 24 August 2026, https://supplymo.com/research/1688-baby-listings.
The underlying data
The evidence contains separate listing-quality and after-sales cohorts. They are not joined, and the combined row count is not a count of unique listings or suppliers. 13 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 sample of 118 successful product-detail API responses from 12 baby-product searches on 1688, 49 responses omitted productShippingInfo.shippingTimeGuarantee; 7 of 10 baby bottle responses omitted it, compared with 2 of 10 responses in each of the teether and baby car seat searches. This is a response-level field-presence result collected on 2026-08-13, not a finding about a rendered 1688 page, supplier terms or actual dispatch performance.
What does an omitted shippingTimeGuarantee key prove?
Only that productShippingInfo in the sampled product-detail API response did not contain shippingTimeGuarantee. It does not establish what a website, app, other API surface or supplier conversation contained.
Can the title and after-sales observations be combined?
No. The title and video measures use a 120-row listing-quality snapshot, while the dispatch and refund fields use a separate 118-response after-sales snapshot. Only 107 internal keyword-offer pairs overlapped.
Does a returned refund-rate value of zero mean no refunds occurred?
No such conclusion is supported. 46 responses returned numeric zero, but the direction check was inconclusive and the platform field's denominator and missing-data convention were not independently verified.
Does this study assess baby-product safety or compliance?
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.
Official API source
Verify the field against 1688’s response schema
1688 multilingual product-detail APIThe official response schema places shippingTimeGuarantee under productShippingInfo. It does not establish what any rendered page, other API surface or supplier conversation contained.Open official 1688 documentationResearch accountability
Author and figure check
Author: Liam Cai. Collected 2026-08-13; published 2026-08-24.
Figure verification: every published count is automatically recomputed from the sanitized rows across the two separate cohorts 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 baby product, variant and destination. Product Check helps organize the specification, supplier evidence, safety and compliance questions, and written order terms to verify before payment.