> For the complete documentation index, see [llms.txt](https://learn.moselle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.moselle.io/analytics/reporting/moselle-reports/sales-reports.md).

# Sales Reports

Sales reports provide detailed sales analysis across channels, product lines, and time periods. Track units sold, sell-through rates, and performance trends to inform inventory and production decisions.

{% embed url="<https://www.youtube.com/watch?v=3QeDBC6o9-g>" %}
Learn how to navigate Sales Reports, apply filters, customize columns, and adjust your table view
{% endembed %}

{% hint style="info" %}
**Quick Answer:** To view sales reports in Moselle, go to **Reports** and select **Monthly Sales** or **Weekly Sales**. Use **Filters** and **Columns** to customize your view, then export as CSV or XLSX. Takes about 1–2 minutes to set up.
{% endhint %}

### Access Sales Reports

Select **Reports** from the menu and choose:

* **Monthly Sales** - Sales data by month
* **Weekly Sales** - Sales data by week

### Graphs

Three graphs display sales performance:

* Sales by Channel
* Sales by Product Lines
* Sales by Sub Line

**Date Filter:** Use the dropdown above the graphs to select a date range. Choose from preset options (Next 30 Days, Next 3 Months) or select custom start and end dates from the calendar. Click **Apply** to update all graphs and the table below.

### Sales Table

The table organizes sales data by Channel, Product Line, SKU, and time period (months or weeks).

**Drill Down:** Click the chevron arrow beside any Channel to expand and view Product Lines, then drill further into SKUs. Each time column shows Units Sold (sum of units sold for that period).

### Customize Columns

Click **Columns** on the far right of the table to customize your view.

#### Column Selection

Toggle columns on or off:

| Column       | Description               |
| ------------ | ------------------------- |
| Archived     | Show archived products    |
| Category     | Product category          |
| Channel      | Sales channel             |
| Gross Sales  | Total revenue             |
| Month        | Time period               |
| Name         | Product name              |
| % of Total   | Percentage of total sales |
| Product Line | Product line grouping     |
| Product Type | Type of product           |
| SKU          | Product SKU               |
| Units Sold   | Number of units sold      |

#### Row Groups

Drag and drop columns to reorder table grouping. Click the **X** button to remove a column from grouping.

#### Values

Displays: Sum of Units Sold

#### Column Labels

Displays: By Month (or By Week for weekly reports)

### Filter Table

Click **Filters** on the far right to refine table data.

Filter by:

* Archived
* Category
* Channel
* Month
* Name
* Product Line
* Product Type
* SKU

Click the chevron arrow beside any filter option to expand and select specific values. Use the search bar above each list to quickly find items (e.g., search for specific SKUs).

### Copy, Paste & Export

**Copy to Spreadsheet:** Select a range of cells and copy them directly to Excel or Google Sheets.

**Export:** Right-click on the table to export as CSV or XLSX file.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.moselle.io/analytics/reporting/moselle-reports/sales-reports.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.