Supplymo research edition
Original research from the supply side
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.
It cannot say that the 120 rows are 120 unique listings or suppliers. Offer and seller identifiers were not retained, so deduplication is impossible.
Liam Cai · Founder, Supplymo
Published 18 August 2026 · Collected 2026-08-02 · Yiwu, China
Evidence figure · MOQ and price-tier structure
102
of 120
Listed MOQ of two or fewer
- 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.
Collected
2026-08-02
Evidence
Version 1 · 120 non-deduplicated result/detail rows
Sample status
Non-random · method and row unit stated
Reuse
CC BY 4.0 · 10 stated limits
Study reading
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.
Study reading
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.
Study reading
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.
Study reading
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.
Research boundary
What this study cannot tell you
- BoundaryIt cannot say that the 120 rows are 120 unique listings or suppliers. Offer and seller identifiers were not retained, so deduplication is impossible.
- BoundaryIt 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.
- BoundaryIt cannot say the 84 one-tier rows offer no volume discount or negotiation. The result records only what priceRangeList displayed in that response.
- BoundaryIt 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.
- BoundaryIt 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.
- BoundaryIt says nothing about freight, package size, duty, tax, delivery time or landed cost because none of those outcomes was sampled.
Questions readers ask
Read the finding without over-reading it
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.