Use this article to understand the bullish ICT Fair Value Gap template block by block. This is not a full trading strategy recommendation. It is a strategy component that detects a bullish Fair Value Gap, stores the relevant price levels in variables, and places a pending buy order from the stored FVG level. Also known as: ICT FVG, bullish Fair Value Gap, FVG block, FVG template, Candle ID 1 2 3, BullFVGHigh, BullFVGLow, pending order at FVG.

The bullish ICT Fair Value Gap template uses two separate decision trees:

The main idea is simple:

The template first checks a three-candle structure. If the structure is valid, it saves the Fair Value Gap boundaries into variables. Later, the EA uses those stored values to place a pending order at the Fair Value Gap level.

This separation is important because the EA needs to remember the detected price zone before it can trade from it.

Video explainer: https://youtu.be/ojBsjbvNuA4?si=_8kBXZk01iIGUSj-&t

The template focuses on a bullish, or buy-side, Fair Value Gap.

A bullish Fair Value Gap is defined with three closed candles:

In this template:

Important: BullFVGHigh does not mean the candle high. It means the higher price boundary of the gap. In this bullish template, that value comes from Candle ID 1 low.

This template requires a pro subscription

The template uses closed candles, not the current forming candle.

The Candle IDs are:

This matters because Candle ID 0 can still change while price moves. Candle ID 1, 2, and 3 are already closed, which makes the logic cleaner and easier to test.

Example:

If you run the EA on the 1H timeframe, the Run per Candle block checks the logic once when a new 1H candle starts.

The template has two separate decision trees.

The left decision tree detects and stores the Fair Value Gap.

The right decision tree checks whether a stored FVG level exists and places the pending order.

This is the core structure:

Detection → Store price levels → Check stored level → Place pending order → Reset variables

The first decision tree looks for a valid bullish Fair Value Gap.

It runs once per candle and checks several Trade Rule blocks. If all conditions are true, the EA stores the FVG boundaries in variables.

The first block is Run per Candle.

This means the detection logic runs once when a new candle forms.

If the EA is attached to a 1H chart and the block uses the Current timeframe, this tree runs once at the start of each new 1H candle.

This prevents the same closed-candle pattern from being checked repeatedly on every tick.

Condition:

Candle ID 1 low > Candle ID 3 high

Plain English:

The low of the most recent closed candle is higher than the high of Candle ID 3.

This creates the basic bullish Fair Value Gap area.

The gap sits between:

This is the first structural requirement. If Candle ID 1 low is not above Candle ID 3 high, there is no bullish gap according to this template logic.

Condition:

Candle ID 2 close > Candle ID 2 open

Plain English:

Candle ID 2 must be bullish.

This means the candle closed above its own open.

The template uses this as a simple way to define bullish impulse. It checks whether the middle candle moved upward.

This is intentionally simple. You can make this stricter later by adding your own impulse definition, for example with a stronger candle body requirement, range filter, trend filter, or other price-action condition.

Condition:

Candle ID 1 high > Candle ID 2 high

Plain English:

The most recent closed candle made a higher high than the candle before it.

This confirms that price continued pushing upward after the bullish impulse candle.

This is a simple momentum check. It does not mean this is the only way to define an impulse. It is just a clean and testable price-action rule.

Condition:

Candle ID 2 low > Candle ID 3 low

Plain English:

The low of Candle ID 2 must be higher than the low of Candle ID 3.

The block name “Liquidity Grab” may sound advanced, but in this template it mainly works as an additional validity check.

It helps confirm the bullish structure and keeps the Fair Value Gap definition cleaner.

If all previous Trade Rule blocks are true, the template stores the detected FVG price levels in variables.

The variables are:

This is where the EA remembers the Fair Value Gap.

Variables work like dynamic memory containers. They can store values while the EA is running and use those values later in another part of the strategy.

In this template, the variables create the bridge between detection and execution.

The first tree finds the Fair Value Gap. The variables remember the price levels. The second tree uses those stored levels to place the order.

This is also why this template is more advanced than a simple entry template. It does not only check a condition and trade immediately. It detects a price zone, stores it, and then uses that zone later.

The same pattern can be used for other strategies too. You can store session highs and lows, swing points, candle levels, supply and demand zones, or any other price area you want to use later.

The second decision tree checks whether a valid FVG level has been stored.

If the stored level exists and the trade filters are clear, the EA places a buy pending order at the stored FVG level.

The second tree also starts with Run per Candle.

This means the EA checks once per new candle whether it should use the stored FVG level for order placement.

This could technically be checked per tick, but per candle is usually enough in this template because the EA places a pending order. Once the pending order is placed, it waits in the market until price reaches it or the order is removed.

Condition:

BullFVGHigh != 0

Plain English:

The EA checks whether a valid FVG entry level has already been stored.

If BullFVGHigh is still 0, the EA has no FVG level to trade from.

This prevents the EA from placing a random pending order before a Fair Value Gap has been detected.

The Count Trades block checks whether there are already open trades or pending orders.

The purpose is exposure control.

The template only wants one active trade or order at a time. Without this check, the EA could keep adding pending orders whenever new FVGs appear.

This block helps prevent duplicate entries and accidental order stacking.

Condition:

Current market price > BullFVGHigh

Plain English:

The EA checks whether the current price is still above the stored FVG entry level.

For a bullish FVG pullback entry, the pending buy order should be placed below the current price at the stored FVG level.

This block acts as a safety check before placing the pending order.

If price is not above BullFVGHigh, the setup is no longer in the expected position for this specific entry logic.

Open Price Level:

Custom Price Level = BullFVGHigh

Plain English:

The EA places a buy pending order at the stored upper boundary of the bullish Fair Value Gap.

Because BullFVGHigh stores Candle ID 1 low, the pending buy order is placed at that exact price level.

In this template, the order is usually placed as a buy limit because the current price should be above BullFVGHigh when the order is created.

The Buy Pending Order block automatically decides whether the order is a buy limit or buy stop based on the open price relative to the current market price.

Check out 04:39 in this video where Nico is explaining that with a hands-on example.

The example template places the stop loss around Candle ID 3 low.

The take profit uses a simple fixed risk-reward structure, for example 300% of the stop-loss distance.

These are example settings only.

They are not a recommendation. You should backtest and adjust the stop loss, take profit, and risk model before using the logic in any live environment.

After the pending order is placed, the template resets the variables.

Reset:

This matters.

Once the pending order has been placed, the EA no longer needs the stored FVG level for that setup. Resetting the variables prevents the EA from placing repeated orders from the same old FVG zone.

After the reset, the EA waits for a fresh Fair Value Gap to be detected.

The template uses two decision trees because detection and execution are separate jobs.

The first tree answers:

“Do we have a valid bullish Fair Value Gap?”

The second tree answers:

“Do we have a stored FVG level, and should we place a pending order from it?”

This makes the logic cleaner:

Without this separation, the EA would be harder to control and debug.

Variables are used because the EA needs memory.

The detection tree finds the FVG boundaries at one moment in time. The order placement tree may use those values later.

The variables connect those two steps.

In this template:

This allows the EA to detect a price zone first and use it later for execution.

Runs the connected logic once when a new candle forms.

Used here to check the FVG logic once per candle instead of on every tick.

Compares two values.

Used here to check candle lows, candle highs, candle opens, candle closes, and stored variable values.

Stores or resets values.

Used here to save BullFVGHigh and BullFVGLow, then reset them after the pending order is placed.

Counts existing trades or orders.

Used here to prevent multiple active trades or pending orders from stacking.

Places a future buy order at a defined price level.

Used here to place the pending buy order at BullFVGHigh.

Candle ID 0 is still forming.

This template uses closed candles: Candle ID 1, Candle ID 2, and Candle ID 3.

That makes the logic easier to test and avoids using values from a candle that can still change.

It does not.

In this bullish FVG template, BullFVGHigh means the upper boundary of the gap.

That value is Candle ID 1 low.

It does not.

In this bullish FVG template, BullFVGLow means the lower boundary of the gap.

That value is Candle ID 3 high.

Do not remove Count Trades unless you understand the consequence.

Without Count Trades, the EA may place several pending orders or stack multiple trades.

That can quickly make the backtest harder to read and increase exposure in ways you did not intend.

If the variables are not reset after order placement, the EA may continue using old FVG levels.

That can cause repeated order placement from a level that should no longer be active.

This template is a logic component.

It helps you detect and trade from a bullish Fair Value Gap, but it does not guarantee profitability.

You still need to test and improve the logic. Common additions include trend filters, session filters, spread filters, risk settings, and stricter entry or exit rules.

Use MT5 Visual Mode to check whether the EA behaves as expected.

Look for these points:

Testing visually is important because the block logic can look abstract in the Builder. Visual Mode lets you connect the block conditions to the actual candles on the chart.

Video example in for Candle ID 1, 2, and 3 marked and the pending order placed at BullFVGHigh.

This template gives you a starting structure.

You can adjust:

The best approach is to change one part at a time, export the EA, and test the difference in MT5.

Do not change five rules at once. If performance changes, you will not know which rule caused it.

Template link: https://app.profectus.ai/?staticTemplateId=FVG&utm_source=fvgHC

The ICT Fair Value Gap template is built around a simple mechanical workflow.

It detects a bullish three-candle Fair Value Gap, stores the gap boundaries in variables, checks whether the stored level is valid for entry, places a pending buy order, and then resets the variables.

The most important part to understand is the separation between detection and execution.

The first decision tree finds and stores the FVG.

The second decision tree trades from the stored FVG level.

Once you understand that structure, you can reuse the same logic for many other price zones and strategy components.

Templates are for educational purposes only. Always backtest, validate, and adjust your logic before using it in live trading.