Is this Flipkart profit calculator 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.
| Slot | Detection | Mode | Used in |
|---|---|---|---|
| Orders | CSV with Order State, SKU, Invoice Amount | Append + dedupe by Order ID | Orders tab, Overview |
| Cancelled Orders | CSV with Order Cancellation Date, Cancellation Type, Reason, SKU | Append + dedupe by Order ID | Orders tab (Cancellations panel), Overview |
| Flipkart P&L | XLSX with PNL Summary and SKU-level P&L sheets | Replace (latest window) | P&L tab, Overview |
| Listings | XLS/XLSX with Seller SKU Id, MRP | Replace | Listings tab |
| SKU Costs Model | XLSX with SKU Costs sheet (the eCommerce_PnL_Model.xlsx) | Merge (manual entries preserved) | Pricing, Predictor, SKU Health |
| FSN Ad Report | CSV with Sku Id, AdGroup ID, Ad Spend, AdGroup CPC (per-campaign-per-SKU, Overall Performance) | Replace (one report at a time) | Ad Spend Input, P&L, SKU Health, Overview |
| 📣 Flipkart Ads Reports (from Ads Manager → Reports) | |||
| Ads: Consolidated FSN | 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) |
Data is stored in your browser's local storage. Re-upload your FK reports if you switch browsers or devices.
Storage used: —
Order volume vs revenue over the selected window
Where orders sit right now
Key metrics compared to the previous equivalent window
From FSN Ad Report or manual entry — for campaign-level analysis see the Ads Intelligence tab
Best performing products in the window
| SKU | Orders | Revenue | Avg Price |
|---|
Highest return rate products — investigate quality or listing issues
| SKU | Orders | Returned | Return % |
|---|
Delivered vs in-pipeline vs returned
| # | City | Orders | Revenue |
|---|
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 |
|---|
Orders, revenue, and return rate by state. High return states cost more per delivered unit.
| State | Orders | Revenue | Delivered | Return % |
|---|
City-level breakdown with return rates — helps identify problem delivery zones.
| City | State | Orders | Revenue | Return % |
|---|
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 |
|---|
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 |
|---|
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 |
|---|
—
From Gross Sales to Bank Settlement
| Line Item | ₹ |
|---|
Where Flipkart's cut goes
| 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 % |
|---|
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 |
|---|
Where your ad budget goes
Green ≥ 5×, Yellow 2–5×, Red < 2×
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.
| Search Term | Campaign | Match | Spend | Clicks | Views | CTR % | Action |
|---|
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 |
|---|
Placement positions with spend but zero conversions. Consider excluding these placements or shifting budget.
| Campaign | Placement | Spend | Clicks | Views | Revenue | ROI | Action |
|---|
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 |
|---|
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 |
|---|
Spend bars + ROI line — spot days where spend spiked but ROI dropped
Average ROI by weekday — find your best & worst performing days
Spend and ROI per campaign per day — sorted by date
| Date | Campaign | Spend | Revenue | ROI | Clicks | Conv |
|---|
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.
| Reason | Txns | Completed | Pending |
|---|
COD (postpaid) orders settle later than prepaid — useful for cash-flow planning.
| Mode | Orders | Settled | Pending | Rate |
|---|
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 |
|---|
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 |
|---|
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 |
|---|
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 Date | Order ID | SKU | Mode | Status | Projected | Settled | Pending | Transactions |
|---|
| Title | SKU | Status | MRP | Selling | Discount % | vs Benchmark | Stock |
|---|
Used only for SKUs missing from the FSN report — proportionally allocated by revenue share
ROI is derived: revenue ÷ spend
Updates as you type
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 |
|---|
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 |
|---|
Bubble size = net units sold
Pick a SKU; landed cost auto-fills if known
Updates as you type
Snapshot using your current settings
| SKU | Type | Purchase (₹) | GST | Transport (₹) | Packing (₹) | Landed (₹) | Source |
|---|
Edit any field, watch profit prediction update
How profit moves as you change price (all other inputs constant)
Saved in this browser · 0 SKU(s)
Fill this in BEFORE you buy stock — see if it pencils out
Updates as you type
Or upload a file via Data Sources tab
As of: —
| SKU | Qty Purchased | Qty On-Hand | Avg Landed | Total Cost |
|---|
| Date | SKU | Group | Qty | Price/unit | GST | Transport | Packing | Landed/unit | Total | Source |
|---|
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.
How weighted-avg cost evolved per SKU as new purchases came in
Courier returns (never delivered) vs Customer returns (delivered then returned)
Why customers send things back
Each return classified by economic impact. Damaged/defective returns are SPF-claimable.
| SKU | Total returns | RTO | Damaged | Quality | Customer | Other | Value at risk |
|---|
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 ₹ |
|---|
| Requested | Type | Order ID | SKU | Class | Reason / Sub-reason | Value ₹ | Status |
|---|
Approved claim amount per SKU (joined via Order ID)
| SKU | Claims raised | Approved | Not approved | Approval rate | Recovered ₹ | Avg per claim |
|---|
Top 10 reasons your claims got rejected — fix these to improve recovery rate
| Rejection reason | Count |
|---|
| Created | Type | Order ID | SKU | Status | Amount ₹ | Reason / Notes |
|---|
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% |
|---|
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.
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 |
|---|
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 |
|---|
Daily units shipped per SKU
Red bars = reorder now
Single entry. For recurring, set "Monthly" — it auto-fills every month forward from the start date.
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 |
|---|
| Date | Category | Amount | Recurrence | Notes | Source |
|---|
| 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 | ||
SellerLens is a free Flipkart calculator for sellers that works from your real data. Instead of typing numbers into a form, you upload the reports you already download from Flipkart Seller Hub — and it computes your 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.
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.
See the selling price at which each SKU actually breaks even once fees, returns and product cost are counted — and reprice with confidence.
Reconciles what your sales imply against what Flipkart actually paid, so revenue, deductions and underpayments are all visible.
True return on ad spend after returns and COGS — plus a waste finder that flags keywords burning budget with zero orders.
The real rupee cost of returns and RTO per SKU, including damaged returns you can still claim back via SPF.
Taxes withheld before payout are part of the math, so the profit you see is the profit that reaches your bank.
🔒 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.
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.
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.
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.
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.
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.