Break-even stop
The break-even stop is a protective stop that becomes active after price has moved in the profitable direction. In the Backtester, it shows how protection based on the current average position price affects a strategy.
How the two values are calculated
BE trigger, % sets the favorable price movement from the current average position price that activates the protection: upward for a long and downward for a short.
BE stop level, % sets the stop itself from the same average price: above the average for a long and below it for a short.
LONG example: the current average price is 100 USDT, the trigger is 1%, and the level is 0.2%. When price reaches 101 USDT, the protective stop is calculated at 100.20 USDT.
Averaging changes the position's average price. The break-even levels are recalculated from the new average, and protection arms again after price reaches the new trigger.
Difference from the regular stop
Stop Market / Stop Limit in the Backtester is measured from the first order price and does not follow the average price after averaging.
Break-even stop is measured from the current average position price and is recalculated after every averaging order.
A 0% level is valid and places the calculated stop at the average price. It does not guarantee a zero financial result because fees still apply and the execution price can differ from the stop level.
Availability
Any user can calculate a strategy with a break-even stop in the Backtester and its optimizer when the selected exchange is BYBIT. The block is visible but disabled for Binance.
For live trading, this setting is supported only by Bybit exchange-broker subaccount robots, called Exchange Account in the panel. Legacy Bybit API robots (Old Grid / API broker) and all Binance robots do not support it.
The break-even stop cannot be combined with the classic hedge robot. The block is disabled while hedge is enabled, and the calculation service rejects that combination.
Configure it in the Backtester
Open the Backtester and select BYBIT.
At the bottom of Risk Management, enable Break-even stop.
Enter the BE trigger and BE stop level.
Validate the pair: trigger must be greater than 0, level must be at least 0 and strictly lower than trigger. Supplying only one value is invalid.
Run the calculation normally.
If you temporarily select Binance or enable hedge, the block is disabled and its tooltip explains why. The previous switch state returns only after every restriction has been removed.
Behavior in the Backtester optimizer
The optimizer does not vary the BE trigger or level. It takes one pair from the main form and applies it to every variation. The fixed values appear below the variation count and in the best variation next to TP and the regular stop.
If values are present but a run excludes them because of another exchange or hedge, the result shows a red explanation. Apply best restores the exact BE pair used by that run. If the run did not use BE, the switch is turned off while the typed values remain in the fields.
Both cloud calculation and the local GPU mode support BE. With BE enabled, the local mode uses the full exact search and may take longer.
At present, a BE close increases the optimizer's total trade count but may be absent from its closure-reason breakdown. The displayed reasons can therefore sum to less than the total trades. A normal single backtest reports BE closures separately.
Results and archive
A single result has a separate Closed by BE stop reason.
Multi-results have a Closed by BE column and summary value. These trades are excluded from the regular Stop Market column and are included in CSV export.
The archive includes BE in the closure distribution and shows the saved pair in the collapsed row, for example BE 1.00% / 0.20%.
Transfer to robots and presets
When transferring a strategy from a backtest result, unsupported robots are disabled in the recipient list. A stopped but compatible Bybit Exchange Account can be selected: the window opens its form with the fields filled, and trading begins only after the robot is enabled. Without an eligible Bybit Exchange Account, the BE strategy cannot be transferred. Opening the Backtester from a supported robot task preserves both values.
This is different from Export tasks on a robot page. That action creates live task copies, so a stopped recipient cannot be selected there.
The preset catalog's To Backtest action transfers the BE pair. To Robot does not transfer it; after the robot form opens, enable BE manually and check both values again.
In the terminal's order-grid optimizer, BE fields appear only for Bybit and remain fixed. Two empty fields mean disabled. Transfer to the order grid, robot creation, and direct launch include the pair only for a supported Bybit Exchange Account. A partial pair blocks transfer and launch.
For the main form, see Backtester: first calculation. To read the output, see Backtester results and archive.