> For the complete documentation index, see [llms.txt](https://docs.flowlity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowlity.com/how-tos/create-forecast-events.md).

# Create and apply forecast events

Forecast events can be created and edited in several places: from the Settings page for bulk management, or directly from the Demand product detail view for quick, contextual adjustments. This guide covers all the ways to work with events.

### Option A — Create from Settings

Go to **Settings >** [**Forecast events**](/settings/forecast-events.md) and click **Create**. This is the best approach when you want to create an event that spans many products or when you are managing events in bulk.

* **Name** — A descriptive name (e.g. "Summer sale 2025").
* **Description** — Optional details about the event.
* **Start date / End date** — The period during which demand will be affected.
* **Impact** — The expected change in demand, expressed as a **percentage** (e.g. +30 %) or in **units**.
* **Products** — Select individual products or use tags.
* **Customers** — Optionally scope the event to specific customers.

You can also link events from the product side: go to **Settings >** [**Products**](/settings/products.md), open a product, and use the **Events** tab to associate existing events.

### Option B — Create from the Demand data table

Open the [Demand](/modules/demand.md) module, click on a product (or select multiple products to view their aggregation), and scroll to the **Forecast events** row in the data table below the chart.

Click the **+** button in any period cell to open the **Add forecast event** dialog. It has two tabs:

* **Create new** — Build an event from scratch. Fill in the name, description, start/end date, impact on forecast (% or units), products (pre-filled with the current product or aggregation), and customer scope.
* **Select from existing** — Browse and search existing events by name. Each event shows its date range, impact, and customer count. Selecting one links it to the current product(s).

Click **Create** or **Save** to confirm. The event immediately appears in the Forecast events row and on the chart.

### Option C — Add a past demand adjustment from the chart

In the product detail view, click the **+** icon on the chart timeline to add a **past demand adjustment**. This lets you correct historical demand for a specific period on the current product.

* **Name** — A descriptive name for the adjustment.
* **Description** — Optional details.
* **Start date / End date** — The historical period to adjust.
* **Past demand value** — The corrected demand value (in units).

Past demand adjustments modify the cleaned demand history, which in turn improves future forecast accuracy.

### Edit an existing event

You can edit events from two places in the Demand product detail view:

* **From the data table** — In the Forecast events row, click on an existing event chip (showing the event name and impact). This opens the **Edit forecast event** dialog where you can modify all fields or **Delete** the event entirely.
* **From the chart** — Click on an event displayed on the chart (shown as vertical markers with the event name and impact). This opens the same edit dialog.

Both methods work for single products and for aggregations of multiple products. When editing an event linked to multiple products, changes apply to all linked products.

### Verify the impact

After creating or editing an event:

* Toggle the **Events** series on the chart to see the event period highlighted.
* Check the **Forecast events** row in the data table to confirm the adjustment is applied during the correct periods.
* Review the **Final forecast** to ensure it reflects the event's impact.

{% hint style="info" %}
Create events ahead of time — the earlier you model known demand changes, the better Flowlity can plan supply to meet them.
{% endhint %}

### Related pages

* [Forecast events and demand adjustments](/concepts/forecast-events.md) — Events lifecycle and how they interact with anomaly detection.
* [Demand forecasting explained](/concepts/demand-forecasting.md) — How the AI forecast works.
* [Forecast events](/settings/forecast-events.md) — Event management settings page.
* [Products](/settings/products.md) — Link events from the product side.
* [Demand](/modules/demand.md) — Where to create, edit, and verify event impact.


---

# 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:

```
GET https://docs.flowlity.com/how-tos/create-forecast-events.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.