> For the complete documentation index, see [llms.txt](https://help.daasity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.daasity.com/core-concepts/metrics/sales-and-profit/dollar-sales.md).

# Dollar Sales

**Description:** Total retail sales value of a product. Represents the gross revenue from units sold (at retail prices).

**Calculation:**

```sql
SUM(sales_dollars) AS dollar_sales
```

**Why It Matters:** Fundamental measure of revenue scale and market performance.

**Metric Type:** Result

**Essence:** Lagging

**Frequency:** Weekly / Monthly / Rolling 52

**Units:** Dollars ($)

**Suggested Breakdowns:** Channel, Product, Retailer, Region, Market

**Questions Answered:**

* How much did we sell this week/month/year?
* Which channels/products/retailers are driving sales?

**Potential Causes of Worsening:** Lower demand, distribution loss, increased competition, pricing shifts.

**Tactics to Improve:**

* Expand distribution
* Optimize promotions
* Improve pricing strategy

**Related Metrics:**

* Unit Sales
* Average Price
* % ACV
* Velocity

**Related Explores:**

* Retail Sales Performance
* Omnichannel Sales Overview

**Related Sources:**

* URS.SALES\_REPORT
* URMS.SALES\_REPORT


---

# 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://help.daasity.com/core-concepts/metrics/sales-and-profit/dollar-sales.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.