Reference · Order Execution
Stop Order: Trigger Price and Execution Risk
Separate a stop order’s activation price from its eventual execution, using a gap example and checks for trigger basis, sessions and order history.
Published Updated
Published by FxTrusts, a supplier of brokerage and prop firm technology. Prepared with AI-assisted research and drafting; reviewed against the cited public sources. Examples are illustrative. Product links describe our services.
What is Stop order?
A stop order activates when its specified trigger condition is met. Under a conventional stop-market model, it then becomes an instruction to execute at available prices. The stop price is a trigger, not a guaranteed fill price; the applicable trigger basis is venue- and instrument-specific.
Understand the event that activates the order
A buy stop is commonly placed above the relevant current market level, while a sell stop is commonly placed below it. What counts as reaching that level depends on the rule: it might use bid, ask, last trade or another defined condition. The chosen platform may impose additional placement or distance restrictions. Record the actual trigger convention instead of assuming that all instruments follow the same visible chart series.
Activation and execution are separate moments
Once a conventional stop-market condition activates, the resulting order still has to execute. The available price can have moved beyond the trigger, especially during a gap, fast market or thin session. That movement can produce an execution less favorable than the stop price. A stop instruction therefore does not establish a fixed maximum loss. A stop-limit instruction changes the next stage by adding a price condition, but introduces the possibility of remaining unfilled.
Review what happened at the trigger time
A useful record includes the resting instruction, effective trigger, relevant price event, activation timestamp and resulting executions or rejection. If an account lacked sufficient resources or the instrument was unavailable when activation occurred, the platform’s policy determines the next state. MetaTrader documents that pending-order activation can still encounter checks. A support investigation should distinguish a condition that never activated from an activated instruction that could not complete.
Explain the order in its actual account context
Terms such as stop loss can describe an attached instruction rather than a standalone pending order. Netting and hedging account models can affect which position an instruction applies to and how later trades change that relationship. Confirm whether a modification replaces a position-level protection, an order-level instruction or both. Do not assume that a stop setting follows every partial close or account migration without testing the documented behavior.
A synthetic sell stop through a price gap
Assume a sell stop activates when the bid reaches 50.00 or lower. The last observed bid before a gap is 50.10; the next available bid is 49.70. Activation at that event can lead to a fill at 49.70 under the declared stop-market model. The 0.30 difference from the stop is not eliminated merely because the trigger was stored correctly.
| Event | Observed bid | Meaning |
|---|---|---|
| Before gap | 50.10 | Trigger not reached |
| Next available quote | 49.70 | Trigger condition met |
| Illustrative execution | 49.70 | Fill differs from the 50.00 trigger |
Implementation checklist
- Record the precise price series and condition used for activation.
- Separate trigger timestamp from execution timestamp.
- Check session, permission and account-state restrictions at activation.
- Explain price-gap risk without describing the stop as a guaranteed loss cap.
Sources
These documents support the reference. Check the original publication for current requirements and the limits of its scope.
- Investor.gov types of orderswww.investor.gov
- SEC trading basics investor bulletinwww.investor.gov
- MetaTrader 5 trading principleswww.metatrader5.com
Continue with the broader guides
Connect this reference to platform selection and the wider operating workflow.