> For the complete documentation index, see [llms.txt](https://doc.karsa.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.karsa.ai/iii.-cluster-designer-creating-clusterization/product-dynamics-management.md).

# Product Dynamics Management

Your products' performance is not static – it changes over time due to seasonality, inventory levels, price changes, competitor activities, and many other factors. For your segmentation in Karsa Labelizer to remain effective and current, it's necessary not only to divide products correctly at the beginning but also to actively manage their **dynamics**.

## What Does "Product Dynamics" Mean?

In the context of Karsa Labelizer, product dynamics primarily refers to two key areas:

1. **Product movements between clusters:** As the performance of individual products changes, it may be advantageous to move them from one cluster (campaign) to another that better matches their current characteristics. Karsa Labelizer can do this automatically.
2. **Handling new products:** Newly added products to your feed usually have no performance history. It's important to have a strategy for how to most effectively incorporate these products into your segmentation structure so they don't remain "lost" or incorrectly categorized.

## Why is Dynamics Management Important?

* **Maintaining cluster consistency and performance:** Continuous, intelligent product movements help maintain high internal consistency of individual clusters, which is key to their predictability and performance.
* **Preventing campaign destabilization:** Uncontrolled or too frequent movements of large numbers of products can disrupt the learning phase of Google algorithms and lead to temporary performance declines. That's why Karsa Labelizer offers tools to manage these movements.
* **Effective start for new products:** The right strategy for new products ensures that even "newcomers" get a chance to prove their potential and won't be unnecessarily placed in underperforming segments just because they don't have data at the beginning.

## What You'll Find in This Subsection

The following pages will explain in detail how to set up rules for managing your products' dynamics in **Cluster Designer**:

* [**Movement Limits**](https://github.com/MJezek6/Labelizer-KB-EN/blob/Main/cluster-designer/product-dynamics-management/movement-limits.md)**:** How to configure whether and under what conditions products can automatically move between clusters, including setting percentage limits and time delays to ensure campaign stability.
* [**New Products Strategy**](https://github.com/MJezek6/Labelizer-KB-EN/blob/Main/cluster-designer/product-dynamics-management/new-products-strategy.md)**:** Description of various approaches to incorporating newly added products into your clusterizations to maximize their chance of success.

By carefully setting these parameters, you'll ensure that your segmentation created using Karsa Labelizer will not only be effective at its inception but will remain relevant and high-performing in the long term.


---

# 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://doc.karsa.ai/iii.-cluster-designer-creating-clusterization/product-dynamics-management.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.