Swiggy Instamart Demand Forecasting with Google TimesFM

This title was summarized by AI from the post below.

Quick commerce moves fast. Forecasting demand for it accurately? That requires next-level Data Science. 🛒⚡ The team at Swiggy has just published a deep dive on Swiggy Bytes into how Instamart revamped its demand forecasting by leveraging Google’s TimesFM foundation model and transitioning from flat forecasts to deep, hierarchical modeling. Building a predictive engine for thousands of SKUs and rider fleet planning comes with massive challenges—like censored sales data from stockouts and high variance from product substitutions. Here is how the team solved it: 🔹 𝐀𝐯𝐚𝐢𝐥𝐚𝐛𝐢𝐥𝐢𝐭𝐲 𝐃𝐞-𝐁𝐢𝐚𝐬𝐢𝐧𝐠: Correcting historical data to account for when items were actually out of stock. 🔹 𝐆𝐫𝐨𝐮𝐩 𝐒𝐊𝐔 𝐀𝐠𝐠𝐫𝐞𝐠𝐚𝐭𝐢𝐨𝐧: Smoothing out demand variance caused by customers substituting similar products. 🔹 𝐃𝐮𝐚𝐥-𝐇𝐢𝐞𝐫𝐚𝐫𝐜𝐡𝐲 𝐅𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤: Separating the overarching business objectives from the optimal modeling level. 𝐓𝐡𝐞 𝐑𝐞𝐬𝐮𝐥𝐭𝐬? 🚀 21–38% relative accuracy improvement for warehouse forecasting across categories. 🚀 7.5% WMAPE improvement & a massive 50% reduction in runtime for OPD forecasting compared to their previous TFT-based system. Huge shoutout to the authors SAHIB MAJITHIA, Satpalsingh Ghunia , and Mano Ranjith Kumar M for sharing the architecture behind this! Check out the full read here: https://lnkd.in/eRB9CxiV #GenerativeAI #SupplyChain #TimeSeriesForecasting #QuickCommerce #DataScience #MachineLearning #SwiggyInstamart #TechBlog

Sunil Rathee Really enjoyed reading this. One of the most practical and honest write-ups I’ve come across on demand forecasting for quick commerce. I had a couple of technical questions, if you’re open to sharing some more details: For availability debiasing, how are you correcting the historical sales and future features? Is it based on an empirical correction using observed availability, or do you have a separate model estimating latent demand? I’m especially curious about SKUs that stay unavailable for long periods (seasonal items), where simply training on available periods doesn’t seem sufficient. Also, for the hierarchical setup using TFT and TimesFM, are you forecasting at a higher aggregation (SKU × warehouse/city, for example) and then allocating to stores? Reason being time complexity of these models for store<>sku level training and scoring would be too bad. If yes, what does the allocation ratio consist of? Is it based on historical fully-instock sales share, OPD, demand share, or some learned allocation model? Would love to understand these aspects a bit better. Great work by the team!

To view or add a comment, sign in

Explore content categories