# Seasonality: how recurring demand affects forecasting

Seasonality is a demand pattern that recurs around comparable periods, such as a sales peak every spring. Optiply can blend a seasonal forecast with a recent-demand forecast, and the **Yearly seasonality** setting controls how much weight the seasonal forecast gets in that blend.

## What seasonality means, next to trend

Seasonality is a recurring demand pattern. A product can have a seasonal peak every year while its longer-term demand stays level, rises or falls. That longer-term direction is the trend: a sustained change in demand over time. Seasonality repeats around comparable periods. A trend continues beyond that pattern.

## How Optiply uses Yearly seasonality in the forecast

Optiply can combine two forecasts of a product's demand for the same future day: a **recent-demand forecast**, based on more recent demand, and a **seasonal forecast**. The recent-demand forecast can reflect recent demand levels and trends. **Yearly seasonality** is the weight of the seasonal forecast in that blend.

- A higher **Yearly seasonality** gives the seasonal forecast more weight.
- A lower **Yearly seasonality** gives the recent-demand forecast more weight.
- When both forecasts are available, `0` uses only the recent-demand forecast and `1` uses only the seasonal forecast.

Optiply blends the two forecasts day by day. A missing forecast is not a zero. With less than a year of sales history, some forecast days can have no seasonal forecast while later days have one. For each day:

- Seasonal forecast missing: Optiply uses the recent-demand forecast rather than blending it with a missing value.
- Recent-demand forecast missing: Optiply uses the seasonal forecast.
- Both forecasts missing: the forecast for that day is 0.

In each of these cases, the **Yearly seasonality** value itself does not change.

Products with advanced forecasting can use a separate weight instead of **Yearly seasonality**, and other enabled forecasting models can change the final result. Use the **Yearly seasonality** blend to understand a product's forecast, not to predict every product's forecast from this setting alone.

## Example: Yearly seasonality of 0.4 for barbecue covers

This example uses made-up numbers. You sell barbecue covers, and demand for them peaks every spring. For one future day in April, Optiply has both forecasts for the product:

- Recent-demand forecast: **10 units**
- Seasonal forecast: **20 units**
- **Yearly seasonality:** 0.4

With the ordinary blend, and no other forecasting model adjusting the result, the forecast for that day is **14 units**:

1. The seasonal forecast's weight is 0.4, which leaves `1 − 0.4 = 0.6` for the recent-demand forecast.
2. Recent-demand contribution: `0.6 × 10 = 6` units.
3. Seasonal contribution: `0.4 × 20 = 8` units.
4. Blended forecast: `6 + 8 = 14` units.

Now **Yearly seasonality** is 0.8 instead of 0.4. The recent-demand forecast keeps a weight of `1 − 0.8 = 0.2`: `0.2 × 10 + 0.8 × 20 = 2 + 16 = 18` units. The spring peak counts for more, so the forecast for that April day rises from 14 to **18 units**.

In Optiply, open the product's demand forecast to check how the spring peak shows up after you change **Yearly seasonality**.

## Where to find Yearly seasonality in Optiply

**Yearly seasonality** is one value for the selected webshop, not a value per product. Select the webshop in the webshop-name dropdown in the main header. You can search the dropdown. Open **Settings** in the navigation menu, then **Algorithm**, and look for **Yearly seasonality**.

To see what **Yearly seasonality** means for one product, use that product's demand forecast to review the resulting planning picture.

## How to change Yearly seasonality in Optiply

Before you change **Yearly seasonality**:

- You need Settings edit access to change **Yearly seasonality**. Administrator access also counts.
- Review how demand behaved around comparable periods, and whether the history contains promotions, stockouts or missing data.
- Choose a value that fits your assortment rather than treating the highest value as the best forecast.

Steps to change **Yearly seasonality**:

1. In the main header, select the webshop in the webshop-name dropdown. You can search the list.
2. Open **Settings** in the navigation menu, then **Algorithm**.
3. In **Yearly seasonality**, enter a value from `0` to `1` in steps of `0.1`.
4. Select **Save**. To keep the saved value instead, select **Undo changes**.
5. Check that **Yearly seasonality** shows the value you saved.

For the other Algorithm controls and the full configuration workflow, follow the Configure Algorithm settings guide.

### If you cannot save Yearly seasonality

- **This field is required**: enter a value in **Yearly seasonality**.
- **The value must be greater than or equal to 0** or **The value must be less than or equal to 1**: correct the value in **Yearly seasonality**.

With view-only Settings access, the **Yearly seasonality** field is disabled. **Save** becomes available only after a valid change, and stays unavailable while settings load or save and during a short cooldown after a change.

## How Yearly seasonality differs from a percentage increase, a report metric and purchase advice

- **Yearly seasonality and a percentage increase.** **Yearly seasonality** balances two forecasts for the same future day. A value of 0.4 is a weight, not a forecast increase of 40% applied to sales.
- **Yearly seasonality and a report metric.** **Yearly seasonality** is a forecast setting. A report metric called seasonality is not automatically this setting or its formula.
- **Yearly seasonality and purchase advice.** The blended forecast is not a purchase quantity. Stock, incoming deliveries and purchasing conditions still matter. As a result, changing **Yearly seasonality** does not guarantee an immediate order or a particular advised quantity.

## Questions customers ask about seasonality

### Does Optiply look at last year's numbers when items sell faster in the coming season?

Optiply can blend a seasonal forecast with a recent-demand forecast, and the **Yearly seasonality** setting controls how much weight the seasonal forecast gets in that blend. With less than a year of sales history, some forecast days can have no seasonal forecast, and Optiply then uses the recent-demand forecast for those days.

### What is the impact if I change the seasonality?

A higher **Yearly seasonality** gives the seasonal forecast more weight in Optiply's blended forecast, and a lower value gives the recent-demand forecast more weight. For example, with a recent-demand forecast of 10 units and a seasonal forecast of 20 units for one day, raising **Yearly seasonality** from 0.4 to 0.8 raises that day's ordinary blended forecast from 14 to 18 units.

### How can I prevent seasonal proposals in this period?

A lower **Yearly seasonality** gives the seasonal forecast less weight, and a value of `0` uses only the recent-demand forecast when both forecasts are available. **Yearly seasonality** is one value for the selected webshop, and the blended forecast is not a purchase quantity, so stock, incoming deliveries and purchasing conditions still shape the purchase advice.

### What does a seasonality factor of 0.7 mean?

A **Yearly seasonality** of 0.7 gives the seasonal forecast a weight of 0.7 and the recent-demand forecast a weight of `1 − 0.7 = 0.3` when Optiply blends the two forecasts for a day. The value 0.7 is a weight, not a forecast increase of 70% applied to sales.

## Related articles on algorithm settings, trend and demand forecast

- [Configure Algorithm settings](/article/settings-algorithm-section)
- [Trend](/article/trend)
- [Demand forecast and product stock history](/article/demand-per-month-or-30-day-forecast)
