Track SKU Return Rates in Shopify
Calculate a Shopify SKU return rate from returned and sold units, then use return reasons to investigate the products that stand out.
TL;DR
To find a problem SKU, divide the units returned by units sold for that SKU and express the result as a percentage. Use the same sales period and return-status rule when comparing products. A high rate points to something worth examining; the return reasons and item condition help explain why it happened.
Hylke Reitsma is founder of Forthsuite and a supply chain specialist with 8+ years of hands-on experience at Shell, Verisure, and Stryker. He holds an MSc in Supply Chain Management from the University of Groningen and writes practical guides to help e-commerce teams run leaner, faster supply chains. Selected by Replit as 1 of 20 founders for the inaugural Race to Revenue Cohort #1 (2026) and certified as a Replit Platform Builder.
TL;DR: To find a problem SKU, divide the units returned by units sold for that SKU and express the result as a percentage. Use the same sales period and return-status rule when comparing products. A high rate points to something worth examining; the return reasons and item condition help explain why it happened.
Track SKU Return Rates in Shopify
Last updated: November 2026
To find a problem SKU, divide the units returned by units sold for that SKU and express the result as a percentage. Use the same sales period and return-status rule when comparing products. A high rate points to something worth examining; the return reasons and item condition help explain why it happened.
SKU-Level Return Metrics Explained
What are SKU return rates?
A SKU return rate is the share of sold units for one SKU that customers returned. Calculate it as returned units divided by sold units for the chosen period, then express it as a percentage. Keep color and size variants separate if each has its own SKU. Label whether you count requested returns or completed returns, since those figures can differ.
Key Metrics to Track
Use consistent units and a mature sales cohort. A physical SKU return rate is units physically returned from that cohort divided by units sold in it, multiplied by 100. Wait until its return window has passed and reconcile to the original orders. A refund share among resolved return units uses refunded units divided by resolved return units; an exchange share uses exchanged units over the same denominator. State how split resolutions are counted. Counts of cases, units and monetary refunds are different measures.
Return reasons are reported explanations to investigate, not proof of a defect or its cause. Compare reasons with inspection findings, variant volume, the sales cohort and any changes to the product page. Repeat purchases and margin can add context, but neither a low return rate nor an exchange proves satisfaction.
Using Shopify's Built-In Analytics for Returns
How to Access Return Reports in Shopify
Open Analytics > Reports and inspect the current product or variant report and its field definitions. Shopify’s sales report documentation distinguishes sales reversals from physical returns. Reversals can include cancellations, edits and refunds without goods coming back; do not treat reversed quantity as a physical-return count.
Check whether your report measures physical returns, requested returns, refunds or sales reversals before calculating a rate. Record its date basis and any filters so the analysis can be repeated.
For a physical-return analysis, reconcile these fields in your report or underlying order and return records:
- Product and variant identity: use a stable variant identifier and its SKU; check missing or reused SKUs.
- Sold units: units in the chosen original-order cohort, with cancellations and test orders handled consistently.
- Physically returned units: units linked back to those sold units and the chosen receipt or completion status.
- Physical return rate: matching returned units divided by matching sold units; do not substitute a reversed-quantity metric without checking its definition.
Keep the original order, variant and return identifiers when exporting data so you can reconcile the numerator and denominator.
Filtering Reports for SKU-Level Data
Use the current report’s available product-variant or SKU dimensions, or reconcile exports when it lacks the needed fields. Sort only after checking the measure and its denominator. A high rate based on very few sales is not comparable to a stable estimate from many orders.
A calendar-period report may record a sale on its order date and a later reversal on its processing date. That is different from following returns from one sales cohort. Use Shopify’s report discrepancy guidance to reconcile dates, and use the same cohort and return-status definition across variants.
Do not assume Shopify has no return-reason data: check the current fields and the records available to your store. Check update timing for the particular report rather than applying an unsupported 24–48-hour delay to every report.
Automating SKU Return Tracking with Forthroute
Forthroute provides a branded Shopify return portal. Carrier-label availability, policy settings and the merchant’s refund action remain separate parts of the workflow.
How Forthroute Automates Returns
Forthroute collects return requests through a branded Shopify portal. Configure the policy and shipping options, then test the request and resolution workflow; this review does not establish a five-minute setup time.
Customers identify their order, select return items and give a reason. Available outcomes and labels depend on policy, account settings, inventory and carrier service. Refund remains the default portal resolution, and the merchant issues any refund. Printerless QR labels are available only for supported services, such as eligible UK Evri ParcelShop returns.
Keep software status separate from warehouse work. A receiving integration needs configuration and a matching return record; inspection and the decision to restock remain operational steps. A webhook or carrier scan alone is not proof of receipt, condition or accurate sellable inventory.
Collecting Return Reasons for Each SKU
Forthroute records reasons supplied with return requests and presents return and product patterns. Review those reports alongside order quantities and inspections; reported reasons are a starting point for investigation.
Test approval rules against your actual policy and exceptions. Forthroute’s request checks and merchant review do not establish that every high-value or final-sale request is automatically rejected. Product-level return counts do not by themselves provide the original sales-cohort denominator needed for a physical SKU return rate.
Using SKU Return Data to Improve Your Business
Use return data to select questions for investigation, then compare the evidence before changing a product or purchasing decision.
Finding High-Return SKUs
Build a variant-level table with matching sold and physically returned units, the return-status definition and a mature original-order cohort. Review both the count and the rate before prioritizing products.
For an illustration, 7 returned units from 20 sold give 35%, while 30 from 200 give 15%. These samples differ substantially in size. Inspect the reasons, item condition and cohort maturity before concluding that the first variant has a persistent quality issue.
Lowering Return Rates Through Product Changes
Once you've identified high-return SKUs and the reasons behind the returns, take steps to address the issues. For example:
- If repeated sizing complaints are confirmed by measurements, correct the size chart and product guidance. Do not automatically tell everyone to size up from a complaint count alone.
- For "not as advertised" returns, enhance your product pages with high-quality images taken from multiple angles, videos showing the product in action, and user-generated photos or reviews.
- If defects recur, inspect the affected units and batches and discuss documented findings with the supplier. A reported reason alone does not establish who caused the problem.
After a change, compare sufficiently mature cohorts with similar products and sales conditions. A lower subsequent rate is useful evidence to examine, not proof that the change alone caused it.
Making Better Inventory Decisions
For confirmed quality problems, review replenishment with the inspection findings. Balance demand, margin, supplier constraints and return costs; low returns or a high exchange share alone do not establish product-market fit.
Track the same physical-return definition over time, alongside sold-unit counts and reported reasons. Check whether a vendor pattern remains after accounting for product mix, shipment damage and cohort maturity before changing suppliers.
Conclusion
SKU return analysis can identify where to investigate sizing, descriptions, product condition or fulfillment. Its usefulness depends on matching records and consistent definitions.
Use your own measured rates. This guide does not establish that 30% of all ecommerce transactions are returned, and product categories and return definitions differ.
A portal can collect requests and reasons and help apply configured rules. It does not eliminate receiving, inspection or the merchant’s refund decision. Measure any reduction in manual work in your own operation.
An exchange can retain sales value, but replacement shipping, incentives and handling affect margin. A smooth process does not guarantee a repeat purchase; measure retention and service outcomes without treating an unsourced 92% figure as your forecast.
Forthroute has no software subscription or monthly return limit. Optional platform prepaid labels cost carrier cost converted to USD plus a 1% handling markup, with processing adjustments when included in the approved billing agreement; the total is rounded up to a US$0.10 increment. Carrier support and account settings determine available label services.
Start with a reconciled cohort and a specific product question, record the intervention and compare later outcomes. Improvement is not guaranteed.
FAQs
How can I lower return rates for specific SKUs in my Shopify store?
Start with sold and physically returned units for matching, mature order cohorts. Compare rates with sample sizes, reported reasons and inspection findings before deciding what is wrong with a SKU.
Where evidence supports a problem, test a more accurate description, sizing guidance or quality-control change. Review later cohorts and relevant costs rather than assuming a portal or exchange option caused an improvement.
How can analyzing SKU-level return data help improve product quality?
Repeated return reasons and inspection results can identify a product or batch worth investigating. Check the volume and whether the records reflect physical goods, refunds without returns or other order changes.
Use those findings alongside demand, margin and supplier evidence. Return data alone does not establish a defect, its cause or which supplier to choose.
How does Forthroute simplify return tracking for Shopify merchants?
Forthroute collects return requests and reported reasons and shows return and product patterns. It also tracks the return shipment. A dashboard count is not automatically a physical SKU return rate without a matching sold-unit denominator.
Keep receiving, inspection, refund completion and sellable-stock decisions distinct, and confirm any integration used to update those records.
Returns Management in 2026: The New Landscape
In 2026, the useful task remains linking a return to the correct order and variant. This guide does not provide an industry study showing a universal adoption shift or a mandatory real-time reporting standard.
Review the current Shopify field definitions before reusing an older query. A reversal metric can include changes where no physical goods are returned.
For multichannel analysis, document channel identifiers, date rules and missing records before comparing rates. A combined dashboard is useful only when those differences are reconciled.
If you use return findings in demand planning, distinguish inspection-confirmed quality issues from reported reasons and sales reversals. Test any proposed integration and purchasing adjustment against your own records.
Run Shopify returns in a branded portal you control — Forthroute, no subscription or monthly return limit.
About the Author
Hylke Reitsma is founder of Forthsuite and a supply chain specialist with 8+ years of hands-on experience at Shell, Verisure, and Stryker. He holds an MSc in Supply Chain Management from the University of Groningen and writes practical guides to help e-commerce teams run leaner, faster supply chains. Selected by Replit as 1 of 20 founders for the inaugural Race to Revenue Cohort #1 (2026) and certified as a Replit Platform Builder.
LinkedIn