Which Meesho products are actually profitable?
Start with the profit contribution of each supplier SKU, not the number of orders it received. A busy SKU can still disappoint after product cost, packaging, advertising and failed-order outcomes. A quiet SKU may be worth keeping if its orders settle cleanly and cost little to fulfil. Whole-store sales and bank deposits cannot show that difference on their own.
The useful review is grounded in order and payment records for the same period. Forecasts help before launch; settled orders show what actually happened. Our payment CSV guide explains how to trace the latter.
Use account plus supplier SKU as the identity
A supplier SKU is the code in a seller's order file. If two seller accounts use the same code, do not combine them before checking whether they mean the same item and cost. Work with the pair seller account + supplier SKU. If your business uses a Master SKU to group related child codes, keep the exact supplier-code mapping visible and leave unknown codes unmapped until you can verify them.
Product variants also deserve care. A medium shirt and a large shirt may share a product name but have different supplier SKUs, sourcing costs or return patterns. Decide whether you are reviewing a child SKU or a deliberately grouped Master SKU, then label the result.
Match payment events to distinct sub-orders
- Choose a seller account, SKU and shipped-order date range.
- Build a list of distinct sub-order numbers from the order details. Keep the account attached to every row.
- Join payment entries by sub-order number. One order may have a settlement, adjustment, return or claim in separate rows.
- Mark delivered-and-kept, customer-return and RTO outcomes separately. Keep payment-only entries visible for investigation instead of silently dropping them.
- Sum the retained amount for the order only after all relevant entries are connected.
Do not divide by raw CSV row count when calculating a return or RTO rate. Use distinct orders from the same cohort. Also check whether a recently shipped order is still pending before calling it a delivered win or a loss.
Add the costs you can trace
| Cost | How to handle it |
|---|---|
| Product purchase or manufacturing | Use the cost for that exact account and supplier SKU, including any inbound amount you allocate per unit. |
| Packaging and other per-order work | Use your own material and handling records; keep the basis consistent across SKUs. |
| Delivery and return charges | Read the actual payment entries. Do not subtract a charge again if it is already inside the net settlement. |
| Ads | Allocate campaign spend using a stated method and include spend that produced no sale when judging campaign economics. |
| Damaged or missing returned stock | Record the observed loss and any later claim or reimbursement separately. |
SKU contribution is the sum of retained settlements for its order cohort minus the direct product, packaging, ad and other costs that are not already reflected in those settlements. It is a business-analysis figure, not a statutory profit or tax calculation. Keep overhead, tax credits and cash timing in their own views.
What to do when a SKU looks weak
First check the data. A missing Orders file, wrong account mapping, duplicate cost deduction or payment-only record can distort the result. Then look for a cause you can change: inaccurate size information, poor quality control, expensive packaging, ad spend that does not convert, or a price that leaves no room for ordinary returns.
Test changes one at a time and compare like-for-like order cohorts. There is no universal RTO threshold or fixed price increase that makes every SKU profitable. A seasonal product, a low-volume variant and a high-volume repeat item call for different decisions.
In the signed-in workspace, SKU Costing lets you maintain purchase, packaging and other costs for seller SKUs and group them under Master SKUs. Use its account and date controls when reviewing the figures. The public profit calculator is useful for a scenario before you have enough actual orders.
Common questions
What is SKU-level profit analysis for a Meesho seller?
It connects each distinct order and its payment outcome to the supplier SKU, then compares retained settlement with product and operating costs for that SKU.
Can two seller accounts use the same SKU code?
Yes. Treat seller account and supplier SKU together when mapping costs and outcomes. The same text code in another account can represent a different product or cost.
How do I calculate an RTO rate for one SKU?
Use distinct shipped sub-orders for the account and SKU as the denominator and distinct RTO sub-orders from the same cohort as the numerator. Keep customer returns after delivery separate.
Try the workflow with your own data.
Open the matching Seller Analytics Hub tool and review the result before using it for dispatch or reporting.
