GTT as a stop-loss for options buying
A GTT (Good Till Triggered) stop-loss for options buying is a single-trigger sell GTT set on a long option position on Zerodha Kite , which releases a limit sell order to the exchange when the option’s last traded price touches your trigger; it works for index and stock options but is not an SL-M, so a fast move past your limit can leave the stop unfilled. GTT gives a long-option buyer a standing exit without re-entering an order each session, but it carries three structural limits that matter more for options than for equity: it releases a limit order rather than a market order, it fires only once, and on F&O it lives only as long as the contract. This article documents whether GTT works for long options, how to set it, and the specific risks of relying on it for a long-option stop.
The GTT reference article covers the product as a whole and the index-option stoploss-invalid prompt covers the nudge you see when you skip the stop on a buy. This page is the risk-and-limitations companion for using GTT as a long-option stop.
Conflict-of-interest disclosure. This guide is published by the WebNotes Editorial Team for informational purposes and is written independently. WebNotes operates a Zerodha account-opening referral programme, disclosed on the pages that carry the referral link; this guide does not carry it and earns no referral commission from the procedure described here.
Does GTT work for long options
GTT works for buying options as a protective stop. After you buy a long call or put, you set a single-trigger sell GTT on that position, with the trigger placed below your entry premium, so that if the option falls to the trigger Zerodha releases a sell limit order to cut the loss. This applies to both index options and stock options. The mechanism is the same conditional facility used for equity: the GTT sits on Zerodha’s servers, monitors the last traded price during market hours, and submits a regular limit order when the trigger condition is met.
The most common setup is a fixed-percentage stop tied to the premium. If a trader buys an index call at Rs 80 and sets a 10 per cent stop, the GTT trigger is at Rs 72, and when the option’s last traded price touches Rs 72 the GTT releases a sell limit order to exit. Zerodha actively nudges option buyers toward exactly this, the “GTT stoploss is invalid” prompt on an option buy is the platform reminding the trader to attach a protective GTT stop before committing premium. So the product not only supports a long-option stop, it is built to encourage one.
Single trigger, not OCO, for a long-option stop
A protective stop on a single long option leg is a single-trigger sell GTT, not an OCO. OCO (One Cancels Other) pairs an upper target leg with a lower stop leg and is the tool for a held equity position where the trader wants to capture an upside target or cut a downside loss, whichever comes first. For a directional long-option buy, the immediate need is the downside stop, so the single-trigger sell is the right construction. A trader who wants a profit target as well can set OCO, but the GTT on an option is still a single-leg order against one contract; it does not span two strikes. A two-leg spread therefore needs a separate GTT on each leg, the single-leg constraint detailed in GTT for F&O on Zerodha .
The limit-order limitation: why a long-option stop can miss
The central limitation is that a GTT always releases a limit order, never an SL-M order . When the trigger fires, Zerodha sends a sell limit at your specified limit price. If the option has gapped down past that limit, a real risk on options, which move faster in percentage terms than the underlying, the sell limit rests above the falling market with no buyer at your price, and the stop does not fill.
This is the difference that bites a long-option stop. An SL-M order, by contrast, sells at market when triggered, so it exits even on a violent move, at the cost of a worse price. A GTT will not chase the option below your limit. A long option that collapses from Rs 72 toward Rs 40 on a sharp move in the underlying can leave a GTT sell limit at Rs 71 entirely unexecuted, so the trader who set the stop is still holding a decaying position. Setting the limit well below the trigger widens the fill probability but worsens the realised price, the standard trigger versus limit price trade-off, more acute on options because of their convexity and gappy quotes.
| Dimension | GTT stop on a long option | SL-M order on a long option |
|---|---|---|
| Order released | Limit sell at your limit price | Market sell when triggered |
| Fill on a fast gap | May rest unfilled above the market | Fills at market, worse price |
| Lifespan | Until contract expiry (F&O GTT) | Single session only |
| Storage | Zerodha servers (broker-server risk) | Exchange order book |
| Best for | A standing multi-day backstop | A guaranteed intraday exit |
The single-fire and re-validation problem
A GTT trigger is valid once. When the option touches the trigger, the GTT releases its one limit sell and then deactivates; it does not re-arm. If that limit sell does not execute, the GTT is marked triggered with the order unfilled, and the protection is spent for that session. Zerodha’s guidance is explicit that a GTT stop, once triggered but not executed, must be placed again the next trading day. For an option buyer this means a stop that “fired” is not the same as a stop that “worked”, and a trader who saw the GTT move to a triggered state must check whether the option was actually sold or is still in the book.
This re-placement burden interacts badly with option decay. A long option that triggered a GTT stop on day one and did not fill keeps losing time value while the trader waits to re-place the GTT the next session, so the loss the stop was meant to cap can widen overnight. Active monitoring closes that gap; a GTT alone does not.
Validity: the contract clock, not the calendar
A GTT on an option is governed by the F&O validity rule, not the one-year equity rule. It is valid only until the contract expires and is invalidated one day after the contract’s expiry. An index-option GTT is additionally cancelled whenever the contract’s lot size changes. A stop set on a weekly index option therefore has a life of days, and a stop on a monthly option a life of weeks, after which it vanishes whether or not it triggered. A buyer who rolls a position to a new expiry must set a fresh GTT on the new contract; the old GTT does not migrate. The full validity matrix across equity and F&O is in GTT validity rules on Kite .
There is one more F&O-specific risk for spread traders. If a GTT closes one side of a hedged position, the margin on the remaining leg can rise, and Zerodha may square off the position if the margin shortfall is not met. A GTT stop that fires on the long leg of a hedge can therefore leave the trader with a higher-margin naked short leg, an outcome a single-leg stop does not anticipate.
When GTT is the right stop for a long option, and when it is not
A GTT stop suits a position the trader is content to leave running across sessions with a standing backstop: a longer-dated index or stock option held as a directional or hedging bet, where the trader wants an automatic exit level without logging in daily, and accepts that a violent gap might leave the stop unfilled and require manual follow-up. For that profile the GTT’s persistence is the value, and the limit-order risk is a tolerable tail case.
A GTT stop is the wrong primary tool for a position the trader cannot afford to leave unmanaged: a large near-expiry long option where a gap-down to an unfilled limit would mean a material unhedged loss, or an intraday trade where a guaranteed market exit matters more than persistence. For those, an exchange-resident SL-M, monitored actively, is the more reliable instrument, accepting that it lasts only for the session and must be re-entered. The honest framing is that a GTT stop on a long option is best-effort protection layered on Zerodha’s servers, not a guaranteed exit, and a buyer should size the position on the premium at risk rather than on the assumption the stop will always fire and fill. The eligibility and rejection rules that decide whether a given option GTT is even accepted are in GTT order limitations and rejection reasons .
See also
- GTT order on Zerodha
- How to place a GTT order on Kite
- GTT for F&O on Zerodha
- GTT stoploss invalid for index options
- GTT validity rules on Kite
- GTT order limitations and rejection reasons
- Why a GTT triggered but did not execute
- How to modify a GTT on Kite
- How to delete a GTT on Kite
- GTT buy OCO on Zerodha
- Why a buy GTT was rejected
- How to fix a rejected sell GTT
- GTT disabled, cancelled, or expired
- SL-M order on Kite
- SL order on Kite
- Limit order on Kite
- Market order on Kite
- Trigger vs limit price
- Futures and options
- Nifty
- NRML product code
- Kite nudges
- Kite alerts
- Order validity types
- Kite
- Zerodha
- Zerodha charges
External references
- Zerodha support: Why should a stoploss be set using GTT when buying stock or index options?
- Zerodha support: Why is the prompt GTT stoploss is invalid displayed when placing an order to buy index options?
- Zerodha support: Are GTT orders available for F&O contracts?
- Zerodha support: What is the validity of a GTT order?
- Zerodha GTT terms and conditions
References
- Zerodha support, Why should a stoploss be set using GTT when buying stock or index options? (as of 21 June 2026).
- Zerodha support, Why is the prompt “GTT stoploss is invalid” displayed when placing an order to buy index options? (as of 21 June 2026).
- Zerodha support, Are Good Till Triggered (GTT) orders available for futures and options (F&O) contracts? (as of 21 June 2026).
- Zerodha support, What is the validity of a GTT order? (as of 21 June 2026).
- SEBI circular on conditional order facilities and broker-client disclosure obligations, MIRSD series.