Your stop-loss method matters after a trade fills. A stop order resting with the broker can keep working when your trading app is closed. A browser-monitored stop needs the browser tab, connection and device to remain active.
This difference is important during a power cut, internet problem, browser crash or device sleep.
How a broker stop-loss works
With broker-side protection, stop-loss and target orders are placed with the broker after the entry fills. The broker watches for the trigger and manages those orders on its system.
This gives the protection a better chance to remain active when:
- You close the Zensibly tab.
- Your device loses its internet connection.
- Your laptop sleeps or shuts down.
- The browser stops responding.
Zensibly calls this choice Broker bracket orders. It places real STOP and LIMIT orders at the broker where the broker and order type support them. Zensibly recommends this setting for new entries when it is available.
A broker order still carries execution risk. A trigger does not guarantee an exit at the trigger price. Fast movement, gaps, liquidity, rejected orders and broker problems can affect the result.
How browser monitoring works
With client-side protection, no stop-loss or target order rests at the broker. The open browser tab watches the price. When price reaches the selected level, the tab sends a MARKET exit request.
This method depends on several parts working together:
- The correct chart tab must stay open.
- The connection must remain active.
- The device must stay awake.
- The broker login must remain valid.
- The exit request must reach the broker and fill.
If the tab closes, the connection drops or the device sleeps, the position has no client-side stop-loss or target until monitoring resumes. A level can be crossed while the tab is inactive.
Why traders confuse the two
Both methods can show a stop line on a chart. The line looks similar, while the protection behind it is different.
The key check is where the active order or rule lives:
- A broker stop lives with the broker after it is accepted.
- A browser-monitored stop lives in the active browser session.
Check the broker order book after entry. Confirm that the expected protective orders exist when you selected broker-side protection. If they are missing or rejected, treat the position as unprotected until you verify the next step.
Want to understand the chart and connection limits before using a position tool? Read the Zen Terminal overview.
A practical protection checklist
Before placing the entry:
- Confirm whether the selected broker supports the required protective order.
- Choose broker bracket orders or client-side monitoring deliberately.
- Check the entry, target, stop-loss and quantity.
- Know what will happen if the internet or power fails.
After the entry fills:
- Check that the intended stop-loss and target are active.
- Read any broker rejection or status message.
- Keep the chart tab open for client-side protection.
- Keep the device awake and connected.
- Know how to close the position from the broker app if needed.
Which one should you use?
Broker-side protection is the safer default when the broker and order type support it. The order does not depend on one browser tab staying alive.
Client-side monitoring may support chart-based behaviour that you want to use. Accept the extra dependency only after you understand it. Keep a backup way to view and close the position through the broker.
Broker support and order behaviour can vary. Zensibly supports Fyers, Zerodha, Upstox, Dhan and Angel One, while individual features may differ by broker. Verify the available protection for your account and instrument before relying on it.