Buy Side and Sell Side Liquidity Explained (BSL, SSL)

Written by Dominic Walsh · Published 23 Jul 2026 · Last updated 20 Aug 2026

Most retail stop losses rest at predictable spots: a few pips above an old high or below an old low. Buy side and sell side liquidity is the smart money term for those two clusters of resting orders. So this guide has one job: teach you to mark both pools on a clean chart and judge which one price is likely to run next.

The terms come from Michael Huddleston, the Inner Circle Trader (ICT), and they anchor the whole smart money concepts (SMC) framework. Nothing here needs an indicator. Still, precise definitions matter, because sloppy liquidity marking is the fastest way to misread a chart.

What Is Buy Side and Sell Side Liquidity?

Buy side liquidity (BSL) is the pool of buy orders resting above a swing high. Two groups build it. First, traders holding short positions park protective buy stops just above the high. Second, breakout traders set buy stop entries at the same level. Both order types fire as market buys the moment price trades there.

Sell side liquidity (SSL) mirrors this below swing lows. There, long holders keep sell stops under the low, while breakdown sellers stack sell stop entries beside them. Thus every obvious swing low doubles as a shelf of pending sell orders.

Watch the direction of each label. BSL sits above highs because the resting orders buy once triggered. Meanwhile, SSL sits below lows because its resting orders sell. Also, do not confuse these labels with the buy side and sell side of the investment industry. In SMC, they describe resting stop orders, not fund managers versus banks.

The Hero Chart: Both Pools on GBPUSD

Now look at a concrete case. The GBPUSD 1-hour chart below printed three equal highs at 1.34803, 1.34809, and 1.34814, a spread of barely one pip. Beneath that range, three equal lows formed at 1.34572, 1.34572, and 1.34576. So both pools sit on one chart: BSL above the triple top, SSL below the triple bottom.

Study what happens later in the frame. Price leaves the highs alone and runs the sell side pool instead, trading through 1.34572 and consuming the stops beneath the equal lows. No single candle predicted that. Yet the two marked pools turned the chart into one simple question, which side supplies the fuel first, and the answer arrived at the lows.

Three touches at each extreme made both pools unusually dense. Equal levels that hold three times read as unbreakable to pattern traders, which is precisely why so many orders gather beyond them. Hence a triple top or triple bottom is less a wall than a warehouse.

Whose Orders Build Each Pool

Picture the traders behind that GBPUSD chart. Shorts sold the triple top and parked protective buy stops just above 1.34814. Breakout buyers added buy stop entries at the same price, hoping to catch a clean break higher. Meanwhile, longs bought the triple bottom and left sell stops under 1.34576, right beside breakdown sellers waiting with sell stop entries. Four groups, two prices, zero coordination.

None of them can see the others’ tickets. Yet their textbooks match, so their orders stack anyway. Uniform education creates uniform placement, and uniform placement creates pools. Large players never need your order data. Plainly, the structure itself broadcasts where the stops live, and that is the entire psychological engine behind liquidity. The chart never shows the orders themselves, only the architecture that implies them.

The graphic below compresses the two pools into one reference card.

Where BSL and SSL Build Up

Liquidity never spreads evenly across a chart. Instead, it stacks at reference points that thousands of traders watch at the same time:

• Equal highs and equal lows. Two or more swings stall within one or two pips of each other. They read as double tops or double bottoms, and they hold the densest stop clusters.
• Previous day and week extremes. Indeed, the previous day high (PDH) and previous day low (PDL) are default stop anchors for intraday traders worldwide.
• Session highs and lows. Asian range extremes are classic targets during the London open. So check exact session boundaries with our forex market hours tool.
• Trendline touches. Each touch of a rising trendline collects fresh sell stops just beneath it.
• Round numbers. Plainly, levels such as 1.1000 on EURUSD attract stops because people think in round figures.

Sometimes several of these references overlap within a few pips. Then the cluster becomes unusually dense, and SMC traders call it a liquidity pool. Indeed, pools rank higher as targets than any single-swing stop.

External vs Internal Liquidity

SMC traders split liquidity by location as well. Internal liquidity sits inside the range, mostly as fair value gaps and minor swings. External liquidity rests beyond the dealing range, above its high and below its low. On EURUSD, for example, an untouched weekly high is external, while a fresh 1-hour fair value gap mid-range is internal. Price tends to alternate between the two. So once an external pool is taken, expect a rotation back toward internal levels, and vice versa. Label the two kinds differently on your chart so the alternation stays visible at a glance.

Why Price Seeks Liquidity

Large players face a mechanical problem. A fund that wants to sell 300 million EURUSD needs buyers on the other side, and quiet mid-range prices rarely offer enough of them. Yet resting buy stops above equal highs are a ready-made wall of market buy orders. Hence price often pushes up into BSL moments before a genuine markdown begins.

Retail traders feel the same event as a raid; our guide to stop hunting in forex covers the trader’s side of it. Still, nothing conspiratorial is required. Stops are the cheapest fuel available, and price gravitates toward fuel.

ICT compresses the idea into one line: price moves from liquidity to liquidity. Between pools, it rebalances inefficiencies. At pools, it fills orders. Thus a marked-up chart becomes a map of targets rather than a stream of random candles.

What the Numbers Can and Cannot Say

Be careful with statistics in this niche. No public feed counts the stops resting beyond a level, so nobody can quote a true hit percentage for sweeps, and any precise figure you meet is marketing rather than measurement. What you can verify is qualitative: raids concentrate at obvious levels, they cluster at session opens, and displacement separates meaningful ones from noise. Treat those as tendencies to test in your own journal, not laws. Keep score yourself, because your pairs, sessions, and execution differ from everyone else’s.

How to Mark BSL and SSL Step by Step

Use this routine before every session. It takes about five minutes per pair once practiced.

1. Open a clean 1-hour or 4-hour chart with no indicators attached.
2. Mark the previous day high and low, then the current week high and low.
3. Highlight every set of equal highs or equal lows formed over the past five to ten days.
4. Label BSL above each untouched high and SSL below each untouched low.
5. Delete a label once price trades through it, because swept liquidity is spent.
6. Then rank what remains. The oldest untouched pool on the higher timeframe is usually the primary draw.

Now you hold a liquidity map. Check every trade idea against it before entry, not after. Then refresh the map at every session close, because levels age fast.

Where Liquidity Sits in the SMC Workflow

Liquidity mapping is stage one of the ICT process, not the whole process. The full sequence runs from context to trigger: higher timeframe (HTF) bias first, then a point of interest (POI), then lower timeframe (LTF) confirmation, then the entry. The daily chart names the pool price should draw toward. Then the 1-hour chart shows the route. Next, the 5-minute chart times the entry after a sweep. Now, if that structure is new to you, start with our primer on what ICT trading is.

Multi-Timeframe Pairing

Pair your timeframes deliberately instead of drifting between charts. A common split marks the zones on H4 or H1 and hunts the trigger on M5 or M15. The higher chart answers one question, which pool and which direction. The lower chart answers another, whether the sweep happened and whether displacement followed. Also keep the pairing fixed for the whole trade, because switching mid-position invites hindsight edits.

A typical bearish sequence runs BSL above equal highs, displaces lower, then returns to a premium zone to distribute shorts. Its bullish twin mirrors the same steps under SSL. Meanwhile, keep charting the pools by hand while you learn; several of our smart money indicators plot equal highs, equal lows, and sweeps automatically on MT4 and MT5 once the skill is solid. Truly, screen time beats shortcuts here.

Session Timing in New York Time

Sweeps cluster around session opens. The London window, roughly 2:00 to 5:00 a.m. New York time, produces the classic raid on the Asian range. The New York window, about 7:00 to 10:00 a.m., often runs whatever London left untouched. Between those windows, pools tend to sit quietly while price drifts. So schedule your screen time around the opens instead of watching every candle print. Midweek sessions, Tuesday through Thursday, tend to produce the cleanest sequences, while Friday afternoons often drift as books flatten ahead of the weekend.

Worked Example 1: EURUSD Sweep of Sell Side Liquidity

Picture EURUSD printing equal lows at 1.0785 and 1.0786 during the Asian session. Longs from the prior New York rally hold sell stops beneath, around 1.0780. So SSL now rests under an obvious double bottom, and every SMC desk watching the pair can see it.

Then London opens at 3:00 a.m. New York time. Price drops fast, trades to 1.0778, and holds below the lows for only two 5-minute candles. Next, a strong bullish candle closes back above 1.0790. The raid filled the sell stops, trapped sellers who chased the break, and spent the pool.

Indeed, this sweep-and-reclaim sequence is one of the most studied patterns in SMC. Price then rallied toward the buy side resting above the Asian high at 1.0824. For entry models built around the move, read our full guide to liquidity sweep trading.

Worked Example 2: A Bearish Raid on Buy Side Liquidity

Now flip the direction. Picture GBPUSD in a daily downtrend, pulling back upward after a strong markdown leg. The 1-hour chart prints equal highs at 1.35208 and 1.35211 late in the New York session. Shorts hold protective buy stops above the pair of highs, and breakout traders stack entries beside them. So a clean BSL pool now caps the pullback, directly against the daily bearish bias.

Here is the sequence a liquidity trader waits for:

1. Mark the pool. Two highs within a pip confirm BSL above 1.35211.
2. Check the HTF draw. The daily chart points down toward SSL near 1.3440.
3. Wait for the run. Price spikes to 1.35228 during the London morning, clearing the pool by under two pips.
4. Demand displacement. Within two candles, a wide bearish body closes back below 1.35190.
5. Enter the retrace near 1.35200 with a stop above the raid high, around 1.35250.
6. Aim at the opposite pool. The SSL near 1.3440 is the mapped draw, with partials at each H1 swing low.

The annotated chart below shows this exact sequence, from marked pool to sweep to displacement to entry zone.

Stop, Target, and Trade Management Logic

Note the stop logic. The stop sits beyond the raid extreme because a second push through the same pool would break the read. Meanwhile, the target sits at the opposite pool because price that rejects BSL has a mapped reason to seek SSL. That asymmetry between a tight invalidation and a distant draw, not any prediction, is what makes the model worth studying.

Manage the position at structure once it moves. Trail the stop behind each new lower high as displacement extends, and take partials at every H1 swing low on the route. If price stalls short of the draw and prints its own upward sweep, close the remainder rather than hoping the map completes.

Common Mistakes and How to Fix Them

The same errors sink most new liquidity traders. Each one has a direct correction:

• Marking every minor swing. Only obvious, widely watched levels hold meaningful stop clusters. Fix: cap the map at five zones per pair, ranked by timeframe and age.
• Trading a sweep without displacement. If price drifts back instead of snapping back, the raid proves nothing. Fix: require a full-bodied close back inside the range before any entry.
• Fighting the higher timeframe draw. Sweeps taken against the daily bias fail far more often. Fix: only act on sweeps that point toward the daily pool.
• Leaving stale labels on the chart. A swept pool is spent, and dead labels invite entries at empty levels. Fix: delete each label the moment price trades through it.
• Parking stops inside the opposite pool. Your protective order becomes part of the next raid. Fix: place stops beyond the deeper structural swing, past the probable sweep zone.
• Treating the map as certainty. Liquidity analysis tilts probabilities; it never removes risk. Fix: size every position as if the read can fail, because sometimes it will.

Keep those corrections visible until they feel automatic. The graphic below pins the recurring errors in one place.

Pre-Trade Liquidity Checklist

Run this list before every liquidity-based entry. It takes under a minute once memorized.

1. Have I marked the previous day high and low plus the week’s extremes on H1 or H4?
2. Does an untouched pool sit in the direction of the daily bias?
3. Has price actually swept a pool within the last few candles, not merely approached it?
4. Did displacement follow the sweep with a full-bodied close back inside the range?
5. Is my entry on a retrace rather than a chase into the move?
6. Does my stop sit beyond the raid extreme, outside the obvious cluster?
7. Is my target the next untouched pool, with partials planned at structure?
8. Is a session window active, or am I forcing a trade in dead hours?

When the Read Fails: Breakout Instead of Reversal

Every liquidity trader eventually meets the sweep that never comes back. Price runs the pool, pauses, then keeps going, because the raid was the first leg of a genuine breakout rather than the end of a move. Expect this failure; it is built into the method. In strong trends, one side gets swept repeatedly while the other side stays untouched for days.

The chart below shows the failure in full. Price takes out equal lows, prints one weak bounce, then breaks down again with full-bodied bearish candles. No reclaim, no displacement back inside the range, no trade.

The Invalidation Rule and the Log

The invalidation rule is strict. A sweep read stays valid only while price closes back inside the prior range within a few candles. Once a candle closes beyond the swept level and holds there, treat the move as a breakout and stand aside, or reassess in the new direction. Also log every failed read: pair, session, the pool that broke, and what the first bounce looked like. A journal of failed sweeps teaches pattern recognition faster than a folder of clean screenshots.

Review that log weekly, not trade by trade. Patterns surface in batches: perhaps your failed reads cluster in the New York afternoon, or on one pair, or during heavy news weeks. Cut the weakest context first and the remaining reads improve without any new theory. Meanwhile, keep the failed charts beside the clean ones, since the contrast trains the eye faster than either set alone.

News adds a second failure mode, since one event candle can clear several pools and leave no tradable reaction. Truly, the honest framing is this: liquidity analysis tells you where the market has a reason to go. It does not say when. Nor does it promise a reaction once price arrives. Hence position sizing and stop placement still do the heavy lifting.

Related Concepts to Study Next

Three neighboring ideas sharpen a liquidity map fast. First, inducement in trading covers the engineered mini-pools that form inside pullbacks and bait early entries before the real zone fills. Second, ICT daily bias explains how to pick the pool price should draw toward each day, which sets the direction you hunt sweeps in. Then revisit stop runs from the victim’s side, because knowing when your own stop is bait teaches placement better than any rule list. Approach the three in that order, map first, bait second, defense third, since each layer assumes the previous one is already routine.

FAQ

Is buy side liquidity bullish or bearish?

Neither, on its own. BSL is simply where buy orders rest above highs. So a run into BSL can fuel a reversal lower or feed a genuine breakout higher. Higher timeframe context decides which reading fits.

What is the difference between BSL and SSL?

BSL sits above swing highs and consists of buy stops plus buy stop entries. SSL sits below swing lows and holds sell stops plus sell stop entries. Hence price runs BSL by trading up and SSL by trading down.

How do I know which pool price will run first?

Check the higher timeframe draw on liquidity first. If the daily chart trends up from a discount, the pool above old highs is the more probable magnet. Also, session timing helps, since the London and New York opens produce most raids.

Are equal highs stronger liquidity than a single swing high?

Usually, yes. Equal highs are visible to more traders, so more stops anchor there. Also, they look like a firm ceiling, which invites breakout orders on top of the stops.

What is the difference between a liquidity sweep and a liquidity grab?

Most traders use the two terms interchangeably, and both describe price running a pool of resting stops beyond a swing point. Some SMC teachers reserve grab for the fast wick-through version and sweep for any run of the level. Either way, the mechanics stay identical: stops fire as market orders and someone absorbs them.

Do liquidity pools always get swept?

No. Many pools sit untouched for weeks, and some never fill at all. Instead, treat each pool as a possible target and demand displacement before acting. Results are not guaranteed; past performance is not indicative of future results.