A Fill-or-Kill (FOK) order combines the constraints of an all-or-none order with the immediacy of an immediate-or-cancel order. It mandates that the entire quantity be executed against available liquidity at the moment it reaches the matching engine. If the full size cannot be satisfied by the current resting orders, the order is killed instantly without leaving any residual quantity on the book.
Glossary
FOK

What is FOK?
A Fill-or-Kill (FOK) order is a conditional trading instruction that demands immediate and complete execution of the entire order quantity, or the entire order is canceled without any partial fill.
FOK orders are critical for strategies requiring precise position sizing without the risk of partial fills or information leakage. Unlike an IOC order, which accepts partial execution, an FOK prevents any execution unless the total demand is met, ensuring a trader never acquires an unintended fractional position that could skew a hedging ratio or arbitrage leg.
Key Characteristics of FOK Orders
Fill-or-Kill (FOK) orders enforce a strict binary execution constraint: the entire quantity must execute immediately at the specified limit price or better, or the order is canceled in its entirety. This all-or-nothing logic eliminates partial fills and is critical for strategies intolerant of fragmented positions.
Atomic Execution Guarantee
The defining characteristic of a FOK order is atomicity. The order is treated as an indivisible unit by the matching engine. If the full quantity cannot be matched against available resting liquidity in a single instant, no trade occurs. This prevents the creation of unintended, partial positions that could expose a strategy to directional risk. Unlike IOC (Immediate-or-Cancel) orders, which allow partial fills, FOK strictly enforces a complete fill or complete cancellation.
Immediate Time-in-Force Constraint
FOK orders carry an implicit Time-in-Force (TIF) of zero. They never rest on the order book. The matching engine performs a single, instantaneous liquidity check:
- Sufficient Liquidity: The entire order executes against the consolidated volume at the limit price or better.
- Insufficient Liquidity: The order is immediately canceled without any partial execution. This contrasts with Reserve (Iceberg) orders, which rest on the book and replenish, and Limit orders, which can remain open indefinitely.
Protection Against Information Leakage
By never posting to the public order book, a FOK order eliminates signaling risk. A large limit order displayed on the book signals intent and can be front-run by predatory algorithms. FOK orders probe for hidden and displayed liquidity simultaneously without revealing the parent order's existence or size. This is essential for executing large block trades in illiquid instruments where displaying any portion of the order would cause adverse price movement.
Interaction with Market Structure
FOK execution success depends heavily on venue liquidity fragmentation. In a fragmented market, a FOK order routed to a single exchange may fail even if sufficient cumulative liquidity exists across all venues. This necessitates a Smart Order Router (SOR) that can simultaneously assess consolidated depth across lit exchanges and Dark Pools before routing. A FOK order without SOR integration is highly susceptible to false negatives in fragmented markets.
Use Case: Arbitrage and Hedging
FOK orders are critical for strategies requiring precise, simultaneous execution of multiple legs:
- Statistical Arbitrage: Ensuring a basket of correlated securities fills completely to lock in a spread.
- Delta Hedging: Instantly acquiring the exact hedge quantity for an options position without residual delta exposure.
- ETF Creation/Redemption: Executing the full basket of underlying securities against the authorized participant's order. In these contexts, a partial fill is worse than no fill, as it creates an unhedged, directional position.
Regulatory and Risk Controls
Exchanges and brokers often impose strict controls on FOK orders to prevent market abuse:
- Order-to-Trade Ratio (OTR): Excessive FOK orders that repeatedly fail can inflate a participant's OTR, triggering regulatory scrutiny under spoofing surveillance.
- Throttling: Venues may throttle participants who submit high-frequency FOK orders that cancel, as this consumes matching engine capacity without contributing to price discovery.
- Pre-Trade Risk Checks: Brokers validate that a FOK order's notional value does not breach credit or position limits before routing, as the fill is instantaneous and irrevocable.
FOK vs. IOC vs. Limit Orders
Structural comparison of Fill-or-Kill, Immediate-or-Cancel, and standard Limit order execution guarantees, partial fill behavior, and market impact profiles.
| Feature | FOK | IOC | Limit Order |
|---|---|---|---|
Partial fills allowed | |||
Enters order book if unfilled | |||
Immediate execution required | |||
Minimum fill requirement | 100% of quantity | Any available quantity | None (rests until filled) |
Duration | Instantaneous | Instantaneous | Day or GTC |
Information leakage risk | Low (all-or-nothing) | Moderate (partial exposure) | High (visible resting order) |
Typical use case | Large block trades | Liquidity sweeping | Passive liquidity provision |
Market impact | Potentially high if filled | Moderate | Low (passive) |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Clarifying the operational logic, use cases, and technical constraints of the FOK order type in electronic trading systems.
A Fill-or-Kill (FOK) order is a conditional time-in-force instruction that mandates a broker or trading algorithm to execute the entire order quantity immediately at a specified limit price or better; if immediate and complete execution is not possible, the entire order is automatically canceled (killed) without any partial fill. Unlike an IOC (Immediate-or-Cancel) order, which allows partial execution of available shares, the FOK order enforces an all-or-nothing constraint. When submitted to an exchange matching engine, the system performs a liquidity check against the current limit order book. If the cumulative volume at the limit price or better meets or exceeds the FOK quantity, the order executes in full; otherwise, the system rejects and cancels it instantly, leaving no residual resting order in the book. This mechanism prevents partial fills that could signal trading intent or create unwanted inventory positions.
Related Terms
Explore the ecosystem of order types and execution strategies that interact with Fill-or-Kill logic, from aggressive liquidity capture to passive dark pool routing.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us