SellerMetric

The problem

Flipkart sellers receive dense Earn More Reports. Finding loss-making SKUs, return spikes, and ad waste usually means hours in Excel and easy-to-miss rows.

Who it’s for

Flipkart marketplace sellers and operators who already export Earn More Reports and need faster, visual reads of catalog health.

What I built

SellerMetric lets a seller upload the report in the browser. SheetJS parses the file locally. Recharts then surfaces profit, SKU performance, and return-rate views so loss-making products are obvious.

Architecture

Client-only processing: the spreadsheet never leaves the device. React renders the UI, SheetJS reads the workbook, and Recharts draws the dashboards. There is no server-side storage of seller reports.

What I’d improve

Richer cohort views and clearer export of “fix these SKUs first” lists.

What was difficult

• Mapping inconsistent Earn More Report columns into a stable analytics model.
• Keeping large workbooks usable entirely in-browser.
• Making loss-making SKUs visible without requiring a data-science background.

Outcomes

• Sellers can inspect profit, SKU, and return rate without a backend login.
• Loss-making products surface from the same files operators already download.
• Privacy-first: report data stays on the seller’s machine.

What I learned

• Marketplace reports are messy; column mapping is the product, not a side task.
• In-browser parsing is enough for typical seller file sizes and removes a trust barrier.

Technology

React · Tailwind CSS · Recharts · SheetJS