Stop Order
A conditional order that activates when price reaches a specified trigger level — typically used for stop-losses (sell stops below long entries) or breakout entries (buy stops above resistance).
What is Stop Order?
A stop order is an inactive resting order that activates only when the market reaches a trigger price. Until then, the order sits dormant at the exchange — it does not appear in the visible order book and does not affect price action. Once price trades at or through the trigger, the stop converts to either a market order (stop-market) or a limit order (stop-limit) and competes for execution like any other order.
For long positions, the protective stop is a sell stop placed BELOW current price. Trigger price = stop loss level. When price drops to that level, the stop converts to a sell order to close the position. For short positions, the protective stop is a buy stop placed ABOVE current price.
Beyond stop-losses, stops are also used for breakout entries: a buy stop ABOVE a resistance level activates only if price breaks higher, capturing the breakout move while ignoring sideways chop. Trailing stops move with price, locking in profits as the trade goes the right direction.
How Stop Order works
Two stop variants exist on every major futures exchange:
Stop-Market: When triggered, converts to a market order. Guarantees the position closes (or opens, in a breakout entry) but the fill price can be worse than the trigger due to slippage. Standard for stop-losses where guaranteed exit is critical.
Stop-Limit: When triggered, converts to a limit order at a price you specify (typically same as or slightly worse than the trigger). The fill price is guaranteed but execution is not — if price gaps past your limit, the stop activates but the limit doesn’t fill, leaving you in the position. Stop-limits are used by professionals who can monitor and convert manually if needed; less common for prop firm traders who need guaranteed exits.
Trigger semantics:
- Trade-through trigger (default at CME): Stop activates when ONE TRADE prints at or through the stop price.
- Bid/ask trigger: Stop activates when the relevant bid or ask reaches the stop price (less common).
Server-side vs client-side:
- Server-side (preferred): The stop order rests at the exchange. If your platform disconnects, the stop still triggers on its own. NinjaTrader’s STP-MKT, Tradovate brackets, Rithmic’s R|Trader Pro stops are all server-side by default.
- Client-side (avoid): The stop is monitored by your local platform and submitted to the exchange when triggered. If your platform crashes or loses connection, the stop never fires. Some custom indicators or external automation tools use client-side stops — be aware.
Trailing stops: Adjust the trigger price as market moves favorably. NinjaTrader’s ATM trailing offset, Tradovate’s % or tick trailing, and platform-side trailing all serve the same goal: lock in profit while letting winners run.
Worked example
Setup: Trader buys 1 ES at 4500.00. Plan: 15-point stop loss (stop at 4485.00), 30-point profit target (sell limit at 4530.00).
Order placement: Submit BUY 1 ES MKT (entry executes at 4500.00). Then submit SELL STOP 1 ES @ 4485.00 STP-MKT (server-side stop-market) AND SELL LIMIT 1 ES @ 4530.00 (profit target). Both as OCO pair.
Outcome A (stop hits cleanly): Price drops steadily to 4485.00. Stop activates as a sell market. Order book at 4485 has good depth; fill at 4485.00 (no slippage). Realized loss: 15 points × $50 = $750. OCO automatically cancels the profit limit.
Outcome B (stop hits with slippage): ES gaps from 4488 down to 4482 on a surprise headline. The trade-through trigger fires at 4485 (one trade printed at or below). Stop converts to market. Inside bid is now 4482.00. Fill at 4482.00 (3 ticks of slippage). Realized loss: 18 points × $50 = $900 — $150 worse than planned.
Outcome C (stop-limit avoids slippage but doesn’t fill): If the trader had used a STOP-LIMIT instead with limit at 4485.00, the gap to 4482 would NOT fill. The limit at 4485 sits unfilled, the position remains long, and price continues lower to 4470 before bouncing — realized loss of 30 points or worse instead of 18. This is why most prop firm traders use stop-market, not stop-limit.
Stop Order vs related concepts
Side-by-side comparison of Stop Order against the most commonly confused alternatives.
| Concept | Definition | Category |
|---|---|---|
| Stop Order this term | A conditional order that activates when price reaches a specified trigger level — typically used for stop-losses (sell stops below long entries) or breakout entries (buy stops above resistance). | Futures Mechanics |
| Market Order | An order to buy or sell immediately at the best available price — guaranteeing execution but exposing the order to slippage based on order-book depth. | Futures Mechanics |
| Limit Order | An order to buy at or below a specified price, or sell at or above a specified price — guaranteeing your fill price but not guaranteeing execution. | Futures Mechanics |
| Bracket Order | A grouped order combining an entry order with two protective exit orders (target and stop loss) — the entry triggers the bracket; once filled, target and stop become active as an OCO pair. | General Concepts |
| OCO Order | A pair of linked orders where executing one automatically cancels the other — used to set a profit target and stop loss simultaneously without holding both as live exposure. | Futures Mechanics |
Why traders fail Stop Order
Using stop-limit instead of stop-market. Stop-limits sound safer (guaranteed price) but during fast moves they often don’t fill, leaving the trader exposed to MUCH larger losses than the planned stop. Default to stop-market for protective stops.
Placing stops at obvious levels. Round numbers (4500, 21000), prior session highs/lows, and visible swing points are where stop-running algorithms hunt. Place stops slightly beyond these levels — give yourself a buffer of 2-5 ticks past the obvious technical level.
Removing stops to avoid “getting stopped out.” The most common account-blowing pattern in prop firm trading: a trader cancels a stop because price is approaching, hoping for a bounce. The bounce doesn’t come, the loss balloons past the original stop, and a 1R loss becomes a 5R loss that fails the daily loss limit.
Using client-side stops on funded accounts. If your platform crashes during the US session and the stop never fires, a single news event can close the entire account. Always use server-side stops (NinjaTrader STP-MKT, Tradovate brackets, Rithmic stops) so the exchange holds the order regardless of your connection.
Frequently asked questions about Stop Order
What is a stop order?
A stop order is a conditional order that activates when price reaches a specified trigger level. The most common use is protective stops: sell stops below long positions, buy stops above short positions. When the market trades at or through the trigger, the stop converts to either a market order (stop-market) or a limit order (stop-limit) and competes for execution.
What is the difference between stop-market and stop-limit?
Stop-market converts to a market order on trigger — guaranteed exit but possible slippage. Stop-limit converts to a limit order on trigger — guaranteed price but possible non-fill if price gaps past your limit. For prop firm protective stops, stop-market is preferred because guaranteed exit prevents catastrophic losses during fast moves.
Are stop orders required at prop firms?
Apex Trader Funding has a "no working orders" rule that effectively requires stops on every position. Other firms (TPT, Tradeify, Lucid, FundedNext) strongly recommend but don't mandate stops. Best practice: every position has a stop the moment it's opened, regardless of firm rules. Stops are non-negotiable for funded-account longevity.
Can my stop order get "hunted" or run by market makers?
Stop-running is real but mostly affects retail-popular levels (round numbers, obvious swing points, prior day high/low). The fix isn't removing stops — it's placing them slightly beyond obvious levels (5-10 ticks past round numbers). Algorithmic stop hunters target visible clusters; a stop placed 5 ticks beyond the cluster is rarely run.
Should I use server-side or client-side stops?
ALWAYS server-side for funded accounts. Server-side stops rest at the exchange and trigger even if your platform crashes or your internet drops. Client-side stops are monitored by local software and never execute if the software fails. Modern platforms (NinjaTrader STP-MKT, Tradovate brackets, Rithmic) default to server-side — verify the order type before submitting.