A breaker block is an SMC label for a previously defined zone that price has crossed and that is then observed with the opposite potential role. Former support becomes a candidate for resistance, or vice versa. A rectangle does not establish a trend reversal, institutional orders or a profitable trade. The boundary and confirmation rules determine which event is being labelled.

What a breaker block is in Smart Money Concepts

This article uses a simplified operational definition: start with a recorded order-block zone, detect its breach using specified conditions and observe a possible change of role. It is an exercise model, not a claim to reproduce every ICT course rule. LuxAlgo’s own Order Blocks & Breaker Blocks documentation describes conversion after mitigation and allows candle bodies instead of full ranges. These are rules of one tool rather than a universal SMC definition.

Record how the original zone is selected and whether it uses the candle body or full high–low range. Choosing the last opposite-coloured candle is one possible rule; it does not reveal who placed orders there. MetaTrader 5 distinguishes exchange order depth from OTC depth based on broker quotes. In its documented OTC price model, charts use Bid, while executions use Bid/Ask. A candle is not a map of all Forex orders or their owners.

Do not confuse a separately named “mitigation block” formation with a tool’s “Mitigation Method” setting. LuxAlgo’s Price Action Concepts settings offer Close, Wick and Average ways to define mitigation. A different author may require a preceding high/low breach, a structural break or another sequence. Record that definition rather than transfer labels between implementations or infer a trade direction from the name alone.

How a breaker forms — liquidity and a break of structure

A high above a recorded swing high followed by a close below it shows a price excursion. It does not show how many stops were activated, who traded or whether a participant deliberately sought liquidity. “Liquidity sweep” can be an interpretive shorthand, but quote OHLC alone cannot establish institutional intent or a quantity of resting orders.

One exercise can require an excursion, a close beyond the whole zone and then a return closing outside it. A version without the excursion is a different rule rather than automatically noise. Compare the definitions in Smart Money Concepts mechanics and change of character (CHoCH). Neither a named break nor a retest proves a future trend reversal.

Same return, two results

Before counting zone returns, record whether its boundaries include wicks or only the body.

Scroll sideways to see the full diagram

Same return, two resultsA source candle O 100, H 114, L 98, C 110 gives a full zone 98–114 and body 100–110. A later candle O 96, H 99, L 95, C 97 approaches from below, touching the full zone at 98–99 but missing the body. One linear price scale is used; this tests contact, not a complete breaker definition.Boundaries change the contact result11411010094Source candleLater returnfull range 98–114body 100–110H = 99Full range: contact YESBody: contact NO

Explicit boundary model: A fictional earlier candle has O = 100, H = 114, L = 98, C = 110. Before the later observation, record two zone variants: full range [98; 114] or body [100; 110]. The later candle has O = 96, H = 99, L = 95, C = 97 and approaches from below.

Its range [95; 99] intersects the full zone at [98; 99], but misses the body starting at 100. In LuxAlgo’s convention reference full range and body are distinct boundary choices. Here we test contact only with a predefined zone. We do not reconstruct a complete breaker qualification or treat contact as proof of institutional orders.

The narrower body zone excludes a contact present in the full range.

Breaker block versus a plain order block — where the difference lies

The same proposed role change appears in the idea of broken support becoming resistance. It is a hypothesis about a later reaction, not a property guaranteed by drawing a level.

A live order-block candidate and a breached zone are different states under the chosen rules. Their source candle may be identical, but the event time and eligible observations differ. A retest, candle confirmation or trade direction must be specified separately. Fully recorded criteria can be reproduced; discretionary zone selection does not make every subsequent comparison inherently subjective.

How to trade a breaker block — entry, stop, target

Use a wholly fictional EUR/USD H1 Bid series, with times in an arbitrary chart clock. Before 10:00, record a bullish-zone candidate at 1.0850–1.0860, a known high at 1.0880 and a low at 1.0848. The zone is 10 pips wide for a 0.0001 pip. Our bearish exercise requires a high excursion closing back below the known high, a later close below both the zone and known low, then a return into the zone closing below it.

Fictional sequence; information becomes available at bar close
Known atBid observationWhat this establishes
11:00; close of 10:00–11:00High 1.0884; Close 1.0876High exceeds the old high by 4 pips, then closes below it. Stop activations are unknown.
12:00; close of 11:00–12:00Close 1.0845Close is below both the zone and recorded low: a candidate under our rules.
13:00; close of 12:00–13:00High 1.0856; Close 1.0848The bar enters the zone from below and closes below its lower boundary.

The full return confirmation is known only at 13:00. A rule waiting for it cannot also claim an earlier entry at the best price of that same bar. In this exercise a final close above 1.0860 invalidates the proposed role change; a close inside the zone leaves the return unconfirmed. These are chosen observation rules rather than proven trading signals.

Different breach rules produce different results on the same bar. Keep the zone 1.0850–1.0860 and midpoint 1.0855. A separate fictional Bid bar has O = 1.0862, H = 1.0864, L = 1.0847 and C = 1.0852.

Our explicit comparisons; not the complete LuxAlgo algorithm
Breach ruleComparisonResult
Wick below lower edgeL is 3 pips below 1.0850Met
Close below lower edgeC is 2 pips above 1.0850Not met
Close below midpointC is 3 pips below 1.0855Met

The low can be observed before bar close, while a condition on the final Close requires the completed bar. Our original sequence still requires a close below the whole zone and known low; this bar fails its zone-close condition. A looser label does not repair that failed condition. If testing trades, separately define entry side, fills, invalidation, exits, costs and position size. An ordinary stop can fill worse; in MT5’s documented OTC model, a short-position stop is checked against Ask, which the Bid candle alone does not supply.

An honest caveat — a breaker is interpretation, not a certainty

Historical labels need an availability-time check. LuxAlgo documents backpainted polarity-change labels in this library indicator. TradingView explains how a pivot detected after five later bars may be plotted on the earlier pivot bar. Record detection time instead of treating the displayed location as knowledge available then. Updating an open-bar value is not automatically a defect; using later confirmation to justify an earlier trade is a different problem.

Geometry and labels are not a performance record. Compare frozen rules on later data, retain failures and include quote sides, commission, slippage and any financing. A chosen retest or higher-timeframe filter needs its own comparison rather than an assumption that adding confirmation improves returns. The order block trading guide describes the source zone; the technical analysis material provides wider context. A simulation does not reproduce every aspect of real execution.

What to do tomorrow

  1. Write the zone-selection rule and freeze the full-range or body boundaries before inspecting the next chart segment.
  2. Record the exact breach condition and when it becomes known. Distinguish an observed wick from a final closing price.
  3. Keep returns that miss the zone, close inside it or pass through it. Do not move the rectangle to fit the eventual result.
  4. Practise the written setup on demo and calculate position size from a chosen planned risk budget. An ordinary stop defines an intended invalidation level, but execution can be worse than that level; a percentage budget does not guarantee the realized loss.