- ago
Quik broker provider feedback: WL7 stop order now deal with market stops only I guess, in this case there is only one price value for a stop order. And that's the trigger price. I may be wrong, but it looks like you get limit price from Quik stop order and show it as trigger price.

E.g. my Quik stop order is: send short limit order with price 10 when price is below 11. WL7 shows this order as Short stop with 10 price, I guess it should be 11, shouldn't it?

0
635
Solved
7 Replies

Reply

Bookmark

Sort
- ago
#1
Firstly, I haven't made any changes to the handling of orders (except for a cancel order fix) in months. Let me have a look in the code.
0
- ago
#2
I havn't used stop orders in production invironment yet), this is why didn't see it before.
0
- ago
#3
I'm not seeing anything wrong. I've tested stop orders extensively and they worked correctly.

P.S. Internally, all stop orders are translated by the QUIK broker provider into stop limit orders as this what platform supports. The limit price is equal to the stop price +/- minimum price step.
0
- ago
#4
I must have given more details), as always, sorry. My case is about stop orders that were set in Quik manualy. Now Quik provider gets such orders and let deal with them. My order was short stop order with price 10 and trigger 11. In WL7 it became short stop with 10 price. But in WL7 this price is trigger price.
0
- ago
#5
So maybe it works OK when WL7 -> Quik, but not OK when Quik -> WL7.
0
- ago
#6
Now I see what you mean: you're talking about stop orders in an Unmapped block. Yes, QUIK lets you enter a Stop Limit order whereas Stop orders placed from WL7 are pure stop orders (Stop ~ Limit price, with respect for the min.price step).

Unmapped blocks incorrectly took the limit price instead of the stop price which is fixed for Russia B26.
1
Best Answer
- ago
#7
A thing to keep in mind here is that a Sell stop order may be recognized as a Short stop by WL. QUIK doesn't help provider tell one from the other.
0

Reply

Bookmark

Sort