Love Vtrender Charts? Check out our new offer!
Markets change their wrappers. The auction does not change its basic questions.
Orders may reach the exchange through different routes. API tagging may change. Algo classification may change. Broker systems may add another layer of naming. But once an order reaches the market, the same question applies: did this activity lift offers, hit bids, get absorbed, or move price?
Terms used in this note: Initiative Buying / Selling (IB/IS), Absorption, COT, Auction, IB30/IS30.
That is why intent matters more than the wrapper.
NSE has reiterated, through multiple circulars including NSE/SURV/55281 dated January 17, 2023 and the consolidated NSE/MSD/67753 dated April 29, 2025, that "trading members should adhere to the Market Price Protection check, by not placing any algorithmic orders on the Exchange as a market order."
The retail algo framework, effective for all brokers from April 1, 2026, gave that line teeth. Every API-routed order is now classified as algo at the exchange layer. Market orders from that population are pre-emptively rejected at the gateway.
The broker-side implementation followed. The most visible example: Kite Connect now requires every market order to carry a non-zero market_protection parameter. Without it, the order is rejected. With it, the broker wraps the market order in a limit at LTP ± protection band before it leaves the broker server.
A buy that used to read "market" now reads "limit at LTP + 1%, IOC-style fill." A sell that used to read "market" now reads "limit at LTP − 1%, IOC-style fill."
The exchange sees a limit order. The trader experienced a market order. The execution behaviour — lift the offer, sweep what's there, fill what fills — is identical for orders that complete inside the protection band.
This isn't an India-only direction. CME, ICE, and Eurex moved to bounded aggression years ago. The Indian framework has caught up.
The textbook definition of delta and Cumulative Order Trade (COT) on a footprint chart was straightforward: count market buys versus market sells. Sum them. That sum read aggression.
That definition was always a proxy. It is now a fragile one.
The exchange-side label on the same aggressive participant has shifted from "market" to "limit." But on the tape:
the offer was still lifted,
the bid was still hit,
liquidity was still consumed,
price still displaced.
Any system that depends on the exchange's order-type label to identify aggression will now under-report aggression on a significant share of orders. The print at the offer is the same print whether the wrapper said "market" or "limit-with-protection."
The intent didn't change. The packaging did.
The Vtrender Orderflow engine has never been built on the exchange's order-type field. It is built on what happens at price.
What the engine watches:
which side of the spread the volume crossed,
how much liquidity was consumed before price moved,
whether the move sustained or reverted,
where the maximum traded volume of the bar concentrated,
whether new business entered at the new price or whether the same participants are rotating,
and how the next bar's open responds to the previous bar's close.
None of those readings depend on whether the order was technically a market order, a protected limit, an IOC, or a converted residual. They depend on what the auction did.
That is why Initiative Buying (IB) and Initiative Selling (IS) remain the relevant primitives. They describe a behaviour, not a wrapper.
Initiative Buying is what shows up when a participant accepts higher prices to get filled, sustains the move, and brings fresh business in behind it. It can arrive through a raw market order in a deep contract, a protected limit at touch in a thin strike, or an IOC sweep — the behavioural signature is the same.
Initiative Selling is the symmetric pattern downward: prices accepted lower, the move sustained, fresh supply confirming.
What the engine looks for:
aggressive participation that crosses the spread,
price acceptance — the move holding rather than reverting,
imbalance expansion across rows of prices,
commitment, measured by where the bar's maximum traded volume concentrates.
None of that requires the exchange to call the order a market order. The auction reveals the intent regardless of how the order was wrapped.
Initiative does not arrive on one timeframe. The desk reads it across three.
IB3 / IS3 — the short fuse. Three-minute initiative is the immediate response layer. It catches:
breakout confirmation off range extremes,
absorption that fails,
early directional control after a balance break,
intraday inventory adjustment at speed.
It is noisy by design, because three minutes is short. In the new framework, where protected-limit wrappers have replaced raw market orders, the three-minute read is actually cleaner — fewer freak prints from blind market orders means the IB3 / IS3 signal sits on a tighter base.
IB5 / IS5 — the smoothing layer. Five-minute initiative smooths some of the three-minute noise. It is the timeframe to consult during:
expiry sessions, where raw participation can spike and reverse within minutes,
rotational opens with no clear early direction,
event-driven whipsaws around macro prints.
It separates true initiative from reactive participation.
IB30 / IS30 — the conviction layer. Thirty-minute initiative is the highest-weight read in the framework. It captures sustained commitment.
When IB30 appears, the auction is accepting higher prices across half an hour, with fresh business confirming. When IS30 appears, supply is overpowering demand across the same window.
Whether the participants behind that flow used market orders, protected limits, IOCs, or stop-converted limits is irrelevant to the read. The 30-minute auction structure reveals intent regardless of execution wrapper.
Two practical reads have shifted:
Reading aggression from delta alone is now thinner ground. Delta on its own — without context of where the volume concentrated, whether the move sustained, and whether fresh business entered — was always a partial read. With wrapper conversion now standard, it is partial enough to mislead. The desk reads delta in combination with bar structure, not standalone.
Footprint reading at the row level is now more important. Where the volume concentrates within the bar — what level held the maximum traded volume, where the imbalances stacked — does not depend on the order-type label. That row-level read is where the engine spends its attention.
The exchange has changed how aggression is packaged. It has not changed what aggression does to the auction.
Price still moves when liquidity is consumed faster than it is replaced. Acceptance still requires fresh business at the new level. Failure still shows up as inability to sustain a move with volume. The auction's two-way mechanism — accept price, reject price — is intact.
The framework's protection bands cap the worst-case fill price on aggressive orders. They do not cap aggression itself. A participant willing to pay LTP + 1% in a thin option strike is still revealing the same intent as one who would have paid market — they just can't pay outside the band.
Order Flow is not concerned with what label a broker interface gives to the route. It is concerned with what happened at the traded price. Did buyers act with initiative? Did sellers act with initiative? Did their aggression produce continuation, or did it fail?
Initiative Buying and Initiative Selling are not opinions about direction. They are structured reads of aggression at the auction level. The question is not whether an order was manually clicked or routed through an API. The question is whether the activity changed the auction — whether one side pressed hard enough at a traded price to shift state.
This distinction matters on NSE and BSE because the same Nifty or BankNifty move can arrive via different execution wrappers in different regulatory periods. The wrapper shifts. The footprint in the Order Flow chart does not.
Smart Candlesticks keep the familiar candle structure while adding execution context. A standard candle shows open, high, low, and close. A Smart Candlestick shows where initiative activity appeared inside that candle — and whether the move had confirmation or was probing into thin tape. The IB30 and IS30 signals mark where one side sustained control long enough within a 30-minute period for the read to carry weight.
MFLOW adds the next layer. Even when price moves, the participation may be new business or old business. A move driven by fresh conviction reads differently from a move caused by short covering, long liquidation, or defensive adjustment. The wrapper does not tell you which. MFLOW does.
COT — Commitment of Trade — tracks which side holds control across the session. When COT flips on repeated tests of the same level regardless of how the order arrived, that is the auction speaking, not the routing label.
For the desk, that's the operational summary:
The exchange may change the wrapper. The auction still reveals intent.
The practical read:
Let the regulatory wrapper be what it is.
Watch where the order actually trades.
Use Order Flow to read aggression at that price.
Use Smart Candlesticks to connect aggression to candle structure.
Use MFLOW to judge whether the flow is fresh or defensive.
The market does not reward the trader who knows the most labels. It rewards the trader who can read intent at the point of trade.
Related reading: Why 12,000 Contracts Moved Price When 45,000 Could Not — location and acceptance as the filter for whether size means anything. Order Flow PLR — the responsive vs initiative distinction in practice. A Beginner's Guide to Reading Order Flow Charts — aggression, delta, and pressure from the ground up.
For the full sequence, the Vtrender Learning Pathway is the starting point. For live practice on Nifty, BankNifty, Sensex, and Bankex, open Vtrender Charts.
Markets don't move because indicators change.
Indicators change because markets move.
A practical reference for NSE & BSE derivatives traders. 366 pages, built to sit open beside live charts.