1688 Scraper — Product & Supplier Search, MOQ & Landed Cost
Pricing
from $3.50 / 1,000 search result cards
Scrape any 1688 category from one English keyword: English titles, MOQ price ladders, landed cost, dropship scores, compliance hints. Or watch a shortlist of offers for price drops and stock changes — daily snapshots, alerts, weekly trend report. Failed runs are never charged.
Full release history lives in git commit messages (git log --oneline); this file records release-visible changes from 0.1.17 onward.
Bugfix release for two defects proven on 0.1.30; prices and limits unchanged.
DELIVERY_STATE ledger: delivered offerIds re-seed the global dedup set, already-charged amounts re-scope the billing plan, and the run base fee is collected at most once per run even across processes. A replacement process whose contract is already fully delivered closes out with zero scraping, zero pushes and zero charges (SUMMARY.resumedAfterMigration).found=60, offers=0), which the old found===0 gate mislabeled as a search failure and escalated to the full anti-bot fallback ladder, ending FAILED. A well-formed empty response with found <= 100 is now classified as a business NO_MATCH — the run ends SUCCEEDED with errorCode=NO_MATCH after a single search request. Real risk-control interception (RGV587/x5sec/TMD) keeps failing the run. Classification rules are documented in docs/failure-semantics.md.httpIdentity counters and searchVia: mtop_identity. PRODUCT_HTTP_IDENTITY=off restores the browser-first behaviour.Never selected as the public default build; superseded by 0.1.30.
Docs only; code identical to 0.1.27, prices unchanged.
keyword field said every English keyword is "translated to Chinese search terms internally"; in fact only pet-supply keywords are mapped (the built-in dictionary is pet-only), and every other English keyword is sent to 1688.com as typed, where 1688's own search matches it (e.g. phone case and stainless steel tumbler return relevant results in cloud runs on 2026-10-07/08). The copy now says exactly that.titleEn is empty when no clean translation exists.actor.json now mirrors the live Store description and SEO fields (push never syncs them).eventChargeLimitReached=true is not an invariant violation when the requested count was fully charged; it only means later charges of that event are blocked.Actor.pushData(items, eventName) can return an aggregate chargedCount spanning the explicit event and the platform dataset event. Delivery accounting now uses the explicit event's ChargingManager.getChargedEventCount() delta, so SUMMARY, pushed-prefix selection and platform reconciliation cannot double-count rows.ChargingManager; the effective cap is the lower of input/platform limits; detail and run-base-fee are reserved; and product/monitor rows use the SDK atomic pushData(rows, eventName) path (budget limit → push prefix → charge). Detail/base settle only after a successful row push, factual ChargeResult counts drive the ledger, and terminal retries are single-flight so one batch is not pushed or charged twice.includeDetails=true requests now auto-downgrade to card-only before proxy/browser startup instead of returning DETAILS_MIN_20. SUMMARY discloses requested/effective/actual delivery shape and reason.NO_MATCH, RISK_CONTROL_ZERO, and infrastructure failures. Only risk-control zero receives one fresh-identity retry.deliveryShape, tokenPath, billingPlan, factual charged counts, errorBuckets, platform-count reconciliation and costGuard.freeRows=0.Listing copy changes from this release remain below.
1688 Scraper — Product & Supplier Search, MOQ & Landed Cost instead of a brand-style name plus a price tag. meta.description (145 chars) and store-copy.md (300-char Store description) are kept byte-identical to each other so the three disclosure surfaces cannot drift.dropshipReadyScore and the landed-cost estimate actually mean, and that failed or zero-result runs cost $0.phone case / 30 items instead of led strip lights / 40, so a first trial lands near $0.25. maxItems.default stays 40 — API callers who omit the field are unaffected.priceMin/priceMax.meta.categories realigned to ["ECOMMERCE","AGENTS"] to match the live Store listing. The local file declared only ECOMMERCE, so a future push would have silently dropped the AI-agents category placement.weightKg: null failed "type": "number" (forensics run RPahJyL8ctKR7pvul: 2 of 3 delivered rows 400-rejected, run FAILED with 0 items; keyword card-only never tripped it only because the search-card parser omits the key entirely, while the offerIds card-only path always materialises weightKg: null). A full all-null schema audit surfaced three more fields with the same code-contract-vs-schema mismatch and they are fixed together: price.min (extractPriceFromContext ships {min:null,…} when no price module; price.max already allowed null — the original author covered max but missed min), salesTotal (parseTransactionCount returns null for listings without a transaction count) and quantityPrices[].minQuantity (tiers whose beginAmount is null are kept). All four now accept null; wrong types (strings) are still rejected. Pinned by tests/task273-schema-null-tolerance.test.js (N1–N8) using the real ajv validator.data-safety.js flush failures now log the platform's invalidItems payload (bounded JSON dump) so future schema rejections are diagnosable from the run log without a forensics build.offerIds + includeDetails=false no longer silently delivers 0 products (run ui0FeqEeUkejFXArA). The combination now means CARD-LEVEL delivery — every offerId goes through the mtop-primary transport (fetchDetailsParallel) and is delivered at card level only (no detail enrichment, no description images), billed search-item × N + run-base-fee exactly like the keyword card-only path (5 IDs ≈ $0.035). Offers the transport cannot resolve are honestly absent and never billed; SUMMARY.detailStatus reports card_only.Crawler1688.seedWarmCardPage) BEFORE the batch fetch — previously a settled cache-hit token stayed page-less, so fetchDetailsParallel skipped tier-1 (warm-page probe) and tier-1.5 (retained reuse) and fell straight to tier-2 fresh mtopdet* sessions (R2M-1: 3/3 RGV587, Cliff breaker TRIPPED, while the SAME token seeded by the keyword search tier delivered 20/20 — R2M-6b). A teardown leak guard (releaseSearchFallbackBrowser) closes any unconsumed seeded page on both paths.offerIds direct-fetch path and states explicitly that includeDetails=true (details enrichment) requires maxItems ≥ 20 — smaller batches fall to the DETAILS_MIN_20 guard (honest refusal, $0 charged); use includeDetails=false for small card-only lookups — and that Price Monitoring (watchlistOfferIds) is a separate mode not subject to that guard (any watchlist size 1–200). The wall itself is unchanged: it is the 0.1.7 economic red line (detail enrichment breaks even only at batch scale).