> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developer.shipbob.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developer.shipbob.com/_mcp/server.

# Analytics & Reports

> Use analytics to identify return trends, product issues, and policy optimization opportunities

The **Analytics** page in the sidebar summarizes your return activity so you can move from reacting to individual returns to fixing the patterns behind them. This guide explains each report and how to act on it.

![ShipBob Returns Analytics](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/ship.docs.buildwithfern.com/c727f7c84420c4b0a9686ea28be37094b9e9d560608d018ea5535b3b7f247751/docs/assets/images/returns-analytics.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260727%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260727T164455Z&X-Amz-Expires=604800&X-Amz-Signature=aee9be4c9111ca09466b68400056391bcabf754c42e7e28d788f73716309cdf5&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

## Choosing a Date Range

At the top of the page, pick the period to analyze: **Last 7 days**, **Last 30 days**, **Last 90 days**, or **All time**. All cards and charts update to the selected range, and key metrics are compared against the previous period so you can see movement.

If you just launched, you may see <em>Your analytics are warming up</em> or <em>No returns yet</em> until enough return data accumulates.

## Key Metrics

Three headline cards sit at the top:

| Metric               | What it tells you                                                                                                                             |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **Retained revenue** | Value you kept instead of refunding — currently through exchanges. The clearest measure of whether your non-refund outcomes are working.      |
| **Return rate**      | The share of orders that resulted in a return over the period. Watch for spikes after new product launches or seasonal peaks.                 |
| **Exchange rate**    | The share of returns resolved as exchanges rather than refunds. A rising exchange rate usually means retained customers and retained revenue. |

## Returns Over Time

The **Returns over time** chart plots **Returns** against **Orders** for the period. Because both lines are on the same chart, you can tell the difference between "returns are up because sales are up" (both rise together) and a genuine problem (returns rising while orders are flat).

## Return Reasons Breakdown

The reasons chart shows which return reasons customers pick most. Use it to:

* **Fix product content** — a dominant "looks different to image on site" or sizing-related reason points at photography or size-chart fixes.
* **Tune your reason list** — if one vague reason (like "Others") dominates, add more specific reasons so the data becomes actionable. Manage reasons in **Settings** — see [Configure Return Policies](/labs/returns/policy).
* **Target flows** — reasons that signal your fault (damaged, wrong item) are good candidates for photo requirements and deduction waivers.

## Top Returned Products

The products chart ranks your most-returned products. A product that appears here repeatedly deserves investigation: a sizing issue, a quality problem with a batch, or a misleading listing. For extreme cases, consider a non-returnable tag, a **Require Approval** flow for that SKU, or blocking specific outcomes — see [Automate Returns with Flows](/labs/returns/flows).

## Turning Insights into Action

Pick one metric to improve per month and tie it to one concrete action; this keeps optimization measurable and manageable.

A simple monthly loop:

1. Check **Return rate** and **Returns over time** for overall direction.
2. Drill into the top reason and top product; fix listings or quality issues at the source.
3. Adjust policy or flows accordingly, and confirm next month that the numbers moved.

## FAQ

#### How often does analytics data update?

Cards and charts refresh for the selected date range and are compared against the previous period. If you are newly launched, some views may stay sparse until enough return activity accumulates.

#### Why am I seeing 'No returns yet' or limited charts?

This usually means your store has not generated enough return events in the selected period. Expand the date range to **All time** and check again.

#### What should I review first each month?

Start with **Return rate** and then investigate the top return reason and top returned product before updating policy or flows.

## Related Guides

* [Managing Returns Day-to-Day](/labs/returns/manage)
* [Exchanges and Upcoming Outcomes](/labs/returns/outcomes)
* [Configure Return Policies](/labs/returns/policy)