CSV with Sku Id, Campaign Name, Conversion Rate (no AdGroup CPC)
Append → FSN Ad Reports slot
Ad Spend Input, P&L, Overview, Ads Intelligence
Ads: Daily Report
CSV with Campaign Name, Date, Ad Spend (no Sku/Keyword/Placement)
Append · persists
Ads Intelligence
Ads: Placement
CSV with Placement Type
Append · persists
Ads Intelligence (Waste Finder)
Ads: Overall Performance
CSV with Total converted units, Sku Id (campaign-level)
Append · persists
Ads Intelligence
Ads: Search Term
CSV with Query column (~800KB, large)
Append · re-upload each session
Ads Intelligence (Waste Finder)
Ads: Campaign Order
CSV with order_id, Advertised FSN ID, Purchased FSN ID
Append · persists
Ads Intelligence
Ads: Keyword
CSV with attributed_keyword, keyword_match_type
Append · persists
Ads Intelligence (Waste Finder)
Storage & Reset
Data is stored in your browser's local storage. Re-upload your FK reports if you switch browsers or devices.
Storage used: —
Get started
See your real Flipkart profit in 5 minutes
Upload the reports you already download from Seller Hub, or explore a demo store first. Everything runs in your browser; your data never leaves this device.
1Download from Seller HubOrders and P&L to start. Returns, settlement, ads and SPF add depth.orders.csvp&l.xlsxreturns.csv
2Drop them hereEvery file is recognised automatically and processed on this device.auto-detectedstays local
3Read your true profitPer SKU, after fees, returns, RTO, ads, COGS and GST, plus money you can recover.15+ views
No signup · No Flipkart API access · Not affiliated with Flipkart
More insights — period comparison, ad spend & top SKUs
Period vs Prior Period
Key metrics compared to the previous equivalent window
Ad Spend Summary
From FSN Ad Report or manual entry — for campaign-level analysis see the Ads Intelligence tab
Top SKUs by Revenue
Best performing products in the window
SKU
Orders
Revenue
Avg Price
Top SKUs by Returns
Highest return rate products — investigate quality or listing issues
SKU
Orders
Returned
Return %
📦
No orders loaded
Drop a Flipkart Order CSV to see status breakdown, geographic distribution, and daily trend.
Status Breakdown
Daily Orders & Revenue
State Distribution
Top States — Stacked
Delivered vs in-pipeline vs returned
Top Cities
#
City
Orders
Revenue
Cancellations — diagnostic only, no P&L impact
Pre-shipment cancellations from your FK Cancelled Orders CSV. These cost you nothing financially (no packing, no shipping, no commission) but reveal why customers walk away. Post-shipment "return cancellations" are excluded — they're return-trip events, not real cancellations.
Top cancellation sub-reasons
Actionable ones marked with 🎯
Sub-reason
Count
%
Cancellations by SKU
Plus cancel rate where shippable data exists
SKU
Cancelled
Shipped
Cancel rate
Recent cancellations (last 50)
Cancellation Date
Order ID
SKU
Type
Sub-reason
Value
Order Patterns — by day of week
When customers actually buy. Useful for ad scheduling, inventory pressure, and weekly trend awareness. Note: Flipkart's Orders CSV exports date only (no time), so hour-of-day analysis is not possible from this report. Day-of-week is the most granular signal available.
Successful orders by day
Orders that shipped or are in pipeline (excludes cancellations)
Total demand by day
All customer intent (successful + cancelled). Cancellation rate per day in red.
Per-SKU day-of-week pattern
SKUs/Groups with ≥20 successful orders only. Best/worst days highlighted.
SKU / Group
Orders
Sun
Mon
Tue
Wed
Thu
Fri
Sat
Insight
Demand Quality — COD vs Prepaid · Channel · Geography
Where your bad orders come from. COD (Cash on Delivery) orders cancel and return at much higher rates than prepaid — understanding the split helps you decide whether to restrict COD on specific SKUs or geographies in Flipkart's shipping settings.
Payment mode breakdown
Cancel and return rates by how the customer paid. COD orders have higher cancellations (customer wasn't committed) and higher returns (easier to refuse at door).
Mode
Orders
Cancel %
Return %
Settled
Pending
Channel breakdown
Flipkart vs Shopsy performance. Shopsy tends to attract more price-sensitive buyers — watch for higher cancel/return rates.
Channel
Orders
Cancel %
Return %
Net Sales
Order quality by state
From your Orders CSV — states with high cancellation or return rates are costing you more per delivered unit. Consider restricting COD or blocking specific pincodes in FK settings for the worst states.
State
Orders
Delivered
Cancel %
Return %
Revenue
Signal
SKU Velocity
which products are accelerating, holding steady, or declining — week over week
SKU Performance Trend
Orders per SKU split into first half vs second half of the selected period. Trend arrow shows direction. Sort by column headers.
SKU
Product
Total Orders
First Half
Second Half
Trend
Revenue
Avg Price
Return %
Signal
Geographic Intelligence
where your customers are — and where returns and cancellations are highest
Top States
Orders, revenue, and return rate by state. High return states cost more per delivered unit.
State
Orders
Revenue
Delivered
Return %
Top Cities
City-level breakdown with return rates — helps identify problem delivery zones.
City
State
Orders
Revenue
Return %
🚩 Problem Pincodes — high return or cancellation rate with meaningful volume
Pincodes with ≥5 orders and return rate above 30%. Consider restricting COD or disabling delivery to these pincodes in your FK seller settings.
PIN Code
City
State
Orders
Returned
Return %
Revenue
Action
Repeat Buyers
customers who ordered more than once — detected by name + pincode match
Repeat Buyer Groups
Grouped by Buyer Name + PIN Code. Same name at same pincode = likely same customer. Orders across different SKUs show cross-sell success.
Buyer
PIN Code
City
Orders
SKUs ordered
Total Revenue
Last Order
SKUs with Most Repeat Purchases
Products that the same customer buys again — high repeat rate = strong product-market fit or consumable behaviour.
SKU
Total Orders
Repeat Orders
Repeat Rate
Avg Revenue/Buyer
💰
No P&L report loaded
Drop your Flipkart P&L XLSX (the file with PNL Summary and SKU-level P&L sheets) to see fees, taxes, and net earnings.
Report Window
—
P&L Statement
From Gross Sales to Bank Settlement
Line Item
₹
Fee Breakdown
Where Flipkart's cut goes
SKU-Level P&L
net units, sales, fees per SKU in the report window
SKU
Gross
RTO
RVP
Cancel
Net
Net Sales
Total Fees
Bank Settlement
Ad Spend
Net After Ads
COGS
Packing
Damage
Overhead
True Net
True Margin %
RoC %
📣
No ads reports loaded
Upload your Flipkart Ads reports (from Ads Manager → Reports) on the Data Sources tab. SellerLens auto-detects all 7 report types: Consolidated FSN, Consolidated Daily, Placement, Overall Performance, Search Term, Campaign Order, and Keyword.
Campaign Health Scorecard
all campaigns at a glance — color-coded by ROI and efficiency
Campaigns
Click column headers to sort. True ROI factors in your return rate and COGS — the number Flipkart doesn't show you.
Campaign
Spend
Revenue
Gross ROI
True ROI
Views
Clicks
CTR %
Conv
Conv %
Avg CPC
Cost/Conv
Signal
Spend Distribution
Where your ad budget goes
ROI by Campaign
Green ≥ 5×, Yellow 2–5×, Red < 2×
Daily Spend & Revenue
From Consolidated Daily Report — all campaigns stacked
Waste Finder
keywords, placements & search terms burning money with zero conversions
⚠Upload Search Term, Keyword, or Placement reports for waste analysis. The Consolidated FSN/Daily reports alone don't contain the granularity needed.
🔴 Negative Keyword Candidates — from Search Term Report
Customer search queries that triggered your ads, got clicks, but produced zero sales. Adding these as negative keywords in FK Ads Manager stops the bleed immediately.
—
wasted in the report period on zero-conversion search terms
Search Term
Campaign
Match
Spend
Clicks
Views
CTR %
Action
🟡 Underperforming Keywords — from Keyword Report
Keywords you're actively bidding on that have low or zero ROI. Consider pausing or reducing CPC.
Keyword
Campaign
Match
Spend
Clicks
Direct Sales
ROI
Action
🟡 Dead Placements — from Placement Report
Placement positions with spend but zero conversions. Consider excluding these placements or shifting budget.
Campaign
Placement
Spend
Clicks
Views
Revenue
ROI
Action
SKU Profitability
true ad ROI per product — after returns, COGS & FK fees — the number Flipkart doesn't show you
⚠Load your Cost Model and FSN Ad Report to enable per-SKU true ROI. Both are needed to cross ad spend with your actual margins.
SKUs where you are actively spending on ads but the economics don't support it.
SKU
Ad Spend
Ad Revenue
Gross ROI
True ROI
COGS/unit
Adj. CPC
Issue
All SKUs — Ad Performance vs True Margin
Sorted by ad spend. True ROI = (ad revenue × (1 − return rate) × (1 − FK fee%) − COGS) ÷ ad spend.
SKU
Product
Ad Spend
Ad Revenue
Gross ROI
True ROI
Units
COGS/unit
Adj. CPC
Ad/Rev %
Signal
Budget Pacing
daily spend rate, month-end projection & efficiency by day of week
⚠Upload your Consolidated Daily Report from Ads Manager for budget pacing analysis.
Daily Spend & ROI Trend
Spend bars + ROI line — spot days where spend spiked but ROI dropped
Day-of-Week Efficiency
Average ROI by weekday — find your best & worst performing days
Campaign Daily Breakdown
Spend and ROI per campaign per day — sorted by date
Date
Campaign
Spend
Revenue
ROI
Clicks
Conv
💳
No settlement data yet
Upload your Flipkart P&L XLSX (the one with the Orders P&L sheet) to see what FK owes you, pending payments, and return deductions.
Settlement Tracker — what does Flipkart owe you right now
Parsed from the Orders P&L sheet in your FK P&L XLSX. Every order's settlement status: projected, paid, pending. Negative pending = return recovery — FK already paid you but will claw it back because the order returned.
By settlement reason
Reason
Txns
Completed
Pending
By payment mode
COD (postpaid) orders settle later than prepaid — useful for cash-flow planning.
Mode
Orders
Settled
Pending
Rate
Settlement Reconciliation
cross-referencing your orders CSV with settlement data to find gaps and discrepancies
⚠Upload your Orders CSV alongside the P&L XLSX to enable reconciliation. Orders CSV gives us delivery status; settlement comes from the P&L Orders P&L sheet.
🔴 Delivered but not settled — FK owes you for these
Orders your CSV shows as Delivered but with no settlement entry or zero projected amount in the P&L. Cross-check with FK seller portal — these may need a claim.
Order ID
Order Date
SKU
Invoice Amt
Status in FK
Action
🟡 Amount mismatch — projected ≠ invoice amount
Orders where the settlement projected amount differs significantly from the Invoice Amount in your orders CSV. May indicate FK fee miscalculation or wrong SKU mapping.
Order ID
SKU
Invoice Amt
Projected
Difference
Note
🟡 Overdue settlements — pending > 30 days
Orders with positive pending amount that have been waiting more than 30 days. FK typically settles within 7-15 days for prepaid and 15-30 days for COD.
Order ID
Order Date
SKU
Mode
Pending
Days waiting
Action
📉 Upcoming clawbacks — FK will deduct these from future settlements
Orders where FK has already paid you but will deduct the amount in a future settlement cycle because the product was returned. Plan your cash flow accordingly.
Order ID
Order Date
SKU
Mode
Settled
Clawback
Net Impact
Order-level ledger
Sorted by pending ↓ · max 300 shown
Order Date
Order ID
SKU
Mode
Status
Projected
Settled
Pending
Transactions
🏷️
No listings loaded
Drop your S_listing*.xls file from Flipkart Seller Hub to see MRP, selling price, stock counts, and benchmark prices per SKU.
Active Listings
Title
SKU
Status
MRP
Selling
Discount %
vs Benchmark
Stock
Ad Spend Input
FSN report (preferred) or manual entry — flows into Overview, P&L, and SKU profit
📥Best path: drop your FSN ad report (the per-campaign-per-SKU breakdown from Flipkart) on the Data Sources tab — it'll appear above and drive accurate per-SKU profit. Fallback: manually enter totals below; they apply only to SKUs not in the FSN report.
Totals (manual fallback)
Used only for SKUs missing from the FSN report — proportionally allocated by revenue share
ROI is derived: revenue ÷ spend
Computed
Updates as you type
Ad ROI (derived)—
Net Ad Profit (Revenue − Spend)—
Days in period—
Avg daily spend—
Per-SKU Ad Allocation
optional — for accurate per-SKU profit, split spend across SKUs
⚠️If you skip this, ad cost is allocated proportionally to revenue across all SKUs in the P&L. That's fine for overall numbers but distorts per-SKU profit (BBINC567 takes most of your budget — ignoring this makes other SKUs look more profitable than they are).
Enter the ad spend per SKU. SKUs from your loaded P&L report appear automatically. Leave blank to skip — it'll fall back to revenue-proportional allocation.
SKU
Type
Net Units (from P&L)
Net Sales
Ad Spend (₹)
Ad Revenue (₹)
SKU ROI
Current Status
🏥
SKU Health needs P&L data
Drop your Flipkart P&L XLSX (and optionally the eCommerce_PnL_Model.xlsx for landed costs + ad spend on the Ad Spend Input tab) to see per-SKU performance metrics.
📊Metrics-only view. Margin %, return rate, ad ROI shown side-by-side per SKU. No PUSH/HOLD/STOP labels — you decide what action to take.
SKU Scorecard
Click any column header to sort
SKU
Type
Net Units
Net Sales
FK Earnings
Ad Spend
Net After Ads
COGS
Packing
Damage
Overhead
True Net
True Margin %
RoC %
Return %
Ad ROI
Trend
Net-After-Ads Profit by SKU
Return Rate vs Margin
Bubble size = net units sold
Pricing Calculator
break-even & target-margin price for any SKU — adjust assumptions live
🧮
No SKU costs loaded
Upload the eCommerce_PnL_Model.xlsx (which contains the SKU Costs sheet), or use the manual costs editor below to enter landed costs.
Inputs — Adjust Live
Pick a SKU; landed cost auto-fills if known
Purchase + GST + transport + SKU packing
Default 47% — upload Returns CSV for SKU-specific rate
% of net sales — e.g. 15.15 for 15.15%
% of selling price — e.g. 15 for 15% margin
Calculated Pricing
Updates as you type
Landed cost / NET unit—
Packaging / NET unit—
Total unit cost (excl FK fee)—
BREAK-EVEN price—
TARGET price (for margin)—
Profit / net unit at target—
Gap vs current price—
Break-Even & Target Pricing — All SKUs
Snapshot using your current settings
Manual Cost Editor
✏️Edit landed cost components for any SKU. Changes persist across reloads. SKUs from the eCommerce_PnL_Model.xlsx XLSX upload are marked (xlsx); if you edit them, they're marked (manual) and won't be overwritten by future XLSX uploads.
SKU
Type
Purchase (₹)
GST
Transport (₹)
Packing (₹)
Landed (₹)
Source
Add a new SKU below if it's not already loaded
Profit Predictor
"What if I sell X units of Y at Z price?" — full simulation
🔮
No SKU costs loaded
Upload the eCommerce_PnL_Model.xlsx or add costs via the Pricing tab editor first.
Scenario Inputs
Edit any field, watch profit prediction update
Total customer orders you expect
Historical avg: ~₹71/order
% of net sales — e.g. 15.15
Predicted P&L
Cancelled—
Shipped—
Returns—
Net units kept—
Net Sales—
FK Net Earnings—
COGS—
Total Costs—
PREDICTED PROFIT—
Margin %—
Profit / net unit—
Sensitivity — Profit vs Selling Price
How profit moves as you change price (all other inputs constant)
New Products Workflow
plan it · track it daily · reconcile at month-end
Your SKU Registry
Saved in this browser · 0 SKU(s)
Plan: New Product Inputs
Fill this in BEFORE you buy stock — see if it pencils out
% of net sales
% of selling price
Pricing Result
Updates as you type
Landed cost / unit—
Cost / NET unit (after returns)—
Total cost / net—
BREAK-EVEN price—
TARGET price—
Profit / unit at expected price—
Margin at expected price—
100-order forecast
Cancelled
—
Shipped
—
Returns
—
Net Kept
—
Net Sales
—
Total Cost
—
Profit
—
Margin %
—
How tracking works
PLANNED SKUs show forecasted numbers (per 100 orders). LIVE SKUs additionally pull real numbers from your Orders CSV — fuzzy-matched on SKU code or product name. The estimated profit uses your historical defaults (23% cancel, 47% return, 15.15% FK fee, ₹60 packaging) until you mark a SKU as Reconciled with month-end P&L data.
Strategic Action Plan
data-driven moves grounded in YOUR loaded files
🎯
Strategy needs more data
Load orders, P&L XLSX, and ad spend to generate strategic recommendations grounded in your actual numbers.
⚠️About these recommendations: they are computed from the data you've uploaded — what's profitable, what's bleeding, what's stocked out. They are not a substitute for your judgment. Use them as a checklist, not a rulebook.
The Big Picture
Pricing Moves
SKU Decisions
Operational Levers
Purchase Ledger
log every purchase · auto-computes rolling weighted-avg cost per SKU
📦How this works: upload a CSV/XLSX with columns Date, SKU, Quantity, Purchase Price, GST, Transport, Packing — or add rows manually below. The dashboard computes rolling weighted-average landed cost per SKU, which feeds into P&L, SKU Health, Pricing Calculator, and Strategy. Download CSV template
Add a Purchase
Or upload a file via Data Sources tab
Selecting a group means this purchase belongs to a shared inventory pool across all member SKUs. SKU field becomes optional in that case.
Landed/unit: —
Rolling Weighted-Avg Cost (current window)
As of: —
SKU
Qty Purchased
Qty On-Hand
Avg Landed
Total Cost
Purchase History
Date
SKU
Group
Qty
Price/unit
GST
Transport
Packing
Landed/unit
Total
Source
SKU Groups
link multiple SKUs that share one physical product
When the same physical product is listed under multiple SKU codes (e.g., BBINC567 + BBINC568 + Induction 01 are all the 2000W cooktop), define a group. Purchases logged against the group flow into a shared inventory pool, and sales of any member SKU draw from it. Cost per unit is computed as the group's rolling weighted-average.
Add a group
Avg Landed Cost Over Time
How weighted-avg cost evolved per SKU as new purchases came in
Drop your Flipkart returns CSV on the Data Sources tab. It auto-detects by columns Return ID, Order ID, SKU, Return Reason. Then you'll see classification, per-SKU return rates, and a list of damaged returns missing SPF claims.
💸Money on the table: damaged/defective returns are older than 30 days with NO SPF claim filed. Estimated unclaimed value: . See list below →
Return Type Mix
Courier returns (never delivered) vs Customer returns (delivered then returned)
Top Return Reasons
Why customers send things back
Per-SKU Return Profile
Each return classified by economic impact. Damaged/defective returns are SPF-claimable.
SKU
Total returns
RTO
Damaged
Quality
Customer
Other
Value at risk
Unclaimed Damages — Money You Can Still Recover
Damaged/defective returns with NO matching SPF claim, > 30 days old. Copy the Order IDs and file SPF claims via Flipkart Seller Hub.
Return Date
Age (days)
Order ID
SKU
Reason
Sub-reason
Value ₹
All Returns
Requested
Type
Order ID
SKU
Class
Reason / Sub-reason
Value ₹
Status
Return Reason → ₹ Impact — who's responsible, what it cost, what's claimable
Every return reason bucketed by responsibility. Use the "Claimable" rows to file SPF claims — these are FK or courier failures, not yours.
Reason bucket
Responsibility
Units
Est. ₹ cost
Claimable?
Action
Replacement Units — invisible cost of sending a second unit
When FK grants a customer a replacement instead of a refund, you ship a second unit at full cost but receive no additional payment. These units don't show up anywhere in your P&L — they're a hidden write-off.
SKU
Reason
Replacements
Unit landed cost
Total hidden cost
Cancellation Responsibility — FK's fault vs buyer vs yours
Not all cancellations are your problem. Marketplace-cancelled orders are FK's operational failures — your inventory was ready but FK's courier or process failed. Seller-cancelled orders hurt your seller rating and should be zero.
By responsibility
Who cancelled
Count
Order value
%
FK's marketplace cancellations — breakdown
Damaged Shipment OBD orders are claimable via SPF — FK's courier damaged your shipment in transit.
Sub-reason
Count
Order value
Claimable?
Seller Protection Fund Claims
recovery from Flipkart for damaged / lost inventory
🛡
No SPF claim report loaded
Drop your SPF claim report XLSX (with sheets named Seller Claims and Auto-Approved Claims) on the Data Sources tab. Recovery amounts will flow into Net Profit, and per-SKU damage analytics will appear here.
Claim Status Mix
Recovery by SKU
Approved claim amount per SKU (joined via Order ID)
Per-SKU Damage Analytics
SKU
Claims raised
Approved
Not approved
Approval rate
Recovered ₹
Avg per claim
Reasons for Rejection
Top 10 reasons your claims got rejected — fix these to improve recovery rate
Rejection reason
Count
All Claims
Created
Type
Order ID
SKU
Status
Amount ₹
Reason / Notes
Inventory Health
on-hand · in-transit · expected returns · days of cover
📊
No inventory data yet
Inventory is computed from Purchases (stock in) + Orders (stock out) + Returns (stock back). Load these via the Data Sources tab and inventory will populate here.
⚠
📦 Returns in Transit — on their way back to your warehouse
From your Returns CSV. Units currently in transit, predicted arrival date (from FK delivery promise or historic median transit time), and expected damage based on per-SKU historic damage rate.
SKU
Return Type
Reason
Units
Requested
Predicted Arrival
Expected Good
Expected Damaged
Historic Dmg%
🔧 Damaged / Defective Stock on Hand
Units physically at your warehouse that are damaged, defective, or non-functional. These are excluded from sellable stock. Enter the count in column H "Damaged Units on Hand" of your Cost Model XLSX. Low-value products accumulate damaged stock quickly — track this to know your true write-off cost.
Non-FK Channel Sales
Units sold on BuiBee, Amazon, and other non-Flipkart channels (including Gift / Damage / Lost write-offs). These deduct from on-hand inventory but do NOT flow into FK P&L or True Net. Load entries via the Non-FK Sales sheet in the cost model template — re-uploading replaces the prior xlsx entries.
Date
Product (Group / FK SKU)
Channel
Channel SKU
Quantity
Selling Price
Notes
Stock Position by SKU
Sorted by urgency. Rates computed from trailing 30-day Returns CSV. Effective stock = on-hand − damaged on hand + expected good returns.
SKU / Group
On hand
Damaged
Non-FK sold
In transit
Sold/day
Return rate
Damage rate
Exp. good returns
Exp. damaged
Effective stock
Days of cover
Status
Sell-through Trend (30 days)
Daily units shipped per SKU
Days of Cover by SKU
Red bars = reorder now
Operating Expenses
indirect costs · allocated by bank settlement share · feeds True Net Profit
💼Track rent, salaries, software, and other overhead. Each entry can be Monthly (auto-repeats forward) or One-time. Total opex in the active window is allocated to SKUs proportional to their bank settlement share — so the cooktop bringing in ₹2,000/unit shoulders more rent than the swatter bringing in ₹200/unit. Result flows into the P&L statement as "True Net Profit" and into SKU Health as "Overhead allocated."
Add an expense
Single entry. For recurring, set "Monthly" — it auto-fills every month forward from the start date.
Allocation in active window
How total opex divides among SKUs based on their bank settlement share. Sums must add up to total opex.
SKU
Bank settle
Share %
Overhead alloc
Expense Ledger
Date
Category
Amount
Recurrence
Notes
Source
SKU Parameters
auto-computed rates from your data · click any cell to override
🎛How this works: rates are auto-computed from your loaded FK P&L, Returns, FSN, and Purchases data. Green (auto) = good sample size · Yellow (low conf) = under 20 data points · Grey (fallback) = no data, using global default · Blue (override) = you set this manually. Hover any cell for the calculation details. These values are NOT yet wired into Pricing/Predictor — review and override anything that looks wrong; flow-through coming in a follow-up.
🎛
No data to compute parameters from
Load at least a FK P&L report to compute cancel/return/fee rates. Returns CSV, FSN report, and Purchases ledger fill in the rest.
SKU
Sample
Cancel Rate
Return Rate
FK Fee %
Damage Rate
Defect Loss Rate
Ad Cost / Order
Packing / Unit
value
override
value
override
value
override
value
override
value
override
value
override
value
override
Free Flipkart Seller Analytics Dashboard — True Net Profit, Per SKU
SellerLens is a free Flipkart seller analytics tool that works from your real data. Upload the reports you already download from Flipkart Seller Hub and it computes true net profit for every SKU after commission, fees, returns, RTO, COGS, GST/TCS/TDS and ad spend. No signup, and nothing leaves your browser. Just want a quick number for one product? Use the instant Flipkart profit calculator.
🧾 Commission & fee calculator
Reads the exact commission, collection, fixed and shipping fees from your Flipkart P&L — your real per-SKU fee load, not a rate-card estimate.
💰 Price & break-even calculator
See the selling price at which each SKU actually breaks even once fees, returns and product cost are counted — and reprice with confidence.
📈 Revenue vs settlement
Reconciles what your sales imply against what Flipkart actually paid, so revenue, deductions and underpayments are all visible.
📣 Ad ROI calculator
True return on ad spend after returns and COGS — plus a waste finder that flags keywords burning budget with zero orders.
📦 Returns & RTO cost
The real rupee cost of returns and RTO per SKU, including damaged returns you can still claim back via SPF.
🏛️ GST / TCS / TDS aware
Taxes withheld before payout are part of the math, so the profit you see is the profit that reaches your bank.
How the Flipkart seller dashboard works
Download your reports from Flipkart Seller Hub — Orders CSV and P&L to start; add Returns, Settlement, Ads and SPF for full depth.
Upload them above (or drag & drop anywhere on this page). Files are auto-detected and processed on your own device.
Read your numbers — true net profit and return-on-cost per SKU, ad waste, settlement gaps and unclaimed SPF, across 15 analysis tabs.
🔒 Private by design: SellerLens is 100% client-side. Your Flipkart reports are processed in your browser and are never uploaded to any server — no signup, no API access, no data stored anywhere but your own device.
Flipkart seller dashboard FAQs
Is this Flipkart seller dashboard free?
Yes — completely free, with no signup and no limits. SellerLens runs 100% in your browser: your Flipkart reports are processed on your own device and never uploaded to any server.
How does the dashboard work out my Flipkart profit?
You upload the standard reports you already download from Flipkart Seller Hub — Orders, P&L, Returns, Settlement, Ads and SPF. SellerLens reconciles them and computes true net profit per SKU after commission, fees, returns, RTO, COGS, GST/TCS/TDS and ad spend.
Does it calculate Flipkart commission and fees?
Yes. Instead of estimating from rate cards, SellerLens reads the exact commission, collection, fixed and shipping fees from your own Flipkart P&L report, so your per-SKU fee load is real, not approximate.
Do I need to connect my Flipkart seller account?
No. There is no API access and no login. You upload report files you already have, and all processing happens locally in your browser — nothing about your business leaves your computer.
Can I try it without my own data?
Yes — use the Load Demo Data option to explore the full dashboard with realistic sample data for a fictional store, then clear it and upload your own reports when ready.