Superbuy Spreadsheet Search: Product Name, Product ID, and Weidian ID

Finds search accepts three useful input kinds: product name text, Product ID, and Weidian ID. Ranking prefers exact ID or Weidian hits, then exact titles, then prefixes/phrases, then token matches. Filters and sort run in the browser against the loaded catalog snapshot; they do not create indexable filter URLs.

Mode 1 — Product name

Type words or a short phrase that appears in the product title. Matching is case-insensitive. The search script tokenizes your query and scores catalog names by how completely those tokens appear, with stronger weight for contiguous phrase and prefix-style hits than for scattered single-word leftovers.

Name search is the right mode when:

• You remember a silhouette or keyword (“gore-tex shell,” “campus,” “tote”) but not an ID
• You are browsing inside a category page and want to narrow titles without leaving that lane
• You are comparing how different rows titled near-identical silhouettes in the snapshot

Name search is the wrong mode when you already have a Product ID typed into a note. Paste the ID instead; exact ID resolution outranks fuzzy title ranking and avoids near-miss titles that share a common word.

Expect imperfect recall. Snapshot titles are only as descriptive as the source rows. Abbreviations, mixed Chinese/English tokens, and truncated marketing strings all reduce name-search precision. If results look noisy, shorten the query to the distinctive tokens and use CNY or category filters afterward.

Mode 2 — Product ID (unique record key)

Product IDs in this catalog are short numeric strings. An exact Product ID query is treated as an identity lookup: the matching catalog record should surface at the top of relevance ordering ahead of title-only matches.

Use Product ID when:

• You copied the ID from a previous shortlist
• A teammate or chat shared a row identity rather than a marketplace URL
• You need to re-open one known card without fighting similar titles

Because Product ID is the unique record key, an exact hit should correspond to one catalog product—not a family of duplicates. If nothing returns, the ID is absent from the current snapshot (wrong digit, outdated note, or never imported). Empty results are not “out of stock” language; this site does not claim live inventory.

Mode 3 — Weidian ID (can match multiple products)

Weidian IDs are longer digit strings typically associated with a Weidian listing identity. Exact Weidian search returns all catalog rows that share that Weidian ID. Duplicates are intentional behavior: the catalog can hold more than one product record pointing at the same Weidian identifier.

That matters because:

• You may see several titles, categories, or snapshot prices for one Weidian ID
• Choosing among duplicates is a research decision; the search UI does not auto-collapse them into one winner
• A Weidian match proves presence in the snapshot, not that every duplicate row is equally current

If you paste a full Weidian product URL instead of digits, use Product Link Preflight. Finds search is optimized for name/ID fields from the search index; preflight explicitly parses Weidian URL shapes and then looks up the extracted ID against the local snapshot—again returning every duplicate.

How ranking actually prefers your query

When you submit a query, the client search prefers, in broad order:

1. Exact Product ID or exact Weidian ID matches
2. Exact title matches
3. Prefix / phrase-oriented title matches
4. Broader token matches

Sort defaults to “Default / Relevance” after a search. You can switch to price ascending, price descending, or name A–Z. Rows without a usable CNY price sort last on price sorts and never satisfy numeric CNY filters.

Filters that work with—not instead of—search

After results appear you can:

• Jump to a category via chip navigation (canonical /finds/{category}/ pages)
• Set custom minimum and maximum CNY
• Use preset bands such as Under ¥100, ¥100–199, ¥200–299, ¥300–499, and ¥500+

Boundaries follow half-open ranges for the middle bands (for example ¥100–199 covers [100, 200)). Missing prices never match a numeric range. Search and filter state stay on the page; they are not mirrored into crawlable query-string result URLs. Numbered /page/N/ slices remain unfiltered snapshot pages.

Practical query patterns

What you have	What to type on Finds	What to expect
Vague silhouette words	Short distinctive name tokens	Ranked title list; refine with filters
Known Product ID	Digits only	Single-record identity preference
Known Weidian ID	Digits only	Every duplicate row with that ID
Weidian product URL	Prefer Preflight tool	Parsed ID + all snapshot matches
Category curiosity only	Open category, then search	Scoped browsing before global search

What search does not do

• It does not query Superbuy account orders or warehouse status.
• It does not validate that an external listing still loads.
• It does not grade sellers or product authenticity.
• It does not invent a “closest match” when an ID is wrong; empty results mean empty results.
• It does not sync filters into SEO URLs for every combination you try.

Debugging empty or odd result sets

1. Confirm you are on Finds or a category Finds page with the search field available.
2. Strip spaces and punctuation from IDs; paste digits only.
3. If a Weidian ID returns many rows, that is duplicate handling—inspect each Product ID.
4. If a name query returns nothing useful, try fewer tokens or a different transliteration fragment.
5. Clear CNY filters if you accidentally excluded “Price unavailable” rows you still wanted to see by ID.
6. For URL paste failures, switch to Product Link Preflight.

FAQ

Why did one Weidian ID show several products?

Because the snapshot can store multiple product records that share the same Weidian ID. Search returns the full set so you can compare titles and Product IDs instead of silently hiding duplicates.

Does relevance sort change when I only filter without searching?

Without an active text/ID query, default ordering follows the catalog’s baseline presentation for that page scope. Relevance ranking becomes meaningful once you submit a query that the search index can score.

Search on this site is a snapshot instrument: three input modes, explicit duplicate Weidian behavior, and filters that stay local. Use Product ID when you need one row; use Weidian ID when you need every linked row; use names when you are still exploring vocabulary.