Liquidity in ICT Trading — Why Price Really Moves (Not Supply and Demand)
Liquidity is the real reason price moves. Not supply and demand. Not retail buying and selling. This guide explains the complete ICT liquidity framework — buy-side, sell-side, engineering, and how to trade it.
The foundational premise of ICT methodology is that price moves to collect liquidity — not because of supply and demand, not because of news, and not because of retail buying and selling pressure. Large institutions need liquidity to fill enormous orders. They engineer price movements specifically to reach areas where retail stop orders and pending orders are clustered, using that liquidity to fill their own positions before reversing.
What Liquidity Actually Means in Markets
In financial markets, liquidity refers to the availability of orders to trade against. When you buy, someone must sell to you. When you sell, someone must buy from you. Retail traders provide liquidity through their stop losses — when a stop loss is triggered, it creates a market order that the institution on the other side of the trade can fill against.
This is why banks do not "move price" the way many traders imagine — they do not push price with unlimited buying or selling power. Instead, they engineer scenarios that cause retail traders to create the orders the bank needs to fill. Stop losses become the bank's buy orders. Pending breakout orders become the bank's sell orders. The entire manipulation phase of AMD is designed to collect this retail-generated liquidity.
Buy-Side Liquidity (BSL) — Where the Stops Are Above Price
Buy-Side Liquidity consists of buy-stop orders and stop losses from short sellers clustered above current price. These exist at swing highs, at equal highs, above round numbers, at previous day highs, previous week highs, and at any level where retail traders are likely to have placed their stop losses on short trades or their buy-stop entries for breakout strategies.
When the algorithm needs to deliver price higher — perhaps to reach a major distribution zone or complete a weekly range — it will target the Buy-Side Liquidity above. Price moves up, triggers all the buy stops and short stop losses above the swing high, collects that liquidity, and then reverses from the distribution level. Retail breakout traders who bought the high are now trapped in losing positions.
Sell-Side Liquidity (SSL) — Where the Stops Are Below Price
Sell-Side Liquidity consists of sell-stop orders and stop losses from long traders clustered below current price. These exist at swing lows, at equal lows, below round numbers, at previous day lows, and at any level where long traders have placed their stop losses.
Equal Lows (EQL) and Equal Highs (EQH) are among the most important liquidity reference points in ICT methodology. When price creates two or more lows at approximately the same level, every retail trader who can see the chart knows those lows are significant support. This means every long trader in that position has their stop loss just below those lows — creating a massive pool of Sell-Side Liquidity that the algorithm is almost certain to target before a major reversal.
Liquidity Engineering — The Deliberate Creation of Traps
Liquidity Engineering is the deliberate process by which institutions create retail trading patterns to generate the liquidity they need. This is not a conspiracy theory — it is the natural result of how large institutions must operate within markets that do not have infinite depth.
The classic liquidity engineering scenario: price is trending bearishly. Institutions need to exit their short positions and enter long positions for the next upward cycle. To do this, they need sell orders to buy against — so they engineer a final bearish push below obvious support levels, triggering all the long traders' stop losses. These stop losses become the sell orders the institution buys against to build their long position. Price then reverses sharply upward, trapping the retail traders who sold the breakdown.
- diamondStop Hunt — Price temporarily moves beyond a significant level to trigger stop losses, then immediately reverses
- diamondTurtle Soup — A stop hunt above a previous high or below a previous low followed by a sharp reversal in the opposite direction
- diamondJudas Swing — The initial move of the session in the WRONG direction to collect liquidity before the real directional move
- diamondHRLR vs LRLR — High Resistance Liquidity Runs face multiple obstacles; Low Resistance Liquidity Runs have clear paths with no opposing structure
- diamondInternal vs External Liquidity — Internal liquidity sits within the current range (FVGs, OBs); External liquidity sits outside the range (swing highs/lows)
How to Use Liquidity Levels in Your Trading
The practical application of liquidity analysis involves three steps: first, identify where liquidity is resting above and below current price; second, determine which pool the algorithm is likely to target next based on HTF context and the current AMD phase; third, position yourself to benefit from the move into that liquidity rather than being caught on the wrong side of it.
Never place your stop loss at the obvious level. If the market structure says stop goes below the last low, and every retail trader can see that same low, your stop will be hunted before the real move occurs. ICT traders place stops beyond the sweep level — far enough that the liquidity hunt cannot reach them before the trade works.
The single most important liquidity concept to internalize: price does not move from support to resistance. Price moves from one liquidity pool to the next. Every move you see on any chart is a delivery from the last liquidity pool that was collected to the next one that needs to be reached.