What is OCO Order?

Indian market context (NSE)

Reference levels: Nifty 50 at 24,300, Reliance Industries at ₹1,300, Bank Nifty futures at 55,000 (lot size 30). Examples below show how OCO Order shows up on Indian index, equity, and futures books — update to live quotes in your journal.

Nifty 50 perspective

OCO Order on Nifty futures at 24,300: verify freeze quantity and tick size on NSE; market orders in opening auction behave differently from continuous session.

Reliance Industries perspective

OCO Order on Reliance (₹1,300): AMO and GTT rules vary by broker; intraday MIS auto-square-off at 15:15 IST overrides resting oco order unless converted.

Bank Nifty futures perspective

OCO Order on Bank Nifty (55,000): bracket/OCO availability depends on broker stack — test fill quality on 100-point stop triggers before live size.

OCO vs bracket vs cover order on Indian brokers

Do not treat these labels as interchangeable in your journal. A “bracket” fill that was really a manual entry plus OCO exits will look like perfect automation in broker UI while your process score should mark it as discretionary entry + OCO exit.

Worked example: Bank Nifty OCO after a long call

You buy one lot of Bank Nifty 52,000 CE at ₹185 after a morning breakout. Immediately place an OCO: sell limit at ₹260 (target) and stop-market at ₹140 (stop). Planned risk is ₹45 × lot size before charges. If the stop fills on a fakeout, the target cancels automatically — you should still tag the outcome as a planned stop, not a “broker error,” unless the OCO link failed and both legs somehow remained live.

• Log planned target and stop prices in the entry note before the OCO is placed.
• Record whether the exit was target-hit, stop-hit, or you cancelled OCO and managed manually.
• On weekly review, compare expectancy for OCO-managed tags vs discretionary exits on the same setup.

Failure modes that distort journal stats

• Partial fills on one leg while the other stays live — broker rules differ; screenshot the order book.
• Modifying quantity on one leg breaks the OCO pair on some platforms.
• Gap opens through the stop — stop becomes marketable and slippage exceeds planned R.
• Trailing the stop outside OCO while leaving the original target — hybrid management needs a separate tag.

How to validate

• Validate OCO Order fills against broker contract notes monthly.
• Measure median slippage in points/₹ for OCO Order on Bank Nifty vs mid-caps.
• Flag sessions with abnormal rejections or partial fills for separate review.
• Compare limit vs market tags only on symbols with similar liquidity.

How to track in TradeLyser

• Record order type, limit price, fill price, and latency on the trade.
• Tag “slippage > plan” when OCO Order fills worse than expected.
• Monthly slippage report by symbol and order type in analytics.
• Reconcile with broker order log quarterly.

Best practices

• Choose OCO Order before the move, not after FOMO entry.
• Default to limits on illiquid mid-caps; markets on urgent exits only.
• Log rejected orders — they reveal unrealistic limit discipline.
• Review slippage in R-multiples, not only rupees.

Common pitfalls

• Chasing with market orders after OCO Order already moved.
• Using limits on fast Bank Nifty breaks without timeout rules.
• Not recording partial fills — skews performance stats.
• Assuming broker fills match intended OCO Order every time.

How to use this in TradeLyser

Create tags “oco-exit” and “manual-exit” under each strategy. Every Friday, sort by exit method — if manual exits beat OCO on the same setup, your OCO distances may be too tight for Bank Nifty noise, not your edge.