Supply & Demand Zones

Supply and demand zone trading starts from a description of how price moves rather than from an indicator. When resting orders at a price are heavily outweighed on one side, price does not oscillate there — it leaves quickly. The area a move departs from is what these strategies mark: a demand zone at the origin of a sharp advance, a supply zone at the origin of a sharp decline. The assumption is that interest at that origin was left partly unfilled, so a later return may produce a reaction. The zone is a place to look for one, with a defined point at which the idea is wrong.

## How a zone is built

Nearly every version of the concept follows three steps, and most disagreements between versions live inside one of them.

Identifying imbalance. The common pattern is a base followed by an impulse: a short consolidation, then a rapid one-directional departure. That gives the familiar taxonomy — rally-base-rally and drop-base-rally for demand, rally-base-drop and drop-base-drop for supply. Other versions skip the base and use the last opposite-colored candle before the move, the gap left between wicks during the impulse (an imbalance or fair value gap), or the swing where market structure broke.

Defining boundaries. A zone has a proximal edge, the side facing current price where entries usually sit, and a distal edge, beyond which the premise no longer holds. Whether those edges come from candle bodies, from wicks, or from the full base range is not cosmetic: it sets entry price and stop distance, and therefore the risk-reward of every trade the rules will ever take.

Defining the return. Some versions place a passive limit at the proximal edge and accept that some zones are cut straight through. Others require confirmation inside the zone — a rejection candle, a lower-timeframe structure shift, a momentum or moving-average condition — trading a worse entry price for a filter.

## Main variants

The versions catalogued here fall into a few families. Pure price-action implementations use zones alone, usually marking them on a higher timeframe and entering on a lower one. Confluence implementations pair zones with a trend filter such as a moving-average cloud, a momentum filter such as MACD, or volume-derived context such as a volume profile's value area and its high- and low-volume nodes, and use that second tool to decide which zones are eligible. Checklist models formalize the sequence into named stages — locate the level, wait for a specified confirmation, execute with predefined risk — mainly to make a discretionary process repeatable. Smart-money framings rename the same structures as order blocks and flipped levels, adding the idea that broken supply becomes demand on retest. Trap and liquidity variants expect price to run past the zone edge before reversing, which moves both the entry and the invalidation.

## What actually differentiates implementations

Two versions can share the name and behave nothing alike. What matters is: how zones are drawn, and whether the rule is objective enough for someone else to reproduce it; whether a zone expires after one touch; whether entry is a limit at the edge or a confirmation trigger; where invalidation sits, and whether it requires a close beyond the distal edge or only a tick; whether counter-trend zones are traded at all; and how targets are set — an opposing zone, a fixed multiple of risk, or a structural level. Timeframe pairing, session, and instrument matter as much as any of it.

## Common mistakes

The most frequent error is retrospective marking: on a finished chart, every consolidation that preceded a move looks like a zone, and the ones that failed are invisible. Closely related is leaving the rule vague enough that the trader decides after the fact which zones counted. Others: ignoring context and taking every zone against a dominant trend; using a fixed position size across zones of very different widths, so risk varies trade to trade; reusing a zone that has already been traded through; and treating any reaction at a zone as a reversal when it may only be a pause.

## Evaluating and backtesting a version

Start by writing the rules until they are mechanical — if a zone cannot be specified without the phrase 'it should look clean', it cannot be tested. Detect zones with a fixed lookback so the test never sees candles that had not printed yet, and be careful with multi-timeframe indicator tools that redraw zones as new data arrives; a repainting zone flatters any backtest.

Then test the counterfactual. Compare the full rule set against a stripped version — plain horizontal support and resistance, or the trend filter alone with no zones — to see whether the zone logic contributes anything beyond its components. Vary the parameters that were arbitrary choices (bodies versus wicks, buffer size, minimum impulse size) and check that results degrade gradually rather than hinging on one setting.

Judge the outcome on the distribution, not a headline number: R-multiples per trade, maximum adverse and favorable excursion to see whether the stop beyond the distal edge is doing real work, and behavior across different regimes and instruments. Include realistic costs — spread and slippage weigh heavily on zone-edge limit entries, which also assume a fill that never happens if price turns a tick early.

Strategies in this concept (25)

Frequently asked questions

How is a supply or demand zone different from a support or resistance level?

A support or resistance level is a single price where the market has previously turned. A zone is an area, and it is defined by origin rather than by touches: it is drawn where an impulsive move began, not where price stalled repeatedly. In practice this means a zone can be valid on its first return, while classical support usually needs prior reactions to be recognised. The zone's width also carries information, since it defines the distance to invalidation.

Does a zone get weaker each time price touches it?

That is an assumption, not an observed fact, and different implementations treat it differently. The usual reasoning is that a return fills some of the resting interest, so less remains for the next visit — which leads to rules like 'fresh zones only' or 'valid for one touch'. Other versions keep zones active until price closes through the distal edge. Because this single rule changes which trades exist, it is worth testing both ways on the same data rather than adopting a convention.

Is it better to enter with a limit order at the zone edge or wait for confirmation?

The two choices trade different things. A limit at the proximal edge gives the best possible price and the tightest stop, but takes every zone, including those that price passes straight through. Waiting for confirmation inside the zone removes some of those, at the cost of a later entry, a wider stop, and missed trades when price reacts immediately without printing a signal. Which one performs better depends on the instrument and timeframe, so it should be measured, not assumed.

Which timeframe should zones be drawn on?

Most implementations separate the two roles: a higher timeframe defines where zones are, and a lower timeframe defines how the entry is taken. The pairing matters because it sets both the number of opportunities and the size of the risk. Higher-timeframe zones are wider and less frequent; lower-timeframe zones are more numerous and more sensitive to noise and cost. When comparing versions of this concept, the timeframe pair should be treated as part of the strategy, not as a preference.

Are order blocks the same thing as supply and demand zones?

They overlap heavily. Both mark the origin of an impulsive move and treat it as an area where unfilled interest may remain. The differences are mostly in the identification rule — order-block definitions typically point to the last opposite-colored candle before a move that broke market structure, while base-and-impulse definitions use the consolidation itself — and in the surrounding vocabulary of liquidity sweeps and structure breaks. On a chart the resulting areas often, but not always, coincide.

Can this concept be backtested objectively?

It can, but only after the discretionary parts are removed. That means a formal definition of what counts as an impulse, how the base is bounded, which edges are used, when a zone expires, what triggers entry, and where invalidation sits. Zones must also be detected using only data available at the time, since indicator tools that redraw zones on new data will produce results that cannot be reproduced live. Once those conditions are met, the concept is as testable as any rule-based system.

All strategy concepts · Explore all strategies