Stop Orders | Spot Trading & Execution

SPOT TRADING & EXECUTION · ORDER TYPES

A stop order is inactive until a trigger condition is met. Once triggered, a common stop-market implementation submits an executable order, prioritising exit or entry execution rather than a guaranteed price.

Risk first. The stop price is a trigger, not a guaranteed execution price. In a fast move, gap or thin market, the resulting order can fill materially beyond the trigger. Trigger source and venue rules also vary.

Last reviewed: 21 August 2026 · Educational content only

Concept
Trigger logic
Risk map
Worked example
Mistakes
Checkpoint
FAQ
Summary

Two stages: trigger, then execution

A stop order separates the decision into two stages. First, the venue monitors a specified reference price. Second, when the trigger condition becomes true, it activates the child order—commonly a market-style order for a stop-market instruction.

For a protective sell stop below the current market, activation is intended to occur after price falls to the trigger. A buy stop above the market can be used to activate after price rises through a level. The economic effect depends on the trader's position and purpose; the mechanism itself is simply conditional activation.

Terminology warning: exchanges use “stop”, “stop market”, “trigger order” and “conditional order” differently. Confirm the child-order type rather than relying on the label.

What exactly triggers the stop?

Trigger input	What it means	Why it matters
Last traded price	Most recent venue trade	A single print can activate the order
Mark/index/reference price	Derived reference used by some venues	Can differ from last trade; more common in derivatives
Bid/ask condition	Best quote reaches threshold	May trigger differently from last price
Venue-specific rule	Exchange-defined conditional logic	Exact behaviour must be read from documentation

For spot orders, the available trigger source may be simpler than on derivatives venues, but it still needs to be known. A stop stored server-side can behave differently from one simulated client-side by trading software.

Execution risks after activation

Gap risk

If price jumps through the trigger, the child market order begins from whatever liquidity is then available.

Slippage

Thin depth can produce an average execution far beyond the stop level.

Trigger noise

A brief print can activate an order even if price immediately reverses.

System dependency

Client-side stops can fail if the application, connection or device is offline; server-side stops depend on venue infrastructure.

A stop can reduce the risk of having no predefined conditional action, but it cannot make an illiquid market liquid or guarantee exit at the trigger.

Worked example

BTC trades around £80,000. A sell stop is set with a trigger at £78,000. During a fast move, the next available bids after activation are 0.4 BTC at £77,950, 0.5 BTC at £77,700 and 0.6 BTC at £77,300.

A 1 BTC stop-market sell could fill 0.4 at £77,950, 0.5 at £77,700 and 0.1 at £77,300.

Proceeds = £31,180 + £38,850 + £7,730 = £77,760 Average fill = £77,760

The £78,000 stop successfully triggered, but the realised price was £240 lower. The stop level controlled activation, not execution price.

Common mistakes and misunderstandings

Calling the stop price a guaranteed exit price.
Not checking which reference price activates the stop.
Assuming a stop prevents gaps or slippage.
Placing stops without considering normal volatility/noise around the trigger.
Assuming a client-side conditional order remains active when the software is offline.

Execution discipline: Treat stop configuration as an execution rule, not insurance. Document the trigger source, child order type and plausible slippage under stressed liquidity.

Knowledge checkpoint

Q1. What happens first when a stop-market order reaches its trigger: execution at the trigger price, or activation of a child order?

Q2. Why can a stop at £78,000 produce an average fill below £78,000?

Q3. How could last-price and bid/ask triggers activate at different moments?

Q4. Why should you distinguish venue-hosted stops from client-side simulated stops?

Self-check: A strong answer should explain both the order instruction and the execution consequence, including what can happen if liquidity or venue state changes.

FAQ

❓ Is the stop price guaranteed?

No. The stop price normally activates the order; the eventual fill depends on the child order and available liquidity.

❓ Can a stop be triggered by a brief price spike?

Yes, depending on the venue trigger source and rules.

❓ Are stop orders stored on the blockchain?

On centralised spot exchanges they are generally venue-side conditional instructions, not blockchain orders.

❓ What is the difference between stop-market and stop-limit?

Stop-market activates an executable market-style order; stop-limit activates a limit order with explicit price protection but possible non-fill.

Summary

A stop order is conditional: the trigger activates another order instruction.
Stop price is not the same as guaranteed fill price.
Trigger source, child-order type and venue hosting determine practical behaviour.
Fast markets can create substantial slippage after activation.

This building block explains execution mechanics and risk. It is not a recommendation, signal or instruction to trade any cryptoasset.