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

"Reverse" command in chart trading results in two separate orders

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

Using the "Reverse" button of the chart trading module results in two separate orders: one to close the current positon, and one to open the reverse position.
Depending on the broker's commission scheme, this can lead to increased trading cost:
If a minimum commission is charged for small order sizes, two separate orders will cost twice as much as one single order.  
From my perspective, expected behaviour is that only one single "big" order is generated to close the current position and to open the reverse position.

Steps to reproduce this issue

Example: FX trading via IB
Buy 20k GBP.USD -> one order "buy 20k" will be generated
Reverse position (via "Reverse" button) -> two orders "sell 20k" will be generated; expected behaviour is that only one single order "sell 40k" will be issued.
Since the order size in this example is rather small, a minimum commission will apply for both sell orders.

Comments (2)
user-offline.png  MultiCharts Support (MultiCharts)
Mar 21, 2013 - 20:56

The behavior is expected. If you want to reverse by 1 order, you should sent such order with required number of contracts.

user-offline.png  seneca (Seneca)
Mar 22, 2013 - 01:08

As the "Reverse" button is intended to reverse the current position: what is the benefit of doing this by two separate orders instead of by just one order? Maybe you may want to shed some light into this.

Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Under Review
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