Absorption, Exhaustion and Iceberg Orders

Defining absorption carefully

Absorption is a practical description of aggressive orders transacting against resting liquidity without producing proportionate price progress. For example, repeated market buys may hit an offer while price struggles to advance. This can suggest a passive seller replenishing inventory. But a retail trader usually cannot prove the participant’s identity or intention. The observable facts are trade volume, repeated fills and the price response at a defined level.

Replenishment at a level

If an offer repeatedly appears after contracts trade, the ladder may show replenishment. Some exchanges support reserve or iceberg orders that display only part of a larger quantity, while other replenishment may come from separate new orders. Without appropriate market-by-order information, it can be difficult to distinguish these explanations. Never state that a screenshot proves a specific institution is hiding size. Use the pattern as a possible clue, not a confirmed identity.

Heavy market buying with little upward progress may indicate absorption, but the same footprint can reflect a temporary liquidity pocket. Compare executed trades with price progress over a fixed interval rather than inferring a hidden iceberg from one bar.

Exhaustion is different

Exhaustion is often used when aggressive activity declines as price extends into a reference area. A rally can make a marginal new high on reduced executed volume, yet still continue if there is little selling pressure. Lower volume does not automatically cause a reversal. Ask whether price fails to hold the new extreme, whether counter-side trades increase and whether the structure changes. The distinction between low initiative and high opposing liquidity is important.

Iceberg detection limitations

Some professional data feeds and tools infer iceberg activity from trade and order-message sequences. Detection depends on exchange rules, feed quality and algorithm assumptions. Hidden liquidity is not always visible to retail platforms, and synthetic iceberg strategies can behave differently from native exchange reserve orders. Treat iceberg labels as estimates with possible false positives. Do not promise a trader that an indicator reveals all institutional orders.

Absorption at support

Consider a hypothetical futures contract revisiting a weekly support area. Large aggressive sells repeatedly transact at the bid, yet price stops falling. A possible long plan waits for a reclaim above a short-term swing and a successful retest. The protective stop is placed where the support thesis is invalidated, with slippage considered. If the level breaks and accepts lower prices, the absorption idea was insufficient and the trade is avoided or exited.

Replay three high-volume tests of a prior high. Note traded volume, price advance, spread and the next two bars. A visible iceberg is not confirmed by spot-FX tick volume; label any conclusion as a hypothesis.

Absorption at resistance

Now reverse the scenario. Strong aggressive buys appear near a prior high, but price cannot hold above it. This might reflect passive supply. A short thesis needs a failed breakout or downward confirmation, not just positive delta. The market could instead absorb supply and break upward later. Keeping both scenarios written down prevents hindsight bias. Position size should be determined by distance to invalidation and account risk, not confidence in the label.

When not to interpret

During a major data release, spread, latency and order cancellations can change rapidly. A stationary price with enormous volume may be a temporary matching effect rather than stable absorption. Feed delays and contract rollover can also create misleading patterns. If a platform loses packets or changes aggregation, stop making fine-grained inferences. The correct decision can be to stand aside until normal liquidity returns.

Evidence checklist

At each suspected event, note the reference price, time, aggressor volume, visible replenishment, price excursion and later confirmation. Write an alternative explanation that does not rely on an unseen institution. Mark the invalidation and expected execution cost. Review ten events without knowing the outcome first, then replay forward. A useful lesson is the difference between evidence that a level is contested and evidence that a profitable trade exists.

Create a falsification test for Absorption, Exhaustion and Iceberg Orders: mark the suspected event, the subsequent traded volume or delta, and the price level that would show the interpretation was wrong. Find a second session with similar volume but a different price response. Explain whether aggressive orders were absorbed, whether the displayed liquidity was replenished, or whether the data simply cannot distinguish those explanations.

Practice questions and model answers

What is the most important observation in this lesson?

Model answer: Identify the measurable event described in “Defining absorption carefully” and relate it to a specific reference price, rather than guessing the identity of a trader.

What would invalidate the trading interpretation?

For Absorption, Exhaustion and Iceberg Orders, distinguish observation from inference. A large delta with little price progress might be consistent with absorption, but it does not identify the participant or guarantee reversal. Define a subsequent price-acceptance test: for example, two closes beyond the marked level, or a failed retest within a fixed number of bars. Log cases where the order-flow interpretation fails and explain which additional evidence would change the conclusion.

How should the position be managed?

In a Absorption, Exhaustion and Iceberg Orders exercise, suppose the account is 10,000 units and the permitted risk is 0.5%, or 50 units. If entry-to-invalidation distance is 25 ticks and each tick is worth 2 units per contract, one contract already risks 50 units before commissions and slippage. A wider stop would require a smaller position or skipping the trade. Recalculate using the actual contract specification and do not assume spot FX has the same centralized volume feed.