Forex order types and execution modes

An order sets conditions for a trade. Its acceptance, activation and execution are different events. Follow a hypothetical EUR/USD CFD request to see which side of the quote matters, how much can actually fill and why a stop level is not a promised execution price.

Instruction type, price agreement and quantity handling are different rules. Available combinations follow the symbol specification and provider policy.

What exactly are we asking the provider to do?

Imagine a client considering a long EUR/USD CFD with a notional amount of EUR 10,000. At EUR 100,000 per lot under the example specification, that is 0.10 lot. The screen shows bid 1.0798 / ask 1.0800. Buying uses the ask; the bid is the selling side. This is a cash-settled contract, rather than a request to receive euros in a bank account.

All prices, quantities and results in this opening case are invented. We assume an eligible account, sufficient margin, an open trading session and the stated order facilities. We will compare alternative instructions; the client is not placing all of them at once. Actual availability follows the symbol and service documentation. [1] [6]

The best ask may cover only part of the amount

For the immediate-buy alternative, suppose confirmed execution can use EUR 4,000 at 1.0800 and EUR 6,000 at 1.0802. Assume the instruction permits those prices and the full quantity executes. The average entry price is:

(4,000 × 1.0800 + 6,000 × 1.0802) ÷ 10,000 = 1.08012 USD/EUR.

The displayed 1.0800 was available for EUR 4,000, not the whole request. Relative to filling all EUR 10,000 at that first ask, the difference is 0.00012 × 10,000 = USD 1.20, or 1.2 pips at USD 1 per pip. This is a model entry-price difference, not a separate fee or the margin deposit. One order can produce several deals; read each price together with its filled quantity. [2]

A stop tells us when to act, not the eventual price

Now consider a separate alternative: a buy stop at 1.0810. In this model, its agreed trigger is the ask reaching or exceeding that level. A later quote of bid 1.0809 / ask 1.0811 meets the condition, although a bid-only chart remains below the stop.

Suppose the eventual confirmation records the full buy at 1.0813. That is 3 pips worse than the stop, but 2 pips worse than the first qualifying ask of 1.0811. Both comparisons are correct because they use different reference points. Activation did not reserve a fill at either price. Without that confirmation, the qualifying quote would establish the price condition alone. Other trigger settings must be checked separately. [1] [4]

A price limit and a quantity policy answer different questions

For a limit-order alternative, suppose the client has an accepted buy limit at 1.0801, placed while the ask was higher. Later, the available asks are EUR 4,000 at 1.0800 and EUR 6,000 at 1.0802. The second price is outside the limit. Assume the provider permits the quantity policies being compared:

  • IOC: EUR 4,000 can fill at 1.0800; the remaining EUR 6,000 is cancelled.
  • FOK: the full EUR 10,000 cannot be supplied within the limit, so none fills.

FOK does not make 1.0802 acceptable, and IOC does not turn a partial fill into the whole position. If a policy keeps a remainder active instead, its later status and expiry need checking. These are stipulated alternatives, not a claim that every retail panel offers every combination. The quantity-policy section explains the platform-specific rules. [6]

A stop-limit can activate without opening a position

Use a separate stop-limit alternative with the same 1.0810 buy trigger and, in a cTrader-style range model, an upper execution boundary of 1.0812: a 2-pip range. Assume default ask activation and a valid, accepted instruction. If the ask jumps to 1.0815, the stop condition is met but that price is outside the permitted range.

The instruction may therefore remain unfilled. A later return to the permitted range may allow execution if it is still active; it does not guarantee it. MT5 uses a different arrangement of stop and future limit levels, described in the detailed comparison. A familiar order name is insufficient to copy settings between platforms. [2] [4]

Read the result before calculating the position

Start with the accepted instruction, then establish the triggering side and time, the filled quantity and every execution price. A EUR 4,000 partial fill creates a different position from a EUR 10,000 fill. An activated but unfilled stop-limit creates no new position in our opening example. If the instruction was meant to close an existing position, non-execution can leave that exposure open.

A screenshot of a candle cannot supply missing ask ticks, quantity or server status. After a timeout, check the history and final confirmation before assuming that nothing happened or sending a duplicate. Keep these records for the later cost calculation: actual entry and exit prices already incorporate the price effects of execution. Commission, financing and conversion need their own records.

Three decisions from the order record

The questions use explicit model conditions. The first checks a trigger, the second calculates a filled price, and the third tests a price restriction. Select an answer or open the worked explanation; it also works without JavaScript.

1. A buy stop is at 1.0810. Has this quote met the stated trigger?

Assume standard ask activation. The bid is 1.0809 and the ask 1.0811. The instruction is accepted and valid, but no execution confirmation has arrived.

Show the answer and explanation

Correct answer: the condition is met, while execution remains unconfirmed. Compare ask 1.0811 with stop 1.0810. Bid 1.0809 does not prevent activation under this rule.

Neither the stop nor the observed ask proves a fill. The provider's confirmation must establish the price and quantity. Return to the trigger/fill distinction.

2. What is the average price of this fully executed EUR 10,000 request?

Confirmed fills are EUR 4,000 at 1.0800 and EUR 6,000 at 1.0802. There are no other fills. This question concerns the entry price, not fees or margin.

Show the answer and explanation

Correct answer: 1.08012 USD/EUR. The weights are 4,000/10,000 and 6,000/10,000: 0.4 × 1.0800 + 0.6 × 1.0802 = 1.08012.

Relative to an assumed full fill at 1.0800, the difference is 1.2 pips, or USD 1.20 for this notional amount. The calculation does not tell us why the prices differed. Return to available size.

3. Can the stated stop-limit fill this buy at 1.0815?

An accepted, unexpired instruction uses ask activation at 1.0810 and a 2-pip range, giving an upper buy boundary of 1.0812. The ask jumps to 1.0815. Use this range model, not MT5's separate future-limit setup.

Show the answer and explanation

Correct answer: no fill at 1.0815 under this restriction. The 2-pip range is 0.0002, so 1.0810 + 0.0002 = 1.0812. A buy at 1.0815 would exceed that boundary.

A later return may allow a fill while the instruction remains active. It is not guaranteed, and an existing position would remain exposed if this were an unfilled exit instruction. Return to the gap example.

The detailed rules behind an order confirmation

The opening case separates price conditions, quantities and fills. The full discussion below adds each order type, protection mechanisms, platform differences, execution modes and historical stress events. Its further numerical scenarios use their own assumptions, recorded here.

The numerical examples are hypothetical. Unless stated otherwise, we assume an EUR/USD CFD with a contract size of 100,000 EUR per lot, a pip of 0.0001 and illustrative non-USD conversion rates of 1.0850 USD per EUR (for EUR accounts) and 4.00 PLN per USD (for PLN accounts), with no conversion fees. Each scenario has its own bid, ask and execution price; the rate of 1.0850 does not apply to every example. The symbol specification and the provider’s execution policy determine the parameters of an actual account.

1. The order journey — from click to execution

An order from a retail platform reaches the provider’s infrastructure. The system checks the symbol, volume, permitted levels and trading availability, among other things. With a CFD, you enter into a contract with the entity identified in the agreement; this does not automatically deliver currency to your own bank account. The underlying OTC FX market is decentralised. A chart from another platform or a central bank reference rate (such as the ECB reference rate, Federal Reserve H.10 or NBP mid-rate) need not be the price your provider uses to activate and execute the order.

Execution of the contract with the client and the broker’s subsequent hedging of its risk are separate operations. Labels such as STP, ECN or A-book do not replace an execution policy. Their meaning and limitations are discussed in the section on execution models; here, we need to establish the reference price, trigger condition and outcome of a particular order.

MT5 gives an order, each deal and the resulting position separate identifiers. A single instruction can produce several deals, so reconstructing the opening case requires the links between those records, not just the final average price.[2]

Look for the sequence of events in the history, rather than just the final result. A pending order may take many days from acceptance to execution. A market buy request skips the wait for a price condition, but it still undergoes server validation and processing:

Stages of an order request
StageMeaning
SubmissionThe instruction has been sent; its acceptance by the server must be confirmed separately.
WaitingThe price condition has not yet been met.
ActivationThe condition has been met according to the selected price and system rules; this need not be the rate shown on a candlestick.
Sent for executionThe system attempts to execute the resulting order.
ExecutionAll or part of the volume has been traded — at the price available at that moment, which need not be the activation level.
Rejection / cancellation / expiryAll or the remaining part will not be executed. A requote proposes a different price, while a timeout requires checking the final status.

A stop level defines the trigger condition, while a limit defines the price boundary. In many systems, a limit has no separate stage in which it turns into another order. Even a correctly submitted instruction may later fail to meet the requirements: available account funds, trading hours or the symbol’s status may change. A “sent” message does not establish any of these conditions. After a timeout in particular, do not automatically send a duplicate without establishing whether the first instruction was executed.

1. InstructionType and directionPrice or conditionVolume and validityAcceptance confirmed2. ActivationRelevant bid or askStop / limit conditionMode and fill policyAcceptance ≠ trade3. ExecutionOne or several pricesConfirmed volumeDeal and positionNo fill is possible
Instruction, activation and execution are separate events. Confirmation that an order has been accepted is not confirmation of a trade; one instruction can be filled in several parts. This is a process model that does not assume a particular CFD hedging route.

2. Order types and position protection

Price axis: four instructions at one quote

Our illustrative EUR/USD model uses bid 1.0849 and ask 1.0851. The levels are illustrative; we omit the required minimum distance and other symbol restrictions. Each instruction is an independent alternative, rather than a recommendation to place four orders at once.

Price axis and typical order conditions
Position on the axisBuySell
1.0900: above both pricesBuy stop: normally ask ≥ 1.0900Sell limit: bid ≥ 1.0900
Ask 1.0851 / bid 1.0849A market buy uses the askA market sell uses the bid
1.0800: below both pricesBuy limit: ask ≤ 1.0800Sell stop: normally bid ≤ 1.0800

The statement “the rate touched 1.0800” is not precise enough. With bid 1.0799 and ask 1.0801, the sell-stop condition has been met, while the buy-limit condition has not. The side of the subsequent fill remains the same: buying at the ask, selling at the bid. In cTrader, changing the trigger mode can change the activation condition, so check the selected setting.

2.1. Market order — execution at an available price

Market order is an instruction to buy or sell without your own price limit. With typical FX quotations, a buy executes at the ask and a sell at the bid. Actual execution at a particular price and for a particular quantity is also called a fill. Its terms are determined by the execution rules. Execution is the priority, but the word “market” does not ensure that the entire volume is available, that there is no delay or that the price will be the one shown when you clicked. The system may reject the instruction or execute it partially if the terms allow.

Compare the confirmed price with the correct side of the quote when the request was sent. The difference from the midpoint also includes part of the spread and is not, by itself, a measure of slippage. The size of the discrepancy depends on price changes, size, transmission time and available quotes. You cannot establish it in advance simply because EUR/USD is a popular pair.

A market order can also close a position. In a netting account, an opposite trade may reduce or reverse existing exposure rather than create a new position. Check the panel to see whether you are sending a new order or selecting the closure of a specific position. We discuss account modes in the section on platforms.

Opening and closing 0.10 lot of EUR/USD: price P&L minus 2 USD, or minus 8 PLN.
With unchanged bid/ask, a full round trip costs one spread. The confirmed buy price equals the ask in this model.
Example — a market order on EUR/USD You see EUR/USD 1.0850/1.0852 (bid/ask) and submit a buy for 0.10 lot, equivalent to 10,000 EUR of exposure under our specification. Confirmed execution at 1.0852 means no slippage relative to the stated ask. If you immediately closed at the unchanged bid of 1.0850, the price P&L would be 10,000 × (1.0850 − 1.0852) = −2 USD (≈ −1.84 EUR at 1.0850 / −8 PLN at 4.00 PLN/USD). This is a 2-pip spread over the full opening and closing cycle, with no commission. The entry cost relative to the midpoint of 1.0851 is half that amount; cost accounting is developed in article 2.8.

2.2. Limit order — execution at the limit price or better

Limit order imposes a price restriction: buy no higher than the limit, sell no lower. In a retail CFD, the instruction may be held on the provider’s server; it need not be a passive quote in a central order book. Available volume and execution rules still matter. A touch of the level on an unrelated chart does not prove that the provider could have executed the order.

A limit may be filled in full, filled partially or remain open. Read the quantity as well as the price: a partial fill of 0.03 out of the requested 0.10 lot does not mean that all the planned volume entered at that price. The remainder waits, is cancelled or expires under the fill policy and time in force.

  • Buy limit in a typical OTC FX panel is set below the current ask; the buy condition concerns the ask at or below the limit.
  • Sell limit is set above the current bid; selling requires the bid to be at or above the limit.
Example — a buy limit on EUR/USD The quote is 1.0849/1.0851. A buy limit for 0.10 lot has a price of 1.0800. A bid of 1.0799 alone is insufficient if the ask is still 1.0801. When the ask falls to 1.0799, the price condition is met; execution at 1.0800 or better still depends on order handling and volume. Without execution, the instruction waits until cancellation or expiry. The stated expiry time must be interpreted in the server’s time zone. We do not assume a guaranteed fill on the first tick here.
Buy limit 1.0800: the condition is not met at ask 1.0801, but is met at ask 1.0799.
A buy limit compares the buying price with the ask. A bid below the limit alone does not prove activation; meeting the condition does not prove execution.

On an exchange, a limit can be immediately executable if its price crosses the opposing quotes; not every limit involves waiting for a pullback. Retail OTC panels often require a pending buy limit below the ask and a sell limit above the bid. This is a rule of the particular implementation. A favourable gap may allow execution at a price better than the limit; the provider’s policy determines how such price improvement is passed on.

2.3. Stop order (buy stop / sell stop)

Stop order is an instruction activated when a specified level is reached. In a typical FX mode, a buy stop is triggered by the ask at or above the stop level, and a sell stop by the bid at or below it. After activation, the system sends the trade for execution without the price restriction of a limit order. This does not guarantee activation outside trading hours or execution exactly at the stop level.

  • Buy stop is set above the current ask, for example 1.0900 when the ask is 1.0851. The ask moving to that boundary is the instruction’s condition, not confirmation of a future trend.
  • Sell stop is set below the current bid, for example 1.0800 with a bid of 1.0849. Once triggered, the selling price may be lower than the stop.

Once triggered, an ordinary stop accepts the risk of the available price. It adds no further test of breakout quality and does not check whether the move will last. If the condition was met only briefly, the executed position remains open despite a subsequent reversal. The order carries out the instruction; assessing signals belongs in the strategies section.

False-breakout risk with a buy stop A hypothetical EUR/USD buy stop at 1.0905, with a volume of 0.10 lot. The first ask that meets the condition is 1.0907, while the confirmation shows a buy at 1.0906. Relative to the stop level, the price is worse by 0.0001, or 1 pip = 1 USD (≈ 0.92 EUR / 4 PLN). Relative to the first ask of 1.0907, it is 1 pip better. These are two different reference measures. A subsequent fall in the bid below 1.0900 does not cancel the executed trade. We treat the price, activation tick and execution tick as assumptions of the model.
A reversal after a stop is a question, not an explanation. A chart can show a brief move and a reversal without identifying who traded or why. A cluster of stops is one possible amplification mechanism; it must not be asserted for an individual execution without evidence. Check both quote sides, server times, quantity and the accepted trigger. Those records help distinguish a price event from an execution problem. Stop placement is developed in the risk-management section.

2.4. Stop-limit order

Stop-limit has an activation condition and a price restriction once that condition is met. Activation does not yet mean entry. If the market skips the permitted price, the instruction may remain unfilled; it does not give you a replacement market order. Check whether the platform requires a separate limit price or a distance expressed in pips.

The same “stop-limit” label leads to different panel settings. Two hypothetical cases show why parameters should not be copied between platforms:

MetaTrader 5: A Buy Stop Limit has its stop above the current ask and the price of the future Buy Limit below the stop. With activation at 1.0905 and a limit at 1.0895, a Buy Limit at 1.0895 is created. If the ask continues to rise and does not return to the limit price, no buy occurs. A Sell Stop Limit reverses the relationship: the stop is below the bid, and the future Sell Limit is above the stop. This is the behaviour of the described MT5 implementation, not a universal price arrangement for all stop-limit orders.[2]

cTrader: an entry level of 1.0905 and a 5-pip limit range for a buy set an upper boundary of 1.0910. An ask of 1.0920 exceeds that boundary by 10 pips: a buy at that price does not satisfy the restriction. A return to the permitted range may allow execution if the order remains active. The trigger side is also configurable; the example assumes the default mode.[4]

A stop-limit exchanges the risk of a worse price for the risk of no execution. This is particularly important when trying to exit an open position: a remaining limit does not remove its exposure. When comparing it with an ordinary stop, you cannot treat the absence of slippage in the history as proof of better protection if some limits never executed at all.

The same gap: a filled stop and an unfilled stop-limit

Consider two separate alternatives for buying 0.10 lot of EUR/USD. Both activate at 1.0905, but the stop-limit alternative in the cTrader model has a 5-pip range, giving an upper boundary of 1.0910. We assume default activation by the ask, trading availability and an unexpired instruction. This compares the logic; it is not a record of actual orders.

Sequence of a hypothetical gap above the activation level
EventOrdinary buy stopBuy stop-limit with a 1.0910 boundary
The ask jumps from 1.0903 to 1.0920Activation condition metActivation condition met
Confirmed quote available for execution: 1.0921Assumed fill at 1.0921: 16 pips worse than the stopNo fill at 1.0921 — outside the limit
The ask remains above 1.0910The position is already openIn the model, the instruction keeps waiting
The ask later returns to 1.0909The return does not change the previous fillAssumed possible fill at 1.0909 if the instruction remains valid

The stop filled at 1.0921 rather than the level of 1.0905 gives a difference of 0.0016 / 0.0001 = 16 pips. With a notional amount of 10,000 EUR, this represents a 16 USD (≈ 14.75 EUR / 64 PLN) worse entry price relative to the trigger. The stop-limit avoided that cost only because it did not buy at all at that moment. Do not assign a profit or zero slippage to a missed trade. In MT5, a limit of 1.0895 after activation at 1.0905 would require an even deeper return of the ask, consistent with its different design.

2.5. Stop-loss and take-profit

Stop-loss and take-profit are associated with a position and can often be prepared when placing a pending order. They protect the resulting position only after that order is executed. MetaTrader describes them as protective levels; cTrader also provides server-side protection options. Handling of all or part of a position depends on the platform and configuration.

A stop-loss triggers closure after an adverse move relative to the set level. It need not close at a loss relative to entry: a long bought at 1.0800, with the bid now at 1.0900 and the SL moved to 1.0870, may finish with a price profit. A standard SL still does not guarantee the price. After activation, check the confirmed fill, fees and final status, especially during a gap.

Take-profit specifies an execution condition after a favourable move. Its price logic usually corresponds to a limit, but the technical method of execution and gap handling follow the provider’s policy. A TP above a long entry does not guarantee a positive net result: commission and financing may exceed the price profit. For both protections in typical FX on MT4/MT5, a long position is checked against the bid and a short against the ask.

Handling SL and TP
EventStop-lossTake-profit
The relevant quote reaches the level without a gapExecution is attempted under the stop rules; price and full quantity still require confirmationExecution under limit-order logic — no worse than the level, in accordance with the platform’s policy
A price gap through the levelAttempted execution at an available price; potentially substantial slippage, with no guarantee of the first visible quoteHandling under the TP rules; a better fill is possible, but a tick alone does not prove full execution
Flash crash (a brief spike)May activate and close — the market returns, but the position is already closedMay execute during a sudden spike
A short position’s SL is triggered by the ask — which may not appear on the chart

The FX chart in MT4 is drawn from the bid; in MT5, the chart price type is a symbol property and can be bid or last. For our short EUR/USD position, we assume an SL at 1.0850 and standard activation by the ask. The bid remains at 1.0844 while the ask rises from 1.0845 to 1.0852: the spread widens from 1 to 8 pips. The ask exceeds the SL by 2 pips, although the bid has not touched it. This is a possible explanation of activation, not automatic proof of correct execution. The ask line on a live chart helps show the difference but does not reconstruct the earlier ask high. Historical ticks on both sides and the server timestamp are required. cTrader allows other trigger conditions to be selected; do not apply the default rule to every setting.[1][5]

Stop-loss gap calculation — pips → USD / EUR / PLN

A long position of 0.10 lot in EUR/USD has a notional amount of 10,000 EUR and a pip value of 1 USD. We set the entry ask at 1.0850, the SL at 1.0800 and a hypothetical post-gap fill at a bid of 1.0740. Planned price P&L: 10,000 × (1.0800 − 1.0850) = −50 USD (≈ −46.08 EUR / −200 PLN). Executed price P&L: 10,000 × (1.0740 − 1.0850) = −110 USD (≈ −101.38 EUR / −440 PLN). The difference from the plan is 60 pips, or 60 USD (≈ 55.30 EUR / 240 PLN) of additional loss. We omit commission and financing. We assume a fill at the first available bid solely for this model; actual execution may occur later and at a different price.

Short-stop example: bid 1.0844 does not touch 1.0850, but ask 1.0852 exceeds the stop.
A short position is closed by buying. A widened ask can meet its SL condition even though the bid candlestick does not show it.
Guaranteed Stop-Loss (GSLO). Some offerings guarantee the price of a specified stop, including during a gap. Check the entity, available instrument, minimum distance, amendment conditions and how the premium is charged. For example, IG UK’s documentation ties the premium to the triggering of the guaranteed stop; this is not a rule for every provider. The SL label alone in the panel does not establish a guarantee. A GSLO does not remove other contract costs or risks across the account.[8]
CHF, 15 January 2015. The SNB discontinued the minimum exchange rate of 1.20 CHF per EUR. The abrupt change in conditions affected clients and providers. FXCM entered into a 300 million USD financing agreement with Leucadia on 16 January; Alpari UK formally entered special administration on 19 January, rather than on the day of the SNB decision. The sources document the decision and financial consequences; they do not reconstruct the price of every stop. The conclusion for this article is limited: a standard SL level does not guarantee a fill when available prices change abruptly.[9][10][11]
A 150-pip gap model for a short position. Assume a short EUR/USD entry at bid 1.0850, an SL at 1.0870 and a later buy fill at ask 1.1000. The price P&L is −150 pips; the planned loss was 20 pips, so the deterioration relative to the SL is 130 pips, not 150. At 0.10 lot, these represent a 150 USD loss, a 20 USD planned loss and a 130 USD difference (≈ 138.25, 18.43 and 119.82 EUR, or 600, 80 and 520 PLN at our illustrative rates). This is an educational model, with no attribution to historical orders after the French election. An actual case would require prices and logs from the particular provider.
Stop-out is an account mechanism, not an order type. Position closure when collateral is insufficient follows separate rules. Not every retail CFD stop-out immediately produces a separate trade on an external market: the provider’s hedging method is another layer. Thresholds, equity and the closing sequence are discussed in article 2.6 on leverage and margin.

Sensitivity to additional pips and lot exposure can be calculated with the pip calculator, the position size calculator and the profit and loss calculator. However, you cannot “calculate” future slippage exactly without knowing the execution price. Separate the planned loss at the SL level from scenarios of larger losses at a worse fill.

2.6. Trailing stop

Trailing stop automates moving the SL after a favourable move. For a long, it moves the SL up; for a short, down. On a reversal, it should not loosen the last protection. The starting condition, distance and where the mechanism runs are implementation features. The built-in trailing stop in desktop MT4/MT5 runs in the terminal, while the described cTrader protections are server-side. An external automation may have different requirements.

In a hypothetical MT4/MT5 example, a long EUR/USD position was filled at ask 1.0850, and the trailing distance is 30 pips, or 300 points with a point size of 0.00001. When the bid reaches 1.0880, the distance condition allows the SL to be set at 1.0850. At bid 1.0920, the new SL is 1.0890. If a reversal triggers the stop and the fill is exactly 1.0890, the price P&L is 40 pips: at 0.10 lot, 40 USD (≈ 36.87 EUR / 160 PLN). This is before fees. An SL at the entry price means zero price P&L with an ideal fill, rather than guaranteed zero net P&L. We assume successful updates and trading availability; the terminal does not amend the SL in an infinitesimal amount of time.

When the desktop MT4/MT5 terminal is switched off, the built-in trailing stop stops sending updates. The last accepted SL remains on the server. If trailing had not yet set the first stop and there was no separate SL, it leaves no protection in place. In cTrader, server-side trailing remains active after the application session ends. This is a difference in where the mechanism runs, not a guarantee of the execution price.[3][5]

2.7. OCO (One Cancels the Other)

OCO (One Cancels the Other) links two instructions so that an event in one cancels the other under specified rules. You need to know whether that event is activation, the first partial fill or full execution. These are not interchangeable moments. Placing two independent stops without an OCO mechanism does not ensure that they cancel each other.

OCO is not a basic built-in order type in MT4/MT5 or one of cTrader’s four main order types. It may be provided by an EA, API or an additional panel. With a local solution, check its dependence on the application remaining active and cancellation confirmations. After a partial fill of 0.04 out of a requested 0.10 lot, it also matters whether the other instruction is removed in full or its volume is reduced proportionally. Simply naming a function OCO does not establish those rules. IBKR documentation shows OCA group variants but is not a specification for your CFD.[12]

2.8. MIT (Market If Touched)

MIT (Market If Touched) sends a market request when the specified level is touched. A buy MIT has its condition below the current price, and a sell MIT above it; unlike a limit, it has no price restriction after activation. It differs from a stop in the direction from which it waits for a touch. Availability and the price used for the trigger depend on the product and interface.

With EUR/USD ask at 1.0851, a hypothetical buy MIT has a trigger of 1.0800. After that price is reached, it may send the buy for execution at 1.0802 if that price is then available. A buy limit at 1.0800 would not permit that fill. MIT does not remove rejection risk or guarantee entry near the trigger. IBKR’s description confirms the design of this order type but does not establish its availability in MT4/MT5 or with a particular CFD broker.[12]

3. Which order to use when — a decision table

Instructions by required condition
SituationOrder typeWhy
Immediate entry, with speed as the priorityMarket orderPriority given to fast execution (no price guarantee)
Entry after a pullback to support or resistanceBuy/Sell limitPrice no worse than the limit (no entry guarantee)
A buy condition above, or a sell condition below, the marketBuy/Sell stopActivation on the relevant side of the quote, with no confirmation that the move will last
An activation condition followed by a price restrictionStop-limitMay remain unfilled after a gap
Closure after a move against the set levelStop-lossMay limit a loss or protect a profit; does not guarantee the price
Taking profit without watching the screenTake-profitClosure under the specified favourable-price condition; costs still affect the net result
Protecting a growing profit in a trendTrailing stopThe SL follows the price instead of remaining fixed
Linked instructions that cancel the other orderOCOThe cancellation condition and handling of partial fills depend on the implementation
A contractual price guarantee for a specified stopGSLOApplies to selected offerings, with a premium and product conditions

4. How the platform executes an order — modes, statuses and models

4.1. Instant execution vs market execution

Instant execution and market execution are the names of MetaTrader modes, not two order types. With instant execution, the client requests execution at the submitted price; the provider may accept it or respond with a requote at different prices. With market execution, the price is established without being agreed again with the client. Slippage can be favourable or adverse; the absence of a requote window does not mean execution is compulsory. MetaTrader also provides request and exchange execution; their availability is a symbol parameter.[6]

Instant is not a measure of speed, and market execution does not prove access to an ECN. A market order under instant execution is still a market order — it simply uses a different way of agreeing the price. Other platforms’ mode names need not correspond exactly to MetaTrader’s terminology. Compare rules rather than similar labels in the panel.

4.2. Statuses, fill policies and time in force

A confirmation may indicate full execution, a partial fill, rejection or expiry. FOK requires the requested full volume or no execution; several quotes can supply it. IOC fills the available quantity and cancels the remainder. Return retains a remainder for further processing where permitted. Its availability depends on both order type and execution mode: do not apply an immediate market Buy/Sell rule to every pending limit. For a market request under MT5 Market Execution, do not assume Return is available. Read the applicable request type, symbol settings and server rules together.[2], [6]

GTC usually means valid until cancelled, DAY until the end of the trading day, and GTD until a specified date and time. MT5 also distinguishes a specified date with expiry at the end of that day. Check the server’s time zone, the symbol’s hours and the behaviour of orders and SL/TP at the day boundary. Some configurations may delete daily orders as well as protective levels. cTrader notes that an instruction activated just before expiry may execute after the stated time; expiry does not automatically cancel execution already under way.[4]

FOK and IOC: apply the quantity policy to the confirmation

Use the weighting method from the opening case for this separate hypothetical FOK request: 0.10 lot (10,000 EUR), confirmed as 0.04 lot at 1.08520 and 0.06 at 1.08540. The average is 1.08532; relative to filling the entire amount at 1.08520, the difference is 0.00012, or 1.2 pips = 1.20 USD (≈ 1.11 EUR / 4.80 PLN). Both fills together satisfy FOK’s full-quantity condition. They do not establish a promise of one price.

Change just one fact: if only 0.04 lot is available and nothing can supply the remaining 0.06, FOK fills nothing; an allowed IOC may fill 0.04 and cancel 0.06. IOC permits a partial fill rather than preventing it. These are model quotes, not data from a broker’s order book.

If the same example concerns a buy limit at 1.08530, the quote of 1.08540 is outside the price boundary. Assuming only those two quotes are available, FOK for 0.10 lot cannot execute the full amount, while an allowed IOC could fill only 0.04 at 1.08520. A quantity policy does not override a price limit.

Book or Cancel (BOC) is a separate passive-order policy in MT5. If the instruction could execute immediately when placed, it is cancelled instead of taking liquidity. MetaQuotes limits this policy to supported limit and stop-limit orders; it is neither FOK nor an instruction to guarantee a later fill.[6]

4.3. Broker execution models — the essentials

The agreement, execution policy and logs establish the counterparty, handling rules and result of a particular CFD order.
An STP or ECN label alone does not establish execution of a particular order. Check the agreement, policy and fill data; provider hedging is a separate operation.

Market maker, STP and ECN describe a different issue from instant or market execution. The former terms concern the provider’s role and how liquidity access is organised, while marketing labels are used inconsistently. For a CFD, the legal counterparty is determined by the agreement. The broker’s hedge is not automatically your order in a bank’s order book. The diagram separates the stages of client order handling; details and conflicts of interest are covered in the article on execution models.

5. Slippage — why your execution price differs from the price you clicked

Model buy stop 1.0905, first activation ask 1.0907 and buy fill 1.0906: 1 pip worse than the stop and 1 pip better than activation ask.
Slippage requires an explicit reference price. The same 1.0906 fill can be compared with stop 1.0905 or first ask 1.0907; this is a model, not an execution promise.

Slippage is the difference between the execution price and a chosen reference point. Specify whether the reference is the relevant bid/ask when the request was sent, the stop level, a quote for a particular volume or the midpoint. For a buy, a higher price is worse; for a sell, a lower price is worse. The same positive exchange-rate difference can therefore benefit the seller and disadvantage the buyer.

Main causes of slippage:

  • Price changes during processing. Transmission, validation and routing take time. Without logs, do not assign a specific number of milliseconds to every order or treat a delay as deliberate.
  • Limited quoted size. The order amount may exceed the volume available at one price. Partial fills at different prices, rejection or a reduction in executed quantity are possible; not every CFD displays a full order book from the external market.
  • A gap. The next available quote may skip the stop level. The fill price need not equal either the trigger or the first tick after the interruption.
  • Technical problems. Incomplete data, a delayed application, a connection or a server require separate diagnostics. A candlestick cannot identify where a failure occurred.

Conditions that help assess slippage risk:

  • Compare order size with an executable quote. A narrow spread for a small volume does not show the price at which a larger amount will execute.
  • Compare quiet periods, data releases and quotation interruptions. Do not draw conclusions about the entire offering from one window.
  • Separate submission, acceptance and execution times. A shorter route to the server reduces one component of delay but does not ensure a particular fill.
  • Check price and volume restrictions separately. FOK does not ensure one price, and IOC does not prevent partial execution. If you require a price boundary, you need an appropriate limit instruction.
Did you know? Positive slippage exists too Execution symmetry. In its historical CFD guidance, ESMA stated that systematically retaining price improvement for the firm while passing deterioration to the client breaches the best execution obligation. This does not mean that favourable and adverse slippage must each occur 50% of the time. Orders may have different directions, times and activation conditions. Assessment requires comparable samples and the total price for the client.[7]
Spread and slippage are separate quantities. Spread widening may trigger a stop on the ask or bid without a proportionate move in the other side. The fill may then differ further from the price at activation. We calculate their effect on costs, without deducting the spread twice from price P&L, in the article on spreads, commissions and swaps.
Documents and logs. The execution policy should specify the prices used, the rules for stops, limits, gaps, partial fills and complaints. To investigate one execution, you need the request, server response, time, quantity and relevant side of the quote. A report of executed trades alone omits rejections and cannot measure their frequency. Nor can the best advertised time substitute for an average.
GBP flash event — 7 October 2016. The BIS/Bank of England report records Reuters trades at 1.1491 at 00:07:41 BST, against a pre-event level near 1.26; other platforms reported lower trades. It separates the rapid fall from the following minutes of disrupted trading and identifies several contributing factors. Some trades were later cancelled or revised. This documents market stress, not the price at which every client’s stop executed.[14]
Scope of client protection. Best execution means an obligation to follow appropriate procedures under the applicable rules, not a guarantee of a positive result or the price of every market order. Account protection and CFD regulation are developed in article 2.6 and the section on regulation. Here, we assess whether order handling complies with the instruction and documentation.

Reconstructing a short stop from three prices

Assumptions: short 0.10 lot of EUR/USD at bid 1.0820, SL 1.0850 and a standard ask trigger. The bid later remains at 1.0844 while the ask rises to 1.0852. We assume confirmed closure at ask 1.0853, with no partial fills. All numbers are illustrative.

Plan, activation and execution of a short position
Reference pointCalculationInterpretation
Plan at SL 1.085010,000 × (1.0820 − 1.0850) = −30 USDPrice loss of 30 pips, before fees
Activation ask 1.0852(1.0852 − 1.0850) / 0.0001 = 2 pipsThe quote exceeds the stop level
Fill 1.085310,000 × (1.0820 − 1.0853) = −33 USDPrice loss of 33 pips (≈ −30.41 EUR / −132 PLN)
Fill relative to the stop3 pips × 1 USD/pip = 3 USD≈ 2.76 EUR / 12 PLN of additional loss relative to the plan
Fill relative to the activation ask1 pip × 1 USD/pip = 1 USD≈ 0.92 EUR / 4 PLN of deterioration after the first known tick meeting the condition

We do not add the spread again in this calculation: the −33 USD result already comes from the actual entry bid and exit ask. The reconstruction does not establish why the provider widened the spread or whether its handling complied with the agreement. A complaint should include the order and position numbers, selected trigger, server times, bid/ask quotes and the price and quantity of each fill. A screenshot of a bid candlestick without the ask does not prove there was no activation.

If an SL amendment is rejected, the last accepted level applies, not the value entered in the panel. If cancellation or closure was sent just before activation, the sequence of acceptance on the server matters. The time on the user’s computer may differ. Do not replace a missing confirmation with the assumption that the instruction must have been accepted.

6. Requotes — why they occur and how to reduce them

Requote is a response proposing different prices in a mode that requires them to be agreed. It is not an executed trade. The proposal may be better or worse; the time allowed to accept it and the permitted deviation depend on the system. Rejection without a new price proposal is a different event.

In MetaTrader, requotes are characteristic of instant execution. With market execution, the price is agreed in advance through acceptance of that mode’s rules, so there is no equivalent window for renewed acceptance. The order may still remain unfilled. Switching to market execution changes the type of price risk; it does not remove it or prove better execution.

When requotes occur most often:

  • Rapid quote changes while the request is being processed.
  • The requested price is not accepted under the instant execution rules.
  • Transmission or processing delays if the price changes during that time; logs establish the cause.

How to handle them:

  • Deviation in MetaTrader is expressed in platform points. With EUR/USD point size 0.00001, a value of 10 points means 0.00010, or 1 pip. A distance of 30 pips is 300 points. Do not assume that the deviation field restricts every order in every mode: check its meaning for the particular request, symbol and server. Units are developed in article 2.4.
Execution adjustments and an erroneous-price clause. If the agreement contains a “Manifest Error” clause, check its exact definition and procedure. A later adjustment to P&L alone does not show whether the original price was erroneous. Explaining an adjustment requires the agreement version applicable at the time of the trade, the provider’s stated basis, the original and adjusted fill, the time and the justification for the reference price. Separate such an adjustment from ordinary slippage and a requote. We do not attribute any historical series of cancellations here without documentation.

7. Orders on MT4/MT5 and cTrader — practical differences

Trailing-stop comparison: the local MT4/MT5 terminal and server-side cTrader protections.
Built-in MT4/MT5 trailing and server-side cTrader trailing have different requirements for continuous operation. A saved SL does not guarantee the fill price.

The platform defines the available functions, while the server and account determine which can be used for a particular instrument. This comparison concerns standard features, without additional panels or automation. Current documentation for the particular application matters more than the platform’s name in an offering.

MT4, MT5 and cTrader features
FeatureMT4MT5cTrader
Pending ordersBuy/Sell Limit, Buy/Sell StopBuy/Sell Limit, Buy/Sell Stop, Buy/Sell Stop-LimitLimit, Stop, Stop-Limit (market is an immediate order); additional types depend on the broker/API
Trailing stopLocal (requires the platform to remain open)Local (requires the platform to remain open)Server-side (works without the platform being open)
Native OCONoNo standard native OCO; additional solutions have their own rulesOutside the four basic types; possible through automation, an API or a feature of a particular implementation
Depth of Market (DOM)Yes: MT4 provides a price ladder and order-management panel; it does not by itself prove a full external order bookYes — exchange or OTC Market Depth according to the instrument and data suppliedYes — the displayed depth follows the supplied prices and quantities
Order expiry timeGTC or a specified date and time (if the broker’s server supports it)GTC, Day, Specific dateGTC or a specified date and time; options depend on the application and broker
Selectable fill policyNo standard selector equivalent to the MT5 FOK/IOC/Return controlsFOK/IOC/Return and supported BOC, depending on order, execution mode and symbolDepends on the interface, API and broker configuration
Netting vs hedgingSeparate positions as standard; local restrictions may depend on the providerMode assigned to the account by the brokerNetting or hedging according to account configuration

Under netting , there is one position per symbol. Additional buying increases its volume; an opposite trade may reduce it, close it or reverse its direction. Under hedging , a new opposite order may open a separate position instead of closing the previous one. Closure should specify the correct position identifier. In MT5, the mode is not freely selected for each order — it follows from the account. After a volume change, also check the current SL/TP; their inheritance follows separate rules.

Did you know? Trailing stops and restarting MT4 Checking trailing continuity. For desktop MT4/MT5, separate three pieces of information: whether the function is enabled in the terminal, whether the first SL has already been successfully saved on the server and the last accepted level. An external EA may also require the application to be running; simply replacing trailing with automation does not remove this requirement. cTrader provides the described server-side protections, but additional cBots and scripts have their own operating conditions.

Check the instruction against a single tick

The bid is 1.0798 and the ask 1.0801. A buy limit at 1.0800 and a sell stop at 1.0800 are waiting. Have both instructions met the standard price condition? Separately, a short position has an SL at 1.0800 checked against the ask. We omit account restrictions, hours and validity; the question concerns only the price condition.

Answer using the correct side of the quote

Buy limit: no, because ask 1.0801 is above the limit. Sell stop: yes, because bid 1.0798 is below the stop. The short position’s SL also meets its condition because ask 1.0801 has exceeded the level of 1.0800. None of these answers determines the final fill price or proves that a trade was executed.

MetaQuotes documents the MT4 DOM price ladder and order controls separately from the MT5 feature set.[13] In the EU framework, best execution considers price, costs, speed, likelihood and other relevant factors; it is not a guarantee that each market instruction achieves its displayed price.[15]

8. What to check in an execution confirmation

First compare the instruction with the result: direction, requested and executed volume, limit or stop, and the price of each fill. Then establish the reference price. For a short SL on a bid chart, the candlestick alone does not establish whether the ask met the condition. For a partial fill, an average price without the quantity is insufficient.

Read the execution mode and fill policy applicable when the order was placed. The account name does not establish whether the system used instant execution, allowed partial execution or accepted a particular trigger condition. A dated record of the specification allows the history to be compared with the rules that actually applied at the time.

Confirmed execution prices are the starting point for financial P&L. Spread and slippage may already be included in them; commission, swap and conversion must be accounted for according to the account history. The next article takes you through this stage: spreads, commissions and swaps.

FAQ — frequently asked questions

How does a market order differ from market execution?

Market is a type of buy or sell instruction. Market execution is a price-agreement mode in MetaTrader. A market order can also operate under instant execution, which may respond with a requote. Read the order type and execution mode separately.

Why did a short position’s stop-loss trigger when the candlestick did not touch the level?

In standard FX on MT4/MT5, a short position is closed by buying at the ask, and its SL checks the ask. The chart may show the bid. Spread widening can therefore meet the stop condition without the bid touching the level. Verification requires historical prices on both sides and the server time; other trigger settings may behave differently.

Does a stop-limit protect against a loss during a gap?

A stop-limit restricts the execution price after activation but may remain unfilled. If it was intended to exit a position, the exposure may remain open. Stop-limit settings have different designs in MT5 and cTrader; check the limit price or range in pips.

Does FOK guarantee execution at a single price?

No. FOK requires the full volume or no execution, but that volume may come from several quotes. A price restriction must come from the appropriate instruction. IOC permits partial execution and cancels the remainder. Policy availability depends on the symbol and mode.

Does a trailing stop work after the platform is switched off?

The built-in trailing stop in desktop MT4/MT5 requires a running terminal. The last successfully saved SL remains on the server but is no longer moved. If the first SL was never saved, trailing alone leaves no protection. The described cTrader protections run server-side; additional automation may have its own requirements.

Does a stop-loss always close a position at a loss?

No. An SL moved above a long position’s entry price or below a short position’s entry can protect a price profit. Net P&L also depends on the fill and fees. A standard stop does not guarantee the price; a contractual guaranteed stop requires separate product conditions.

Sources and further reading

  1. MetaQuotes: MT4 Order Types — Bid/ask, basic types and the bid chart.
  2. MetaQuotes: MT5 Basic Principles — Order/deal/position, netting, stop-limit and statuses.
  3. MetaQuotes: MT5 Executing Trades — Built-in terminal trailing and instruction parameters.
  4. Spotware: cTrader Orders — Stop-limit, trigger options, validity and execution after activation.
  5. Spotware: Trade Protections — Server-side protections and the four SL trigger modes.
  6. MetaQuotes: Symbol Properties — Execution modes, quantity policies, Return and symbol parameters.
  7. ESMA: Q&A on CFDs, ESMA35-36-794 — Historical guidance, section 9, paragraphs 33–35: asymmetric slippage and logs; not a current price schedule.
  8. IG UK: What is a guaranteed stop? — Example GSLO terms from one offering, not all brokers.
  9. SNB: decision of 15 January 2015 — Discontinuation of the minimum rate of 1.20 CHF/EUR.
  10. FXCM: financing announcement, SEC — 300 million USD financing, agreement dated 16 January 2015.
  11. FCA: News for customers of Alpari UK — Formal special administration on 19 January 2015.
  12. Interactive Brokers: Order Types and Algos — MIT and OCA groups; this provider’s documentation does not prove availability for every CFD.
  13. MetaQuotes: MT4 Depth of Market — Price ladder and order-management controls; the panel does not establish one global external book. Accessed 15 November 2026.
  14. BIS Markets Committee: The sterling flash event of 7 October 2016 — January 2017, printed pp. 1 and 5–9: phases, Reuters prices, multiple factors and later trade revisions. Accessed 15 November 2026.
  15. MiFID II: consolidated text of 6 June 2026 — Article 27: execution factors and client order-execution policy. EU scope; consolidated text is a documentation aid. Accessed 15 November 2026.

The numerical scenarios are our own educational models. Platform documentation and examples of offerings confirm the design of the described functions but do not replace the agreement and data for a particular account.

Your learning progress

Finished this lesson? Mark it yourself. Opening or scrolling a page never marks it complete.

Progress requires JavaScript and browser storage.

Saved only in this browser. No account or cross-device sync. Clearing site data can erase your progress.

Jarosław Wasiński

Editor-in-chief, ForexMechanics.com • Macro & FX analyst

Independent analyst and practitioner with over 20 years of experience in financial markets. Actively involved in Forex since 2007, with a focus on fundamental analysis, OTC market structure, and disciplined capital risk management.

  • Creator and editor-in-chief of MyBank.pl, providing reliable financial education since 2004.
  • Author of hundreds of in-depth market commentaries, structural analyses, and educational materials for traders and investors.
  • Advocate for market transparency, promoting education grounded in hard data and institutional reports (BIS, ESMA, CFTC).

All content is educational and informational only – it does not constitute investment advice or a recommendation. Remember: leveraged trading (Forex/CFD) carries a high risk of rapid capital loss.