# Building Reports With Mo

{% hint style="info" %}
**Quick Answer:** Open Mo, describe the report you need in plain language, and Mo builds it from your live Moselle data. Refine conversationally, then export to CSV when it's ready.
{% endhint %}

## What is Reporting with Mo?

**Reporting with Mo** lets you create any view of your business data through a natural language conversation. Instead of navigating preset dashboards, you describe what you need — and Mo surfaces a structured, actionable output tailored to your channels, SKUs, and business context.

### What You Can Build

* **Custom data views** — Any slice of your sales, inventory, forecast, or catalog data, grouped and filtered however you need
* **Charts and dashboards** — Inline bar charts, line graphs, stat cards, and full dashboard overviews generated directly in the conversation
* **Weekly Sales reports** — Sell-in units and revenue by SKU and channel, compared week-over-week and against the active forecast
* **Inventory Coverage reports** — Weeks of supply remaining per SKU based on current stock and forecasted demand
* **Forecast Variance reports** — The gap between Mo's forecast and actual sell-in or sell-through, surfacing where the plan was over or under
* **Weeks of Supply (WOS) reports** — See how long your inventory will last by SKU, channel, or warehouse
* **Sales Velocity reports** — Measure how fast products are selling and spot trends early
* **At-risk SKU lists** — Surface items approaching stockout before it's too late
* **Overstock summaries** — Identify excess inventory tying up cash or warehouse space

### Key Benefits

* **Your data, your way:** Get the exact slice of data you need without configuring report builders
* **Live data:** Reports pull from your current Moselle data, so results are always up to date
* **Conversational refinement:** Adjust filters, groupings, or columns by continuing the conversation
* **Export-ready:** Download the final table as a CSV when it's ready

## Guides

{% content-ref url="/pages/SsegIvFSHIYfzmHQdcXS" %}
[Mo Standard Reports](/analytics/reporting/mo-reports/mo-standard-reports.md)
{% endcontent-ref %}

{% content-ref url="/pages/Dlc8GAJGV7FQH8Q9j9gA" %}
[Mo Custom Reports](/analytics/reporting/mo-reports/mo-custom-reports.md)
{% endcontent-ref %}

{% content-ref url="/pages/bhnbOdyzHJU16Tc1oHKc" %}
[Upload Your Files to Mo](/mo/tips/upload-your-files-to-mo.md)
{% endcontent-ref %}

{% content-ref url="/pages/DAsnRIRTbbjM6bgR0RLM" %}
[Save Your Favourite Prompts](/mo/tips/save-favourite-prompts.md)
{% endcontent-ref %}

## Tips for Better Report Prompts

Getting the most out of Mo's reporting comes down to being specific. Here are the patterns that consistently produce better first outputs:

**Always specify the time period.** Mo defaults to a reasonable window but explicitly stating the period removes ambiguity.

* Examples: `"last 7 days"`, `"last 4 weeks"`, `"MTD"`, `"Q1 2026"`

**Define channel scope upfront.** Blending channels without intention produces averages that can mislead.

* Examples: `"all channels"`, `"DTC only"`, `"Sephora US only"`, `"excluding Amazon"`

**Specify the output format.** Telling Mo how you want the data presented gets you to a usable result faster.

* Examples: `"ranked by units"`, `"as a table"`, `"highlight gaps"`, `"show totals"`

**Export to Excel.** Add `"export this as an Excel file"` to any prompt and Mo will generate a downloadable `.xlsx` file.

**Too much data?** Narrow with: `"top 10 SKUs by..."` or `"only show SKUs where coverage is below 8 weeks"`

**Too little data?** Broaden with: `"include all SKUs, even those with zero sales"`

**Combine reports.** Ask Mo to pull multiple data types in a single output:

* `"Show me weekly sales and inventory coverage side by side for all active SKUs"`


---

# Agent Instructions: 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:

```
GET https://learn.moselle.io/mo/key-capabilities/building-reports-with-mo.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.