We realized these cases and are willing to subsidize the incurred expenses of this failure ka. Apologies for this mistake. One case caused by 3PL (WS16052200864) and another case caused by our own fleet (WS16052500064). Both cases happened from initial wrongly status update and recorrected later on. Unfortunately our system triggered the first status that API. We’ve pushed hard to the 3PL and our fleet by highlighting that the shipping status of this project must be specially aware due to it cannot recorrected as usual because of the top-up factor ka.