← All docs

Search & Part Numbers

XSearch is built for catalogs where shoppers search by part number as often as by name.

Part numbers go straight to the product

When a search is exactly a product's SKU, UPC or MPN, XSearch returns that product rather than everything that shares part of the number.

  • Any letter case. gvsbth4, GVSBTH4 and Gvsbth4 all find the same product.
  • Variant SKUs. Pasting the SKU of one variant (for example a single color or size) finds its parent product. Stores indexed before this feature need one reindex for every variant SKU to be searchable.
  • Part numbers inside longer queries. A pasted product title such as "raritan px3-5611r-e2 networked pdu – 208v" finds the product by its part number even though the marketing words don't all match.
  • As you type. Partial part numbers and SKUs surface matching products in the search dropdown and on the results page alike.

Fewer empty results pages

By default every word in a search must match, which keeps results precise. If a search of three or more words finds nothing, XSearch retries once with a slightly looser match — most, not all, of the words — so "rack blank spacer" still finds "Rack Line-Up Spacer Kit". Searches that already have results are never loosened.

Tuning it: Settings → Search Matching

  • Term matching — whether every word must match (the default) or any word.
  • Minimum should match (advanced) — a precise rule such as 75% or 2<75%, which overrides term matching.
  • Typo tolerance — off by default. It works with the best fields and most fields match types; the default cross fields type doesn't support it.
  • Match type — how words are matched across fields.
  • Searched fields & boosts — which fields are searched and how much each counts. By default name counts three times as much as description, SKU, search keywords, brand and categories.
  • Typeahead suggestion fields — which fields drive as-you-type matching. The default is name, SKU, MPN and brand. Variant SKUs follow the SKU setting.

Matching changes apply to the next search; no reindex is needed.