# Order size incorrectly scaled for TradeBullet **URL:** \ **Category:** C2\ **Created:** [May 8, 2012, 3:14pm UTC](https://forums.collective2.com/t/order-size-incorrectly-scaled-for-tradebullet/5676 "2012-05-08T15:14:09Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![PanuHaaramo](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/panuhaaramo/32/238_2.png) [@PanuHaaramo](https://forums.collective2.com/u/PanuHaaramo)\ **Post date:** [May 8, 2012, 3:14pm UTC](https://forums.collective2.com/t/order-size-incorrectly-scaled-for-tradebullet/5676/1 "2012-05-08T15:14:09Z")
Hi, looks like order size scaling is working incorrectly when sending orders to TradeBullet. In this case the original order size was 1150 and my scaling is 25% (with $10 000 max) so my order size should have been 288. Instead C2 sent to TradeBullet order to sell 138 and in the next sync 150 more was sold: 2012-05-03 17:17:14:057 (2012-05-03 14:17 UTC) Processing new Collective2 order: TB Order TB629246 \ PLACE SELL 138 HCII LIMIT 14.94 DAY, System: 1st , Signal: 73306490 Please check. Thanks, - Panu ---
**Author:** ![MatthewKlein](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/matthewklein/32/21382_2.png) [@MatthewKlein](https://forums.collective2.com/u/MatthewKlein)\ **Post date:** [May 8, 2012, 3:23pm UTC](https://forums.collective2.com/t/order-size-incorrectly-scaled-for-tradebullet/5676/2 "2012-05-08T15:23:41Z")
This was a Sell To Close order. For "to Close" orders, the quantity sent is based on the amount of the OPENING position your TradeBullet reported to us as filled. Signal 72481150 (one of the 2 legs which was the matching BTO order) was never acknowledged as filled, and thus the closing order size was smaller than you expected. Matthew ---
**Author:** ![PanuHaaramo](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/panuhaaramo/32/238_2.png) [@PanuHaaramo](https://forums.collective2.com/u/PanuHaaramo)\ **Post date:** [May 8, 2012, 3:32pm UTC](https://forums.collective2.com/t/order-size-incorrectly-scaled-for-tradebullet/5676/3 "2012-05-08T15:32:12Z")
OK, can you fix that? It’s not possible to autotrade without sync enabled so you can assume the position size always matches scaling. - Panu ---
**Author:** ![MatthewKlein](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/matthewklein/32/21382_2.png) [@MatthewKlein](https://forums.collective2.com/u/MatthewKlein)\ **Post date:** [May 8, 2012, 3:54pm UTC](https://forums.collective2.com/t/order-size-incorrectly-scaled-for-tradebullet/5676/4 "2012-05-08T15:54:02Z")
This is not really a bug. It’s the design: closing sizes are based on opening fill reports. I don’t think we’ll be able to change that. ---
**Author:** ![PanuHaaramo](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/panuhaaramo/32/238_2.png) [@PanuHaaramo](https://forums.collective2.com/u/PanuHaaramo)\ **Post date:** [May 8, 2012, 4:03pm UTC](https://forums.collective2.com/t/order-size-incorrectly-scaled-for-tradebullet/5676/5 "2012-05-08T16:03:05Z")
Yes I understand this was built as a feature at the time when autosync was not yet working and thus autotrading was a pain. But nowadays when sync is available this feature causes more harm than good. Of course it could be made available as an option if someone for some reason would still like to use this feature. ---
**Author:** ![PanuHaaramo](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/panuhaaramo/32/238_2.png) [@PanuHaaramo](https://forums.collective2.com/u/PanuHaaramo)\ **Post date:** [May 14, 2012, 9:41am UTC](https://forums.collective2.com/t/order-size-incorrectly-scaled-for-tradebullet/5676/6 "2012-05-14T09:41:23Z")
Today I got again a big slippage because of this "feature". I really hope it can be turned off in the future.