๐Ÿ“Š Case Study: How Swiggy Uses Data Analytics to Optimize Delivery & Customer Retention

๐Ÿข Company Overview

Swiggy is one of Indiaโ€™s largest food delivery platforms, competing with Zomato.

  • Founded: 2014
  • Cities served: 500+
  • Daily orders: ~2.5 million
  • Delivery partners: 300,000+

๐ŸŽฏ Business Problem

Swiggy faced 3 major data challenges:

  1. High order cancellation rate
  2. Increasing delivery time in peak hours
  3. Declining customer retention rate

๐Ÿ‘‰ Key question:
How can Swiggy use data to reduce delivery time and improve customer retention?

๐Ÿ“‚ Dataset Overview (Sample Data for Analysis)

๐Ÿ“… Orders Dataset (1 Month Sample)

MetricValue
Total Orders 7,50,000
Completed Orders 6,30,000
Cancelled Orders 1,20,000
Avg Order Value (AOV) โ‚น320
Peak Hours 7 PM โ€“ 10 PM

๐Ÿšš Delivery Dataset

MetricValue
Avg Delivery Time 38 minutes
Target Delivery Time 30 minutes
Late Deliveries 2,10,000
On-Time Deliveries 4,20,000

๐Ÿ‘ค Customer Dataset

MetricValue
Total Customers 2,00,000
Repeat Customers 1,10,000
New Customers 90,000
Retention Rate 55%
Churn Rate 45%

๐Ÿ“Š Data Analysis Performed

1. ๐Ÿ“‰ Cancellation Rate Analysis

Formula:
Cancellation Rate = Cancelled Orders / Total Orders

= 1,20,000 / 7,50,000 = 16%

๐Ÿ‘‰ Insight:

  • High cancellation during peak hours
  • 60% cancellations due to late delivery

2. โฑ๏ธ Delivery Time Analysis

  • Avg delivery time = 38 min (Target = 30 min)
  • Peak hour delay = +12 minutes

๐Ÿ‘‰ Root causes:

  • Traffic congestion
  • Poor delivery partner allocation
  • Restaurant preparation delays

3. ๐Ÿ” Customer Retention Analysis

Retention Rate = 55%

๐Ÿ‘‰ Segment Analysis:

SegmentRetention
Fast delivery (<30 min)72%
Late delivery (>40 min)38%

๐Ÿ’ก Insight:
Delivery time directly impacts retention

4. ๐Ÿ’ฐ Revenue Impact Analysis

Revenue = Orders ร— AOV

= 6,30,000 ร— โ‚น320 = โ‚น20.16 Crore

๐Ÿ‘‰ Loss due to cancellations:

= 1,20,000 ร— โ‚น320 = โ‚น3.84 Crore lost revenue

๐Ÿง  Advanced Analytics Used

๐Ÿ”ฎ Predictive Model (Churn Prediction)

  • Features used:
    • Delivery time
    • Order frequency
    • Order value
    • App usage

๐Ÿ‘‰ Output:

  • High-risk churn users identified = 35,000 users

๐Ÿงช A/B Testing

Test: Faster delivery vs Normal delivery

GroupAvg DeliveryRetention
A (Control)38 min55%
B (Improved)28 min70%

๐Ÿ‘‰ Result:
+15% increase in retention

๐Ÿ“ˆ Key Insights

  • ๐Ÿ“Œ Delivery delay is the biggest driver of churn
  • ๐Ÿ“Œ Peak hour inefficiency causes revenue loss
  • ๐Ÿ“Œ Faster delivery increases repeat orders
  • ๐Ÿ“Œ Predictive analytics helps identify churn early

๐Ÿš€ Recommendations

  1. Dynamic Delivery Allocation
    • Use AI to assign nearest delivery partner
  2. Peak Hour Surge Planning
    • Increase delivery partners from 7โ€“10 PM
  3. Restaurant SLA Optimization
    • Penalize slow restaurants
  4. Customer Retention Campaign
    • Offer discounts to high-risk churn users

๐Ÿ“Š Business Impact (After Implementation)

MetricBeforeAfter
Delivery Time38 min29 min
Cancellation Rate16%9%
Retention Rate55%68%
Revenueโ‚น20.16 Crโ‚น24.5 Cr

Small improvements in delivery time can lead to massive revenue growth.

Scroll to Top