Skip to content

Order Types: Nine Names for Three Instincts

Priya's phone is open to Zerodha. Tata Motors is sitting at ₹952, and she wants in.

The button in front of her doesn't ask "do you want to buy Tata Motors." It asks something narrower: how badly do you want this, right now? Every order type that exists is just a different answer to that one question.

Speed, or a price

Priya has two honest options.

She can say "just get me in, whatever it costs" — that's a market order. It fills almost instantly, at whatever the best available price happens to be the moment it lands. Fast, but she gives up control over the exact number.

Or she can say "get me in, but only at ₹950 or less" — that's a limit order. It sits there and waits. If nobody's selling at ₹950, she doesn't get filled. She's traded speed for control.

She goes with the limit order. She's not in a hurry, and ₹950 feels like a fairer entry than chasing ₹952.

Six thousand kilometers away, Jake's looking at Tesla on Robinhood. It's trading at $228, and he's got the same two options, just in dollars instead of rupees. He also picks the limit order — $220, not a cent more. Different ticker, different currency, identical instinct: he'd rather wait than overpay.

What happens after you're in

Priya's order fills at ₹950. Now she owns the stock — and a new fear shows up: what if it drops?

She doesn't want to sit refreshing the app all afternoon, so she sets a stop-loss order at ₹930: if the price falls that far, sell automatically, no matter what. The moment it's triggered, it behaves exactly like the market order from before — get her out now, price be damned. It's not there to get her a good price. It's there to stop a bad day from becoming a terrible one.

Jake does the version of this that keeps moving. Instead of a fixed stop-loss, he sets a trailing stop — 5% below whatever Tesla's current price is. If Tesla climbs to $250, his stop climbs to $237.50 right along with it. It only ever moves in his favor. If Tesla ever reverses hard, he's protected at whatever the best level was on the way up, not the level he started at.

Some traders take the stop-loss idea one step further and add a price condition to the exit too — a stop-limit order: "once it hits ₹930, sell, but only at ₹928 or better." More control over the exit price, but a real risk attached — if the stock is falling fast, it can blow straight through ₹928 without ever giving you a fill, and you're left holding a position with no exit at all.

The order that outlives the day

Priya's limit order for Tata Motors filled the same afternoon. But she's also had her eye on Reliance for a week, waiting for it to dip to ₹1,480 — and she doesn't want to keep re-entering that order every single morning.

Most orders are day orders by default — if they don't fill by market close, they just die, and you're starting over tomorrow. Priya doesn't want that. So she sets a GTT — good-till-triggered, Zerodha's version of a standing order — and it just sits in the background for weeks, watching Reliance, ready to fire the moment it touches ₹1,480. NSE gives it a long leash: a GTT stays alive for up to 365 days before it expires untriggered. Internationally the same idea goes by GTC, good-till-cancelled — Jake sets one on Robinhood for Tesla at $200, except his leash is shorter. Robinhood cancels any GTC order that hasn't filled within 90 days. Same patience, different budget for it.

When "some of it" isn't good enough

A different problem shows up for institutional money, not individual investors like Priya or Jake — but it's worth knowing because it explains behavior you'll see on any order book.

A trading desk that wants to buy 50,000 shares right now, all at once or not at all, uses a fill-or-kill (FOK) order — the whole thing executes immediately, or the whole thing is cancelled. Nothing sits around half-done. A slightly looser cousin, immediate-or-cancel (IOC), will take whatever quantity is available right now and cancel the rest — no lingering partial order left waiting in the book.

And when that same desk wants to buy something big without spooking the market — because showing "buyer wants 50,000 shares" would make every seller raise their price — they use an iceberg order. It only displays a slice of the total, and on NSE that slice can't be just anything: the rules require the "disclosed quantity" to be at least 10% of the full order, so for 50,000 shares the smallest sliver they're allowed to show is 5,000. The moment that slice fills, another 5,000 quietly appears behind it, until the full size is done. Everyone else in the market just sees a steady trickle of 5,000-share trades, never the 50,000-share whale behind them. US venues run the same trick under a different name — a reserve order — but regulate the visible piece differently: instead of India's percentage floor, NASDAQ sets a flat minimum display size, so an equally large US order can legally show a much thinner sliver of itself than an Indian one ever could.

Automating the whole decision

Back to Priya. A few weeks in, she's tired of placing three separate orders every time she wants to trade intraday — one to enter, one for the target, one for the stop-loss. So she starts using a bracket order: she sets all three at once — buy at ₹950, sell at ₹970 if it goes her way, sell at ₹940 if it doesn't. She places it once in the morning and doesn't touch her phone again until one side triggers.

What the exchange does after you hit submit

Priya's limit order doesn't just sit there waiting — from the moment she taps submit, it's alive inside the exchange's matching engine, moving through a small set of states whether she checks her phone again or not: acknowledged, then partially filled, fully filled, cancelled, rejected, or expired if nothing happens in time. Every broker's order-history screen — Kite, Robinhood, doesn't matter which — is really just a window into which of those states an order currently sits in.

Two rules decide what happens inside that engine, and they're the same two rules on every exchange in the world.

The first is price-time priority: at any given price, whoever got there first gets filled first. Think of a queue at a ticket counter — a better price cuts the line entirely, but among orders sitting at the identical price, it's strictly first-come-first-served. Priya's ₹950 order sits behind everyone else who already offered ₹950, however long ago they placed it.

The second only matters when a trader — more realistically, a firm running several algorithms at once — accidentally sends a buy order and a sell order for the same stock at the same time. Left alone, those two orders would trade against each other: a wash trade, and both India and the US have rules against letting it happen by accident. NSE runs a PAN-based Self-Trade Prevention Check: if an incoming order would match a resting order under the same PAN, the incoming order is cancelled automatically, no exceptions. NASDAQ's version, Self Match Prevention, gives the firm more choice — cancel the older resting order, cancel the newer one, or shrink both by the overlapping size — but the worry underneath is identical: two orders from the same hand shouldn't quietly trade with each other and rack up two sets of fees for no real trade.

Same instincts, two markets

Priya never placed nine different "kinds" of orders. She placed a handful of instructions, each one answering the same underlying question in a slightly different way: speed or price, protection or exposure, visible or hidden, today or standing. Jake, on the other side of the planet, made the exact same set of decisions — just in dollars, on Tesla, on Robinhood.

The order ticket has a lot of buttons on it. But underneath, there are only ever three instincts: how fast you want it, how much downside you're willing to risk, and how much of your hand you're willing to show.

Continue the system

A curated path through the next concept, so one essay becomes a map.

Related essays

Market Abuse

Quote Stuffing and Marking the Close: When the Abuse Is the Traffic, Not the Order

Spoofing needs one fake order and one real trade it's propping up.

Spoofing needs one fake order and one real trade it's propping up. This is a different abuse — no single order has to be fake at all. Flooding a market's official reference-price window with enough rapid, aggressively-priced order traffic can walk the price on its own, because the calculation reacts to standing orders, not just completed trades. Athena Capital's 2014 'Gravy' algorithm and a 2012 Ruchi Soya futures-expiry manipulation that took SEBI nine years to fully close out are the same mechanism at two different reference-price systems, a decade apart.

Surya · 8 min read

Market Abuse

The Correction That Isn't: How Cancel and Amend Get Used to Launder a Trade

Spoofing exploits the cancel side of a trade's lifecycle.

Spoofing exploits the cancel side of a trade's lifecycle. Cherry-picking exploits the allocation step. There's a third abuse living in the same neighborhood, and it targets the operation this site's cancel/amend/delete essay treats as routine: the post-execution correction. India's client-code-modification abuse and Deutsche Bank's Russian mirror trades show what happens when 'who does this trade actually belong to' gets decided after the outcome is already known — with the audit trail relabeled as a mistake instead of a value transfer.

Surya · 8 min read

Market Abuse

Latency Arbitrage: The Millisecond Nobody Else Has

Two regulators looked at the same problem — a trader with a faster line can act on a price change before the rest of the market even knows it happened — and proposed the identical fix.

Two regulators looked at the same problem — a trader with a faster line can act on a price change before the rest of the market even knows it happened — and proposed the identical fix. One built it. One shelved it after industry pushback. What latency arbitrage actually is, why India's regulator proposed a speed bump and never deployed one, and why a US exchange built the same idea into its own legal structure instead — with paired Indian and international examples throughout.

Surya · 7 min read