What Is a Liquidity Pool in ICT Trading?

What Is a Liquidity Pool in ICT Trading?

A liquidity pool in ICT trading is a price area where resting orders concentrate: protective stop losses, breakout stop entries, and pending limit orders. Because those orders execute at market when touched, the pool represents ready-made volume that institutions can fill large positions against.

The logic is mechanical, not conspiratorial. A fund that wants to buy 500 million of EURUSD cannot click a market buy without moving price against itself. It needs counterparties selling in size at one place. Where do forced sellers appear? Below an obvious swing low — where longs have stop losses (sell orders) and breakout traders have sell stops stacked together.

So when price drops through that low, a burst of sell-side volume executes automatically. The institution buys into that burst. The pool of resting orders becomes the fuel for the fill. This is why ICT describes highs and lows not as "support and resistance" but as Buy-Side Liquidity (BSL) and Sell-Side Liquidity (SSL) — inventory waiting to be taken.

Three order types make up almost every pool:

• Protective stops — longs stopped below lows create sell flow; shorts stopped above highs create buy flow.
• Breakout entries — stop orders from traders who buy new highs or sell new lows, adding to the same burst.
• Pending limits — resting bids and offers layered around obvious levels and round numbers.

The larger and more obvious the level, the more orders accumulate behind it, and the more attractive the pool becomes as a target.

Is This the Same as a DeFi Liquidity Pool?

No. If you arrived here from crypto, note that the term collides with a completely different concept. A DeFi liquidity pool is a smart contract holding token pairs (e.g., on Uniswap) that lets an automated market maker quote prices. An ICT liquidity pool is a chart-analysis concept about where orders rest.

Everything below concerns the ICT meaning. The two share only the word "liquidity."

Where Do Liquidity Pools Form on a Chart?

Pools form wherever the largest number of traders would place a stop or trigger an entry. The predictable locations:

• Above equal highs / below equal lows. Equal Highs (EQH) and Equal Lows (EQL) are the densest pools. Two or three touches at the same level convince retail traders the level is "strong," so stops pile up just beyond it — every retest adds another wave of shorts with stops above the level.
• Beyond clean swing points. Any obvious fractal high or low that stands out on the timeframe carries stops behind it, even without an equal counterpart.
• Session highs and lows. The Asian range high/low, London high/low, and previous New York session extremes are reference levels the whole market watches, so orders concentrate there daily.
• Previous day, week, and month extremes plus opens. Previous daily high/low and the weekly open are algorithmic reference points; price repeatedly trades back to them.
• Round numbers. Stops cluster at psychologically round figures — behavior documented in Federal Reserve Bank of New York research on stop-loss orders in currency markets, which found they cluster near round numbers and can fuel self-reinforcing price cascades when triggered.
• Trendline touch sequences. Three touches of a rising trendline mean a crowd of longs with stops just below the line. ICT treats trendlines not as support but as a diagonal pool being built for later collection.

Notice the pattern: the more textbook-obvious a level looks, the bigger the pool behind it. Obviousness is the mechanism, not a coincidence.

Draw on Liquidity: How ICT Reads Pools as Targets

ICT's core claim about price delivery is that markets move from liquidity pool to liquidity pool. The next significant pool is the Draw on Liquidity (DOL) — the magnet price is being delivered toward. Instead of asking "is this level support?", the ICT question is "which pool hasn't been taken yet, and which side is the algorithm reaching for?"

This reframing changes trade management completely. Targets go in front of pools (where opposing orders will absorb your exit), and stops go where no obvious pool sits — not one tick behind the level every other trader is using.

The timeframe hierarchy: HTF pools are bigger magnets

Pools inherit the weight of the timeframe that built them. A low that has held on the weekly chart for three months has accumulated far more resting orders than a low formed an hour ago. Practical hierarchy:

1. Monthly/weekly extremes — campaign-level targets; price may take weeks to reach them.
2. Daily highs/lows — the standard swing-trade DOL.
3. Session and intraday pools — Asian range, London high, prior-day extremes; targets for day trades.

When pools conflict, the higher timeframe usually wins. A 15-minute pool above equal highs means little if the daily chart is being delivered toward a sell-side pool 3% lower — the small pool gets consumed as fuel on the way down.

Internal vs external range pools

Within any dealing range, ICT splits liquidity into two classes. External Range Liquidity is the pools at the range extremes — the high and the low. Internal Range Liquidity is everything inside: Fair Value Gaps (FVG), Order Blocks, and minor swing points within the range.

Price alternates between them: take external liquidity (sweep the range high), then reverse to internal (fill an FVG inside), then extend toward the opposite external pool. If price just swept external liquidity, look for an internal array to trade back to — and vice versa. This alternation is the skeleton of most ICT trade models.

How Liquidity Pools Get Engineered

Not every pool forms organically. ICT argues that some are deliberately built — "engineered liquidity" — so a large player has something to fill against later.

Equal-high painting: price rallies to a level, sells off, rallies to the same level again, and stalls. The chart now shows a clean double top. Every technician marks resistance; shorts enter with stops just above; breakout buyers place buy stops there too.

The pool above those equal highs is now dense — and it was created by the price behavior itself. The subsequent run through it, then reversal, is the classic engineered sweep.

Inducement: a minor, tempting pool is left just in front of a real point of interest. Example: after a bullish Market Structure Shift, price leaves a small swing low just above an untested Order Block. Early longs buy the minor pullback with stops below that minor low.

Price dips through it — collecting their stops as Inducement — then delivers the real reaction from the Order Block below. The shallow pool exists to trap participants and fuel the fill at the deeper level.

You cannot verify intent, and you don't need to. What matters is the repeatable pattern: obvious minor pools directly in front of major HTF levels get consumed first far more often than not, so plan entries behind the inducement, not in front of it.

What Happens When a Liquidity Pool Gets Hit?

A pool being touched is not a signal by itself. Two very different outcomes follow, and the difference is what happens immediately after the orders execute.

Sweep then reversal. Price spikes through the level, executes the resting orders, and closes back inside the prior range — typically leaving a long wick. That rejection says the burst of orders was absorbed by opposing institutional interest: the stops were the point, not the breakout.

This is the Liquidity Sweep (or stop hunt), and it is the seed of reversal setups like Turtle Soup and the Judas Swing. Confirmation comes from displacement — an energetic move away from the level that breaks short-term structure and leaves an FVG.

Break then continuation. Price trades through the pool and keeps delivering: bodies close beyond the level, pullbacks are shallow, and old resistance orders flip to support the move. Here the pool's orders were consumed as fuel for expansion toward the next pool, not as an exit for a reversal. Genuine breaks usually occur when a larger DOL sits farther beyond the level.

Rule of thumb: wick through plus close back inside favors reversal; bodies closing beyond plus acceptance favors continuation. Time matters too — sweeps during a London or New York Kill Zone carry more weight than moves in dead hours, because that is when institutional volume is actually present.

How to Build a Liquidity Pool Map (Step by Step)

A liquidity pool map is a marked-up chart of where the meaningful pools sit relative to current price. Build it top-down before the session, not mid-trade.

Step 1 — Mark external pools on the HTF

On the daily and weekly chart, mark the dealing range: the most recent significant high and low. Label the buy-side pool above the high and the sell-side pool below the low. Add the previous week's high/low and the weekly open.

Step 2 — Add 4H/1H swing pools and equal highs/lows

Drop to 4H and 1H. Mark equal highs, equal lows, and clean swing points inside the HTF range. Flag any minor pool sitting directly in front of an HTF Order Block or FVG as probable inducement.

Step 3 — Add session levels and round numbers

Mark the Asian range high/low, the current day's open, the prior day's high/low, and any round number within reach. These are the intraday pools that get worked during Kill Zones.

Step 4 — Decide the draw and rank the pools

Given HTF structure and bias, decide which side is the likely Draw on Liquidity. Rank pools by timeframe weight and freshness — untapped pools matter; levels already swept twice do not. Expect price to consume near-side minor pools on the way to the major one.

A liquidity scanner such as LiquidityScan can flag equal highs/lows and sweep events across hundreds of pairs automatically, but the ranking logic above is what makes the map tradeable.

Worked example: BTCUSDT

Suppose BTCUSDT has daily equal highs at 118,400–118,450 (three touches over two weeks), the weekly open at 116,900, Monday's Asian low at 117,250, and an untested daily low at 115,800. Price trades at 117,600 in the New York AM session.

The map reads: dense buy-side pool above 118,450; minor sell-side pools at 117,250 and 116,900; major sell-side at 115,800. Price rallies and spikes to 118,610 — through the equal highs — then closes the hour back at 118,150, leaving a wick. Buy-side was swept and rejected. Displacement follows: a drop through the 117,900 short-term low leaves a 1H FVG and shifts structure bearish.

Now the sequence is legible: external buy-side taken, so the draw flips to sell-side. Price consumes the Asian low at 117,250, bounces briefly from the weekly open pool at 116,900 (a lower-timeframe reaction, not a reversal), and delivers into 115,800 within two sessions. Each leg ran pool-to-pool — the map wrote the route in advance.

Mistakes to avoid

• Marking every wick as a pool. If your chart has 30 lines, you have zero read. A pool needs obviousness — a level many participants used. Three to six levels per timeframe is plenty.
• Ignoring the hierarchy. Trading a 5-minute pool against the daily draw is fighting the current with a teaspoon.
• Treating a touch as a signal. Wait for the sweep-versus-break evidence: closing bodies, displacement, structure.
• Using swept levels. Once a pool is consumed, the orders are gone. Fresh liquidity, fresh magnet — retire the old line.
• Placing your own stop inside a pool. The whole lesson of the concept is that the obvious spot is where stops get collected. Put yours beyond structure that would truly invalidate the idea, not one tick behind the crowd's level.

Once you understand what a liquidity pool is in ICT terms — engineered clusters of resting orders that price is delivered toward — charts stop looking random. Every session becomes a question of which pool is next, and every level you mark either holds orders or holds nothing.

Frequently Asked Questions

Is a liquidity pool the same as support and resistance?

No — the interpretation is inverted. Support/resistance theory expects obvious levels to hold and treats a break as a signal to follow. Liquidity pool theory expects obvious levels to be run precisely because stops rest behind them, then judges the reaction. Same lines on the chart, opposite trade logic.

Can you see liquidity pools on a chart, or are they invisible?

Resting orders themselves are not visible on a candlestick chart — pools are inferred from structure: equal highs, clean swings, session extremes, round numbers. In futures you can partially verify with depth-of-market or order-flow tools, but ICT's approach is to trust the inference and confirm with price's reaction after the level is hit.

Which liquidity pools are strongest?

Higher-timeframe, untapped, and obvious. A weekly low that has held for months and shows equal lows combines all three: long accumulation time, orders still resting, and maximum participant attention. Freshness matters as much as size — a pool swept last week has already given up its orders.

Do liquidity pools exist in crypto and stocks, or only in forex?

Any market with stop orders and leveraged participants builds pools. Crypto is arguably the cleanest example: 24/7 trading, heavy retail leverage, and visible liquidation cascades around obvious levels. Stocks show the same behavior around prior highs/lows and round numbers, though opening auctions and gaps complicate session-level analysis.

Related query paths

The liquidity pool is the noun; the queries below cover the verbs — how pools are classified, engineered, and finally taken.

• What Is a Liquidity Sweep? — the definitional next step: what actually happens when a pool gets run.
• BSL vs SSL in SMC: Identify Liquidity — classify every pool on your map as buy-side or sell-side correctly.
• Equal Highs & Equal Lows (EQH/EQL): Engineered Liquidity — a deep dive on the densest pool type and how it gets painted.
• Internal vs External Liquidity: An SMC Trader's Guide — the range framework that tells you which pool price reaches for next.
• Inducement vs Liquidity Sweep: A Trader's Guide to SMC Setups — separating the bait pool from the real collection event.
• Liquidity Sweep Explained: The ICT Stop Hunt — turn the sweep-then-reverse pattern into an executable entry model.
• Draw on Liquidity (DOL): How to Predict the Next Target — how it connects to draw on liquidity ict.