• Getting started
    • Steps to get started
    • Subscribe to a paid plan
    • Instructions
    • Pricing
    • Discounted Pro
  • Features (Trade logic)
    • List of all Trading features
    • Entry logic: Entry by Premium
    • Entry logic: ATM %
    • Entry logic: Straddle Width
    • Entry logic: Straddle Premium
    • Move Stoploss to Cost
    • Positional trades
    • Premium Matching functionality
    • Re-Entry / Re-Execute
    • Wait & Trade
    • Underlying based Entries & Exits
    • Range Breakout
  • Advanced Settings
    • List of all Advanced Settings
    • Entry order delay & Exit order delay
    • Calculate entry & exit using Average price or LTP
    • Re-entry method
    • Re-entry timing settings
    • SL order placement delay
    • Re-entry max count Type
    • Re-execute order delay
  • Order types
    • Order type: SL-Limit
    • Limit / SL-Limit EXIT orders
    • Limit / SL-Limit ENTRY Orders
  • Other features
    • Square off individual legs
    • Clientwise Stoploss & Target
    • Auto exit on margin error
    • Retry button for individual orders
    • Telegram Notifications
    • Advance placement of Re-Entry orders
    • Multiplier
  • Important topics
    • Limit Price Protection (LPP) mechanism
    • BSE Sensex, Bankex & NSE Midcpnifty
  • Broker Setup
    • Zerodha
    • Upstox
    • IIFL
    • Bigul by Bonanza
    • Tradejini
    • 5Paisa
    • AC Agarwal
    • Jainam Duck
    • Flattrade
    • Kotak Securities (Kotak Neo)
    • Fyers
    • Motilal Oswal

Clientwise Stoploss & Target


Clientwise Stoploss & Target (aka. Portfolio level Stoploss & Target)

This functionality allows a trader to set a portfolio level Stoploss or Target for a particular client id. If this overall Stoploss or Target is hit, all algos running on that particular client id will immediately exit. This functionality also allows Trailing of the stoploss, locking of profit, trailing of profit, and locking & trailing of profit at the client id (portfolio level).

I. Settings:

Click on Clientwise P&L seen on the top of the main page to view P&L of all client IDs configured on your Quantiply account.

Click on the Settings button ‘⚙️ ‘ under the individual Client ID container. It will open a pop up where the Target setting, the Stoploss, Trailed stoploss can be defined, for a particular Client ID.

There are 4 settings:

  1. Overall Target
  2. Overall Stoploss
  3. Trailing Stoploss, Lock profit , Trail Profit, Lock & Trail Profit
    1. Trailing Stoploss
    2. Lock Profit
    3. Trail Profit
    4. Lock & Trail Profit
  4. Trailing Frequency Interval (in secs & minutes)

All the values specified for target, stoploss, traling stoploss, lock profit, trail profit, lock & trail profit are given in amount (in rupees).

II. Stoploss or Target hit indication:

Upon hitting the ClientIDwise Target, the individual client id card turns green, and, upon hitting ClientIDwise Stoploss, the individual client id card turns red, to indicate Target or Stoploss type of exit.

This functionality also helps view client id wise live Total MTM.

III. Trailing frequency interval setting:

The Trailing frequency interval setting can be specified in seconds or in minutes. The default minimum setting is 5 seconds, which means that the system will check the running PNL's high every 5 seconds to check of the trailing stoploss or lock, trail or lock & trail profit conditions are met or not. If conditions are met, the stoploss or profit is trailed/locked based on your setting type.

The trailing frequency interval setting can be set to one of the following values: 5 secs (default lowest setting), 10 secs, 15 secs, 30 secs, 45 secs and 1 minute.

IV. Other important points:

  1. Upon click on the individual client id card, the algo table will filter out and show only those algos that are configured for the selected client id. So, click on any single client id or multiple client ids will act like a filter. The filter can be deactivated by deselecting the client id again, which will in turn show all the algos in the algos table.
  2. Say you have a total of 5 algos enabled for a particular client id, 3 of them are currently active, and the other 2 a configured to run at a later time in the day. If, the clientID wise SL or target is hit while the 3 algos are running, the 3 algos will immediately exit, and the other 2 algos which were configured to run later in the day, will NOT fire ie. those other 2 algos will not run as client ID wise SL or Target is already hit.
  3. In the above scenario, if you want the other 2 algos to run, then the client id wise Stoploss or Target setting can be modifed to a higher number. Once the SL or Target setting is increased, the client id wise SL and Target counters are reset and the positions in the other 2 algos will be taken.
  4. ClientID wise Stoploss and Target can be modified while algos are active and trades are open.
  5. This functionality considers all active algos running on a particular client id, in calculating the total current MTM, whether its a Positional algo running from previous days or current day Intraday algos. It will consider the MTM of all currently active individual algos. For example, if your client id wise Stoploss is set to Rs. -10,000, and you have 2 algos running - 1 positional algo from yesterday and 1 intraday algo which entered trades today. If the combined MTM of both these algos becomes Rs. -10,000, then both these algos will exit immediately.
  6. Once all algos exit upon hitting the Target or Stoploss for the current day, the Client ID wise Target or Stoploss counter will get reset by midnight on the same day, and fresh PNL calculations will start the next day morning as per the Target or SL settings given by the user.
  7. If you do not wish to have the same target or stoploss the next day for the client id, then it is important to reset or remove the Target or Stoploss setting for the next day. If the setting is not removed, it will apply for the next day as well.