Market Microstructure: Orders, Quotes, Trades, and Price Formation
Updated September 19, 2026
Market microstructure studies how trading rules, order types, quotes, matching, and participant constraints turn buying and selling decisions into transactions. It explains the mechanism around a price move; it does not let an observer identify a trader's motive from a candle or one order-book snapshot.
Quotes are not trades
A limit order can add displayed liquidity at a specified price. A marketable order can execute against available resting orders. Quotes may be added, modified, canceled, partially filled, or fully executed, so displayed size is conditional rather than a promise to remain.
Price changes and the order book
When available quantity at the best price is consumed or removed, the best bid or offer can move to another level. The price impact of an order depends on its size relative to executable depth, matching rules, latency, and concurrent order activity. “Large candle” is an outcome, not proof of who caused it.
Matching, queues, and price impact
Electronic venues apply a rulebook to decide how eligible orders match. Price priority and a time or other priority rule are common, but the exact rule belongs to the venue. A displayed order at the best price is not automatically first in line, and a view of the book does not expose every queue position, routing decision, or data-feed limitation.
Spread, depth, and price impact are related but different measurements. The spread is the gap between the best displayed bid and offer. Depth is displayed quantity across levels. Price impact is the change in average execution price for a stated order under current conditions. A narrow spread can coexist with shallow depth; a deeper book can still change before an order arrives.
Concrete execution example
Suppose a buy order is larger than the quantity offered at the best price. Part may execute at that offer and the rest at higher offers. The prints establish completed trades, but they do not identify whether the initiating participant was hedging, liquidating, reacting to news, or expressing a directional view. The appropriate conclusion is about the observed execution and available liquidity, not hidden motive.
Put numbers around the same idea. If two contracts are offered at 100.00 and three at 100.25, a four-contract marketable buy may fill two at 100.00 and two at 100.25 if nothing changes first. Its average execution price would be 100.125, not 100.00. That is a simple depth-and-size illustration, not a claim about any particular exchange's matching engine or a promise that the visible book will remain in place.
A resting buy limit at 100.00 presents a different trade-off. It may keep the worst execution price at the limit, but it can sit behind earlier orders at the same level and receive no fill while price moves away. A useful microstructure review asks which risk matters for the situation—price certainty or execution certainty—without pretending either order type removes risk.
Order instructions have tradeoffs
| Instruction | Primary control | Main risk |
|---|---|---|
| Market order | Execution priority | Execution price can differ from the displayed quote. |
| Limit order | Worst acceptable limit price | The order may not execute. |
| Stop order | Triggers an order after a specified condition | Trigger and execution price can differ; handling varies by venue and broker. |
What the data can support
- Quotes can show displayed supply and demand at recorded moments.
- Trades show executions, not the full reason behind them.
- Repeated replenishment can be observed, but participant identity or intent requires stronger evidence.
- Spread, depth, and cost-to-trade measures describe different parts of execution quality.
What a reader can observe without overclaiming
A careful observer can note that the spread widened, that displayed depth declined, that trades repeatedly printed at a price, or that a stated quantity would have reached multiple levels in the visible book. Those statements retain the time, venue, and feed limits of the data. The observer cannot infer a named participant, an unobserved inventory, or a guaranteed next price path from those facts alone.
Latency and aggregation matter here. A chart, tape, or depth display may show events after a delay or combine activity in a way that changes the apparent sequence. During a rapid move, the state seen on screen can be stale by the time an order is entered. When the conclusion depends on sequence or queue position, use data with known scope and precision rather than a visual impression.
A disciplined review
- Name the venue, instrument, contract, session, and feed.
- Separate order-book events from completed trades.
- Measure the relevant size across multiple levels, not only top of book.
- Record data gaps, aggregation, and latency.
- Treat motive labels such as accumulation, spoofing, or liquidation as unverified unless evidence supports them.
Common bad inferences
- “The tape proves who is in control.” It reports activity, not the full participant inventory or intent.
- “A large print proves conviction.” It proves an execution, not why either side acted.
- “The book predicts the next bar.” Resting liquidity can change, cancel, or execute.
- “One platform view is the market.” Feed coverage, aggregation, latency, and venue differ.
When microstructure evidence is most fragile
Fast markets, scheduled releases, thin sessions, and contract transitions make ordinary observations harder to interpret. During a fast move, a feed may show a sequence after it has already changed; quoted depth may refresh quickly; and an order's reported time may not answer every sequencing question. The correct response is not to discard the data, but to narrow the conclusion and state the timing and coverage limits.
Different asset classes and venues also publish different levels of detail. A workflow designed around one exchange's full-depth futures feed should not be assumed to describe another venue's consolidated, delayed, or partial book. Read the exchange rulebook and the data-vendor documentation when execution decisions depend on a specific order type, matching behavior, or timestamp.
Practical observation workflow
- State the contract, exchange, session, and data-feed scope.
- Observe best prices and depth at the quantity relevant to the question.
- Separate changed quotes from completed trades and record the time resolution.
- Compare conditions with spread, volatility, and scheduled events.
- Write conclusions at the strength of the evidence: “depth declined” is narrower than “one side took control.”
Review the record after the session. Compare the anticipated spread and depth with the actual fills for the stated size. If the visible book repeatedly failed to describe executable conditions, identify whether the issue was timing, feed coverage, order size, or an exceptional market condition. This is an execution-quality audit, not a trading signal.
Continue with market liquidity basics for spread, depth, and cost-to-trade measurement.
Sources, scope, and change risk
Reviewed September 19, 2026 against the following first-party or regulatory sources:
Order handling, matching priority, stop behavior, market-data depth, and trading hours differ by venue, instrument, broker, and platform. Verify the current rulebook and order ticket for the exact market.