+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-276

Position sizing: prevent partial fills

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

This issue is discussed in this thread on the support forum:


Currently, I might set a position size of $10,000 per automated trade (rounded downward).  This works fine as long as there is at least $10,000 in available capital. MultiCharts will buy about $10,000 worth of securities.
However, if there is a lower amount of available capital (e.g., $1,000 or $5,000), then MultiCharts will place a buy or limit order for a smaller amount of securities that matches the availability capital (e.g., just $1,000 or $5,000 worth of securities).    This is a particular problem if the available capital is just $100 or $200 -- then it places tiny trades that are basically just "noise" and generate additional broker fees.
I would like to have an option that says "trade only if there's sufficient capital for a complete fill, and don't make partial fills."  Even better would be to have a "minimum fill" setting -- i.e., logic that says "only trade if there's at least $___ available for the fill."  For example, I could then have it execute fills at anywhere between $2,500 and $10,000, depending on available capital, but no lower.

Steps to reproduce this issue

See support thread.

Comments (0)
Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
  • Posted by
    user-offline.png  Xyzzy (Xyzzy)
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    0 subscriber(s)
    Click here to show the list of subscribers
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates