Stop Loss vs Stop Limit in Futures: What Each One Does When It Triggers

The difference is what the order turns into once your trigger price trades. The CFTC's glossary defines a stop order as one that becomes a market order when a price level is reached, and a stop limit order as one that takes effect on a trade at the named price and can fill only at that limit or better. One is trying to get out; the other is trying to get out at a price.

That much is the textbook answer, and on futures it is incomplete in a way that matters. CME's list of the order types Globex supports for futures does not include a plain stop market. What it includes is a stop with protection, and a stop with protection also ends up resting at a price ceiling when the market runs past it. So the real question is not whether your stop has a limit on it. It is how far away that limit sits and who chose it — you, or the exchange.

What is the difference between a stop loss and a stop limit order in futures?

A stop order becomes a market order at the trigger price; a stop limit order becomes a limit order at a price you nominate separately. Both sit dormant until a trade happens at the trigger, and on Globex neither goes on the book before then. The gap between them opens up afterwards, in what the surviving order is willing to pay.

The CFTC's glossary places a sell stop below the market and a buy stop above it, and notes stop loss order as the same instrument under another name. The same glossary carries the market-if-touched order, which also becomes a market order at a price but is placed the other way round — a sell MIT above the market, a buy MIT below. Placement, not mechanism, is what separates a stop from an MIT.

On CME Globex both stop varieties are marked futures only. The exchange's client documentation lists five order types available for futures, of which the stop limit and the stop with protection are the two that require a trigger, and neither is offered on options. In the message protocol they are two numbers in the same field: 3 for a stop with protection, 4 for a stop limit, alongside 1 for market with protection, 2 for limit and K for market limit.

What actually happens when a stop order triggers on CME Globex?

A stop is not on the order book while it waits. CME's documentation says an accepted stop does not go on the book immediately: it has to be triggered by a trade at the price it was submitted with. Until that trade prints, the stop is an instruction waiting on a condition, not liquidity anyone can hit.

The trigger condition itself differs slightly between the two types. A stop limit activates when its trigger price trades. A stop with protection activates on a trade at the trigger price or beyond it, which is what allows a fast market to trip it without printing exactly on your number.

There is also a validation step when you submit, and it depends on which market state the contract is in. During the continuous state, a buy stop's trigger has to sit above the last trade price and a sell stop's below it, with the settlement price standing in when there is no last trade to measure against. During the pre-open and no-cancel states the comparison is made against the settlement price instead. Get the relationship backwards and the order fails that check when you submit it.

Market state governs acceptance more broadly too: CME's iLink documentation confines a stop to three market states — pre-open, open and no-cancel — and rejects it in any other.

Is a stop-market order guaranteed to fill in futures?

No. A stop with protection is the closest thing CME Globex offers to a stop-market order, and it carries a price ceiling whether or not you asked for one. On trigger it enters the book as a market order carrying a protection price limit, which is worked out from the trigger: protection points are added for a buy and taken off for a sell.

It fills at every level between the trigger and that protection price limit, and whatever is left over is placed on the book at the protection price limit. That leftover is a resting limit order. It may fill a second later, or it may sit there while the market walks away.

CME's own worked example makes the shape of it concrete. Ten ESM1 contracts are bid with a stop trigger of 133000 and protection points of 300, giving a protection price limit of 133300. Two fill at 133025, three at 133200 and two at 133225 — seven of ten. The next offer is at 133375, past the ceiling, so the remaining three rest at 133300 rather than paying up.

You cannot look the protection points up here. CME documents them as usually half the product's non-reviewable range and publishes the ranges per product on its own site, so the figure varies by contract and is not reproduced in this post. What the message traffic reveals is the honest description: a stop with protection is submitted as type 3, acknowledged back as type 4 — a stop limit — and reported as type 2, a plain limit order, from the moment it triggers onward. The exchange is telling you what it really is.

What happens when a stop limit order is triggered but not filled?

It becomes an ordinary resting limit order and you stay in the trade. The trigger fires, the order goes onto the book at your limit price, it fills at any level between the trigger and that limit, and the unfilled balance simply waits there. CME's client documentation has a figure devoted to this outcome, headed as a stop limit triggered but not filled.

The geometry is easy to get backwards. A buy stop limit carries its limit above its trigger; a sell stop limit carries its limit below. The limit is the worst price you will accept, so the distance between the two numbers is the slippage you have pre-authorised, and nothing past it.

This is the trade-off in one line. A stop with protection hands the ceiling to the exchange, which places it a set distance from the trigger — a distance derived from the product rather than from your trade. A stop limit hands it to you, and a tight limit on a fast move means the order triggers, fills nothing, and leaves you holding the position with a live loss and an order sitting behind the market. If your reason for the stop was to cap the loss, a limit that the market has already left behind does not cap anything.

The comparison with a plain limit order is direct: a limit protects your price and accepts that it may not trade, which is the same bargain described in market orders versus limit orders in futures. A stop limit just delays that bargain until a trigger fires.

What can stop a futures stop order from working at all?

Three exchange mechanisms can interrupt a stop independently of how you set it up, and all three are described in the CFTC's glossary. None of them is a malfunction, and each can leave an order unfilled while it operates.

The first is stop logic functionality. The glossary entry scopes it to futures on CME's Globex system and gives its purpose as preventing the excessive price movement that cascading stops can cause. If stops firing would carry the market past predefined values, matching halts for a moment in what the entry calls a Reserved State, which leaves room for more bids and offers to arrive. Nothing matches during that halt, including your triggered stop.

The second is the daily price limit: the glossary defines it as the most a contract may move up or down in one session, measured from the previous settlement and fixed by exchange rules. A stop whose fill would require trading past that boundary cannot fill while the limit holds, which is the situation covered in limit up and limit down in futures.

The third is price banding, described in the same glossary as a CME Group and ICE mechanism that price-verifies every incoming order and rejects the ones with clearly erroneous prices, with the bands reviewed through the day and adjusted. That one bites on entry rather than exit, but it is why a stop submitted at an absurd price does not quietly rest.

One term the glossary does not carry is trailing stop — searched across the whole glossary page on 23 September 2026, along with gap and slippage, none of which appear. It is not among the five order types CME lists for Globex futures either.

Which stop type should you use on a funded futures account?

On an account with a drawdown line, the question is which failure you can afford: a fill worse than you wanted, or no fill at all. A stop with protection risks the first. A stop limit risks the second, and the second is the one that ends accounts, because the position keeps losing while the order waits.

Work it through on a Lumen account, which is a simulated account trading live market data, with a real payout on the profits. Its drawdown line is set a fixed amount under the best balance the account has ever closed a day on, and it never falls. The part that decides this question is in the drawdown article: the line is watched in real time all session rather than only at the bell, and touching it liquidates the account on the spot. Recovering afterwards does not undo the breach. A stop limit that triggers and does not fill leaves the loss running against a line that is being watched tick by tick.

The scale is easy to underestimate. On the E-mini S&P 500 one tick is worth $12.50, per the instruments table, which was checked against CME contract specifications on 31 August 2026. The drawdown article's worked example for a $50K account uses a $2,000 line, and $2,000 divided by $12.50 is 160 ticks on a single contract. At a quarter-point tick that is forty index points, and ten contracts compress the same room into sixteen ticks. An unfilled stop does not need long at that resolution.

Nothing else in the account will stop you either. None of the programs currently sold carry a daily loss limit, the rule that at many firms shuts a trader down for the session once losses pass a set figure, so the drawdown line is the only automatic brake.

FAQ

Does CME Globex accept a plain stop-market order?

Not as such. CME's client documentation lists a stop with protection rather than a bare stop market, and it reaches the book as a market order whose ceiling is the trigger adjusted by a pre-defined range of protection points — added on a buy, deducted on a sell. In the message protocol the order is submitted as type 3, acknowledged as type 4 — stop limit — and reported as a limit order from the trigger onward. Protection points are usually half the product's non-reviewable range, which CME publishes per product.

Why did my futures stop order get rejected?

Two documented reasons sit at the exchange. A stop's trigger price is validated against the market when you submit it: in the continuous state a buy stop must be above the last trade price and a sell stop below it, with settlement used if there is no last trade, while in the pre-open and no-cancel states both are compared against settlement. Separately, CME's iLink documentation limits a stop to three market states — pre-open, open and no-cancel — and has it rejected in the rest.

Can a stop limit order leave me stuck in a losing futures trade?

Yes, and that is the risk it trades for price control. CME documents that a triggered stop limit fills across the levels between its trigger and its limit, and that any quantity left unfilled goes on resting there as a limit order priced at your limit. If the market moves through your limit before the order fills, you hold the position with the order resting behind the market. On an account whose drawdown line is monitored in real time, that unfilled balance keeps losing while you wait.

Does the exchange guarantee my stop will fill at my trigger price?

No. Both Globex stop types are documented as filling across a range of prices rather than at one. A stop with protection fills between the trigger and a protection price limit set by CME, and CME's worked example shows a ten-lot filling seven contracts across three price levels before the remaining three rest at the ceiling. Beyond that, the CFTC's glossary describes stop logic functionality, which pauses matching in a Reserved State so that a cascade of stops cannot drive prices past predefined values, and a daily price limit capping how far a contract may move in one session at all.