Zerodha MCX options far-month contracts order rejected Kite commodity options illiquidity

Why far-month MCX commodity option orders are rejected on Kite

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

A far-month MCX commodity option rejection on Kite is a Zerodha risk-management block: orders in commodity option contracts beyond the permitted near-month window are rejected before they reach the Multi Commodity Exchange , because those contracts carry near-zero liquidity and would expose the trader to a fill at a price far from fair value. For most commodity options on Kite you can trade only the current (near) month; the next month opens one day before the current contract expires, and energy options carry a wider two-month window.

The rejection is intentional and it is set at the broker layer, not by MCX. The exchange may list option series several months out, but Zerodha’s pre-order validation refuses to forward an order in a far-dated, illiquid series. The result is a rejection that never appears in your order book, only in the order status notification, which is why the block confuses traders who expect to see a failed exchange order they can re-place.

Conflict-of-interest disclosure. This guide is published by webnotes.in 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 rejection says and where it appears

The order does not enter the MCX order book. Zerodha adds a layer of order validation that checks an order against its own rules before sending it to the exchange, and rejects anything that fails, to keep order processing on Kite fast. A far-month commodity option order fails the contract-eligibility check, so it is rejected at this stage. You will not find it in the Orders tab as a rejected exchange order; the reason shows in the order status notification (the rejection reason on the order’s status line), worded around the contract being a far-month commodity option that is blocked for illiquidity.

This is the same broker-side pre-validation that handles several other Kite blocks, so the symptom, a rejection you cannot see in the order book, is shared with rejected orders not in the order book generally.

Why far-month commodity options are illiquid

Commodity option liquidity in India concentrates almost entirely in the near-month contract. Open interest and traded volume in a gold, silver, copper or zinc option fall away sharply for any series beyond the current month, and for many commodities the further series barely trade at all. A contract with little or no resting depth has two problems that matter for an option order.

First, the last traded price can be stale or absent, so there is no reliable reference for what the option is worth right now. Second, a market or aggressive limit order placed into a thin book can execute at a price unrelated to fair value, because the only counterparty resting in the book may be far from the theoretical price. The combination, low liquidity and high volatility in the underlying commodity, is exactly the condition Zerodha cites for blocking far-month commodity options.

Bullion and base-metal options sit at the thin end of this. Energy options, by contrast, draw enough flow that Zerodha extends the tradable window, which is why the rule treats them differently.

What you can actually trade

The permitted window depends on the commodity.

Commodity option groupTradable months on Kite
Bullion (Gold, Silver and their mini variants)Current (near) month only
Base metals (Copper, Zinc, Aluminium, Lead, Nickel)Current month only
Energy: Crude Oil, Crude Oil MiniUp to two months
Energy: Natural Gas, Natural Gas MiniUp to two months

For the current-month-only contracts, the next month does not appear as tradable until one day before the current month’s contract expires. Place an order in a series beyond this window and Kite rejects it. The fix is to switch to the permitted near-month series, or to the second month where energy options allow it, and re-place the order there.

This is narrower than the futures position. MCX lists and Zerodha permits several months of commodity futures, so a trader used to rolling a far-dated futures position is often surprised that the option leg of the same commodity is restricted to the near month. The difference is liquidity: commodity futures hold volume further out than commodity options do.

The market-order restriction that travels with it

Even inside the permitted near-month series, a second restriction applies to commodity options. Market and stop-loss-market (SL-M) orders are restricted in stock and commodity options for lack of liquidity. A market order in an illiquid option can fill at a price far from the LTP because it sweeps whatever is resting in a thin book.

The workaround Zerodha documents is to use a limit order priced through the LTP so it behaves like a market order without the impact-cost risk. For a buy, set the limit price well above the LTP; for a sell, set it well below. The order then fills at any price up to your specified limit, which is the controlled equivalent of a market order. This is the same technique used for the ETF open-of-session market-order block and for market orders rejected when there are no trades in the instrument .

One constraint on the limit-through-LTP trick: a limit price placed too far from the LTP is itself rejected on stock and index options under the freak-trade band, covered at why limit orders far from the LTP are rejected . On commodity options the near-month series usually trades close enough that a sensible through-LTP limit clears, but keep the price realistic.

How this differs from other commodity-option blocks

A far-month rejection is a contract-eligibility block, not a margin or surveillance block. Three adjacent situations produce different messages.

A near-month commodity option order that fails for lack of margin is an RMS block, covered at how to fix an RMS rejection on Zerodha , and it names margin, not the contract month. A market order rejected because there are simply no trades in the instrument is the no-trades block at market order rejected because there are no trades , which can hit even a near-month contract early in the session. And a price-band rejection, covered at how to fix a price-band rejection on Zerodha , is an exchange-level DPR breach, not a broker contract block. Read the rejection reason carefully: the far-month block names the contract being a far-dated commodity option, the others name margin, no trades, or the price band.

MIS leverage interacts here too. Zerodha allows MIS intraday product for energy options but blocks MIS for all other commodity options, so a base-metal or bullion option must be taken with the NRML carry-forward product and the full SPAN-plus-exposure margin. That is a separate restriction from the far-month block, but it lands on the same illiquid bullion and base-metal series.

Frequently asked questions

Why is my far-month MCX option order rejected on Kite?
Zerodha blocks orders in far-month MCX commodity option contracts because they have almost no liquidity. With few or no resting orders, a trade can print at a price far from fair value. Only the near month, and two months for energy options, is permitted.
Which MCX option contracts can I trade on Zerodha?
For most commodity options you can trade only the current month. The next month becomes tradable one day before the current contract expires. Crude Oil, Crude Oil Mini, Natural Gas and Natural Gas Mini options allow up to two months of contracts at Zerodha.
Is the far-month block an MCX rule or a Zerodha rule?
It is a Zerodha risk-management restriction, not an MCX rejection. MCX may list further-dated option series, but Zerodha blocks them at its own order-validation layer before the order is sent to the exchange, because far-month commodity options are illiquid.
Why can't I see the rejected far-month order in my order book?
Zerodha validates the order and rejects it before sending it to MCX, to speed up order processing on Kite. A rejection at this broker layer never reaches the exchange order book, so it shows only in the order status notification, not the Orders tab.
Can I place a market order in a near-month MCX option?
Market and SL-M orders are restricted in commodity options for lack of liquidity. Use a limit order priced through the last traded price, a buy above the LTP or a sell below it, which fills like a market order up to your specified limit without the impact-cost risk of a true market order.
When does the next-month MCX option contract become available?
For most commodity options, the next month opens for trading one day before the current month’s contract expires. Until that point only the current near-month series is tradable on Kite, and orders in any further-dated series are rejected.

See also

External references

References

  1. Zerodha support, Why is an order in far-month commodity F&O contracts getting rejected? (as of 21 June 2026).
  2. Zerodha support, Which commodity options contracts can I trade on Kite? (near-month restriction; two-month window for energy options; MIS allowed only for energy options).
  3. Zerodha support, Why is my rejected order not displayed in the order book? (broker-layer pre-exchange order validation).
  4. Multi Commodity Exchange of India Limited, Contract specifications and option series listings (as of 21 June 2026).

Published by

webnotes.in 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. Revisions are tracked against the SEBI and NPCI rule changes referenced in the article.

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