Stop-Limit Orders: Two Prices and the Risk of No Fill

One instruction with two stages

The stop condition determines when the next instruction becomes active. The limit condition determines which prices that instruction may accept. In MetaQuotes' order properties, stop-limit types have a separate StopLimit price for the resulting pending limit order. Check the destination system's terminology because an order with a similar label may express the second condition differently.

This order is useful to understand precisely because it cannot guarantee both an exit and a bounded execution price. If no counterparty is available at the limit or better after activation, the trade need not happen. A position that the trader intended to close can continue moving in value.

A sell example through a price gap

Suppose a hypothetical long position is near 100.00. A sell stop-limit has a stop trigger of 99.00 and a sell limit of 98.80. Assume these values are permitted by this venue and the relevant trigger price moves directly from 99.10 to 98.50.

Possible sequence for the illustrative sell stop-limit

Event	Order consequence	Position consequence
Before trigger	Stop condition waiting	Long remains open
Trigger observed at 98.50	Sell limit becomes active at 98.80	No close is established yet
Best available bid remains 98.50	98.50 is below the acceptable sell limit	Long may remain open
Acceptable liquidity later becomes available	A fill may occur subject to quantity and rules	Only filled quantity is closed

The 0.20 distance between trigger and limit is not a guaranteed loss allowance. It is a relationship between two order prices. If the market continues lower and never offers an acceptable execution, the remaining position can lose substantially more than that price distance suggests.

Verify both prices after any translation

For a copied instruction, compare the source trigger, destination trigger, resulting limit, quantity and expiry. If an instrument uses a different price tick grid, rounding either value can change when the order activates or which fills it permits. A record containing only one “stop price” is insufficient to audit both stages.

Also record the accepted order type. Replacing a stop-limit with a stop-market, even at the same trigger, changes execution behavior. Do not silently assume equivalence when the destination supports fewer order types.

Plan the unfilled state

Decide how the open position and any active remainder will be observed after activation. A cancellation request can itself race with execution, so confirmation and final position reconciliation matter. Manual intervention or a different order can create excess quantity if an earlier order fills at the same time.

The lifetime and filling-policy reference explains why a remainder may persist, expire or be canceled. Spotware's order documentation is another primary example of platform-specific order behavior. Use current documentation and controlled account testing to establish behavior; a label alone is not sufficient evidence.