Order Types in Trading: IOC, FOK, OCO, Iceberg, Pegged

Jibin JoseKnowledge Base

An order type is the instruction that tells a venue how to price and match an order, while a time-in-force instruction tells it how long that order should remain live; together, and combined with conditional instructions such as one-cancels-the-other (OCO), they give an institutional desk control over price, duration and display without changing the underlying instrument or quantity.

Executive Summary

What: Institutional order types fall into three families: order types that set how an order is priced and matched (market, limit, stop, stop-limit, pegged, iceberg, hidden, market-on-close), time-in-force instructions that set how long it stays active (Day, Good-Till-Cancel, Good-Till-Date, Immediate-or-Cancel, Fill-or-Kill), and conditional or linked instructions that connect multiple orders (OCO, one-triggers-the-other, bracket, trailing stop). How: these instructions are carried in the Financial Information eXchange (FIX) protocol through fields such as OrdType (tag 40), TimeInForce (tag 59) and ExecInst (tag 18), then translated by an Order Management System (OMS) or Execution Management System (EMS) into the specific dialect each venue accepts. Who: buy-side and sell-side trading desks, algorithmic strategy designers and connectivity teams configuring Direct Market Access (DMA) or Smart Order Routing (SOR) all rely on this vocabulary daily, though the exact set of supported instructions varies by venue and asset class.

What Are the Core Order Types Used on an Institutional Desk?

The core order types set the price condition under which an order can match: a market order accepts the best available price, a limit order sets a maximum buy or minimum sell price, and a stop order becomes a market order once a trigger price is reached. A stop-limit order behaves like a stop order but converts into a limit order rather than a market order at the trigger, trading certainty of activation for control over the execution price.

A pegged order does not carry a fixed price at all; instead it tracks a reference price, typically the primary market’s bid or offer, the midpoint of the inside quote, or a volume-weighted benchmark, and recalculates its limit as that reference moves. An iceberg (or reserve) order displays only a fraction of its total size on the book, replenishing the visible portion as it fills, while a hidden order carries no displayed size at all and rests unseen until it matches. A market-on-close order is priced at the closing auction rather than at entry, and the equivalent constructs at the open are assembled from a time-in-force instruction: a market order carrying an “at the opening” instruction produces a market-on-open, and a limit order carrying the same instruction produces a limit-on-open.

What Does Time in Force Control, and What Do IOC, FOK, GTC and GTD Mean?

Time in force controls how long an order remains eligible to match once it reaches the order book, independently of the price instruction attached to it. A Day order expires at the end of the trading session if unfilled, while a Good-Till-Cancel (GTC) order stays live until it is filled or explicitly canceled, and a Good-Till-Date (GTD) order expires at a specified future date.

Immediate-or-Cancel (IOC) requires that any quantity not matched the instant the order reaches the book be canceled, but accepts a partial fill for the rest. Fill-or-Kill (FOK) is stricter: the full order must match immediately in its entirety, or the whole order is canceled with no partial execution. Both are used to limit the time an order rests exposed on the book, which matters most for orders whose information content decays quickly, such as the aggressive slices of an execution algorithm.

What Are OCO, OTO and Bracket Orders, and How Do They Link Multiple Orders?

OCO, OTO and bracket instructions link two or more orders so that the state of one changes the state of the others, without requiring the trader to manage each leg manually. A one-cancels-the-other (OCO) instruction pairs two orders, commonly a limit order and a stop order, so that the execution of either one automatically cancels the remaining order. A one-triggers-the-other (OTO) instruction does the reverse: a parent order’s fill activates one or more child orders that were dormant until that point.

A bracket order combines both relationships around a single parent position: an OTO leg sends the parent order, and once it fills, an OCO pair made of a profit-target limit and a protective stop is activated, with either leg’s fill canceling the other. A trailing stop is a variant of a stop order whose trigger price recalculates at a fixed offset from the market as it moves favorably, then holds once the market reverses, functioning as a pegged stop rather than a fixed one.

Order Types, Time in Force and Conditional Instructions: FIX Reference Table

The table below maps each instruction to the FIX field that typically carries it, in FIX 4.4 and later; venues and brokers can restrict which values they accept, so this is a reference for the standard, not a guarantee of support on any given connection.

Instruction What it does When a desk uses it Main risk FIX tag
Market order Matches immediately at the best available price Urgent execution when price certainty matters less than fill certainty No control over execution price, exposure to slippage in thin books OrdType (40) = 1
Limit order Matches only at a specified price or better Default order type when a maximum or minimum price matters May not fill at all if the market never reaches the limit OrdType (40) = 2
Stop order Becomes a market order once a trigger price is reached Protective exit or breakout entry tied to a trigger level Fill price can gap past the trigger in fast markets OrdType (40) = 3
Stop-limit order Becomes a limit order, not a market order, once triggered When execution price control outweighs certainty of a fill after trigger May not fill after triggering if price moves through the limit OrdType (40) = 4
Pegged order Tracks a reference price (primary, market or midpoint) rather than a fixed limit Maintaining a competitive price without manual repricing Reference price can move against the order faster than it repegs OrdType (40) = P; peg type via ExecInst (18); offset via PegOffsetValue (211)
Trailing stop Stop trigger that recalculates at an offset as price moves favorably Locking in gains on a position without setting a fixed exit price Whipsaw markets can trigger the stop on a temporary reversal OrdType (40) = P with ExecInst (18) = a (Trailing Stop Peg); offset via PegOffsetValue (211)
Iceberg / reserve order Displays only a set clip of total size, replenishing it as it fills Working a large order while limiting the size signaled to the book Displayed clip can still leak intent through repeated replenishment patterns MaxFloor (111) sets the displayed quantity
Hidden order Rests on the book with no displayed size at all Minimizing signaling on venues that support non-displayed liquidity Non-displayed orders typically yield priority to displayed ones at the same price No single standardized ExecInst code; usually a venue-specific flag or a zero-display iceberg
Market-on-close Prices the order at the closing auction rather than at entry Benchmarking execution to the official close, for index and fund flows No control over the closing price itself OrdType (40) = 1 with TimeInForce (59) = 7; the legacy OrdType (40) = 5 is marked as no longer used from FIX 4.3 onward
Day Order expires unfilled at the end of the trading session Default duration when the order should not carry overnight risk Loses queue priority and expires if the session ends before a fill TimeInForce (59) = 0
Good-Till-Cancel (GTC) Order stays live until filled or explicitly canceled Resting limit orders meant to persist across sessions Can sit forgotten and fill at a stale price well after entry TimeInForce (59) = 1
Good-Till-Date (GTD) Order expires automatically on a specified future date Time-bounded strategies that should not persist indefinitely Expiry date must be tracked and reconciled across systems TimeInForce (59) = 6
Immediate-or-Cancel (IOC) Fills what it can immediately, cancels the unfilled remainder Aggressive slices where resting risk should be minimized Partial fills can leave a residual position to manage TimeInForce (59) = 3
Fill-or-Kill (FOK) Fills the entire order immediately or cancels it in full All-or-nothing execution where partial fills are unusable Low probability of a fill in size on thin or fragmented books TimeInForce (59) = 4
At-the-opening / at-the-close Order participates only in the opening or closing auction Benchmarking to the official open or close print No participation, and no fill, outside the auction window TimeInForce (59) = 2 (opening); 7 (close)
One-Cancels-the-Other (OCO) Fill of either linked order automatically cancels the other Setting a profit target and a protective stop on the same position at once Latency between the two venues can let both legs fill before cancellation lands ContingencyType (1385) = 1
One-Triggers-the-Other (OTO) / bracket A parent order’s fill activates one or more dormant child orders Automating an exit plan the moment an entry order fills Child orders are inert and provide no protection before the parent fills ContingencyType (1385) = 2 (bracket combines OTO and OCO, no single tag)

Do All Trading Venues Support the Same Order Types?

No. Each venue publishes its own rulebook of supported order types, time-in-force values and matching-engine behavior, and no single instruction set is universal across exchanges, multilateral trading facilities and non-displayed venues. A pegged order accepted on one venue may have no equivalent on another, an iceberg’s minimum displayed clip can differ by market, and some time-in-force values, such as at-the-opening, only apply where an opening auction exists at all. Connectivity teams manage this variation at the FIX session and gateway level; our article on market connectivity for institutional desks covers how that layer is built and maintained.

How Do the OMS and SOR Translate These Instructions Into Venue-Specific Orders?

An Order Management System (OMS) captures the trader’s intent, order type, time in force and any linked instructions, in a single internal representation, then an Execution Management System (EMS) and Smart Order Routing (SOR) engine translate that representation into the FIX dialect and order type each destination venue actually accepts, splitting a parent order into child orders where needed and mapping a request such as “iceberg, GTC, primary peg” onto whatever combination of tags the venue supports. Execution algorithms extend this further by generating and adjusting child order types automatically over the life of a parent order; the mechanics are covered in our algorithmic trading product overview.

What Pre-Trade Risk Controls Apply to Aggressive Order Types?

Order types that bypass normal queue behavior, such as IOC, FOK and market orders routed with Direct Market Access (DMA), are typically subject to tighter pre-trade limits than resting limit orders, since they can execute in full before a human has a chance to intervene. Price collars, maximum order size and duplicate-order checks are applied before these instructions reach the market; our articles on pre-trade risk controls in electronic trading and DMA trading cover those controls and the access model in detail.

When Do These Order Types Fall Short?

  • Venue fragmentation: an instruction that behaves one way on a lit exchange can behave differently, or not exist, on a dark venue or a single-dealer platform, which is why routing logic, not the order type alone, often determines the outcome.
  • Latency between linked legs: OCO and bracket instructions depend on a cancellation message reaching the second venue before it can also fill, and under network or matching-engine latency both legs can execute, leaving an unintended position.
  • Signaling despite concealment: iceberg and hidden orders reduce, but do not eliminate, information leakage; repeated replenishment of an iceberg’s displayed clip can itself become a detectable pattern.
  • Pegged orders in fast markets: a peg recalculates on each reference update, but during a rapid move the reference itself can shift faster than the repeg cycle, so the effective price achieved can lag the intended target.
  • FOK and large size: requiring an entire quantity to match immediately becomes progressively less likely to succeed as order size grows relative to displayed liquidity, particularly outside the most liquid instruments.

None of this constitutes trading or compliance advice; which order types, time-in-force values and conditional instructions are appropriate for a given order depends on the instrument, the venue, the firm’s own risk policy and its regulatory obligations, and that determination remains the responsibility of the trading desk and its compliance function.

How Quod Supports Order Type Configuration and Routing

Quod Financial is not a venue and does not define which order types or time-in-force values a market accepts; those rules are set by each exchange, multilateral trading facility or venue operator. What the Quod platform provides is the layer that lets a desk express an order once, market, limit, pegged, iceberg, OCO or otherwise, inside its EMS, and have the SOR and connectivity layer translate it into the specific FIX fields and values each destination venue supports, without the trader having to track every venue’s rulebook manually. Order type selection and repegging logic can also be embedded inside execution algorithms rather than set once at order entry; details are covered in the Algorithmic Trading product overview. Quod’s connectivity, documented in the FIX protocol article, handles the message-level translation; it does not extend the set of order types a venue itself is willing to accept.

Frequently Asked Questions

What is the difference between IOC and FOK orders?

Immediate-or-Cancel (IOC) fills whatever quantity it can immediately and cancels the rest, accepting a partial fill. Fill-or-Kill (FOK) requires the entire order to fill immediately or cancels it in full, with no partial execution accepted.

What is a pegged order and what does it peg to?

A pegged order tracks a reference price rather than carrying a fixed limit, commonly the primary market’s bid or offer, the midpoint of the inside quote, or a volume-weighted benchmark, and its effective price recalculates as that reference moves.

How is an iceberg order different from a hidden order?

An iceberg order displays a fixed clip of its total size on the book and replenishes it as that clip fills, so part of the order is always visible. A hidden order displays no size at all and rests entirely unseen until it matches.

What is the difference between GTC and GTD orders?

A Good-Till-Cancel (GTC) order stays live until it is filled or explicitly canceled, with no built-in expiry. A Good-Till-Date (GTD) order expires automatically on a specified future date without requiring a manual cancellation.

Do all venues accept the same order types?

No. Each venue publishes its own supported order types, time-in-force values and matching-engine behavior, so an instruction accepted on one venue may have no equivalent, or a different implementation, on another.

What is a bracket order?

A bracket order combines a one-triggers-the-other (OTO) relationship, where a parent order’s fill activates child orders, with a one-cancels-the-other (OCO) pair, typically a profit-target limit and a protective stop, so that filling either exit leg cancels the other.

Does the FIX protocol itself define which order types a venue must support?

No. The FIX protocol standardizes how an order type is encoded and transmitted, through fields such as OrdType and TimeInForce, but each venue independently decides which of those values it will accept and how its matching engine will behave for each one.

What is the main risk of using aggressive order types like IOC or market orders?

These instructions can execute in full, or partially, before a human has an opportunity to intervene, which is why they are typically subject to tighter pre-trade risk limits, such as price collars and maximum order size, than resting limit orders.

Relevant Products

To see how order type selection, pegging and routing are configured inside a single OMS/EMS workflow, request a demo, download the product brochure, or contact the Quod Financial team directly.