Black Friday Sale! Up to 50% off on MultiCharts with the Advanced Strategy Pack Learn more...
+1 888 340 6572
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Feature request MC-1926

Automatic position sizing based on Risk Amount

Go to the next issue (open or closed)
Go to the next open issue

When placing an entry order with a stop loss order attached to it there should be an option to automatically calculate and set the position size based on a set risk amount. When you change the entry order level or the attached stop loss order level, position size changes accordingly based on the set risk amount.
This is a basic money management technique. If this routine would be automated, it would provide traders with more time to check the quality of their trades instead of on calculating the position size manually.

Steps to reproduce this issue

AgenaTrader has implemented this very well (with even more risk and moneymanagement options). I attached a link to their online help where their implementation of automatied risk and money management is explained.

Comments (2)
user-offline.png  Michael B (michael b)
22 nov. 2017 - 00:35

Excellent request. I'm also hoping for this option in Multicharts. Who will take a step ahead with this possibility. Thank you in advance!

user-offline.png  mika971 (mika971)
08 nov. 2019 - 23:31

hi ,
Please check the tool i've developped :

Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    Not determined
  • Status
    Not Reviewed
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
Attachments (2)
  • /pm/public/files/show/733
    Position size is automatically adjusted uploaded 10 sept. 2015 by madema (madema)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates