Flipkart Marketplace Platform · View 04 of 25 · 2 · People and journeys
The trough, and what it decides
- Payment is the deepest dip: the UPI handoff leaves the app, and a client-held basket does not survive it — so cart state lives server-side
- The second dip is being oversold at checkout, which decides that stock is reserved before money is requested, not after
- A double debit with no order is the failure customers never forgive — hence one idempotency key from intent to capture
What the platform owes each phase
- Find and Decide are cache-served and may degrade; Reserve, Pay and Confirm may not
- The queue page at the top of the hour is a deliberate fairness mechanism, not an outage
- Confirmation is emitted from the order event, so the screen and the notification cannot disagree
Numbers
- 1.5M orders/hour assumed at peak against a 250k/hour daily average
- 11.4% drop-off at payment is the measured baseline the design is trying to move
- Oversell rate is a zero-tolerance metric, not a percentage target