SSD Grocery
Selection Expansion

Customers wanted essentials — SSD couldn't deliver them

The SSD network in India had built its selection around electronics, personal care, and discretionary items. But as quick commerce competitors (Zepto, Blinkit, Swiggy Instamart) pulled customers with everyday grocery promises, a gap became undeniable: Amazon's SSD customers were going elsewhere for spices, pulses, snacks, and cookies — items that don't require special handling and could absolutely be fulfilled same-day.

The SSD promise is strongest when it covers the full household basket. If customers need to place a second order elsewhere for grocery staples, the stickiness of the SSD relationship weakens — and with it, Units Per Basket (UPB), a key health metric for the programme.

The selection gap also represented a significant untapped volume opportunity. Fresh Dry Grocery Hubs already had this inventory. The missing piece was the network infrastructure and operational playbook to route it through SSD.

Five parallel workstreams, one program

I structured this as a full program with five parallel workstreams — not a sequential project. Moving sequentially would add months to a timeline with a clear competitor clock running:

4-city pilot launched December 2025

City selection was intentional — a mix of Tier 1 (Bangalore), Tier 2 (Kolkata), and Tier 3 (Madurai, Thiruvananthapuram) markets to stress-test the playbook across different operational environments. If the framework holds in Madurai, it'll hold anywhere.

Q1 2026: network-wide rollout planned pending pilot learnings and SnOP capacity clearance.

Grocery inside SSD creates new operational complexity

• Expiry management: For the first time, SSD FCs are holding items with sell-by dates in the days-to-weeks range — not the months-to-years range of electronics or personal care. Expiry tracking, rotation, and write-off processes had to be built from scratch.
• Colocated vs. standalone FC routing: For colocated SSD FCs (sharing space with a standard FC), grocery inbounds directly from Fresh Dry Grocery Hubs. Standalone SSD FCs require a DC connection point — a more complex routing chain that needed separate configuration.
• Cube allocation for grocery: Grocery items are typically lighter but bulkier than SSD's historical mix. Cube allocation formulas (how much space to reserve per item category) needed recalibration to avoid over-reserving space for high-volume grocery lines.
• Return & refund mechanism: Grocery returns are operationally different — a half-eaten bag of chips can't go back to the shelf. Reverse logistics and refund policies for grocery were defined and integrated into the existing SSD return flow.

What this unlocks for the SSD network

• 6–10% volume share once grocery selection is stabilised across the network — a meaningful incremental contribution to overall SSD demand
• Improved UPB (Units Per Basket) — customers adding grocery staples to existing SSD orders rather than placing a separate order elsewhere
• Repeatable framework — the onboarding playbook built for non-special handling grocery becomes the template for the next category expansion (chilled, dairy, produce)
• Competitive positioning — SSD as a viable same-day grocery channel directly challenges the quick commerce competitors stealing basket share on staples

Other projects in this space