1688 finds · quantity and variant checks

PikoBuy 1688 Finds: Check MOQ, Variants and Seller Questions

A low unit price is not a complete offer. Record the minimum order, quantity tier, pack meaning, exact SKU and unanswered seller questions before a 1688 listing earns a place in your shortlist.

PikoBuy supports 1688 sourcing, but the current listing controls the offer

PikoBuy's beginner guide names 1688 among the platforms where shoppers can find products. It tells users to confirm specifications, colour and size, then paste a product link or keywords into the search box. At order submission, the guide requires the selected specifications, colour, size and quantity. It also warns that prices are subject to actual purchase and that an out-of-stock order is refunded.

Those statements support a practical PikoBuy 1688 finds workflow. They do not turn a thumbnail, starting price or old spreadsheet row into a guaranteed offer. PikoBuy's terms describe its role as displaying links and facilitating third-party purchasing, while saying it cannot review every merchant or product for quality, safety, legality, authenticity or accuracy.

Treat the 1688 page as a dated source. Your spreadsheet should preserve what the live page shows, what you selected, and what remains uncertain. If a minimum quantity, pack definition or SKU cannot be established, keep the row in research rather than presenting it as ready to order.

Capture identity before comparing price

Begin with the source marketplace, seller or company name, listing title, original URL and check date. Then describe the actual product represented by the row. Include the item type, material claim, construction features, intended use and any model or batch name the seller uses. Copy labels accurately; do not translate an unclear option into a more confident claim.

Next, record the displayed selling unit. One selected option may mean one piece, one pair, one set, one carton, a sample, a component or a deposit. A cheap number has no analytical value until you know what that number buys. Keep the listing's wording beside your plain-language interpretation so another reviewer can challenge it.

Spreadsheet fieldEvidence to saveFailure signal
Source identityMarketplace, seller, URL, check dateOnly an image or redirected link
Selling unitPiece, pair, set, pack or cartonUnit inferred from price alone
Product scopeIncluded parts and exclusionsCover image shows more than the option
Option stateSelected style, colour, size and quantityStarting price copied before selection
Open questionsQuestion, response and response dateAssumption stored as a fact

Decode MOQ, quantity tiers and pack arithmetic

MOQ means the smallest order a seller currently accepts for the relevant offer, but the listing may express it at different levels. A page-level minimum may apply across all variants; a SKU minimum may apply to each colour or size; a carton rule may require fixed multiples. Do not assume that mixing variants satisfies a total minimum unless the live page or seller confirms it.

Quantity pricing needs the same discipline. Capture each relevant threshold, the stated unit and the selected SKU. A lower tier price may unlock only at a larger quantity, while a sample or small-order price can be different. Store the tier you actually expect to use, not merely the lowest number visible on the page.

Use two calculations. Orderable quantity = required selling units × items per selling unit. Extended product amount = selected tier price × required selling units. Add seller-to-warehouse delivery as a separate field when shown. If “two” means two packs of ten, the product count is twenty; multiplying the displayed price by two without recording the pack size would understate both quantity and likely parcel weight.

Leave room for a verification status: confirmed on page, confirmed by seller, inferred, or unknown. Only the first two are strong enough for an order-ready row. An inferred MOQ can guide a question, but it should not drive a final budget.

Lock the exact 1688 variant before saving the find

Variant names are part of product identity. Record the original SKU label and a careful interpretation for style, colour, size, material, capacity or version. Select options in the same sequence you will later use at PikoBuy order entry, then check whether the price, availability, minimum and image change.

Watch for coupled options. A size may exist only in one colour; a material upgrade may change the price tier; a printed version may have a separate minimum; a “custom” choice may require seller approval. Do not combine evidence from different selections into one idealized row. If two variants have different commercial terms, give them separate rows or clearly separate scenario columns.

Size letters deserve special caution. “L” is a seller label, not a measurement. Save the current chart, units and measurement basis when available, and note whether the chart appears to describe the garment or the recommended body. For products without sizes, record the dimensions that determine whether the chosen capacity or model is correct.

  1. Select the intended style or model.
  2. Select the exact colour or finish.
  3. Select size, capacity or specification.
  4. Enter the intended quantity.
  5. Recheck price tier, availability, minimum and included parts.
  6. Copy the final option strings into the spreadsheet and order notes.

Ask seller questions that can change the order decision

A useful seller question closes one specific evidence gap. It includes the URL or product identifier, the intended SKU and quantity, and the answer format you need. “Is this good?” invites a vague response. “For option A, black, size 42, quantity three, can colours be mixed to meet the stated minimum?” can produce a decision-ready answer.

Prioritize questions about selling unit, mixed-variant eligibility, live stock, selected-tier applicability, included components, material specification, size-chart basis, customization, production status and domestic dispatch conditions. Ask only what the page does not already answer. Long questionnaires slow review and make it harder to attach each response to the correct row.

Store the question, response, date and relevant SKU together. A reply is evidence of what was communicated at that time, not a permanent guarantee. If the listing later changes or the order uses another option, recheck the answer. PikoBuy's current search flow mentions contacting customer service when an item cannot be found, but it does not promise a seller's response time or outcome; keep timing fields blank until confirmed.

Worked example: compare a low headline price with an orderable option

Assume a 1688 listing shows storage pouches with three materials, four colours and quantity tiers. The cover price is attached to the lightest material at the largest tier. Your shortlist needs twelve medium pouches in two colours. The page uses a selling unit of one pouch, but the minimum may apply per colour.

  1. Save the seller, source URL and check date before working with the numbers.
  2. Select the medium material and intended size; record the option strings exactly.
  3. Enter twelve units and capture the tier that becomes active for that selection.
  4. Check whether six black plus six grey satisfies the minimum, or whether each colour must reach it separately.
  5. Record the selected unit price and extended amount, not the cover price.
  6. Keep domestic delivery separate and note that international parcel cost is still unknown.
  7. If mixed colours are unclear, send one SKU-specific question and mark the row pending.

If the seller requires twelve units per colour, the proposed basket is not equivalent to twelve mixed units. The honest result may be to increase quantity, choose one colour, find another listing, or reject the candidate. That decision is more useful than preserving an attractive but unavailable headline price.

Use four gates before moving a 1688 find to order-ready

Identity gate: the source, seller and intended product are recorded. Quantity gate: selling unit, MOQ, multiple and applicable tier are confirmed. Variant gate: the exact SKU and its size or specification evidence are saved. Communication gate: every decision-critical question has a dated answer, or the uncertainty is explicitly accepted.

Failing a gate does not always mean deleting the find. Use statuses such as discovered, comparing, awaiting clarification, verified and ordered. The status should become less confident when a link, option or seller answer changes. Never carry an old verification date forward after substituting a new listing.

At PikoBuy order submission, compare the live specifications, colour, size and quantity with your verified row. After warehouse arrival, use the available inspection evidence to check visible identity and selected attributes. Warehouse photos can confirm some received details; they cannot retroactively prove that an MOQ, material claim or seller promise was correct.

Fact-check basis

Checked August 30, 2026 against PikoBuy's current Beginner's Guide and Terms of Service. The public guide supports 1688 discovery and requires specifications, colour, size and quantity at order submission. No fixed 1688 MOQ, price tier, pack size, seller response time, stock level, product quality or purchase outcome is assumed.

Related independent research

Use the marketplace link verification guide to preserve the original source, the PikoBuy keyword search workflow to build a comparison set, and the warehouse photo routine after an order arrives.