What 120 1688 result/detail rows showed about listed MOQ and price tiers
A low number beside “minimum order” looks decisive, but it is only one field in a purchase decision. In this non-random snapshot, 102 of 120 non-deduplicated rows returned a listed MOQ of two units or fewer, while 84 returned only one displayed price tier. Both still need a product-specific supplier check before payment.
The one-line version, free to quote with attribution: In a Supplymo snapshot of 120 non-deduplicated result/detail rows from 12 selected English searches on 1688, 102 returned a listed minimum order quantity of two units or fewer and 84 returned one displayed price tier; neither field confirms checkout acceptance, a negotiated production MOQ or a final supplier quote.
Liam Cai · Founder, Supplymo
Published 18 August 2026 · Collected 2026-08-02 · Yiwu, China
- Listed MOQ of two or fewer
- 102
- Listed MOQ above two
- 18
n = 120 non-deduplicated result/detail rows. Collected 2026-08-02. Twelve deliberately selected English searches, ten retained result/detail rows each. Rows were not de-duplicated by offer or seller.
102/120
returned a listed MOQ of two or fewer
A displayed minimum is not confirmation that checkout or the supplier will accept the exact order.
84/120
returned one displayed price tier
One tier does not prove that no other price, discount or negotiation exists.
36/120
returned multiple displayed tiers
All 36 multi-tier rows in this draw returned three displayed tiers.
9%
median rounded spread among multi-tier rows
A within-row display measure, not a negotiated saving or landed-cost result.
A low listed MOQ is a clue, not an accepted order
81 of 120 rows returned minOrderQuantity equal to one, and 102 returned two or fewer. That is useful for screening: it tells a buyer which rows may be worth asking about first. It does not tell the buyer which variation the number covers, whether a carton or mixed-batch condition applies, or whether the supplier will accept the order today.
Before paying, ask the supplier to repeat the exact SKU, pack unit and accepted quantity in the quote. If any of those differ from the listing, use the written quote rather than the search-card number.
One displayed tier answers less than it appears to
84 rows returned one priceRangeList row; 36 returned more than one. The narrow conclusion is about the API surface: it tells us how many bands were displayed in that response. It cannot tell us that a supplier has no volume price, will not negotiate, or uses the same terms in another channel.
A buyer comparing suppliers should ask for the same three quantities on every quote—for example the intended trial order, the likely reorder and a higher-volume case. That creates comparable commercial answers without pretending the listing has already supplied them.
The final displayed tier is not another name for MOQ
Among the 36 multi-tier rows, the median start quantity of the final displayed price band was 500 units. That figure is easy to misread as what a buyer “has to” order. It is not. It marks where the last displayed band begins; minOrderQuantity is a separate returned field.
The median rounded displayed-price spread across those 36 rows was 9%. Because exact prices were not retained and SKUs were not normalized, that number is evidence about display structure—not a savings promise, margin estimate or final payable price.
A buyer-ready quantity check needs the missing commercial terms
Confirm five things together: the exact SKU and specification, the order and pack unit, the quantity the supplier will accept, the price at each comparison quantity, and every separate packaging or China-side delivery charge. A low MOQ without the unit is ambiguous; a tier price without the SKU can be incomparable.
Supplymo's MOQ calculator helps structure those questions. Product Check is the next step when the buyer needs the listing, supplier answer, packaging and shipping inputs reviewed together before payment.
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 say that the 120 rows are 120 unique listings or suppliers. Offer and seller identifiers were not retained, so deduplication is impossible.
- It cannot say that a listed MOQ of one or two guarantees a one- or two-unit order. No order preview, checkout or supplier confirmation was performed.
- It cannot say the 84 one-tier rows offer no volume discount or negotiation. The result records only what priceRangeList displayed in that response.
- It cannot say a buyer should order 500 units. That is the median start of the final displayed band among multi-tier rows, not a required MOQ.
- It cannot treat the 9% median as a negotiated saving. Exact prices were not retained and the rows were not normalized by SKU, material or pack unit.
- It says nothing about freight, package size, duty, tax, delivery time or landed cost because none of those outcomes was sampled.
How the sample was collected
- Source
- com.alibaba.fenxiao.crossborder:product.search.keywordQuery-1 + com.alibaba.fenxiao.crossborder:product.search.queryProductDetail-1 (read-only)
- Sampling frame
- 12 deliberately selected English reseller-oriented keyword searches, first result page only. Ten successful result/detail rows were retained per keyword in their stored response order, for 120 non-deduplicated rows. The ordinal is storage order within each keyword, not a preserved API rank field.
- Collection window
- Single session ending 2026-08-02 in China
- Write operations
- None. No order, order preview, 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.
Does a returned listed MOQ of one or two prove the supplier will accept that order?
Method. Treat minOrderQuantity as a displayed field only and check whether any order-preview, checkout or supplier-confirmation call was made.
Result. 102 of 120 rows returned a listed MOQ of two or fewer; no acceptance or supplier-confirmation call was made.
Conclusion. No. The field is a pre-payment clue, not confirmation of a production MOQ, SKU/packaging minimum, negotiated MOQ or accepted order.
Does one returned price tier mean a seller offers no volume discount or negotiation?
Method. Count priceRangeList rows without treating an absent second displayed tier as evidence about off-page negotiation or another channel.
Result. 84 of 120 rows returned one displayed price tier.
Conclusion. No. One returned tier describes this API surface at collection time; it does not prove the seller has no other price, discount or negotiable term.
Does the last displayed tier start quantity tell a buyer what they must order?
Method. Calculate that median only among multi-tier rows and keep it separate from minOrderQuantity.
Result. Among 36 multi-tier rows, the median last displayed tier began at 500 units.
Conclusion. No. It is the start of the last displayed price band, not a mandatory order quantity or recommended purchase size.
Can the rounded tier spread be used as a final savings or landed-cost claim?
Method. Retain only a rounded within-row displayed-price spread and verify that freight, tax, packaging, sample and final quote data were not collected.
Result. 36 multi-tier rows had a calculable rounded spread; the median was 9%.
Conclusion. No. It is not a negotiated saving, SKU-normalized comparison, freight estimate or landed-cost result.
Are the 120 rows 120 unique listings or suppliers?
Method. Inspect the retained source schema for offer and seller identifiers before publication.
Result. Neither offer ID nor seller ID was retained, so offer-level and seller-level deduplication cannot be performed.
Conclusion. The denominator is 120 non-deduplicated result/detail rows only.
The stated limits, in full
All 10 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. It covers the first result page for 12 deliberately selected English reseller-oriented searches and does not represent all 1688 products, categories, languages or ranking contexts.
- 2.The 120 observations are non-deduplicated result/detail rows, not 120 verified unique listings or distinct sellers. Neither offer ID nor seller ID was retained, so one offer or seller may appear more than once.
- 3.A returned listed MOQ is a listing field, not confirmation of a production minimum, SKU or packaging minimum, negotiated MOQ, order-preview acceptance, stock availability or a final supplier quote.
- 4.One returned displayed price tier does not show that a seller offers no volume discount, another price channel or negotiation. It only describes priceRangeList on this API response at collection time.
- 5.The last displayed tier start quantity is not the quantity a buyer must order. It marks the start of the final displayed price band among multi-tier rows only.
- 6.The displayed-tier spread is a whole-percentage value derived before exact prices were discarded. It is not a SKU-normalized saving, negotiated discount, margin, final payable price or independently reproducible price audit.
- 7.The calls used the English cross-border distribution channel. Buyers using the domestic interface, another language, account state, filter or sales channel may see different fields or terms.
- 8.No freight, package dimensions, chargeable weight, tax, duty, delivery time or landed-cost result was sampled. The study makes no transportation or total-cost claim.
- 9.This is a single-session snapshot. Listing fields and supplier terms can change, and the data does not establish a trend.
- 10.Nothing here says a platform or a seller has done anything wrong. The study records what selected API fields displayed before payment and where buyer confirmation is still needed.
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 snapshot of 120 non-deduplicated result/detail rows from 12 selected English searches on 1688, 102 returned a listed minimum order quantity of two units or fewer and 84 returned one displayed price tier; neither field confirms checkout acceptance, a negotiated production MOQ or a final supplier quote.
How to cite this study
Liam Cai. "Listed MOQ and displayed price tiers across 1688 result/detail rows." Supplymo, 18 August 2026, https://supplymo.com/research/1688-moq-structure.
The underlying data
120 rows from 12 deliberately selected English keyword result/detail calls. Offer and seller identifiers were not retained, so these are not 120 verified unique listings or sellers. 10 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 result?
In a Supplymo snapshot of 120 non-deduplicated result/detail rows from 12 selected English searches on 1688, 102 returned a listed minimum order quantity of two units or fewer and 84 returned one displayed price tier; neither field confirms checkout acceptance, a negotiated production MOQ or a final supplier quote. The denominator is result/detail rows rather than unique products or suppliers, and the full method and limits are published on this page.
Are these 120 unique 1688 listings?
No. They are 120 non-deduplicated result/detail rows from 12 selected English searches. The source sample retained neither offer IDs nor seller IDs, so it cannot prove how many unique offers or suppliers the rows represent.
Does a listed MOQ of one mean I can buy one unit?
Not necessarily. minOrderQuantity is a field returned by the listing-detail API. The supplier still needs to confirm the exact SKU, pack unit, quantity, current stock, price and whether the order will be accepted. This study made no order-preview or checkout call.
Does one displayed price tier mean there is no volume discount?
No. 84 of 120 rows returned one priceRangeList row, but that only describes the displayed API response at collection time. It does not rule out another sales channel, an updated quote or supplier negotiation.
Does the 500-unit figure mean buyers must order 500?
No. Among the 36 multi-tier rows, 500 was the median start quantity of the final displayed price band. It is not a required order quantity, a recommendation or a production MOQ.
Is the 9% median a guaranteed saving?
No. It is the median whole-percentage spread between the minimum and maximum displayed tier prices among 36 multi-tier rows. Exact prices were not retained, SKUs were not normalized and no freight, tax, packaging or final quote was collected.
How was the data collected?
Supplymo used 1688's read-only multilingual keyword-search and product-detail APIs in one session. It retained ten successful result/detail rows for each of 12 deliberately selected English search terms. No order, payment, enquiry, message or logistics endpoint was called.
Can I reuse the data?
Yes. The sanitized CSV and evidence JSON are available under CC BY 4.0. Attribute Supplymo and link to this page so the observation unit, collection date and limitations travel with the figures.
Official field definitions
The 1688 API fields this study read
These official Open Platform pages define the search and product-detail response fields. They do not validate a supplier, endorse this study or replace a current order preview and written quote.
Figure verification: every published count was deterministically recomputed from the sanitized rows and checked against the tracked source-file hash. No independent human reviewer is claimed.
Use it on your product
Check the quantity terms before supplier payment
Start with the listing, target SKU, trial quantity and likely reorder. If the unit, packaging or quote is missing, turn it into a supplier question instead of guessing.