A slippage model is a simulation component that calculates the difference between the expected price of a trade and the price at which the order is actually filled. It quantifies execution degradation caused by market impact, latency, and bid-ask spread dynamics during the interval between signal generation and order completion within a backtesting engine.
Glossary
Slippage Model

What is a Slippage Model?
A slippage model is a quantitative simulation component that calculates the divergence between an order's intended execution price and its actual fill price, accounting for latency, liquidity constraints, and adverse market movement.
These models typically ingest order book depth, tick-level volume profiles, and volatility regimes to estimate fill probability at each price level. By incorporating a slippage model, quantitative developers prevent look-ahead bias and generate realistic implementation shortfall estimates, ensuring backtested strategies reflect genuine execution constraints rather than idealized theoretical prices.
Core Components of a Slippage Model
A slippage model quantifies the divergence between a theoretical decision price and the actual execution price. The following components decompose this cost into its constituent parts for accurate simulation.
Bid-Ask Spread Cost
The immediate cost of crossing the spread to execute a market order. This component captures the difference between the mid-price and the prevailing bid or ask.
- Quoted Spread: The difference between the best bid and ask at order arrival.
- Effective Spread: Double the difference between the trade price and the mid-point at the time of order entry.
- Realized Spread: Measures the market maker's revenue after accounting for adverse price movements post-trade.
In a backtesting engine, this is often modeled as a fixed half-spread penalty applied to every aggressive order.
Temporary Market Impact
The transient price concession required to attract liquidity and fill an order. This cost decays rapidly after execution completes as the order book replenishes.
- Linear Impact Models: Assume impact scales proportionally with order size relative to average volume.
- Square-Root Models: A non-linear relationship where impact scales with the square root of participation rate, widely validated in empirical microstructure research.
- Resilience Decay: The speed at which the price reverts to its undisturbed level, typically modeled as an exponential decay function.
This component is critical for sizing child orders in execution algorithms like TWAP and VWAP.
Permanent Market Impact
The irreversible price movement caused by the information content of a trade. The market interprets aggressive buying or selling as a signal of informed trading and adjusts the equilibrium price accordingly.
- Information Leakage: The degree to which an order reveals private alpha, permanently shifting the fair value.
- Kyle's Lambda: A canonical measure of permanent impact, defined as the price change per unit of net order flow.
- Cumulative Effect: Unlike temporary impact, this component does not decay and accumulates over the life of a meta-order.
Accurate permanent impact modeling is essential for strategies with large directional positions or long execution horizons.
Delay Cost
The adverse price movement that occurs between the decision time and the initial order arrival due to latency, processing, or intentional scheduling delays.
- Latency Slippage: Price drift during network and system processing, critical for high-frequency strategies.
- Scheduling Drift: The cost of waiting to execute a slice in a scheduled algorithm, often modeled as a Brownian motion with drift.
- Opportunity Cost: The risk that an unfilled limit order misses a favorable price move, a direct trade-off against spread capture.
Delay cost is the primary driver of the implementation shortfall metric used to evaluate execution quality.
Order Book Resilience
The rate at which depleted liquidity replenishes after a trade. A resilient book recovers quickly, minimizing the cumulative impact of sequential orders.
- Resilience Parameter: The exponential decay constant governing how fast the order book returns to its steady-state shape.
- Hawkes Process Models: Self-exciting point processes that capture the clustering of order book events and liquidity regeneration.
- Queue Position Effects: The interaction between order cancellation rates and new limit order arrivals at each price level.
Backtesting engines with order book replay capability can directly measure resilience rather than relying on parametric approximations.
Adverse Selection
The cost incurred when trading against counterparties with superior information. This component captures the probability that a fill occurs precisely when the market is about to move against the position.
- Pre-Trade Toxicity Metrics: VPIN (Volume-Synchronized Probability of Informed Trading) estimates the likelihood of informed flow.
- Post-Trade Drift: The average price movement following a fill, used to calibrate adverse selection in limit order models.
- Spread Capture Trade-Off: Passive orders earn the spread but suffer adverse selection; the model must balance these competing forces.
Adverse selection is the primary reason limit orders are not risk-free and must be modeled stochastically.
Frequently Asked Questions
Clear answers to common questions about simulating execution shortfall in backtesting engines.
A slippage model is a simulation component that calculates the difference between the expected price of a trade and the price at which the order is actually filled due to latency and market movement. It works by applying a mathematical function to the theoretical execution price, typically incorporating factors such as order size relative to available liquidity, the current bid-ask spread, and volatility. In a backtesting engine, the model intercepts the fill logic and adjusts the fill price downward for buy orders or upward for sell orders, degrading the simulated performance to reflect real-world execution costs. Advanced models decompose slippage into temporary market impact (which reverts) and permanent impact (which shifts the equilibrium price).
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.
Related Terms
A slippage model does not operate in isolation. It is a critical component within a larger ecosystem of execution simulation, cost analysis, and market dynamics. The following concepts are essential for understanding how slippage is quantified, simulated, and mitigated.
Market Impact Model
A mathematical function that decomposes the adverse price movement caused by a trade into temporary impact (liquidity demand) and permanent impact (information leakage). While slippage is the realized difference, the market impact model is the predictive engine that estimates it pre-trade. Common implementations include the Almgren-Chriss framework and the I-Star model, which parameterize impact as a power-law function of trade size relative to average daily volume.
Implementation Shortfall
The definitive metric for measuring total execution cost, defined as the difference between the theoretical portfolio value at the decision price and the actual realized value after execution. It is the sum of explicit costs (commissions, fees) and implicit costs (slippage, missed trades). A slippage model provides the implicit cost component, making it a direct input into the implementation shortfall calculation used for best execution regulatory compliance.
Fill Simulation
The logic within a backtesting engine that determines whether a simulated order is executed, based on available historical volume, order book depth, and queue position. A slippage model is invoked only after a fill is confirmed. The interaction is critical:
- Aggressive orders cross the spread and incur immediate slippage.
- Passive orders join a queue and may experience opportunity slippage if unfilled.
- Fill probability decays with limit price distance from the mid-price.
Transaction Cost Analysis
The quantitative framework for measuring the total cost of executing a trade. TCA systems consume the output of slippage models to generate post-trade reports that benchmark execution quality against arrival price, VWAP, or an implementation shortfall baseline. Key decompositions include:
- Delay cost: Slippage from waiting to execute.
- Spread cost: Crossing the bid-ask spread.
- Impact cost: Price movement caused by the order itself.
Order Book Replay
A high-fidelity simulation technique that reconstructs the historical limit order book depth at each price level. Unlike a simple slippage model that applies a fixed percentage haircut, order book replay allows for dynamic slippage estimation by simulating a market order walking up the book. This captures the non-linear relationship between order size and available liquidity, revealing the true cost of executing large orders against thin markets.
Tick-Level Simulation
A backtesting resolution that replays every individual trade and quote update. Slippage models operating at this granularity can distinguish between quote-driven slippage (the spread widening before a fill) and trade-driven slippage (the price moving after a fill). This distinction is essential for latency-sensitive strategies where the sequence of events within a single millisecond determines profitability.

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