What is pulling and stacking in DOM? How displayed depth changes and why it is not a promise of execution
Pulling and stacking describe resting size leaving or arriving at a DOM price level. Learn what the changes measure, what causes them, and why displayed depth never guarantees a fill.

What pulling and stacking mean on a DOM
Pulling is a decrease in the displayed resting size at a price level on the depth of market. Stacking is an increase in that displayed size. Both terms describe changes in market depth over a short window. They do not describe trades, and they do not tell you that the orders will still be there when price arrives.
That last point is the reason for this article. Many traders read a growing bid as "support" and a shrinking offer as "sellers giving up." The DOM shows neither. It shows the visible quantity of limit orders resting at each price at a given moment, and pulling and stacking columns show how that quantity moved.
Get professional chartbooks for Sierra Chart
DOM, footprint, heatmap and market profile setups, installed in seconds. Our trading courses cover the method behind them.
“Chartbooks are superb, I save a lot of time! Thanks for these quality products.”
How pulling and stacking are calculated
A DOM ladder lists prices vertically, with bid size on one side and ask size on the other. If you need a refresher on which column is which, see Sierra Chart DOM columns explained: resting depth vs recently traded volume.
Pulling and stacking compare the current displayed quantity at each price with a reference value, usually the quantity at the start of a measurement period or when price last moved through that level. The difference is shown as a positive number (stacking) or a negative number (pulling).
A simple ES example, with a 0.25 tick:
- At 5000.00 the bid shows 420 contracts.
- A few seconds later it shows 610. The column shows +190 at that price. That is stacking.
- Then it drops to 280. The column now shows a net -140 versus the reference. That is pulling.
The same logic applies to NQ (0.25 tick) or CL (0.01 tick). In CL, a tick is small, so size often spreads across many levels and changes at a single price are noisier than in ES.
What the reset rule changes
The number you see depends heavily on when the counter resets. A column that resets when the inside price changes will show small, fresh numbers in a fast market. A column that accumulates for longer can show large figures that mostly reflect old activity. In Sierra Chart, recent versions of the Trade DOM include pulling and stacking columns with their own settings. Column names and reset options vary by version, so open the DOM column configuration in your installation and read the description of each pulling/stacking setting before you trust the values.
Why a decrease in depth is not always a cancellation
This is the most common misreading. Displayed size at a price can fall for several reasons:
- Cancellation. A participant removes the order. This is a true pull.
- Execution. Market orders trade against the resting size. The quantity drops because it was filled, not withdrawn.
- Modification. An order is reduced or moved to another price. One level shrinks, another may grow.
- Iceberg or display quantity orders. CME Globex allows orders with a smaller displayed quantity. The visible size refreshes after fills, so stacking can appear at a level where the true size was always larger than displayed.
Some DOM implementations try to separate traded volume from cancellations by subtracting trades at that price. Whether your column does this is a setting or a design choice you must verify. If it does not, a level being traded through will look like heavy pulling. Compare the pulling value with the recent traded volume at the same price. The distinction between resting orders and executed trades is covered in market depth vs time and sales.
Why displayed depth is not a promise of execution
Resting liquidity is an offer to trade, not a commitment. A limit order can be cancelled up to the moment it is filled. Three practical consequences:
- Size can leave before price reaches it. A 900-lot offer in NQ two ticks above the market can disappear in milliseconds. A plan that assumes it will hold price has no basis in the data.
- You only see part of the book. Depth feeds show a limited number of price levels, and implied or hidden size may not appear. Stacking ten levels away tells you little about what sits beyond the visible range.
- Some displayed orders are not intended to trade. Placing orders with intent to cancel before execution is spoofing, which is prohibited under US commodities law and enforced by the CFTC. Enforcement does not mean every large order you see is genuine, so treat displayed size as information with uncertainty, not as intent.
Queue position also matters. Even if size at a level stays, your own order joins the back of the queue at that price. Large stacked size ahead of you can mean you do not get filled before price leaves.
How to read pulling and stacking in practice
Use the columns as context, not as triggers. A routine that keeps the reading honest:
- Confirm the data. Pulling and stacking need market depth data from your feed. If the bid and ask size columns are empty or frozen, the derived columns are meaningless.
- Check the reset behavior. Watch the column through a few price changes on a replay or a quiet session and note when it zeroes.
- Pair it with trades. When a level shows heavy pulling, check whether volume traded there. Pulling with no trades is a cancellation story. Pulling with matching trades is an execution story.
- Watch the reaction, not the size. What matters for review is how price behaved after the change. Did price trade into the level, stall, or move through? Record it, without assuming the depth caused it.
- Keep instrument context. ES typically shows deep size at each tick. CL and RTY (0.10 tick) are thinner, so the same absolute change means something different.
A concrete ES observation: offers at 5002.00 through 5003.00 stack by several hundred contracts while price sits at 5001.50. Price then rallies, and as it approaches, those offers pull before any trades print there. The data only says size appeared and then left. It does not say who placed it or why.
Seeing the history of depth changes
A DOM shows the present. To review how depth built and disappeared over time, a historical depth or heatmap view is more useful. Setup steps and data requirements are in Sierra Chart market depth historical graph setup, and the available studies are listed in the Sierra Chart studies reference. If you want the ladder and a liquidity heatmap side by side without building the layout yourself, a Sierra Chart DOM with heatmap chartbook gives you that workspace ready to open.
When you build or save your own layout, Sierra Chart stores it as a chartbook (.Cht file). The chartbooks documentation explains how they are saved and reopened.
A note on EURUSD
Spot forex has no single central order book. Depth shown on a forex platform is your broker's or liquidity provider's view, so pulling and stacking there reflect that venue only. For a centralized book in euro, look at the CME euro FX futures contract, where depth comes from one exchange.
DOM terminology quick reference
| Term | What it measures | What it does not tell you |
|---|---|---|
| Resting liquidity | Limit orders displayed at a price | Whether they will stay |
| Stacking | Increase in displayed size at a price | Intent, or total hidden size |
| Pulling | Decrease in displayed size at a price | Whether it was a cancel or a fill, unless trades are separated |
| Market depth changes | Net movement in the book over a period | Future price direction |
Conclusion
Pulling and stacking are bookkeeping on displayed depth: size added, size removed, measured against a reference that depends on your settings. They are useful for describing what the book did. They are not evidence of what participants will do, because any resting order can be cancelled before it trades. Verify your data, learn the reset rule, separate cancellations from fills, and review reactions rather than reading size as a promise. For a configured DOM and heatmap workspace you can study this on, browse the Sierra Chart chartbooks at SierraOnShop.
FAQ
Is pulling the same as absorption?
No. Pulling is a change in resting depth before or without trades. Absorption describes traded volume hitting a level while price fails to move. They come from different data, depth versus executions.
Why do my pulling and stacking columns show nothing?
Usually market depth data is not enabled on the feed, the symbol has no depth subscription, or the columns were added but the DOM is not receiving updates. Check that bid and ask size columns are live first.
Can pulling and stacking be backtested?
Only if depth data was recorded. Standard tick data stores trades, not the full order book, so historical depth changes require stored market depth data from your feed.
Do large stacked bids mean price will go up?
No. Stacked bids are displayed orders that can be cancelled at any time. They describe the current book, not a future price move.
Set this up in Sierra Chart in seconds
Written by
Clement
Futures trader for more than seven years, specialized in order book and order flow scalping on US index futures, now building automated strategies. Founder of SierraOnShop.
More about the authorRead the order flow with the right tools
Start with a professional Sierra Chart chartbook, or learn the method with our trading courses.
“Just received the footprint chartbook. Installation took 30 seconds, works perfectly on Sierra 2800.”