# Sales Velocity Report

{% hint style="info" %}
**Quick Answer:** A sales velocity report measures how fast your products are selling over a given time period — typically expressed as units sold per week. It is one of the most important metrics in inventory planning. In Moselle, Mo can build one for you in under 5 minutes from your live data.
{% endhint %}

## What is Sales Velocity?

**Sales velocity** is the rate at which a product sells over a defined time period. Unlike total sales volume (which tells you how much sold), velocity tells you **how fast** something is moving.

A SKU that sold 500 units over 12 weeks has a very different velocity profile than one that sold 500 units in 4 weeks — and they require very different planning responses.

### Why Sales Velocity Matters

* **Replenishment timing:** Velocity determines when to reorder. Rising velocity means you need stock sooner; declining velocity means you can delay
* **Forecast validation:** Comparing actual velocity against forecasted demand reveals where your plan is drifting
* **Promotional decisions:** Declining velocity is often the earliest signal that a product needs a promotional push or pricing adjustment
* **Capital efficiency:** Velocity helps you identify where inventory is moving too slowly and tying up cash

## What Makes a Great Sales Velocity Report?

A great velocity report does not just tell you what sold — it tells you the **rate** at which things are selling. The best ones are:

* **Time-period specific:** Velocity over the last 4, 8, or 12 weeks tells a very different story than a full-year average
* **Channel-separated:** DTC velocity and wholesale velocity behave differently and should never be blended without intention
* **Trend-aware:** Is velocity accelerating, declining, or flat? The direction matters as much as the number
* **Comparable:** The most useful velocity reports let you benchmark SKUs against each other or against prior periods
* **Visual:** Charts and graphs make trends and outliers immediately obvious at a glance

### Key Metrics to Include

| Metric                    | What It Tells You                                        |
| ------------------------- | -------------------------------------------------------- |
| Average weekly units sold | The core velocity number — how fast the SKU is moving    |
| Trend direction           | Whether velocity is accelerating, stable, or declining   |
| Channel breakdown         | How velocity differs across DTC, wholesale, Amazon, etc. |
| Forecast variance         | Gap between actual velocity and forecasted demand        |
| Sell-through rate         | What percentage of available inventory has sold          |

## Before You Start: Make Sure Your Data Is Clean

A velocity report is only as reliable as the sales data feeding into it. Before pulling the report, confirm:

* [ ] **Sales history is synced and complete.** Check that your connected sales channels are up to date with no gaps in order history
* [ ] **Returns and cancellations are handled correctly.** Net sales — not gross — should be the basis for velocity
* [ ] **You know your time window.** Velocity over 4 weeks vs. 12 weeks can look very different, especially for seasonal products
* [ ] **New SKUs are flagged.** Products with less than 4 to 8 weeks of sales history will have statistically unreliable velocity numbers

## How to Build a Sales Velocity Report with Mo

**Time Required:** 5 minutes **Difficulty:** Beginner

{% stepper %}
{% step %}

### Open Mo and Set Your Context

Click **Mo** in the left sidebar to open the chat page. Be specific about the time window and channel scope from the start. A strong prompt looks like:

> "Can you pull a sales velocity report for all active DTC SKUs over the last 8 weeks? I want to see average weekly units sold and flag anything with declining velocity."

You can also scope the request to a product line, collection, or specific SKU set.
{% endstep %}

{% step %}

### Review the Output

Mo will return a SKU-level breakdown that typically includes:

* Total units sold in the selected period
* Average weekly velocity (units per week)
* Trend indicator — is velocity going up, flat, or down?
* Channel breakdown if requested

Start with the trend column. Rising velocity SKUs may need a reorder conversation. Declining velocity SKUs may need a promotional push or a forecast adjustment.
{% endstep %}

{% step %}

### Visualize the Data

Ask Mo to present your velocity data as charts and graphs — no spreadsheet wrangling required.

> "Can you show me a graph of weekly sales velocity by SKU over the last 8 weeks?"

> "Show me a bar chart comparing velocity this month vs. last month across all active SKUs."

Seeing the data visually often surfaces patterns that are easy to miss in a table — like a SKU that has been quietly losing velocity for six consecutive weeks.
{% endstep %}

{% step %}

### Compare to Your Forecast

Hold your velocity numbers up against your active forecast. Ask Mo:

> "Which SKUs have actual velocity that is more than 20% above or below their forecasted demand?"

Significant gaps between actual velocity and forecasted velocity are a signal to update your forecast — which in turn affects your WOS, reorder points, and purchasing decisions.
{% endstep %}

{% step %}

### Slice, Filter, and Export

Mo can cut this report multiple ways. Common follow-up asks include:

> "Show me the top 10 SKUs by velocity over the last 4 weeks"

> "Which SKUs have had declining velocity for 3 or more consecutive weeks?"

> "Break this down by sales channel"

Once you have the view you need, export the report to share with your team or bring into your weekly ops review.

{% hint style="success" %}
**Tip:** Ask Mo to generate a visual before any stakeholder meeting. Charts communicate trends far more effectively than raw tables.
{% endhint %}
{% endstep %}
{% endstepper %}

## How to Read Your Sales Velocity Report

| Velocity Trend              | What It Means                        | Recommended Action                            |
| --------------------------- | ------------------------------------ | --------------------------------------------- |
| Accelerating                | Demand is growing                    | Review reorder points, update forecast upward |
| Flat / Stable               | Predictable, consistent sell-through | Maintain current plan                         |
| Declining (mild)            | Early softness                       | Review marketing activity, consider promotion |
| Declining (significant)     | Demand is eroding                    | Adjust forecast down, pause future buys       |
| New SKU — insufficient data | Too early to trend                   | Flag separately, reassess in 4 to 8 weeks     |

## Best Practices for Sales Velocity Reports

**Always use a rolling window, not a fixed date range.** "Last 8 weeks" is more useful than "January 1 to February 28" because it keeps your numbers current and comparable week over week.

**Segment new SKUs from established ones.** Velocity on a product live for 3 weeks is not comparable to one live for 2 years. Tag new SKUs separately so you are not drawing false comparisons.

**Weight your velocity for seasonality.** If your brand has strong seasonal peaks, velocity pulled during a peak period will look inflated compared to a quiet period.

**Pair velocity with sell-through rate.** Velocity tells you how fast something is selling in absolute terms. Sell-through rate tells you what percentage of available inventory has sold. Together, they give a complete picture of product performance.

**Use velocity to validate your forecast, not replace it.** Velocity is backward-looking. Your forecast is forward-looking. The magic is in comparing the two.

## WOS and Sales Velocity: Better Together

Sales Velocity and WOS reports are most powerful when used side by side. Velocity tells you the rate of sell-through; WOS tells you how long your supply will last at that rate.

* **High velocity + low WOS:** Urgent reorder — this SKU is flying and you are about to run out
* **Low velocity + high WOS:** Excess risk — demand has slowed but inventory is piling up
* **Stable velocity + healthy WOS:** You are in good shape — no action needed
* **Accelerating velocity + healthy WOS:** Watch closely — you may need to pull a PO forward

Building both reports into your weekly routine gives you a complete, real-time pulse on your inventory health.

## Frequently Asked Questions

<details>

<summary>How do I know if my velocity numbers are reliable?</summary>

Velocity becomes statistically meaningful after 4 to 8 weeks of consistent sales history. For newer SKUs, flag them separately and revisit once enough data has accumulated.

</details>

<details>

<summary>Can I separate velocity by sales channel?</summary>

Yes. Specify the channel in your prompt (e.g., "DTC only" or "wholesale only") or ask Mo to break the report down by channel after pulling the initial view.

</details>

<details>

<summary>What is the difference between sales velocity and sell-through rate?</summary>

Velocity measures absolute units sold per week. Sell-through rate measures what percentage of available inventory has sold. Both metrics together give you a complete picture of product performance.

</details>

<details>

<summary>How often should I run a sales velocity report?</summary>

Weekly is the recommended cadence for active inventory management. Running it alongside your WOS report in a regular ops review gives you the most complete view of inventory health.

</details>

## Related Guides

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

{% content-ref url="/pages/ZiMAO4xUpdTQI2yoZWu5" %}
[Weeks of Supply (WOS) Report](/analytics/reporting/mo-reports/mo-standard-reports/wos-report.md)
{% endcontent-ref %}

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

{% content-ref url="/pages/c4dFnjgxugHPw5eYNdWG" %}
[Sales Reports](/analytics/reporting/moselle-reports/sales-reports.md)
{% endcontent-ref %}


---

# 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/analytics/reporting/mo-reports/mo-standard-reports/sales-velocity-report.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.