<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Anand Choudhary on Medium]]></title>
        <description><![CDATA[Stories by Anand Choudhary on Medium]]></description>
        <link>https://medium.com/@theanandchoudhary28?source=rss-ff3a49b8e130------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8853TyUE0OhJNWqY3cEnKQ.jpeg</url>
            <title>Stories by Anand Choudhary on Medium</title>
            <link>https://medium.com/@theanandchoudhary28?source=rss-ff3a49b8e130------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:51:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@theanandchoudhary28/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Actionable Recommendations for Market Managers: The Push-List Approach]]></title>
            <link>https://udaan.dev/actionable-recommendations-for-market-managers-the-push-list-approach-bf609b7694c6?source=rss-ff3a49b8e130------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf609b7694c6</guid>
            <category><![CDATA[recommender-systems]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[Anand Choudhary]]></dc:creator>
            <pubDate>Fri, 26 Jun 2026 05:13:38 GMT</pubDate>
            <atom:updated>2026-06-26T05:13:38.299Z</atom:updated>
            <content:encoded><![CDATA[<p>Every morning, thousands of udaan Market Managers step into India’s vibrant, chaotic markets carrying a simple but heavy responsibility: to help millions of <strong>kirana</strong> (traditional Mom &amp; Pop) entrepreneurs make the right buying decisions at the right time. To make that mission more precise and data-driven, we built the <strong>Push-List</strong>, a multi-signal recommendation engine that replaces generic top-seller lists with hyper-localized daily shortlists.</p><p>In India’s retail space where a storefront’s physical footprint is measured in square feet, inventory space is premium real estate. Behind every single product recommendation is a critical choice that directly impacts a small retailer’s working capital, inventory turnover, and ultimately, their livelihood.</p><p>Unlike consumer e-commerce, India’s retail landscape operates through assisted selling, fragmented demand, sparse digital signals, and highly localized buying behavior. This makes the offline-to-online digitization of this ecosystem a fascinating technical frontier. The engineering challenge at udaan was way beyond building another standard recommendation engine; it was about architecting intelligence that survives and thrives in the unique chaos of Bharat’s commerce.</p><h3>TLDR;</h3><p>We have deployed field sales representatives in udaan that visits kirana shops to onboard retailers and drive repeat orders. These field sales representatives are called <strong>Market Managers (MMs)</strong>.</p><ul><li><strong>The Problem:</strong> Empowering India’s kirana ecosystem to make better business decisions through data intelligence delivered to the last mile.</li><li><strong>The Solution:</strong> A multi-signal recommendation engine that delivers a daily Top K product list.</li><li><strong>The Impact:</strong> 22% basket size increase and 15% lift in high-margin product adoption.</li></ul><h3>Problem</h3><p>In the fragmented domain of traditional B2B trade, empowering frontline teams means solving an immense problem of data scale and signal quality. Market Managers must optimize supply chains and inventory choices across thousands of independent kirana storefronts while navigating a highly volatile product catalog characterized by dynamic pricing and shifting hyper-local availability.</p><p>In the high-stakes world of B2B e-commerce, Market Managers (MMs) are the drivers of daily operations and revenue. Every morning, Market Managers (MMs) in B2B e-commerce face a critical decision: <strong>Who do I visit today, and what exactly should I pitch?</strong></p><p>With only a few minutes to convert a sale, getting this wrong means losing client’s attention and trust.</p><ul><li><strong>The Context Gap:</strong> Generic “Top Seller” lists ignore buyer-specific needs. Pitching flour to a baker who stocked up yesterday is an inefficient rookie mistake.</li><li><strong>The Data Desert:</strong> Sparse user interaction data makes it hard to derive meaningful insights from browsing behaviour alone.</li><li><strong>The “Average” Trap: </strong>One-size-fits-all recommendations ignore business attributes, purchase cycles, and local demand patterns.</li></ul><p><strong>The core constraint? </strong>Time. Market Managers need a <strong>short, pre-ranked list </strong>they can act on immediately, not a catalog to sift through.</p><h3>Approach</h3><p>We built <strong>The Push-List:</strong> a unified recommendation engine that transforms billions of data points to produce a daily shortlist of exactly K high-conversion likelihood products.</p><p><strong>The Human + AI Philosophy</strong>: The Push-List doesn’t replace the judgment of our Market Managers. Instead, it provides them few moments of clear, actionable insight. This frees our frontline teams from administrative guesswork, allowing them to focus entirely on building trust, nurturing relationships, and driving persuasion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ery2umyQcfemmkNrL7Svkw.png" /></figure><h3>Why Push List ?</h3><p>The Push-List is a time-saving tool designed for speed and precision rather than another list of products. Here is how it solves the core challenges:</p><ul><li><strong>Precision over Volume:</strong> We moved away from “what sells the most” to “what does this specific buyer need right now?” The Market Manager acts as the consultant, validating the recommendation using their real-world knowledge of the shop.</li><li><strong>Respecting the Clock:</strong> By limiting recommendations to a focused Top K, we eliminate choice paralysis and cognitive load, allowing Market Managers to pitch confidently within that crucial few-minute window.</li><li><strong>Intelligent Prioritisation:</strong> The engine accounts for purchase history and timing, ensuring we never pitch a product to a client who is already fully stocked.</li></ul><h3>What We Didn’t Build (And Why)</h3><ul><li><strong>Pure Collaborative Filtering:</strong> Sparse data in B2B e-commerce; many buyers have less than 5 purchases.</li><li><strong>Single LightGBM Model:</strong> Black box model; Market Managers couldn’t understand why items were recommended.</li><li><strong>Real-Time Deep Learning: </strong>Overkill for daily batch updates; inference latency not needed.</li><li><strong>Third-Party Recommendation Systems : </strong>Couldn’t encode B2B constraints like margin, inventory and clusters.</li><li><strong>Top Sellers Only: </strong>Already tried model; ignores buyer-specific context.</li></ul><p><strong>The Lesson:</strong> In B2B, <strong>interpretability &gt; sophistication.</strong></p><p>The ensemble’s signal-based slots give Market Managers an intuitive mental model for each recommendation, unlike a single opaque gradient boosted score. Market Managers trust the system more when they can validate the logic.</p><h3>Key Idea</h3><p>We designed a <strong>triple-threat ensemble architecture</strong> that listens to three distinct behavioural signals:</p><ol><li><strong>The Heartbeat (Replenishment):</strong> When will buyers run low on purchased products? It ensures that we capture the recurring revenue without manual intervention.</li><li><strong>The Hyper-Local Pulse (Geo-Trends):</strong> What’s trending in specific neighbourhoods? It capitalises on local demand spikes and trending products.</li><li><strong>The Digital Breadcrumb (App Activity):</strong> What did buyers recently view or add to cart? It tries to convert high-intent browsing into sales.</li></ol><p>These signals are merged through a custom <strong>Slotting Engine</strong> that balances conversion probability with strategic business goals (margin formation, inventory movement).</p><h3>Architecture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0LgstVJwrLRFZh5NuGuAzg.png" /></figure><p><strong>The Brain:</strong> A custom merger that distributes K slots across signals in fixed proportions so the list isn’t dominated by a single signal on any given day.</p><p><strong>The Overlay:</strong> We inject margin-makers (high-margin private labels, key value items, and near-key value items) to balance volume with profitability.</p><p><strong>The Flow: </strong>Rather than viewing the system as isolated technical boxes, the data flow can be traced across a single continuous narrative as</p><ul><li><strong>Millions of Transactions:</strong> Ingesting raw, historical B2B invoice lines across our entire commerce platform.</li><li><strong>The Purchase Heartbeat:</strong> Predicting unique replenishment cycles at a buyer-product specific level.</li><li><strong>Neighborhood Intelligence:</strong> Aggregating regional buying trends via H3 geospatial grids to solve local data sparsity.</li><li><strong>Digital Intent:</strong> Capturing real-time app interactions like views and cart additions via a priority funnel.</li><li><strong>Business Constraints:</strong> Overlaying profit margins, inventory availability, and product category mixes.</li><li><strong>The Push-List:</strong> Delivering a curated, 20-slot daily checklist straight to our Market Managers’ mobile screens.</li></ul><h3>Implementation</h3><h4>1. The Math of “When” (Replenishment via Modified Poisson Gamma)</h4><figure><img alt="MPG model graphs showing Repeat Rate and Purchase Probability against ‘days since last purchase’" src="https://cdn-images-1.medium.com/max/1024/1*nEzI2NbF4FO7FCfZXteJhA.png" /></figure><p>We moved beyond simple averages. Replenishment is buyer-product specific, not a single average across either dimension. Using a <strong>proprietary adaptation of the Poisson Gamma </strong>framework, we estimated a buyer’s unique purchase “heartbeat”.</p><ul><li><strong>The Logic:</strong> The model predicts the purchase probability for any user-item pair by analysing historic purchase attributes and the number of days since last purchase.</li><li><strong>The Recency Penalty:</strong> We calculated the average interval ( <em>t_mean</em> ) and added a critical constraint. If a buyer exceeds their usual product interval by ( 2 × <em>t_mean</em> ), the model realises the pattern is broken (perhaps they switched to a different item) and de-prioritises the item by applying a recency based penalty.</li><li><strong>Why this works:</strong> Unlike simple averages, the Modified Poisson Gamma (MPG) model handles <strong>irregular purchase patterns</strong> and applies a <strong>recency penalty</strong> which helps us to assess buyer’s product specific behaviour in real time.</li></ul><h4>2. The Geometry of “Where” (H3 + Greedy Clustering)</h4><p>Trends are neighbourhood-specific, but data can be sparse. To solve this, We used an open-source geospatial indexing system <strong>H3 hexagonal grid </strong>to map buyers spatially, then applied an <strong>Iterative Greedy Merger</strong> to solve sparsity.</p><ul><li><strong>Clustering:</strong> Geospatial clustering helps us to understand what is selling in a neighbourhood.</li><li><strong>Solving Sparsity:</strong> By using Iterative Greedy Merger, algorithm automatically absorbs “weak” neighbours (hexagons with low buyer counts) into <strong>larger, statistically significant clusters.</strong></li><li><strong>The Human Touch:</strong> Numeric cluster IDs like 8528347 mean nothing to sales teams. We built a <strong>phonetic name generator</strong> to create memorable identifiers: KOPA, ZITI, MELA.</li></ul><h4>3. The Digital “Window Shopping” (App Priority Funnel)</h4><p>Not all app events are equal. We need to establish hierarchy based on purchase intent to ensure we capture the most actionable signals.</p><ul><li><strong>Signal Extraction &amp; Ranking:</strong> We built a <strong>priority-ranked signal extraction</strong> to capture intent. We ranked these by frequency and recency.</li></ul><ol><li><strong>Add to Cart (Priority 1):</strong> High-intent signal. The user wants the product now.</li><li><strong>Listing Impression (Priority 2): </strong>General interest. The user is browsing the product.</li></ol><h4>4. The Business Overlay (Margin Formation)</h4><p>Data is great, but profit matters. We added a final layer of business intelligence through different measures.</p><ul><li><strong>Context Tags:</strong> We attach useful tags to every item to help the Manager frame their pitch (e.g., “Trending in KOPA”, “Price Drop”).</li><li><strong>Strategic Insertion:</strong> We deliberately slot in Margin Makers and incentive-driven products to ensure the sales mix is healthy for the company’s bottom line.</li></ul><h4>5. The K-Slot Brain (The Slotting Engine)</h4><p>The final Push-List isn’t random, it’s a <strong>strategically balanced allocation.</strong></p><ul><li><strong>Conversion Possibility Score:</strong> We calculated this weighted score based on attributes at the buyer, cluster, and city levels derived by Wilson Score (statistical method to calculate confidence interval for a proportion) corresponding with pre-defined thresholds.</li><li><strong>Slot Ranking Formula:</strong> We then apply a category adhered strategic mix (Replenishment, Geo-trends, and App activity) to fill the slots. This dynamic mix has products recommended by all 3 strategies and ensures a perfect balance of margin-makers and sale drivers.</li><li><strong>The Overflow Safety Net:</strong> New buyers with no app activity? The engine <strong>auto-fills empty slots</strong> with geo-trends to ensure a complete K-item list.</li></ul><h4>6. Production Infrastructure (Scaling to Millions)</h4><p>The pipeline runs daily across millions of buyer-product pairs ensuring:</p><ul><li><strong>Batching &amp; Partitioning:</strong> Since data size was millions, we used batch APIs to update relevant Postgres tables.</li><li><strong>Resilience:</strong> Rigorous timeout and retry logic ensures server hiccups don’t result in data loss.</li></ul><h3>Development Challenges</h3><p>Transitioning the Push-List from concept to production meant navigating a series of critical algorithmic and engineering bottlenecks.</p><p>Initially, we built a user-level collaborative filtering model using dense embeddings (1 for purchase, 0 for no purchase) across our entire product catalog. However, calculating these pairwise across millions of users proved computationally slow and unscalable. Even after converting to sparse matrices, data sparsity and long processing times forced us to abandon this approach and pivot to a decentralized ensemble architecture that slots distinct behavioral signals into a unified list.</p><p>Once the framework was set, balancing items suggested by behavioral signals with margin-makers required tight collaboration with field teams. We mathematically fixed allocation fractions for each signal and built an over-deduplication layer to ensure no products are repeated across slots. Determining the exact positioning and ranking of high-margin items within the list was another puzzle which we solved through product team discussions and by designing a composite score that blends historical conversion rates with active product promotion strategies.</p><p>To improve the accuracy of our rankings, we also had to refine our conversion probability metric: the Wilson Score. Initially calculated only at broad geographic cluster and city levels, we re-engineered the score to ingest buyer-specific signals. We also expanded our definition of a digital “impression” to include high-intent actions like product views and add-to-cart events rather than final purchases only.</p><p>Finally, our early prototypes suffered from severe production infrastructure bottlenecks. The engine generated massive lists containing hundreds of recommendations per buyer, causing widespread API timeouts and delivering delayed or empty lists to Market Managers. We cut the payload to 20 slots to match the fast-paced reality of field visits, and by overhauling our database write layer to use robust batch APIs equipped with retry and timeout circuit breakers.</p><h3>Results</h3><p>To measure the business impact of the Push-List, we tracked performance metrics over a continuous 12-week observation window across all operational markets. Because the system was scaled directly to production across our entire network, we utilized a pre-vs-post rollout analysis.</p><p>This long observation window allowed us to establish our baseline data while the system was offline and stabilize and scale the changes to all markets while troubleshooting infrastructure bugs and optimizing ground recommendation quality. The final weeks data represented the steady-state post-rollout period where the human+AI loop operated at full scale.</p><p>We tracked metrics weekly to smooth out day-to-day fluctuations. We tracked Average Basket Size (ABS) separately for Staples and FMCG (Fast-Moving Consumer Goods), as they operate independently. High-margin product metrics were evaluated by tracking both the weekly number of distinct buyers purchasing those items and the average variety of unique high-margin items ordered per buyer.</p><h4>Quantitative Impact (Bengaluru Pilot)</h4><p>The data shows a clear basket size boost and increase in high-margin items adoption. Here is the tangible impact we witnessed after deploying the Push-List in Bengaluru.</p><figure><img alt="Quantitative results from the Push-List pilot" src="https://cdn-images-1.medium.com/max/1024/1*LVOT_xfl91a7XD_Lg5Bijg.png" /></figure><p><strong>Basket Size Boost:</strong></p><p>Because we predicted needs accurately, buyers bought more per visit:</p><ul><li>+22% Average Basket Size increase for Staples.</li><li>+18% Average Basket Size increase for FMCG (Fast-Moving Consumer Goods).</li></ul><p><strong>Margin Maker Effect:</strong></p><p>By strategically slotting high-margin items and related products into the list, we saw:</p><ul><li>+15% increase in weekly users buying Margin Maker products.</li><li>+9% increase in the average quantity of Margin Maker items ordered per user.</li></ul><h4>Qualitative Wins</h4><ul><li><strong>Reduced Prep Time: </strong>Market Managers shifted from <strong>administrative list generation</strong> to <strong>strategic sales execution.</strong></li><li><strong>Confidence Boost:</strong> Top 3 slots now consistently contain high-probability items, so no scrolling is needed.</li><li><strong>The “Nudge” Strategy:</strong> By training our Geographic-model on the <strong>75th percentile</strong> of historical quantities instead of average, we nudged buyers toward aspirational yet realistic volumes without pushback, <strong>directly driving GMV growth.</strong></li><li><strong>Context Tags</strong>: Managers can now frame pitches with data-driven tags like “Trending in your area”. It acts as collaborative, data-backed business recommendation that helps the retailer optimize their capital.</li></ul><h3>Edge Cases We Handle</h3><h4>1. The “Stockout” Problem</h4><p><strong>Scenario:</strong> Push-List recommends any item, but warehouse is out of stock.</p><p><strong>Solution:</strong></p><ul><li>Daily inventory sync filters out unavailable items before scoring.</li><li>Fallback: Replace with next-best item from same category.</li></ul><h4>2. The “New Buyer” Cold Start</h4><p><strong>Scenario: </strong>Buyer has zero purchase history.</p><p><strong>Solution:</strong></p><ul><li>Use Geo-cluster trends (similar businesses in same area).</li><li>Bootstrap with “industry starter pack” (e.g., Bakery Essentials).</li><li>After first purchase, replenishment model kicks in.</li></ul><h4>3. The “Seasonal Spike” Anomaly</h4><p><strong>Scenario:</strong> Occasional events drives 10x demand for certain items.</p><p><strong>Solution:</strong></p><ul><li>Geo-trend model naturally captures this (local surge → higher ranking).</li><li>Recency weighting ensures recent spikes override old patterns.</li></ul><h4>4. The “Lapsed Buyer Re-engagement”</h4><p><strong>Scenario:</strong> Buyer stops purchasing staple items and we have to ensure that buyers never run out of key items.</p><p><strong>Solution:</strong></p><ul><li>Recency penalty in MPG model (if <em>t_current</em> &gt; 2 × <em>t_mean</em>, deprioritise).</li><li>Alert Market Manager: “Buyer hasn’t ordered flour in 45 days (usual: 15 days)”.</li></ul><h3>Conclusion</h3><p>The Market Manager’s dilemma about <strong>“Who do I visit and what do I pitch?” </strong>is a universal problem in B2B sales. By moving away from generic “Top Seller” lists and embracing a <strong>multi-signal ensemble</strong>, we turned data into a competitive advantage.</p><p>Technology often promises automation. In commerce, however, the far greater opportunity is augmentation. At udaan, we learned that the best recommendation systems don’t try to replace the people closest to customers. Instead, they help them make better decisions faster and with confidence.</p><p><strong>The Push-List didn’t just organise a catalog, it organised the day.</strong> It transformed chaotic mornings into focused missions, proving that when you give sales teams the right insights, they don’t just sell more but they also <strong>sell smarter. </strong>Because ultimately, behind every algorithm is a kirana entrepreneur trying to grow their business, and a Market Manager standing right there to help them make that happen.</p><h3>Next Steps</h3><p>The Push-List organised the day. The next milestone is about organizing the moment, moving from a static morning snapshot to an anticipatory, real-time recommendation reacting to demand signals during the visit.</p><h4>1. Shifting from Batch to Real-Time Urgency</h4><ul><li><strong>Live Geo-Trend Streaming:</strong> Replace the 12-hour batch cycle with streaming updates, so geo-trend signals reflect localized demand spikes happening at the moment.</li><li><strong>Instant Operational Alerts:</strong> Transition to real-time communication triggers (like instant message alerts) so Market Managers can capitalize on hyper-local demand while it’s hot, not the next morning.</li></ul><h4>2. Predictive Discovery &amp; Solving the Cold Start</h4><ul><li><strong>Neighborhood Collaborative Filtering:</strong> Surface net-new catalog items a buyer hasn’t tried yet by mapping the high-volume purchasing patterns of their regional peers.</li><li><strong>Intelligent Onboarding:</strong> Handle the “cold-start” problem properly. Right now, new buyers get generic geo-cluster defaults. The goal is a lightweight predictive layer that kicks in from day one using regional peer patterns.</li></ul><h4>3. Closing the Data Loop</h4><ul><li><strong>Dynamic Feedback Ingestion:</strong> Every interaction, call outcome, and rejection will feed directly back into the scoring model in real time.</li><li><strong>Continuous Model Refinement:</strong> By closing the loop between recommendation and reality, the system automatically self-corrects, outcomes are fed back as training labels ensuring the precision of the tool sharpens with every single signal.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf609b7694c6" width="1" height="1" alt=""><hr><p><a href="https://udaan.dev/actionable-recommendations-for-market-managers-the-push-list-approach-bf609b7694c6">Actionable Recommendations for Market Managers: The Push-List Approach</a> was originally published in <a href="https://udaan.dev/">engineering-udaan</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>