A trailing stop loss follows the trade after price moves in the favorable direction.

For a long trade, the stop can move up as price makes new highs. For a short trade, it can move down as price makes new lows.

The idea is attractive: keep the trade open while it is working, but protect part of the move if price reverses.

Personally, I do not use trailing stops much.

The main reason is practical: I mostly do algorithmic trading, and a robust trailing stop is harder to code, test, and operate than regular stop-loss and take-profit levels.

A simple SL/TP plan is easier to reason about in logs, easier to replay, and easier to compare across trades. With trailing stops, the exact exit path depends on every price update and every trailing rule.

Scrolling through trading discussions and talking with different traders, the topic feels divided.

Some traders like trailing stops because they help protect profit and fight emotional holding. Others dislike them because they can get triggered by normal volatility and remove a position before the larger move happens.

A Reddit r/stocks discussion on trailing stop-loss orders shows that split pretty clearly: some users prefer wide trailing stops, some warn against tight stops, and some think the tool only fits certain trading styles.

The tighter the trailing stop, the more likely it is to react to normal noise.

A 1% or 2% trailing stop can sound safe, but many assets can move that much without the original trade idea being wrong.

That means a trailing stop can reduce downside, but it can also create whipsaw: the trade exits, price recovers, and now the trader has to decide whether to re-enter at a worse price.

There is also evidence that trailing stops can work in some tested settings.

Quant Investing published a stop-loss research summary where trailing stop losses outperformed traditional stop losses across several wider stop levels in their tested period, especially around the 15% to 20% range.

That does not mean every strategy should use a trailing stop. It means the idea deserves testing instead of being dismissed only because it is more annoying to implement.

A trailing stop is not one single rule.

It can trail by percentage, ATR, market structure, close price, high and low, intrabar ticks, daily evaluation, or broker-side order behavior. Each version can produce different exits.

For an algorithmic system, those details matter because the backtest, live order, broker execution, and lifecycle journal all need to agree on what the rule actually means.

If Quantarya supports trailing stops, I would want them to be explicit and measurable.

The trade record should store the trailing method, distance, update rule, current stop level, every stop movement, final exit reason, drawdown, drawup, and realized result.

Without that detail, a trailing stop becomes hard to audit. With that detail, it becomes another strategy component that can be compared against fixed stops, ATR stops, and TP1/TP2/TP3 exits.

My current preference is still regular SL/TP and ATR-style protection because it is simpler to code and review.

But I would not say trailing stops are invalid. Traders use them, the community is divided, and some data suggests they can outperform regular stops in specific settings.

This is not financial advice. It is a process opinion: if a trailing stop fits the strategy, test it properly, make the rule explicit, and journal the full path instead of only the final exit.