The complexity of CFD trading comes not only from the market itself, but also from the tools used by users - especially the combination and triggering logic of various conditional orders. The design principle of the Wmax platform is: no matter how complex the trading strategy is set by the user, its execution path must be clear, traceable, and free of black boxes. This article focuses on frequently used functions such as stop-loss/take-profit orders, trailing stop-loss, and conditional order nesting, and explains how the platform ensures that users have complete control over their own strategies through mechanism design.

Stop loss and take profit: clear boundaries between market price and limit price

Wmax provides two stop loss/take profit types: market price (Market) and limit price (Limit). When selecting the market price type, once the trigger price reaches the set value, the system will immediately execute the liquidation at the best price available at that time to ensure that the risk exposure is closed quickly, but slippage may occur due to insufficient liquidity. When selecting the limit type, the system will only execute the transaction when the market price reaches or is better than the specified price. If the market jumps past this price, the order may not be executed.

The platform clearly marks the applicable scenarios and potential results of the two types of orders on the order placing interface, and forcibly displays on the order confirmation page: "Limited price stop loss may be invalid in the gapping market." All trigger records include the original setting value, actual trigger time, transaction price and slippage data, and users can fully trace back in the "Order History". Not hiding failure cases is the first step to transparency.

Trailing Stop: Mechanism Logic of Dynamic Protection

Trailing Stop is a common tool used by users to lock in floating profits. The implementation logic of Wmax is: when the position profit reaches the tracking distance set by the user (such as 50 points), the system automatically activates a dynamic stop loss position, which moves up (long) or down (short) synchronously with the favorable price movement, but will not be adjusted in the opposite direction.

The key is that the activation and update of trailing stops rely entirely on real-time quote flow and do not rely on K-line closing prices or delayed data. Once the price fluctuates in the opposite direction and reaches the dynamic stop loss level, the system will immediately send a market price closing order. Please note: Trailing stop is a local client function and will not take effect during network interruption or terminal shutdown. The platform clearly indicates this restriction in the function description and recommends using server-side stop-loss orders in high-risk scenarios.

Nested conditionals: policy freedom and execution isolation

Wmax supports the nested logic of conditional orders "If A is traded, trigger B", allowing users to construct staged entries, pyramid positions or hedging strategies. For example: after the first long order is completed, the second buy order and corresponding stop loss order at a higher price will be automatically placed.

The execution of this type of order has strict isolation: the main order and the sub-order exist independently in the system queue, and the completion of the main order is the only prerequisite for the activation of the sub-order. If the main order is partially filled due to insufficient liquidity, the sub-order will be activated on a proportional basis; if the main order is canceled, the sub-order will be automatically invalidated. All relationships are displayed as visual links in the order list, and users can check the status of each link at any time. The premise of strategic freedom is that the causal relationship of each link can be verified.

Priority and conflict handling of risk control triggers

When multiple orders meet the trigger conditions at the same time (such as stop loss and take profit being touched on the same K line), Wmax will be processed according to the preset priority: liquidation > stop loss > take profit > other conditional orders. This order is based on the urgency of risk control and cannot be modified by the user to ensure consistent system behavior under extreme market conditions.

If the user sets both server-side stop loss and local trailing stop loss at the same time, the two run in parallel and do not affect each other. Once any one is triggered, the position will be closed and the other order will automatically become invalid. The platform does not merge, optimize, or interfere with the coexistence of multiple orders, but faithfully executes each independent instruction. The certainty of the mechanism is higher than the smoothness of the experience.

User Autonomy: Matching Tool Openness and Responsibility

Wmax fully opens complex order tools to users, but it is not enabled by default and does not provide "intelligent recommendations". All advanced functions require users to actively turn on and complete a brief risk recognition confirmation (such as "I understand that the limit price stop loss may not be executed during a gap"). This design is designed to ensure that users of complex tools have basic cognitive readiness.

In addition, the platform provides a "simulation condition single test" function: users can verify whether the strategy logic is triggered as expected in the historical market replay. This is not about predicting the future, but about testing whether the understanding of the mechanism is accurate. True autonomy is not about having unlimited tools, but about making fully informed choices about what execution risks to take.

Conclusion: Transparency does not lie in the number of functions, but in the visibility of the logic

Wmax does not pursue automated gimmicks such as "one-click order following" and "smart profit taking", because that means black boxing decision-making. We believe that the real need of professional traders is not to be handled by the system, but to still be able to clearly see the execution basis of each step in complex strategies.

In a market full of uncertainty, the greatest certainty that a platform can provide is to make the mechanism itself a trustworthy infrastructure - not beautifying results, not hiding failures, not making choices for users, but only ensuring that there is clear, consistent, and verifiable logical support behind every click.