SHARKRULE / Learn

Stop Market vs Stop Limit: why a triggered order may not fill

A stop price activates an instruction; it is not a promised sale price. A stop-limit order then needs matching buyers or sellers within its limit. A conventional stop-market order instead seeks available market prices, which may differ sharply from the trigger. Even the name needs checking: Binance Spot documents different behavior for its Stop Market interface and API orders.

SharkRule · Reviewed

First separate the trigger, the price boundary and the fill

This guide explains conditional Spot orders using a hypothetical sale of an asset already held. It does not suggest what to buy, sell or use as a stop level. Stop-loss describes an intended purpose; the actual order type determines what happens after activation.

The trigger price decides when the conditional instruction becomes active. The limit price, if present, sets the worst permitted execution price: a sell limit accepts that price or higher, while a buy limit accepts that price or lower. The fill price is the price of an actual matched trade. These three values need not be equal.

A price touching the trigger does not reserve liquidity. An order can progress from waiting to active and still have zero executed quantity. It can also execute only part of its quantity. Check the exchange’s trigger reference and exact product; do not import Futures mark-price conventions into a Spot order.

Binance Spot: the interface and API can differ

Binance’s Stop Market support page, checked on 2026-10-06, says its Spot interface uses a slippage tolerance through a stop-limit mechanism. The order can execute partly, with an unfilled remainder staying open as a limit order. The label alone therefore does not establish that everything will sell immediately.

The same page says that this interface slippage-tolerance feature is not supported for API orders: API stop-market orders execute as market orders. STOP_LOSS is the Spot API name relevant to a stop-loss market instruction; STOP_LOSS_LIMIT is a separate type. Check the supported types for the exact pair and route. Do not assume an app setting carries over to an API connection.

The comparison below describes mechanisms, not a list of SharkRule features. Only the current dashboard can establish which connections and rules your account can use.

What happens after activation?
InstructionExecution constraintWhat may remain uncertain
Conventional stop-market / Binance API STOP_LOSSAttempts market execution after the trigger; the trigger is not a fill-price boundaryFinal price and full completion
Stop-limitMatches only at the limit price or betterWhether any or all of the quantity fills
Binance Spot interface Stop Market with toleranceDocumented stop-limit behavior within the selected tolerancePartial fills and an open remainder

Worked example: the market gaps below a sell limit

Every amount, price and fee here is invented for arithmetic, not a trading recommendation or a current exchange rate. Assume 10 units of fictional asset A were acquired at 105 quote units each, costing 1,050 before any acquisition fee. Compare two alternative instructions with a stop of 100; the stop-limit also has a sell limit of 99 and remains open until canceled. Assume valid order parameters and enough available balance.

The reference price crosses 100, but when the activated order reaches the book, the best available bids are 4 units at 98 and 6 units at 97. Assume those bids remain available to this order. A conventional market sale would receive (4 × 98) + (6 × 97) = 974 quote units, averaging 974 ÷ 10 = 97.40. This is an illustrative full fill, not a guarantee.

With a hypothetical 0.10% fee deducted in the quote currency, the fee is 974 × 0.001 = 0.974 and net proceeds are 973.026, approximately 973.03. Against the assumed acquisition cost, the loss is 1,050 − 973.026 = 76.974, before any acquisition fee. The stop at 100 did not cap the loss at 50.

The sell stop-limit at 99 cannot match either bid, so it sells zero units in this snapshot. All 10 units remain exposed to further price changes. No sale fee arises in this example because there is no fill; that does not mean there is no loss in the value of the holding. The order could execute later if suitable bids arrive while it remains active.

Two alternative orders against the same hypothetical bids
Order after triggerUnits soldGross sale proceedsUnits still held
Conventional market sale10974 quote units0
Sell limit at 990010

A partial fill needs a separate remainder check

Now change the hypothetical book: 4 units can be sold at 99.50, and the remaining bids are at 98. The same activated sell limit at 99 can execute those 4 units but cannot sell below 99. Gross proceeds are 4 × 99.50 = 398. At the same invented quote-currency fee, 398 × 0.001 = 0.398, leaving 397.602 net quote units, approximately 397.60.

The other 6 units remain unsold. Do not record a completed ten-unit exit or treat those six units’ displayed value as cash proceeds. A later cancellation stops only the still-open remainder once confirmed; it does not reverse the sale of the four units. More fills may arrive before cancellation is confirmed.

This example assumes an order that stays open until canceled. Other permitted duration instructions can cancel unfilled quantity instead. Read the final exchange status, executed quantity, trade records and remaining balance together. A status such as CANCELED does not erase fills that happened first.

Common mistakes when a stop appears not to work

  1. Reading the stop price as a guaranteed execution price. The trigger and the resulting order have different jobs.
  2. Using a chart touch as proof of execution. Verify the relevant pair, trigger reference, time and exchange trade records; a candle does not show your queue position or matched quantity.
  3. Assuming a wider gap between stop and limit guarantees a fill. A different boundary changes which prices are acceptable but cannot create liquidity or guarantee completion.
  4. Assuming every order called Stop Market uses identical rules. Check the exchange, Spot product and submission route, including any tolerance or price-protection behavior.
  5. Replacing an uncertain order immediately. A delayed response can hide an accepted or partly filled order; sending another can duplicate the intended action.

A practical checklist before treating an exit as complete

Use this checklist to review an order specification or a hypothetical test. It is not a recommendation to place an order or choose a stop distance.

  1. Identify the exact Spot pair, sell/buy direction, supported order type, trigger reference, limit or tolerance if any, quantity and duration.
  2. Check available balances, current pair filters, permissions and fees. A conditional instruction still depends on exchange acceptance and execution rules.
  3. Record the exchange order identifier and distinguish acceptance, activation and each fill. Keep completed quantity and open remainder separate.
  4. Reconcile the fills, fee amounts and fee assets with the final balance. Use actual charges; the example’s 0.10% quote fee is not a Binance fee quote.
  5. If a Binance order outcome is uncertain, block further Binance submissions while reconciling that order. A timeout or a pause is not confirmation of rejection or cancellation.
  6. Before any replacement, establish the original order’s final state and any still-active remainder. Pausing automation alone does not confirm cancellation of an order already sent.

What neither order type can guarantee

A stop instruction cannot guarantee a maximum loss, an exact price or complete execution. Gaps, slippage, fees, thin liquidity, exchange outages, trading restrictions and rejected or canceled orders can change the outcome. A simulation with perfect fills cannot establish how a live order would behave in a queue or during an outage.

SharkRule is independent exchange automation software, not a financial or investment advisor and not affiliated with or endorsed by Binance. This guide explains exchange mechanics; it does not confirm support for these stop types in SharkRule. Available connections and controls depend on the current dashboard, account and location, and exchange eligibility rules apply.

Frequently asked questions

Why did my stop trigger without selling anything?

Activation may have created a limit order with no suitable buyers at or above its sell limit. Also check rejection, cancellation and the actual order type. Only trade records and executed quantity establish a sale.

Does a sell limit of 99 force execution at exactly 99?

No. If a sale occurs, it can execute at 99 or a better price, such as 99.50. It cannot match bids below 99, and it may not execute at all. Fees are separate from the execution-price boundary.

Will Binance’s interface slippage tolerance apply to API stop orders?

The Binance Stop Market FAQ checked for this guide says that this tolerance feature is not supported for API orders. Verify the current documentation and your submission route instead of assuming the settings carry over.

Does canceling after a partial fill undo the sale?

No. Confirmed fills remain trades. A confirmed cancellation concerns only the unfilled remainder, and fills may occur while a cancellation request is in transit. Reconcile the final executed quantity before considering another instruction.

Official documentation and references

Prepared with AI assistance from the linked official documentation. Examples are hypothetical; no live account tests or return comparisons were performed.