The product moved 412 units last month. The shop’s own dashboard called it a bestseller. Then the month closed and the contribution was almost nothing. Nothing was broken. The product really did sell. What was wrong was the level of detail. A product total averages every variant underneath it. One variant can quietly cancel out three good ones. The answer was sitting in a TikTok Shop SKU report nobody had opened.
A TikTok Shop SKU report is the only view that separates them. It is also the least opened report in the seller centre. The product level looks sufficient until the number stops making sense. This is written for the seller running ten to fifty SKUs across one or three markets. The person reading the report is usually the same person doing everything else. There is no analyst to hand it to.
Below is what the report actually shows and which row to look at first. It also covers the two figures that have to move from the product row down to the SKU row. Until they do, none of it means anything.
A product total is an average pretending to be a fact
Every product figure in a shop dashboard is a weighted average of its variants. That is fine when the variants behave similarly. It is actively misleading when they do not. Take a three-size product. Volume concentrates in the middle size, at 80 percent. A 40 percent return rate sits on the largest. The product number still reports as perfectly healthy. So a good size pays for a bad one.
The trap closes slowly. The first month looks fine. In the second month the return rate on one variant creeps up. The product total dips a little, which reads as seasonality. By the third month the variant has eaten the margin on the whole line. Someone decides this product is not working. That is the wrong decision at the wrong level.
The SKU row turns that into a specific question. Which variant? At what return rate? Since when? That is a question with an answer. “The product is not working” is not.
Four figures that belong on the SKU row
Most sellers look at units and revenue per SKU and stop. Those are the two least informative numbers on the row. They look good while the product is quietly failing. These four change a decision.
| Figure | Why it has to be per SKU | What it changes |
|---|---|---|
| Net contribution after refunds, platform fee and shipping | Shipping cost per unit differs by variant weight and size | Which variant to reorder, which to drop |
| Return rate | One size or colour usually carries almost all of it | Whether the problem is the listing photo or the product |
| Creator-driven share of units | Commission sits on some variants and not others | Which variant to push to creators next round |
| Days of cover at current velocity | Velocity per variant is not proportional to the product total | Whether a restock is urgent or imaginary |
Two of these are already standard in a shop’s reporting. Two usually are not. Return rate per SKU pays for itself fastest. The fix is often a photo or a size chart rather than a product change.
The variant that carries the product
In most catalogues one variant carries the line, at 60 to 85 percent of units. A TikTok Shop SKU report is the only view that shows which one. That is not a problem. The problem is that teams plan the next order as if the split were even. Then they hold dead stock on the variants nobody wanted while the good one sells out twice.
Once you know which variant carries the line, three things change at once. The restock order stops being a guess. The creator brief stops being about “the product”. It starts being about the size or colour that actually converts. The photography budget goes to the variant that sells instead of being spread evenly across a range.
There is a limit worth stating. A SKU report tells you which variant wins. It does not tell you why. Sometimes the cause is price. Another time it is a photo. Or it is simply that the middle size fits more people. The report narrows the question from “the whole product” to “this one row”. A person still has to answer it.
Return rate is a SKU problem before it is a product problem
A product-level return rate of 9 percent sounds acceptable. It tells you nothing. Split across five variants it might be 3, 3, 4, 4 and 31. That 31 is the entire reason the product is not making money. A single variant at 31 percent is a listing defect. The size chart is wrong, the colour is misleading, or the photo shows a different finish.
This is the cheapest fix in the whole catalogue, and SKU level is the only place it shows. Fixing a size chart costs nothing. Fixing a product that genuinely does not work costs a relaunch.
DAMI keeps the SKU breakdown beside the product total rather than in a separate export. The two are read in one pass instead of two sittings a month apart. DAMI also carries the net figure down to the variant row. That figure is what remains after refunds, platform fee and shipping. The variant row is where the decision actually happens.
The order to read it in
Open the SKU report before the product report, not after. Product first is how the wrong question gets asked. SKU first means the product total arrives already explained. Then read in this order. Contribution, return rate, carrying variant, days of cover. Anything after that is detail. DAMI orders the view that way by default. Each person opening it then works from the same sequence instead of reaching a different conclusion.
One honest caveat on attribution. In a shop with several traffic sources, the creator-driven share of a variant is approximate. A single month is also a small sample. Treat a one-month outlier as a question rather than a verdict. Confirm it over two cycles before you cut a variant.
This sits inside a wider reading problem. The four reports that answer four different questions covers where the SKU view belongs relative to the others. The seven-stage map is the starting point if you are not sure the reporting is what is broken. If the variant question is settled and the problem is what to do with the creators pushing it, the outreach chain is the next step. The DAMI analytics workspace is where the SKU row and the video that drove it sit in one view.
FAQ
How many variants are too many to read this way?
Beyond roughly fifteen SKUs per product, the report stops being readable. It starts being a spreadsheet. At that point, sort by contribution and read the bottom five. The variants losing money are the only ones that need a decision this week.
Should a variant with a high return rate be dropped immediately?
No. Drop it after you have checked the listing. Most high-return variants are a photo or size-chart problem, not a product problem. If the return rate survives a corrected listing for two cycles, then it is the product. Dropping it is right.
Does the SKU report work if I sell the same product in three markets?
Only if you filter the report by market. The same SKU can carry a line in one market and fail in another. The reasons often have nothing to do with the product. Creating an account starts you with one market. That is the right number to learn this report on before the second one doubles the rows. Filter the TikTok Shop SKU report by market from week one. The second market then costs you nothing extra.
