TrackingNo Latency and Duplicate TrackingNo Issues

Dear Partner,

If you have experienced the below two issues since Thursday 30/8, please note we have been working with logistics team closely and urgently to resolve them.

• For integrated logistics channels(pickup & dropoff), severe latency on fetching TrackingNo when calling Init API(AirwayBill latency is most likely caused by its precedent step of fetching TrackingNo).

Workaround:

• Retry calling Init or GetOrderDetails API in 10-15 mins for multiple times;

• Batch arrange shipment in Seller Centre

• Return duplicate TrackingNo after calling Init API

Workingaround:

• Retry calling Init or GetOrderDetails API and it should return the correct trackingNo

Sincere apology for the inconvenience it brought and we will keep you updated.