ecommerce_ops · workflow
DoorDash personalizes store feed using store2vec vector embeddings and gradient-boosted models
Geographic constraints caused severe sparsity in DoorDash's consumer-to-store matrix, making standard collaborative filtering impractical; the initial knowledge-based recommender lacked latent semantic signals about store similarity and consumer preferences.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Session order data collected
Each sentence used for training is a list of stores viewed together in a user session.
Tools used
store2vecword2vecgensimLightGBM
Outcome
By incorporating store2vec latent features and gradient-boosted machine models, DoorDash saw approximately 20% improvement in offline AUC and approximately 5% increase in click-through rate in initial email tests, building on a prior 25% CTR gain from the initial recommendations system.
Results
Volume25%
Grounding & classification
Source type: technical build writeup
20 fields verified against source quotes.
personalizationpredictive analyticsrecommendation systemproduct catalogmetric backednamed customerproduction runtime claimedtools describedworkflow describedecommerceaccuracy improvementconversion increasetechnical build writeupecommerce opsdata sync enrichment