DoorDash uses LLM-generated profiles and content embeddings to improve semantic search and recommendations across verticals
DoorDash faced a persistent bottleneck where personalization depended on embedding quality, which in turn depended on data quality — but sparse metadata flattened catalog richness across all verticals. Behavioral co-visitation approaches tried to bypass this dependency but could not capture identity, context, and intent.
source quote
source quote
source quote
source quote
source quote
source quote
Deploying LLM-generated profiles with content embeddings improved semantic search and homepage discovery: null search rate fell 3.65%, core search CVR rose 0.66%, and generative personalized carousels drove a 2.4% relative increase in homepage order rate.
Show all 14 reported metrics
Compare to your context
Tell us your scale, team, and constraints. We'll show what changes at your size, what fails at your scale, and whether this case is a fit, needs adaptation, or won't scale to you. Free demo, no signup.
Frequently asked questions
What did this team achieve with this AI workflow?
Deploying LLM-generated profiles with content embeddings improved semantic search and homepage discovery: null search rate fell 3.65%, core search CVR rose 0.66%, and generative personalized carousels drove a 2.4% rel…
What tools did this team use?
LLMs, gemini-embedding-001, Qwen 3 Rerank model, Metaflow, MiniLM, Google Gemini embeddings, Qwen embedding models, text-embedding-005, text-embedding-3-large, OpenAI.
What results were reported?
7D active customer share: +0.0724%; Null search rate: −3.65%; core search session CVR: +0.66%; Dish query ranking improvement: 7.8% (source-reported, not independently verified).
How is this ecommerce ops AI workflow structured?
LLM profile generation → Incremental embedding pipeline → Embedding index publishing → Semantic query retrieval → Item-level reranking → Generative personalized carousels.
Related ecommerce ops cases
Now compare it to your context
This case is one data point. Whether its pattern fits you depends on your volumes, your stack, and your exception load — that comparison is the step no case study can do for you.