Read Product Returns Analytics

Interpret return rates, reasons, trends, and product impact with matching and date context.

Before you begin

Confirm the active organization, date range, product selection, and the completeness of Orders and Returns data. Resolve obvious unmatched SKUs and orders before relying on product comparisons. Know whether the question concerns return volume, return rate, reasons, refunds, or operational stage.

How it works

Returns analytics combines return records with product and order context to show supported product-level patterns. Counts describe recorded events, while rates require an appropriate sales or order denominator. Reason and status distributions depend on the organization’s configured values and the quality of historical classification.

Step-by-step

Open the product or Returns analytics view in the correct organization.
Select the date range that matches the decision you are investigating.
Review total orders or sold units alongside return counts when a rate is displayed.
Compare products by stable SKU and inspect parent-child grouping.
Break results down by configured return reason, status, or stage when available.
Look for changes over time rather than relying on one isolated total.
Open underlying return records for products with unusual values.
Check order, ticket, SKU, and refund matches behind the result.
Record the operational question and evidence before changing product or return processes.
Recheck the same view after data-quality corrections or a complete reporting period.

Check your result

You can explain the date range, numerator, denominator, grouping, and source records behind the conclusion. Products with high counts caused by high sales volume are not automatically confused with products that have a high return rate.

Common problems

The rate seems impossible: inspect duplicate returns, missing order denominators, date boundaries, and parent-child aggregation.

Many reasons are blank: historical records may predate the current required classification or import mapping.

A product is absent: confirm SKU matching and whether both order and return evidence exist in the selected range.

Refund totals differ from Returns: payment timing, partial refunds, and external processing can use different states and dates.

Permissions and data notes

Analytics inherits organization and module access. Results are operational evidence, not a substitute for payment-provider or accounting records. Small samples can produce unstable rates, so always review counts and underlying records before making a product decision.