Stop-Limit Trigger and Fill Worksheet
Separate the stop trigger from the limit-price condition in each scenario.
For a hypothetical sell stop at 95 and a sell limit at 94, price 96 does not trigger. Price 95 triggers and is at least 94, so it qualifies on price. Price 93 meets the stop trigger but falls below the sell limit. Across these three scenarios, two triggers are met and one price qualifies.
What this helps you check
A stop-limit order has two decisions: whether the trigger condition activates it, and whether the observed price satisfies the resulting limit. This worksheet checks independent price scenarios and keeps those conditions separate. It makes a common planning mistake visible without pretending to reproduce a live order book.
Price qualifies means a limit-price condition was met. It does not mean an order filled. This worksheet does not carry an activated order from one row into the next, model available liquidity, or infer position linkage and reduce-only behavior.
Your worksheet
No account connection requiredInputs are processed in your browser by this calculator. There is no quote lookup or file upload for the calculation. Site measurement and consent are handled separately by the site's privacy and consent controls.
CSV schema: scenario (text), observed_price (number). Header required; comma delimiter. Numeric fields use decimal points. Timestamps require Z or a numeric UTC offset. The original input remains unchanged.
Interactive calculation requires JavaScript. The method and hypothetical worked example below remain readable.
Your result
Calculated from supplied values. See the notes and boundaries before interpreting the result.
Check the example by hand
For a hypothetical sell stop at 95 and a sell limit at 94, price 96 does not trigger. Price 95 triggers and is at least 94, so it qualifies on price. Price 93 meets the stop trigger but falls below the sell limit. Across these three scenarios, two triggers are met and one price qualifies.
- Scenarios supplied
- 3
- Trigger conditions met
- 2
- Price-qualified scenarios
- 1
Exact example inputs
{
"side": "sell",
"trigger_price": "95",
"limit_price": "94",
"trigger_reference": "Last traded price",
"csv": "scenario,observed_price\nAbove trigger,96\nAt trigger,95\nBelow limit,93"
}The example is invented to demonstrate the method. It is not a current market quote, a provider's fee schedule or verified trading performance.
How the worksheet works
- Independent sell scenario triggers if observed_price<=trigger_price; buy triggers if observed_price>=trigger_price.
- After trigger, sell price qualifies if observed_price>=limit_price; buy qualifies if observed_price<=limit_price.
- A qualified price is only a price condition. Display 'Price qualifies; execution still depends on liquidity and venue rules'.
- Non-triggered scenarios cannot qualify for an activated limit order.
Price qualifies means a limit-price condition was met. It does not mean an order filled. This worksheet does not carry an activated order from one row into the next, model available liquidity, or infer position linkage and reduce-only behavior.
Boundaries to keep in view
- Observed price is a simplified scenario proxy, not a live book or a path simulation.
- Trigger reference and reduce-only/position linkage depend on the actual provider.
- Trigger met does not mean order filled.
Compare resources for this task
Stop-limit planning benefits from venue order documentation and a record of your own assumptions. Journals, chart exports and spreadsheets can support review, but their role is different from the venue that defines and executes an order.
Official sources and scope
The sources document formats, mechanisms or record workflows. The arithmetic and editorial comparison on this page use the supplied worksheet definitions.
- Kraken stop loss limit orders
Trigger activates a limit order; execution is not guaranteed and the order may be independent of the position.
Reference checked 2026-10-01. Consult the source for current product rules. - Coinbase Advanced order types
Market, limit and stop-limit mechanisms, partial fills and execution uncertainty.
Reference checked 2026-10-01. Consult the source for current product rules.