Published September 15, 2026 · Updated September 16, 2026 · 15 min read
How Demand-Zone and Liquidity Tools Work
Demand zones, order blocks, and liquidity sweeps turn chart observations into repeatable rules. This guide explains what the tools measure, their exact score weights, how to read their output, and why no detected area guarantees a reaction.
Author and publisher: StrongBuyAnalytics · Methodology creator: Ammar Aljanabi, Founder and Publisher
Table of Contents
Concepts and Observable Evidence
A demand zone is a price area associated with a prior low or base from which price moved upward with measurable strength. A supply zone is the inverse: an area associated with a prior high or base followed by downward departure. An order block is a rule-defined candle or compact area connected to an impulse. Different platforms use these terms differently, so the algorithm’s definitions matter more than a label.
These tools observe OHLCV data—open, high, low, close, and volume—and derive features such as candle body, range, width relative to volatility, departure, retests, pivots, and reclaim. They do not observe a complete list of hidden institutional intentions or prove that unfilled orders remain at a level. “Institutional” explanations may be a useful hypothesis, but the code-confirmed output is a pattern in market data.
A liquidity level is an area where prior highs, lows, or clustered reactions make stop orders and breakout interest plausible. A sweep generally describes price moving beyond such a level and then reclaiming it under defined candle conditions. The event is evidence of rejection under the rule; it is not proof of who traded or what price will do next.
How Zones Are Built and Maintained
A systematic detector first validates chronological market bars and calculates volatility context. It identifies candidate pivots or origin candles only after sufficient left and right context exists, reducing the risk of calling an unfinished swing a confirmed pivot. The candidate must be followed by a directional departure. Zone boundaries are then derived from the origin price action according to the tool’s rules.
Quality is not the same as proximity. A zone may have clean formation characteristics but sit far from current price. Conversely, price can be inside a weak, repeatedly tested zone. Freshness tracks whether price has returned after departure. Retests may consume available interest, so the tool lowers the freshness component rather than assuming that every touch makes a zone stronger.
Invalidation is essential. If price decisively passes through a zone under the applicable rule, the historical area is no longer treated like an intact setup. Market-data completeness also matters: splits, bad ticks, missing bars, thin volume, and provisional candles can distort bounds and scores. Detection should therefore be treated as conditional on valid input data.
Order-Block Score Weights
The code-confirmed demand-zone/order-block quality score combines four normalized components:
Body quality: 28%
Zone width quality: 22%
Impulse quality: 28%
Freshness: 22%
Body quality evaluates the relevant origin candle’s body characteristics. Width quality rewards a more usable, volatility-aware area rather than an excessively broad zone. Impulse quality measures the directional move away. Freshness reflects whether subsequent action has revisited the area. Body and impulse receive the largest equal weights; width and freshness receive slightly smaller equal weights.
A weighted score provides consistent ranking, not a measured chance of success. For example, an 80 score does not mean an 80% probability of a bounce. Calibration would require a carefully defined outcome, horizon, universe, costs, and out-of-sample study. The displayed score is a rule-based description of setup characteristics and is not an investment recommendation.
Liquidity-Sweep Scoring
The liquidity-sweep score has two components: 60% level strength and 40% reclaim. Level strength carries more weight because a sweep of a weak or arbitrary level provides less structural information. Reclaim assesses how convincingly price moves back through the level after penetrating it under the detector’s rules.
Score = 0.60 × level strength + 0.40 × reclaim score. This is a relative setup-quality calculation, not a probability, promise of reversal, or recommendation.
A high-quality reclaim can still fail if the broader trend is powerful, news changes available information, or liquidity disappears. A lower score can still precede a large move. The score orders observations according to specified features; it does not contain all causal information in the market.
A Responsible Research Workflow
Confirm data and timeframe. Verify ticker, venue, adjustment method, bar interval, timestamp, and whether the latest candle is complete. A daily zone and a five-minute sweep describe different auctions and should not be merged without an explicit multi-timeframe plan.
Inspect components. Do not stop at the total. Determine whether body, width, impulse, or freshness drives a zone score and whether level strength or reclaim drives a sweep score. A balanced setup differs from one supported by only a single feature.
Define invalidation before entry. Decide which close, penetration, or structure change invalidates the idea. Estimate spread, gap risk, and position size. Check scheduled earnings and material disclosures because technical levels can be bypassed when new information arrives.
Keep technical and fundamental claims separate. A zone can help describe location; it cannot establish fair value. A healthy balance sheet cannot guarantee that a short-term zone will hold. StrongBuyAnalytics report scores are deterministic, section-based, and separate from stock-page scores; AI writes narrative but does not set that deterministic score.
Worked Example — Illustrative Only
Illustrative normalized inputs, not real-market data: A fictional bullish order block has body 70, width 80, impulse 90, and freshness 60. Its score is (0.28 × 70) + (0.22 × 80) + (0.28 × 90) + (0.22 × 60) = 75.6.
A separate fictional downside sweep has level strength 75 and reclaim 50. Its score is (0.60 × 75) + (0.40 × 50) = 65. The correct reading is that the first pattern ranks well on the selected zone features and the sweep has stronger level evidence than reclaim evidence. Neither result is a 75.6% or 65% success probability. A researcher still needs timeframe alignment, invalidation, transaction-cost assumptions, and independent context.
Real-Market-Data Context
Source: StrongBuyAnalytics chart pipeline, which combines Polygon history with recent Yahoo Finance bars when available. Provider schedules, caches, and market hours can introduce delays.
Limitations
Zone boundaries and pivots depend on timeframe, volatility, data quality, and rule choices. Confirmed pivots necessarily lag. Adjusted data can differ by provider, and thin markets can produce unstable patterns. Scores omit news, options positioning, queue priority, full depth, and hidden orders. Repeated parameter tuning creates overfitting; visually selected examples create hindsight bias. Gaps can move through invalidation levels before an exit is possible. No score is a probability or recommendation, and no zone or sweep guarantees support, resistance, reversal, or favorable execution.