Zerodha stop-loss trigger price permissible range LPP Kite error tick size

The stop-loss trigger price not within the exchange permissible range error

From WebNotes, a public knowledge base. Last updated . Reading time ~10 min.

The error “The difference between the limit price and trigger price for SL orders is over the exchange permissible range” on Kite means the gap between the trigger price and the limit price in your stop-loss-limit order is wider than the band the exchange allows. NSE caps that difference for all stock, currency and index F&O contracts, on both new orders and modifications, so a too-wide gap is rejected.

The fix is to narrow the gap and keep both prices inside the instrument’s limit-price-protection band, on the correct side of the last-traded price, and on a valid tick. This article covers the exact message, the NSE rule behind it, the limit-price-protection (LPP) ranges that bound a valid order, the tick-size and price-direction rules that trip the same intent, and how to set a trigger that the exchange accepts.

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.

What the message says

You place a stop-loss-limit (SL-L) order, which carries two prices: a trigger price that activates the order, and a limit price that caps the fill once it is active. Kite rejects it with “The difference between the limit price and trigger price for SL orders is over the exchange permissible range.” The rejection is about the distance between those two prices, not about either price on its own. You may have set both inside the day’s circuit limits and still be rejected, because the gap between them is too wide.

The rule applies symmetrically to new orders and to modifications of an existing SL-L order, so widening the gap on an order that was previously accepted will trip the same rejection. It applies across all stock F&O, currency F&O and index F&O contracts.

Why the block exists: the NSE permissible-range cap

The rule sits in NSE circulars for the equity, F&O and currency-derivative segments, which reject an SL-L order when the difference between the trigger price and the limit price exceeds a permitted limit. The permissible range is not a single fixed number. It is calculated per instrument from the trigger price, a percentage, and a minimum absolute range in rupees that depends on the instrument type. The purpose is pre-trade risk control: a stop-loss-limit order with a huge gap between trigger and limit can, once triggered, sweep the book far from the trigger and fill at a price the trader never intended, the same freak-trade risk that drives the broader limit-price-protection framework.

The LPP band that bounds a valid order

Alongside the trigger-limit gap, both prices in an SL-L order must sit inside the instrument’s limit-price-protection (LPP) range, the dynamic band the exchange keeps around the live price to block freak trades. The LPP range is adjusted continuously as the contract price moves.

InstrumentLPP rangeWorked example
NSE futuresPlus or minus 3 per cent around the reference priceAt a reference of Rs 20,000, orders must sit between Rs 19,400 and Rs 20,600
Options, premium above Rs 50Plus or minus 40 per centAt a premium of Rs 100, between Rs 60 and Rs 140
Options, premium below Rs 50Plus or minus Rs 20 (absolute)At a premium of Rs 10, between nil and Rs 30

For a limit order, the limit price must be inside the LPP range. For a stop-loss-limit order, both the trigger and the limit price must be inside the LPP range. So a valid SL-L order satisfies two constraints at once: the trigger-limit gap is within the permissible range, and each price is within the LPP band. A separate but related rejection, “the order was cancelled by the exchange because the price is outside the current allowed limit price protection range,” fires when a price breaches the LPP band even though the order was accepted at entry, because the band moved.

The tick-size and price-direction rules

Two further rules reject orders that look like the same mistake. The trigger price must be a multiple of the instrument’s tick size, commonly 5 paise, or the order is rejected with the tick-size error “the trigger price is not a multiple of tick size.” A trigger of 100.03 fails because it is not a multiple of 0.05; round it to 100.05.

The trigger must also sit on the correct side of the last-traded price. For a buy stop-loss the trigger is above the last-traded price; for a sell stop-loss the trigger is below the last-traded price but above the lower circuit. A trigger on the wrong side produces a different message (“trigger price can’t be higher than price” or “trigger price can’t be lesser than price”), and the order either fails or sits pending without executing. These are not the permissible-range error, but they are the rejections traders most often confuse with it, because all three concern where the trigger and limit prices sit. The SL-M-as-SL-L behaviour and the trigger-versus-limit-price distinction explain how the two prices interact once the order activates.

How to set a valid trigger

Build the order from four checks. First, narrow the gap: keep the trigger and limit prices close together so their difference is inside the permissible range. Second, keep both prices inside the LPP band for the instrument, plus or minus 3 per cent for futures, plus or minus 40 per cent or Rs 20 for options by premium. Third, set the trigger on the correct side of the last-traded price, above it for a buy stop-loss, below it for a sell stop-loss. Fourth, round the trigger to a valid tick, a multiple of 5 paise for most instruments. An order that satisfies all four is accepted.

Where you genuinely want a trigger far from the current price, a GTT order is the right tool. A Good Till Triggered order holds a resting trigger and submits the order only when the price reaches it, so it is not bound by the live permissible-range and LPP bands that constrain a standing SL-L order at entry. For a protective stop that sits well away from the current price, the GTT route avoids the permissible-range rejection entirely.

What this is not

This rejection is distinct from the other ways an order fails on Kite, and the fix differs for each. It is not a price-band rejection , which is about the limit price breaching the day’s circuit limits rather than the trigger-limit gap. It is not the no-trades market-order rejection. It is not an RMS rejection for margin, and not the order-being-processed in-transit lock. The permissible-range message is specifically about the distance between your trigger and limit prices, and the cure is to bring them closer, inside the LPP band, on the right side of the price, on a valid tick.

See also

External references

References

  1. Zerodha support, “The difference between the limit price and trigger price for SL orders is over the exchange permissible range”, applying to new and modified SL-L orders across stock, currency and index F&O (as of 21 June 2026).
  2. NSE circulars for the equity, F&O and currency-derivative segments capping the SL trigger-limit gap, with the permissible range derived from the trigger price, a percentage and a minimum absolute range.
  3. Zerodha support, limit-price-protection ranges: plus or minus 3 per cent for NSE futures, plus or minus 40 per cent for options above Rs 50, plus or minus Rs 20 below Rs 50 (as of 21 June 2026).
  4. Zerodha support, trigger price must be a multiple of tick size (commonly 5 paise) and on the correct side of the last-traded price (as of 21 June 2026).

Frequently asked questions

What does the exchange-permissible-range error on a stop-loss mean?
The gap between your trigger price and limit price in a stop-loss-limit order exceeds the range the exchange allows. NSE caps that difference for all stock, currency and index F&O contracts, so a too-wide gap is rejected on both new orders and modifications.
How do I set a valid trigger price?
Narrow the gap between the trigger and the limit price so it falls within the permissible band, keep both prices inside the limit-price-protection range for the instrument, set the trigger on the correct side of the last-traded price, and make the trigger a multiple of the tick size.
What is the limit-price-protection range?
It is a dynamic band the exchange keeps around the live price to stop freak trades. For NSE futures it is plus or minus 3 per cent; for options above Rs 50 premium it is plus or minus 40 per cent, and below Rs 50 it is plus or minus Rs 20 as an absolute value.
Which side of the last-traded price should the trigger be?
For a buy stop-loss the trigger is above the last-traded price; for a sell stop-loss it is below the last-traded price but above the lower circuit. A trigger on the wrong side leaves the order pending or rejected, a separate but common cause.
Why does my trigger get rejected for tick size?
The trigger price must be a multiple of the instrument’s tick size, commonly 5 paise. A trigger like 100.03 is rejected with a tick-size error because it is not a multiple of 0.05. Round the trigger to the nearest valid tick.
Can I use a GTT order to get around this?
Yes, where you want a trigger far from the current price. A GTT (Good Till Triggered) order holds a resting trigger and places the order only when the price is reached, which sidesteps the live permissible-range and LPP bands that apply to a standing SL-L order.

Reviewed and published by

The WebNotes Editorial Team covers Indian capital markets, payments infrastructure and retail investor procedures. Every article is fact-checked against primary sources, principally SEBI circulars and master directions, NPCI specifications and the official support documentation published by the intermediary in question. Drafts go through a second-pair-of-eyes review and a separate compliance read before publication, and revisions are tracked against the SEBI and NPCI rule changes referenced in the methodology section.

Last reviewed
Conflicts of interest
WebNotes is independent. No relationship with any broker, registrar or bank named in this article.