TradingView Reversal Order Size vs Position Size

A TradingView strategy set to trade two contracts can display a four-contract sell marker when it reverses direction. Before changing the quantity setting, check the position on each side of that fill. Moving from long two contracts to short two requires a sale of four: two close the long, and two establish the short.
For NQ and MNQ traders, separating transaction quantity from remaining exposure prevents a misleading chart label from turning into an unnecessary sizing change. This guide explains that distinction and gives you a practical way to audit a reversal.
Why a reversal can show a larger order
By default, Pine Script's strategy.entry() automatically reverses an opposite position. It adds the existing position's quantity to the requested new entry quantity. TradingView's chart markers show the transaction quantity. Direction restrictions, including strategy.risk.allow_entry_in(), can change this behavior. These rules are documented in TradingView's reversal documentation.
Keep three numbers in your review: the signed position before the fill, the signed transaction, and the signed position afterward. Treat buys as positive and sells as negative. Then apply a simple accounting check:
Position afterward = position before + signed transaction.
For the hypothetical two-contract reversal, the calculation is +2 + (−4) = −2. A four-contract transaction and a two-contract final position describe different parts of the same event.
Read a complete two-contract sequence
Imagine a simulation with no intervening fills or quantity changes:
Start flat. The position is zero.
Buy two. The position becomes +2, or long two.
Reverse to short two. Sell four. The position becomes −2.
Close the short. Buy two. The position returns to zero.
The sequence transacts eight contract-sides altogether: two bought, four sold, then two bought. At no completed step is the net position four contracts. You have two contracts on the long leg and two on the short leg, with both legs requiring an entry and an exit.
Unequal sizes follow the same arithmetic. Long two to short three requires selling five. Short three to long one requires buying four. If an earlier partial exit has already reduced a long position to one, reaching short two requires selling three. Write down the position immediately before the reversal rather than relying on the original entry size.
Separate reversals from pyramiding and partial exits
Pyramiding controls successive entries in the same direction made through strategy.entry(). It does not govern strategy.order(). TradingView explains that distinction in its strategy properties guide.
For example, adding another two-contract buy to an existing two-contract long, when permitted, produces a four-contract long. That is an increase in open exposure. Selling four from a two-contract long produces a two-contract short. The matching number four conceals two very different position paths.
A partial exit deserves its own line in the ledger. Starting long two and selling one leaves long one. It should not be recorded as a new one-contract short merely because the transaction's action is “sell.”
TradingView supports scaled exits through multiple strategy.exit() calls. Its multiple take-profit FAQ also warns that separate exit calls at one stop level can generate multiple order alerts. Review the filled quantities and their sequence, rather than counting markers as if every marker represented a new position.
The order-creation function matters too. strategy.order() applies its quantity to the net position without strategy.entry()'s automatic reversal sizing. A sell order for two against a long two therefore reaches flat. See TradingView's order command documentation. Do not transfer assumptions between these commands without checking which one generated the fill.
Translate the remaining position into NQ or MNQ exposure
CME specifies NQ at $20 per index point and MNQ at $2 per index point. Both use a 0.25-point minimum tick, giving tick values of $5 for NQ and $0.50 for MNQ. See CME's NQ specifications and MNQ specifications.
After the example reversal ends short two, a one-point rise changes gross open P&L by −$40 for NQ or −$4 for MNQ. Using the four-contract transaction as the remaining position would double those exposure estimates incorrectly.
Suppose, purely for illustration, the new short has a stop 25 points above its entry. The price-distance calculation is 2 × 25 × $20 = $1,000 for NQ, or 2 × 25 × $2 = $100 for MNQ. These amounts exclude costs and assume an exit at that price. A stop does not guarantee the calculated loss limit. The old long's realized result is separate.
For the broader contract comparison, read NQ versus MNQ contract size and position sizing.
Count transaction costs using traded quantity
TradingView's commission settings apply to entries and exits and offer per-contract, per-order, and percentage modes. The selected mode matters. Under a hypothetical fee of $1 per contract per side, the four-contract reversal costs $4. The entire example sequence costs $8 because it transacts eight contract-sides.
Remaining exposure and cost accounting therefore need different quantities. Keep the reversal fill's full transaction quantity in your cost check, even though the final position is smaller. For a separate sensitivity test, use the NQ and MNQ commission and slippage guide.
Audit the event before changing settings
Identify the exact fill. Save its symbol, time, order ID, action, and quantity. Include any fills immediately before and after it.
Reconstruct the position path. Apply the signed arithmetic one fill at a time. A same-bar screenshot alone may hide the sequence.
Check sizing assumptions. Verify whether sizing uses contracts, cash, or a percentage of equity. Inspect explicit quantities in the script when available.
Classify the action. Decide whether it increased an existing position, reduced it, closed it, or reversed it.
Compare the result with the intended position. Investigate any unexplained remainder before changing a setting to make the marker look smaller.
For automated execution, TradingView distinguishes strategy.order.contracts, the executed order quantity, from current-position fields. Its strategy alerts reference defines these placeholders. Check whether your receiving system expects a transaction instruction or a target position, and verify its actual starting position. The same number can have different consequences under those two interpretations.
Reconcile broker fills separately from the simulation. If the broker starts flat while the simulation starts long two, copying a sell-four transaction would create a different result. Review the alert-versus-chart troubleshooting guide when the records disagree.
The useful final check
A larger marker is a reason to inspect the position path. The audit is complete when the starting position, each transaction, the ending position, and the associated costs reconcile. Keep those records together so a normal reversal can be distinguished from an actual sizing or execution error.
Educational information only. Futures involve substantial risk. All examples are hypothetical and do not recommend a position size or predict trading results.
Get AORDS through Whop and follow the access instructions sent by email. Cancel anytime.
© 2026 AORDS. Trading involves risk. Past performance does not guarantee future results.