> 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/data-models/data-explores/digital-analytics-unified/ecommerce-orders-and-revenue-by-order-date-explore.md).

# Ecommerce Orders & Revenue (by Order Date) Explore

Your primary Explore for order and revenue analysis across all sales channels, **formerly known as Order & Order Line Revenue**. Contains order-line data with attribution, customer details, and SKU attributes for most reporting needs. Calculates refunds as of order date (except Shopify which uses return date). Filter by sales channels using Business Unit dimensions and SKU Hierarchy from your BSD sheet.

{% hint style="success" %}
The Majority of your reporting needs can be Built Using The Order and Order Line Revenue Explore. Daasity Recommends starting with this Explore when building Reports or [The Transactional Sales Report Explore](/core-concepts/data-models/data-explores/digital-analytics-unified/transactional-sales-report-explore.md).
{% endhint %}

{% hint style="success" %}
The Order and Order Line Revenue Explore will calculate Sales Metrics for **Refunds as of the Order Date** (NOTE: Shopify Sales are calculated as of the Return Date) **For a true 1:1 comparison with Shopify Logic use the Transactional Sales Report Explore.**
{% endhint %}

{% hint style="success" %}
You can filter by Sales Channel (i.e. Shopify and Amazon Seller Central stores by using the Business Unit Dimensions (see below)
{% endhint %}

<figure><img src="/files/tjehuBNuFk9D4voOVm6x" alt=""><figcaption><p>Sales Channels and Store Type Dimensions</p></figcaption></figure>

{% hint style="success" %}
You can use the SKU Hierarchy Dimensions from your [SKU Hierarchy tab](/core-concepts/custom-data-and-enrichment/custom-attributes/products-and-hierarchy/sku-hierarchy.md) in your BSD Sheet.
{% endhint %}

<figure><img src="/files/iY6lJnXpO7i8YA6NyrGJ" alt=""><figcaption><p>SKU Hierarchy</p></figcaption></figure>

<figure><img src="/files/Wx1hLtflJjmuewFz9lAJ" alt=""><figcaption><p>Order Attribution Data</p></figcaption></figure>

<figure><img src="/files/9ow3oiExg6jWziglmnCV" alt=""><figcaption><p>Key Measures</p></figcaption></figure>


---

# 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/data-models/data-explores/digital-analytics-unified/ecommerce-orders-and-revenue-by-order-date-explore.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.