> 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/forecast.md).

# Forecast

See how many units of each product your active subscriptions will deliver in the coming weeks, months and year, to plan stock and fulfillment.

The **Forecast** tab shows how many units of each product variant your active subscriptions will deliver in upcoming periods. Use it to order stock, plan packing and talk to suppliers ahead of time.

The numbers come from your real subscriptions: their products and quantities, how often they deliver, and their next order dates.

## View the forecast

{% stepper %}
{% step %}

### Open the Forecast tab

In the app menu, click **Analytics**, then click the **Forecast** tab. The **Product Delivery Forecasting** table opens.

If you have no active subscriptions yet, you see **Welcome to Forecast** instead.

![The Product Delivery Forecasting table with the date range button and search field highlighted](https://3752025337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F479XnzvtVA5dDE3Rt2Uh%2Fuploads%2FFgjM6Swk9aP0UU3t1iiB%2Fanalytics-forecast-table.png?alt=media)
{% endstep %}

{% step %}

### Read the table

Each row is one product variant. The numbers are units to deliver.

| Column                | Period                                                                   |
| --------------------- | ------------------------------------------------------------------------ |
| **Product**           | The product and variant name.                                            |
| **Custom Date Range** | The period you pick with the date range button. See the next step.       |
| **Next Week**         | Monday to Sunday of next week.                                           |
| **Next Month**        | The whole of next calendar month.                                        |
| **Next 3 Months**     | The next three calendar months, starting on the first day of next month. |
| **Next year**         | January 1 to December 31 of next year.                                   |

The fixed periods start at the next week, month or year, not today. Deliveries due later this week or this month appear only in **Custom Date Range**.
{% endstep %}

{% step %}

### Pick a custom period

Click the date range button above the table. Choose a preset or type the dates, then click **Apply**. The **Custom Date Range** column updates.

| Preset                               | Period                                                       |
| ------------------------------------ | ------------------------------------------------------------ |
| **Today**                            | Today.                                                       |
| **Tomorrow**                         | Tomorrow.                                                    |
| **Next 6 months**                    | From the first day of next month, for six months.            |
| **Next 2 years** to **Next 5 years** | From January 1 of next year, for the number of years chosen. |

Each preset shows its exact dates in the list. You cannot pick dates before today.

![The Forecast date range picker with the presets and their dates](https://3752025337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F479XnzvtVA5dDE3Rt2Uh%2Fuploads%2Fs79hlrl0nMEzChwlnTqC%2Fanalytics-forecast-date-range.png?alt=media)
{% endstep %}

{% step %}

### Find a product

Type in **Search by product name**. The table shows the variants of matching products. Click the **X** in the field to clear the search and the custom period.
{% endstep %}
{% endstepper %}

## How units are counted

For each active subscription that includes the variant, the app counts the deliveries that fall in the period and multiplies them by the quantity on the subscription. Then it adds up all subscriptions.

* **Delivery frequency, not billing frequency.** A prepaid subscription billed every 3 months that delivers every month counts one delivery per month.
* **Skipped orders** are left out.
* **Subscriptions with an end** stop counting after their last order.
* **Paused, cancelled, failed and expired** subscriptions are not counted.

### Example

A customer subscribes to 2 bags of coffee every 2 weeks, with the next order on the 5th of next month. The deliveries next month fall on the 5th and the 19th, so **Next Month** shows 2 deliveries × 2 bags = 4 units for that variant, plus the units from all other subscriptions with the same variant.

{% hint style="warning" %}
The table shows up to 10 product variants at a time. If you sell more subscription products, search for a product by name to see its variants.
{% endhint %}

## Good to know

* The forecast uses each subscription as it is today. Customers who change products, quantities or dates later change the forecast too.
* The forecast does not know about failed charges. A renewal that fails still counts as a delivery.
* The page date range, **Compare to** and **Auto-refresh** do not apply to this tab.
* For the orders scheduled for one subscription, open it and check [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/forecast.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.
