Swiggy Uses 350+ Features and Multi-Task MLP to Predict Customer
Swiggy developed an in house predicted lifetime value model using more than 350 pre order features and a multi task MLP for Food and Instamart.
By Dillip Chowdary • Sep 03, 2026 • Source: InfoQ
What happened
words". It doesn't restrict the intro paragraph size, but let's make them 40-50 words so the total is within 750-900. * Let's calculate: 10 paragraphs of exactly 80 words = 800 words. Plus 2 intro paragraphs of 45 words = 890 words.
InfoQ Homepage News Swiggy Uses 350+ Features and Multi-Task MLP to Predict Customer Lifetime Value Architecture & Design Online InfoQ Architect Certification (Sept 14): The sociotechnical side of architecture. 0:00 0:00 Normal1.25x1.5x Like Reading list Swiggy has developed an in-house predicted lifetime value (pLTV) model to estimate the long-term value of new customers across its food delivery and Instamart quick commerce businesses.
How it works
The model is designed to generate a useful signal before a customer's first order, allowing Swiggy to use predicted value in advertising bid optimization rather than relying on short-term conversion metrics. Swiggy pLTV model architecture (Source: Swiggy Blog Post) The prediction problem is complicated by sparse early signals and a highly skewed target distribution.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
Why it matters
Swiggy notes that a large share of new users place no orders during their first 30 days, while a relatively small group generates substantially higher lifetime value. See the full write-up from InfoQ via the source link for quotes and complete context.
Who is affected
Read the original coverage at InfoQ via the source link above for the complete details and primary quotes.
What to watch next
Cross-check release notes and official docs before changing production systems based on early reporting.
Developer Action Items
- ☐ Diff the official changelog for Swiggy Uses Features Multi-Task before you bump — APIs, defaults, and removed flags only.
- ☐ Install through the vendor's documented channel in staging; keep a one-command rollback and time-box the canary.
- ☐ Grep your repo for old flag names, lockfile pins, and plugin versions that the notes mark as breaking.
- ☐ Prefer the first patch cut over the day-zero tag unless you have a reason to be on the leading edge.
- ☐ If InfoQ did not name a region, plan, or SKU, screenshot the official availability line before you promise it to users.
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Over 3 Million WordPress Sites Affected by Migration Plugin Vulnerability
Read →
Cisco Warns of Unpatched Secure Email Flaws, Patches Critical Switch Vulnerabilities
Read →
Microsoft Teams, Outlook fail to launch on ARM-based Windows PCs
Read →
Claude Code skill: no emdashes
Read →
Today's Tech Pulse briefing
Full briefing →
Advertisement