Order Flow Trading: Reading the Order Book for Directional Signals

Most retail indicators are built from closing prices. Order flow trading throws that away and looks at something more direct: who is actually hitting the book, buyers or sellers, and with how much size. Price is the outcome. Order flow is the cause. If you can read the cause a few seconds before the outcome, you have an edge that most chart-based traders never see.

This is not the same as static order book imbalance, which we covered in the order book imbalance guide. That looks at resting liquidity. Order flow looks at executed trades, the aggressive side, the tape.

Aggressor side and cumulative delta

Every trade on LMEX has an aggressor: the side that crossed the spread to get filled. A market buy lifts the ask and counts as buy volume. A market sell hits the bid and counts as sell volume. Cumulative volume delta, or CVD, is just the running sum of buy volume minus sell volume.

CVD tells you the story behind a price move. Price rising on rising CVD is real buying pressure. Price rising while CVD falls is a warning: price is drifting up but aggressive sellers are stepping in, and that divergence often precedes a reversal.

import pandas as pd

def cumulative_delta(trades: pd.DataFrame) -> pd.Series:
    # trades has columns: price, size, side ('buy' or 'sell' = aggressor)
    signed = trades["size"] * trades["side"].map({"buy": 1, "sell": -1})
    return signed.cumsum()

def cvd_divergence(price: pd.Series, cvd: pd.Series, window=30):
    price_trend = price.diff(window)
    cvd_trend = cvd.diff(window)
    # bearish: price up, delta down. bullish: price down, delta up.
    bearish = (price_trend > 0) & (cvd_trend < 0)
    bullish = (price_trend < 0) & (cvd_trend > 0)
    return bullish.astype(int) - bearish.astype(int)

Streaming the tape from LMEX

Order flow needs trade-by-trade data, which means WebSocket, not REST polling. You subscribe to the public trades channel and accumulate delta in real time. If WebSocket clients are new to you, our LMEX WebSocket tutorial covers the reconnection handling that trips up most first attempts.

import json, websockets, asyncio

async def stream_delta(symbol="BTC-PERP"):
    url = "wss://ws.lmex.io/ws/futures"
    delta = 0.0
    async with websockets.connect(url) as ws:
        await ws.send(json.dumps({"op": "subscribe",
                                   "args": [f"tradeHistoryApi:{symbol}"]}))
        async for msg in ws:
            data = json.loads(msg)
            for t in data.get("data", []):
                signed = t["size"] * (1 if t["side"] == "BUY" else -1)
                delta += signed
                # feed `delta` into your signal logic here
    return delta

Absorption and exhaustion

The two setups worth watching are absorption and exhaustion. Absorption is when heavy aggressive selling hits the book but price does not fall, because a large passive buyer is soaking it up. That hidden buyer usually wins, so absorption at support is a long signal. Exhaustion is the opposite: a sharp move on climactic volume that suddenly stops printing new delta, meaning the aggressive side has run out of ammunition.

Neither shows up on a candlestick chart until after the fact. That is the entire point of trading flow instead of price.

Why this is hard

Order flow is genuinely predictive, but it decays fast. A CVD divergence might give you a five to thirty second head start, not a five hour one. That makes execution latency and clean data more important than on any swing strategy. If your data feed lags or your orders sit in a slow queue, the edge is gone before you act.

It also generates false signals in thin markets. On a low-liquidity contract a single large trade swings CVD violently without meaning anything. Filter by liquidity and stick to the deepest LMEX perpetuals when you start.

Frequently Asked Questions

Q: Is order flow trading the same as scalping?

They overlap. Order flow is a signal source, scalping is a holding-period style. Many scalpers use flow as their primary trigger, but you can also use CVD divergence to time entries on longer swing trades.

Q: Can I compute CVD from REST data?

Poorly. REST trade endpoints return batches with gaps, so your delta will be approximate. For anything you plan to trade on, use the WebSocket trade stream so you count every print.

Q: What timeframe should I watch CVD on?

Match it to your holding period. Intraday traders watch tick or 1-minute CVD. Swing traders watch daily CVD against daily price to spot accumulation or distribution over weeks.

Q: Does order flow work in trending markets?

Best in them, actually. Sustained one-sided delta confirms a trend has real participation behind it. The divergences are most useful for spotting where that participation dries up.

Related Articles