E-commerce Search Evaluation Datasets

Public product-search datasets give teams ready-made judged relevance data before they have built their own judgment lists. Four recur throughout search evaluation and fine-tuning work: Amazon ESCI, its community extension ESCI-S, Wayfair’s WANDS, and the Home Depot Kaggle set. They differ less in size than in what their labels mean, and that difference decides which one fits which job.


The Datasets at a Glance

DatasetReleased byDomainScaleLabels
Amazon ESCI DatasetAmazonGeneral e-commerce; English, Japanese, SpanishVery large4-class: Exact / Substitute / Complement / Irrelevant
ESCI-S DatasetCommunity (shuttie)Same as ESCIESCI pairs + enriched product metadataSame ESCI labels, unchanged
WANDS DatasetWayfairHome goods, furniture~42K query–product pairs3-class: Exact / Partial / Irrelevant
Home Depot Product Search RelevanceHome Depot (Kaggle)Home improvement~74K query–product pairsContinuous 1–3, average of crowdsourced annotators

All four are human-labeled query–product pairs, so all four work as ready-made judgment lists for offline evaluation, and all four support graded metrics such as NDCG. Home Depot’s averaged scores have to be discretized first.


Label Schemes Are the Real Difference

ESCI labels shopping intent, not text match. The Substitute and Complement grades capture the two near-misses that dominate product search: a product that could replace the requested one, and a product that goes with it. That shape has spread beyond the dataset. Allegro modeled the labeling guidelines for its 380K+ judgment set on it, and Etsy plans to split its “partially relevant” grade along the same complement/substitute line. See Semantic Relevance.

WANDS collapses the near-misses into one Partial grade. That’s simpler to annotate, but you can’t tell a substitute from an accessory. Its queries come from real Wayfair traffic, and its judgments are dense: the WANDS note records 358.9 relevant products per query on average. Dense judgments change how fusion should be tuned. In How to Tune Hybrid Search in Qdrant, RRF did best at high k on WANDS, while datasets with about one relevant document per query preferred low k.

Home Depot’s scores are averages. A decimal 1–3 score suits regression-style relevance prediction better than classification. It is the oldest of the four and is used as a smoke test.


Choosing One


They Don’t Substitute for Each Other

The clearest evidence is in Fine-Tuning Sparse Embeddings for E-Commerce Search. A SPLADE model fine-tuned on ESCI beat BM25 by 27.5% in-domain (nDCG@10 0.389). Its gains shrank on the other catalogs:

Evaluated onFine-tuned nDCG@10vs BM25
Amazon ESCI (in-domain)0.389+27.5%
WANDS0.355+7.9%
Home Depot0.384+10.0%
MS MARCO0.751−17.9%

On Home Depot, the off-the-shelf model beat the ESCI-tuned one (0.391 vs 0.384). Training on all three e-commerce sets together, 50K samples each, gave up some in-domain ESCI score (0.372) and gained on WANDS (0.366) and Home Depot (0.410).

Two consequences:

  1. Evaluate on more than one catalog. A result on ESCI alone says little about another retailer’s products. Running the same model on ESCI, WANDS and Home Depot is a cheap check of zero-shot transfer across catalogs.
  2. Never evaluate on the data you trained on. ESCI works as a fine-tuning corpus: Exact and Substitute become positives and Complement is dropped. Once a model has trained on it, ESCI is no longer a neutral benchmark for that model. Split by query, as Model Selection and Fine-Tuning Evaluation describes.

Limits

  • Label noise. ESCI was crowdsourced before LLM labeling existed. WANDS judgments in home goods are partly matters of taste: style, color and material are subjective.
  • Frozen relevance. Commerce relevance drifts. Etsy keeps an evolving labeling guideline because “face masks” meant costume masks before 2020 and protective masks after. A static public dataset can’t follow that drift. See Do LLM Judges Actually Agree With Us.
  • Not your catalog. These datasets help you shortlist, calibrate annotator guidelines, and test methods before investing in custom annotation. As Retrieval Benchmarks and Leaderboards puts it, the decision still belongs to judgments on your own queries and products. Relevance Program Setup covers building those.
  • The LLM-judge boundary sits where ESCI is hardest. Allegro’s judge reached F1 around 0.94 on exact matches but only 0.51 and 0.33 on separating “highly substitutable” from “substitutable”. The substitute boundary is where LLM judges are least reliable.
  • Relevance labels can manufacture other evaluation sets. sQuIrRel reuses the ESCI label scheme to derive query-to-product-type labels from a relevance model’s exact matches. It is a method on internal Amazon data, not a dataset to download.

People