Bitunix Multi-Trade on the ticket: why a second long stays separate instead of merging

The rule in one line

Non-Multi-Trade (default) merges same-direction size on a pair into one position. Multi-Trade keeps each open as its own position.

Ticket setup checklist

1. On the Bitunix app Futures page, open the Cross/Isolated control on the ticket.
2. At the bottom of that menu, tap Multi-Trade, then Confirm.
3. Multi-Trade can be enabled only when Single-Currency Hedge Mode is already active, and only with no open positions and no open orders.
4. Multi-Trade cannot be enabled in Portfolio Margin mode or One-Way mode.
5. Pick Isolated Multi-Trade or Cross Multi-Trade before you size. Isolated keeps each leg's risk separate. Cross still manages legs independently but shares the margin account.

Worked steps on the ticket

1. Confirm Single-Currency Hedge Mode is on and the account is flat.
2. Enable Multi-Trade from the margin-mode menu.
3. Official Multi-Trade walkthrough path: set leverage to L (guide shows 20x), choose Market Order, enter quantity qty, tap Open Long on BTCUSDT or your pair.
4. Open a second long on the same pair the same way. Under Multi-Trade you now see two positions, not one merged row.
5. Attach TP/SL per position. Close one with Close or Market Close All on that row while the other stays open.
6. Recheck available margin after each open. Independent legs still consume margin from the same wallet in Cross Multi-Trade.

Formula for the mental model

merged_default = sum(same_direction fills on pair) multi_trade = list of independent positions (margin_i, stop_i, liq_i)

Nothing in Multi-Trade changes the maker/taker schedule by itself. It changes how size is stored and closed on the ticket. Funding still settles on each open position that is held at the funding time.

What changes it

• Turning Multi-Trade off later returns new opens to the default merge behavior once the mode rules allow a switch.
• Cross Multi-Trade still shares wallet margin across legs, so one leg can pressure the shared balance even when TP/SL are separate.
• Isolated Multi-Trade isolates risk per position, which is the stricter ticket choice when you want independent liquidation lines.
• You still choose order type (market, limit, and the rest) on each ticket send. Multi-Trade does not replace order type.
• Live BTC mark around the fetch for this piece sat near 75,387. That number is context only; the Multi-Trade rule does not depend on the print.

Common mistakes

1. Trying to enable Multi-Trade while a limit rests or a hedge leg is open.
2. Staying in One-Way mode and looking for Multi-Trade. The help center says One-Way blocks it.
3. Assuming two Cross Multi-Trade longs cannot stress each other because TP/SL differ. They still share margin.
4. Hitting Market Close All on the wrong row and closing the leg you meant to keep.
5. Treating the guide's 20x setting as a required leverage. Set L from your own risk limit tier instead.

FAQ

Is Multi-Trade the same as Hedge Mode? No. Hedge Mode lets long and short coexist. Multi-Trade splits multiple positions in the same direction. Bitunix requires Single-Currency Hedge Mode before Multi-Trade can turn on.

Does each Multi-Trade leg have its own liquidation price? Yes under the help-center description: liquidation calculations of each position are handled separately and do not affect one another.

Can I use Multi-Trade on web the same way? Bitunix publishes a matching Web guide. The App article is the source for this piece; confirm the same menu labels on web before you switch.

What happens to fees? Fees still follow maker/taker on each fill. Multi-Trade only changes position accounting on the ticket.

Checklist close

Flat account, Single-Currency Hedge Mode on, Multi-Trade confirmed, then open legs one at a time with per-leg TP/SL. If the ticket still merges, Multi-Trade is not actually on.