> For the complete documentation index, see [llms.txt](https://subscriptions-docs.tech-arms.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://subscriptions-docs.tech-arms.io/features/analytics/revenue.md).

# Revenue

See how much your subscription orders earn, split into first and renewal orders, and estimate the revenue from upcoming renewals.

The **Revenue** tab shows how much money your subscriptions bring in. It splits revenue into first orders and renewal orders, shows average order value and revenue per customer, and estimates what upcoming renewals will earn.

In the app menu, click **Analytics**, then click the **Revenue** tab.

![The Revenue tab with its six cards](https://3752025337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F479XnzvtVA5dDE3Rt2Uh%2Fuploads%2FVl0LFuBtgK53oJ9d7BrC%2Fanalytics-revenue-cards.png?alt=media)

The tab uses the date range and **Compare to** period at the top of the page. To learn how to change them and which orders are counted, see [Analytics](https://subscriptions-docs.tech-arms.io/features/analytics.md).

## How revenue is counted

* Revenue comes from subscription orders only: the first order that started each subscription and every renewal order that was charged successfully.
* Each order counts with its full total in your store's currency: products after discounts, plus shipping and taxes, plus any one-time items bought in the same checkout.
* The total is recorded when the order is placed. Refunds, cancellations or edits made later in Shopify do not change it.

## Cards

| Card                             | What it shows                                                                                             | Comparison |
| -------------------------------- | --------------------------------------------------------------------------------------------------------- | ---------- |
| **Total order revenue**          | The total of all subscription orders placed in the period, first and renewal orders together.             | Yes        |
| **First time order revenue**     | The total of the first orders placed in the period, the checkouts where customers started a subscription. | Yes        |
| **Recurring order revenue**      | The total of the renewal orders placed in the period.                                                     | Yes        |
| **Average order value**          | **Total order revenue** divided by the number of first and renewal orders placed in the period.           | Yes        |
| **Average revenue per customer** | **Total order revenue** divided by the number of different customers who placed those orders.             | Yes        |
| **Next Day estimated revenue**   | What your active subscriptions are expected to charge in the coming days. See below.                      | No         |

### Example: Average order value and revenue per customer

In the last 30 days you had 10 first orders worth 400.00 and 20 renewal orders worth 800.00, from 15 different customers.

* **Total order revenue**: 1,200.00
* **Average order value**: 1,200.00 ÷ 30 orders = 40.00
* **Average revenue per customer**: 1,200.00 ÷ 15 customers = 80.00

## Estimate upcoming revenue

The estimated revenue card does not use the date range at the top of the page. It always looks forward from now.

{% stepper %}
{% step %}

### Choose how far ahead to look

On the estimated revenue card, open the menu in the top-right corner and choose **Next Day**, **Next 7 Days**, **Next 30 Days**, **Next 90 Days** or **Next 360 Days**. The card title changes to match, for example **Next 30 Days estimated revenue**.
{% endstep %}

{% step %}

### Read the estimate

The app takes every **active** subscription whose next order date falls between now and the end of the chosen period. For each one, it multiplies the subscription's order amount by the number of orders expected in that period, based on its billing frequency.

The order amount is the subscription's current product prices after discounts, plus its delivery price. Taxes are not included.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
The estimate is a guide, not a promise. It does not account for:

* paused subscriptions,
* orders customers have skipped,
* subscriptions that end after a set number of orders,
* price changes that apply only to later orders,
* charges that may fail.

To count longer periods, it treats a month as 30 days and a year as 360 days.
{% endhint %}

## Charts

![The History and estimated revenue and Order amount per Day charts](https://3752025337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F479XnzvtVA5dDE3Rt2Uh%2Fuploads%2FbtofDKVnInJMfM4NnZ4j%2Fanalytics-revenue-charts.png?alt=media)

### History and estimated revenue

Compares what you earned recently with what you can expect soon, at three points: **7 Days**, **30 Days** and **90 Days**.

* **History revenue**: the total of subscription orders placed in the last 7, 30 and 90 days.
* **Estimated revenue**: the estimated revenue for the next 7, 30 and 90 days, calculated as described above.

This chart does not use the date range at the top of the page.

### Order amount per Day

The total of subscription orders placed in each day of the period. Use the menu in the top-right corner to group by **Daily**, **Weekly**, **Monthly** or **Yearly**. The title changes to match, for example **Order amount per Month**.

When a comparison is on, a second line shows the comparison period.

## Good to know

* If you sell in several currencies, order revenue is always shown in your store's currency. The estimated revenue adds up each subscription's amount in the currency the customer pays in, without converting it.
* Estimated revenue covers active subscriptions only. Reactivating paused subscriptions raises it.
* For a product-by-product view of upcoming deliveries, use the [Forecast](https://subscriptions-docs.tech-arms.io/features/analytics/forecast.md) tab. For the orders scheduled for each subscription, see [Upcoming orders](https://subscriptions-docs.tech-arms.io/features/subscriptions/upcoming-orders.md).

*If you need help, feel free to reach out to us via in-app* [***Live chat***](https://go.crisp.chat/chat/embed/?website_id=c4ae10a3-f762-4968-b35a-c931caf62a96)***,*** [***Book a call***](https://calendly.com/ta-subscription-app-support/30min) *or at* [***support@tech-arms.io***](mailto:support@tech-arms.io)***.***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://subscriptions-docs.tech-arms.io/features/analytics/revenue.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
