Buy-Side and Sell-Side Liquidity in ICT: Where Stops Rest

If there is one idea that sits at the center of ICT trading, it is liquidity. Rather than asking "where is support?", ICT asks "where are other traders' orders waiting?" This lesson explains buy-side and sell-side liquidity, why those orders cluster where they do, and how to map them on your chart.

What it is

In general finance, liquidity describes how easily something can be bought or sold. ICT uses the word more specifically: pools of resting orders sitting at predictable prices. Many of those orders are stop-losses, which turn into market orders when triggered.

Buy-side liquidity (BSL)

Buy-side liquidity rests above highs. It includes:

• Buy stops protecting short positions. A trader who sold below a high usually puts the stop just above it.
• Buy-stop entry orders from breakout traders waiting for price to clear the high.

When price trades above the high, these orders become buys.

Sell-side liquidity (SSL)

Sell-side liquidity rests below lows. It includes:

• Sell stops protecting long positions placed just below a low.
• Sell-stop entry orders from traders waiting for a breakdown.

When price trades below the low, these orders become sells.

Why it matters

Large participants need opposing orders to fill big positions. A large seller is easier to fill when many buy orders appear at once, such as when buy stops trigger above a high. ICT teaches that this is one reason price so often runs just beyond obvious highs and lows before turning. Treat that as a working explanation rather than a proven fact: we cannot see every order, and many moves through highs simply keep going.

Where liquidity tends to rest

Equal highs and equal lows

Two or more highs at almost the same price look like strong resistance to many traders, so stops pile up just above them. ICT treats equal highs and lows (often within a few pips) as especially attractive pools. The cleaner and more obvious they look, the more orders are assumed to be resting there.

Old highs and lows

Reference points that many traders watch:

• PDH / PDL: previous day high and low.
• Previous week high and low.
• Previous month high and low.
• Session highs and lows, such as the Asian range covered in Opening Prices and the Asian Range.

The higher the timeframe, the more significant the level is usually considered.

Trendline liquidity

A trendline with several clean touches invites traders to buy each touch with a stop just beneath the line. That creates a band of sell-side liquidity running along the trendline. ICT traders often expect price to eventually break such a line to run those stops. See Trendlines for the conventional view.

How to identify it

1. Start on the daily chart and mark the previous day, week and month highs and lows.
2. Mark obvious swing highs and lows from your market structure analysis.
3. Highlight equal highs and equal lows, which are usually within a few pips on intraday charts.
4. Mark any clean trendline with three or more touches.
5. Label levels above price as buy-side liquidity and levels below as sell-side liquidity.
6. Rank them by significance: higher timeframe and more obvious usually ranks higher.

Worked example: a level map on GBP/USD

Prices are illustrative. During the London session, GBP/USD trades at 1.2725. A trader builds this map before the New York AM kill zone (07:00–10:00 ET).

The equal highs at 1.2750 and 1.2752 are only 2 pips apart, so the trader expects buy stops resting around 1.2753 to 1.2760. The PDH at 1.2768 sits not far above, making the 1.2750 to 1.2768 band a dense buy-side area.

The trader does not simply buy, hoping price will reach those highs. Instead, the map frames two scenarios:

• If her daily bias is bullish, the equal highs and PDH are logical targets for a long trade taken from a discount area.
• If her bias is bearish, a run above 1.2752 to 1.2768 that quickly fails would be a candidate sweep, a possible short setup with a stop above the run's high. That idea is explored in Liquidity Sweeps and Stop Hunts.

Either way, she plans her stop-loss away from the obvious clusters, since a stop sitting exactly at 1.2753 would itself be part of the pool.

How traders use it

• Targets: Opposing liquidity is the most common ICT profit target. Long trades aim at buy-side levels; short trades aim at sell-side levels.
• Setups: A level being swept and rejected can mark a reversal, especially inside a kill zone.
• Stop placement: Knowing where the crowd puts stops helps you avoid putting yours in the same place. Then size the position from that stop with the Position Size Calculator.
• Draw on liquidity: The most significant nearby pool is often called the "draw," the level price is expected to seek next.

Common mistakes

• Marking every minor high and low. Focus on obvious, significant levels.
• Assuming price must reach a level. Liquidity is a magnet in theory, not a guarantee in practice.
• Ignoring timeframe hierarchy. A weekly low usually outranks a 5-minute equal low.
• Placing your own stop at the obvious spot. Your stop then becomes someone else's liquidity.
• Forgetting that "equal" is approximate. Highs a couple of pips apart count; there is no need for an exact match.

Summary

Buy-side liquidity rests above highs; sell-side liquidity rests below lows. These pools consist largely of stop-losses and breakout orders, and they cluster at equal highs and lows, previous day, week and month extremes, session ranges and trendlines. ICT traders map these levels to choose targets, spot possible sweeps and place stops sensibly. Treat liquidity as a guide to where price may go, and always manage risk in case it does not.