Orders, stops and exits
Order types, size inputs, protective exits and what actually happens at the venue when each one fires.
暂无该语言版本——显示英文。
Order types #
| Type | Behaviour | Use when |
|---|---|---|
| Market | Fills immediately at the best available price | You need in or out now and accept slippage |
| Limit | Rests at your price until filled or cancelled | You care about price more than certainty |
Limit orders have two extra controls:
- Time in force — how long the order rests before the venue expires it.
- Post-only — the order is rejected rather than crossing the spread, so it always pays
the maker fee.
Market orders on thin books can fill far from the last price. The ticket shows the current spread and an estimated total before you send.
Sizing #
The ticket accepts either side of the pair:
- Base quantity — how much BTC, SOL or whatever the base asset is.
- Quote amount — how much USDT you want to spend or receive.
Both fields stay linked by price. Check which one is active before typing a number: a size typed in the wrong unit is the most common first-trade error.
Protective exits #
An exit is an instruction to the venue, not a note in the app. Once armed, it survives a closed browser, a logged-out session and a dead laptop.
| Exit | What it does |
|---|---|
| Stop-loss | Fires a closing order when the trigger price is touched |
| Take-profit | Fires a closing order at your target, in one or more legs |
| Trailing stop | Follows price in your favour and fires on a set retracement (venue-dependent) |
Multi-leg take-profits split the position: 60% at first target, 40% at second reduces the position in two steps instead of one.
Warning
On a gap, a stop becomes a market order and can fill well past its trigger. A stop bounds
your intended loss, not your worst possible loss.
Entry with exits in one action #
The ticket's Exits panel attaches stops and targets to the entry order, so the position is never unprotected between the fill and the exit setup. On venues that support native brackets, the three legs are submitted together.
If the venue does not support native brackets, JW3 arms the exit legs immediately after the entry fills. In that window the position is briefly unprotected — the ticket tells you which mode applies before you send.
Changing exits #
- Widen or tighten a stop — replaces the leg at the venue.
- Add a target — adds one more take-profit leg.
- Remove an exit — leaves the position unprotected; the app warns before removing the
last stop.
Partial closes and reduce-only #
A partial close reduces the position without touching the rest. Reduce-only orders can shrink a position but never flip it, which prevents the classic mistake of closing "long" into an accidental short.
When an order does not fill #
| Situation | What to do |
|---|---|
| Limit rests unfilled | Wait, reprice, or cancel — check the queue depth first |
| Rejected: insufficient margin | Reduce size or leverage |
| Rejected: post-only would cross | Reprice away from the spread |
| Partially filled | The remainder still rests unless time-in-force expired |
| Disappeared after a venue error | Run a reconcile read; never assume it cancelled |
The venue is the source of truth for order state. JW3's view is a cache with timestamps — when they disagree, trust the venue.
清单
- Order type matches the urgency of the trade
- Exits attached before sending, not after
- Understood whether the stop is held by the venue