> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/toolkits/orderflow-concepts-tm/stacked-imbalances.md).
# Stacked Imbalances
Stacked Imbalances are powerful visual confirmations of aggressive institutional participation. They occur when market participants execute large market orders in a single direction, overwhelming the limit orders and leaving behind a "stack" of consecutive price levels with one-sided volume.
When the toolkit detects a stacked imbalance, it highlights the zone on your chart, providing a clear visual representation of aggressive buying or selling pressure. These zones often act as strong support or resistance on subsequent retracements.
### Configuration
* **Show Stacked Imbalances**: Master toggle to enable or disable the highlighting of stacked imbalance zones.
* **Threshold %**: This setting defines how aggressive the volume must be to qualify as an imbalance. For example, a threshold of `300%` means the buying volume at a specific price level must be at least 3x (300%) greater than the selling volume (or vice versa) to be flagged as an imbalance.
* **Min Levels**: Defines how many consecutive imbalanced price levels must stack on top of each other to draw the zone. The default is `3`, meaning you need at least three back-to-multi-level imbalances in a row to confirm strong directional conviction. A lower number (e.g., 2) will show more zones but with less conviction, while a higher number (e.g., 4 or 5) will only highlight extreme momentum.
---
# 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://docs.candelacharts.com/toolkits/orderflow-concepts-tm/stacked-imbalances.md?ask=&goal=
```
`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.