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

Aggregating multiple orders for same ticker before sending them - reducing trading costs for clients

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

I am automating multiple individual strategies on each stock ticker I trade. Some tickers may have 10 or more strategies applied to them. It is my understanding that each of these strategies sends a separate order to the broker. Therefore, I am required to pay commissions on each individual order even though all the orders are for the same ticker and happen at the same time.
It would be great to have MultiCharts add an option that would allow orders generated from multiple strategies to be aggregated before being sent. For example, if I have 5 strategies applied to SPY and each strategy is allocated 10 shares to trade, I would pay a $5.00 commission to trade these 50 shares. However, if there was an option to aggregate these individual orders and send them as one order for 50 shares, then my commission would be $1.00.
This would be a great way for MultiCharts to save their clients money and streamline the automated trading process. I am not a programmer, but the code required to execute orders in such a manner does not seem complex.
This would be a big help for me and others. I appreciate your consideration!

Steps to reproduce this issue

Please see description above

Comments (0)
There are no comments
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 (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