Returns & fees
Return rate, and what it actually costs your margin
Returns by reason code and by SKU, and the margin impact of each — the revenue reversed plus the non-recoverable cost, allocated to the product it came from.
The problem
Returns show up as a lump refund total. You know they are high; you do not know which SKU or which reason is driving most of it, or how much margin it is actually costing.
How Sellrics does it
Sellrics categorizes every return by reason code and SKU (backend/api/return_reasons.py) and computes return impact (backend/api/return_impact.py) — the revenue reversed plus return shipping, restocking, and write-off cost — expressed against that SKU’s contribution margin.
What the numbers mean
Return rate is returned units ÷ ordered units. Refund is the money given back. Return impact is larger than the refund: it adds the costs you do not recover. A reason concentrated on one SKU usually points to a listing, sizing, or packaging fix.
A worked example
Illustrative example- Scenario
- 312 returns in the month, $41,250 in refunds.
- What Sellrics surfaces
- "Damaged" is 118 of them (37.8%, $15,780) — and it clusters on a few heavier SKUs, meaning packaging, not product. "Defective" (74) points at a supplier batch. The buyer-changed-mind returns (56) are the cost of doing business.
- The move
- Fix packaging on the damage-cluster SKUs, raise the supplier batch with defect data attached, and leave the changed-mind returns alone.
Returns by Reason
Sample · 312 returnsSample data — your returns split by reason, with refund value.
See it with sample data
Fictional sample dataA view from the Sellrics dashboard, on fictional sample data — no store connected, nothing stored.
Returns by Reason
Sample data · Last 30 days