What is a trigger price? Trigger vs limit price on a stop order

Trigger wakes it up, limit gets it filled

Here's the one sentence to hold on to: the trigger price and the limit price are two numbers with two different jobs — one decides when the order starts to move, the other decides what price it's willing to fill at once it does.

Think of the trigger price (stop) as an alarm clock. Once you set it, the order doesn't go and queue in the order book right away. It sits in the background, asleep, watching the market price. When the market touches your trigger, the alarm goes off and only then is the order activated and thrown into the market. Until it triggers, it's invisible in the order book and holds no place in the queue.

The limit price (limit) governs what happens after activation. When the alarm rings, the system doesn't just fill at any price with its eyes shut — it places a limit order at the limit price you set. Put another way: the trigger decides when to act, the limit decides the price you'll accept when you do.

Binance's help page on stop-limit orders adds a few details worth knowing. The trigger can sit above or below the current price; their example has the market at 2,400 and a trigger at either 3,000 or 1,500. Before the trigger is hit, the limit order isn't active, even if the market touches your limit price first. And triggered only means the limit order has gone to the order book, not that it filled: on the website the order status changes to [Submitted], and in the app a green tick appears next to [Conditions].

Once that split clicks, those two boxes stop looking redundant and start looking like two switches: the first decides when your order wakes up, the second decides whether you're willing to fill at that price once it has. For how this sits alongside plain limit and market orders, the full picture is in what the order types are and how they differ; here we're staying tight on the trigger-and-limit pairing.

Why the wrong setup triggers but never fills

This is where stop orders trip people most: the order clearly triggered, yet the position doesn't move an inch. The cause usually isn't the system — it's a limit price that doesn't make sense.

Picture a stop-loss. You're holding some coin and you figure you'll cut and walk once it drops far enough. You put the trigger somewhere below the current price — fine so far. But then you set the limit too high — say, higher than the trigger itself. Here's what happens: the price slides down, touches the trigger, the order wakes up — and it walks into the order book carrying a limit well above where the market is. Nobody wants to buy from you at that price, so the order just lies there with no counterparty. The price keeps falling, and your stop-loss is a stop-loss in name only.

The opposite can bite too. Set the limit hugging the trigger, then have the market drop hard and fast, and the price "jumps" over that narrow band — again, nothing to fill against. This is the built-in weakness of a stop-limit: it protects your price floor, but it doesn't guarantee a fill.

Stop-market vs stop-limit

Once that trap sinks in, the obvious question is: is there a way to make it fill for sure once triggered? The usual answer is the stop-market, with a catch on Binance's own screen that we'll get to. The difference between the two is worth a few paragraphs to lay out clearly.

Stop-limit: protects the price, not the fill

The stop-limit is exactly what we described above: once triggered, it posts an order at the limit price you set. The upside is you lock in a floor — your fill won't come in worse than that limit. The cost is that when the market rips straight through your limit, the order may not fill and the stop comes to nothing. It suits the mindset of "I'd rather not fill at all than accept a bad price."

Stop-market: protects the fill, not the price

The stop-market flips that: once triggered, it takes whatever's on the book and fills at market, without fussing over the exact price. In its plain form it almost always fills once triggered, so you're not left stranded. The cost is the fill price is uncertain — when it's volatile and the book is thin, your actual fill can land a fair bit worse than the trigger. That gap is slippage. What slippage is on a market order covers this in detail, and it's worth a look before you set a stop-market so you go in with eyes open.

Binance's own spot screen adds a wrinkle. Its help page on stop market orders says you set a slippage tolerance (0.1% to 5%) and the order runs in the background as a stop-limit with that tolerance; once triggered it can fill fully or partly, and whatever doesn't fill stays open as a limit maker order. So on that screen a stop-market also caps how far the fill can slip, and in a fast move part of it can still be left behind. Orders placed through the API don't support the tolerance and execute as market orders.

To close it in one line: a stop-limit protects the price, a stop-market protects the fill. One fears filling too badly, the other fears not getting out when it should. Neither is strictly better — it comes down to which you fear more. We won't make that call for you; we'll just lay the costs of each side by side so you can weigh them yourself.

How to order the prices on a sell stop

When a stop order throws an error or gets rejected, nine times out of ten it's because the prices are in the wrong high-to-low order. Let's walk through the case people tie themselves in knots over most — the sell stop.

The logic of a sell stop is "if it drops to a certain price, I sell." So the trigger normally sits below the current market price — meaning as the price falls and reaches that point, you act. Get that direction right and the rest follows.

Once triggered, it posts a sell order at the limit price. That limit usually goes at or a touch below the trigger, to leave room to fill: you've already decided to walk if it breaks the trigger, so setting the limit above market would mean you also don't want to sell cheap — the logic contradicts itself, and the platform will typically reject the order or throw a notice.

So for a sell stop, an easy sense of direction is: market on top, trigger below it, limit at or below the trigger. The moment you put the limit above market, or set the trigger in the wrong direction, the error shows up. Settle in your head first whether you're selling on the way down or on the way up, lock that direction in, then fill in the three numbers — far less painful than poking at it until the error clears.

This "order the prices by the rules" idea gets thornier on an OCO, because an OCO ties a take-profit and a stop-loss together, so it has to satisfy two sets of ordering constraints at once — which makes rejections more likely. If you're planning to use OCO, read what a Binance OCO is and why it keeps getting rejected next; that one spells out the hard "limit > market > trigger" rule for a sell.