Flipkart Marketplace Platform  ·  View 05 of 25  ·  2 · People and journeys

Journey — Seller, Listing to Settlement

The supply side of the marketplace, from a phone-only signup to money in a bank account seven days later.

Editable source SVG draw.io All views
Small seller long tail, 1.4M sellers Goal — Be listed, sell, and be paid, without a back office Trigger — Signing up with a PAN and a GSTIN on a phone Done when — Money in the bank on T+7, matching what the app said 1 · Onboard KYC 2 · List catalog 3 · Win Buy Box 4 · Ship ◆ moment of truth 5 · Get paid ◆ moment of truth 6 · Reconcile What they do Submits PAN, GSTIN Adds bank account Matches to a product Sets price and stock Watches the offer rank Packs and hands over Reads the payout Disputes a deduction Where Seller app OTP and documents Listing tool or bulk API Seller dashboard Pinot backed Manifest label and pickup Payout statement Dispute case How it feels Delighted Fine Frustrated Behind the glass Seller onboarding KYC and risk score Catalog moderation Buy Box scoring Fulfilment engine Settlement ledger Dispute workflow Where it hurts KYC stalls for days Rejected, no reason SLA breach, no warning Deduction unexplained What would fix it Async KYC with status Reason code on reject Show the Buy Box gap Predictive SLA alert Line-item statement Traceable ledger entry How we know KYC p50 4 h Live in 15 min Buy Box win rate SLA breach 1.8% T+7 on time 99.9% Dispute age p90 User Journey — Seller From First Listing to Settlement Settlement is the only phase where the platform holds the money of another business; the ledger behind it is why view 13 exists. v 1.0 · owner Product + Enterprise Architecture · date 2026-09

The trough, and what it decides

  • Listing rejection with no reason code is the worst moment: moderation must return a machine-readable cause, not a status
  • An unexplained deduction at reconcile destroys trust in the ledger, which is why settlement is double-entry and every line traces to an order line
  • KYC is asynchronous with a visible state machine, because a seller staring at a spinner for two days churns

Decisions

  • Bulk feed and single-listing UI hit the same API, so a brand and a long-tail seller cannot diverge in behaviour
  • Seller analytics is served from a real-time OLAP store, never from the transactional shards
  • Payout timing is a policy input keyed on seller risk band, not a constant

Targets

  • KYC decision p50 4 hours, p95 24 hours
  • A price change visible on every surface within 15 minutes
  • T+7 settlement on time 99.9%, reconciled to the paisa
◀  Journey — Buying in a Sale Hour All views Journey — Return and Refund  ▶
Solution Architecture v1.0 · Open source on Microsoft Azure · Enterprise Architecture · 2026-0905-journey-seller-listing-to-settlement