Swiggy improves hyperlocal food search relevance using two-stage small language model fine-tuning
Swiggy's search must handle highly complex Indian food queries spanning regional dish names, dietary preferences, preparation styles, and occasion-based intents across millions of items, which simple string matching cannot resolve.
Generic string matching does not retrieve relevant items for complex food queries, and base pre-trained language models without domain adaptation produced inconsistent search results across hyperlocal spaces.
The two-stage fine-tuned all-mpnet-base-v2 model outperformed all baseline variants in overall MAP and Precision@5; the system includes an incremental training pipeline and is currently in experimental phase with a small cohort.
Frequently asked questions
What did this team achieve with this AI workflow?
The two-stage fine-tuned all-mpnet-base-v2 model outperformed all baseline variants in overall MAP and Precision@5; the system includes an incremental training pipeline and is currently in experimental phase with a sm…
What tools did this team use?
all-mpnet-base-v2, all-MiniLM-L6-v2, TSDAE, BM25.
What results were reported?
Stage 1 training documents: 996,000; Stage 2 query-item training pairs curated: more than 300,000; Query embedding generation latency constraint: up to 100 milliseconds; Precision@1 improvement: significantly improving (source-reported, not independently verified).
What failed first in this deployment?
Generic string matching does not retrieve relevant items for complex food queries, and base pre-trained language models without domain adaptation produced inconsistent search results across hyperlocal spaces.
How is this ecommerce ops AI workflow structured?
Customer search query submitted → Unsupervised domain adaptation → Supervised query-item fine-tuning → Embedding similarity retrieval → Incremental training feedback loop.