API error! If you notice that tracking number is not generated when - - PowerPoint PPT Presentation

▪ If you notice that tracking number is not generated when you set your

• rder status to ‘ready-to-ship’

✓ Please contact our Seller Helpdesk immediately × Kindly refrain from inputting your own tracking number as this will result in the cancellation of your order → A penalty will be incurred when Seller cancels an order

DO NOT input your own TN while API error!

▪ ZALORA charges Per Product Service Fee, not per package. Packing two

• rders into one will not save costs, but results in troubles

✓ If you notice that the same customer places multiple orders with same delivery address, please pack and ship them separately × Kindly refrain from packing multiple orders into one as 3PL will only scan

• ne tracking number per package and charge the customer COD for the

scanned AWB only → Seller needs to bear the loss for the package when COD amount is not paid by customer

DO NOT pack multiple orders into

• ne!

▪ If so, more than one tracking number will be generated. The COD amount will be also separated by item. ✓ Same logic. If you accidentally found two AWB generated for one

• rder as photo shows, please still ship out separately!

× Kindly refrain from packing items with different tracking number into one as 3PL will only scan one tracking number per package and charge the customer COD for the scanned AWB only → Seller needs to bear the loss for the package when COD amount is not paid by customer

DO NOT process an order with multiple items separately!

▪ The tracking number cannot be changed in the system after the auto- generation ✓ Please contact our Seller Helpdesk immediately for a solution × If sellers use their own AWBs, customer would not be able to track the parcel × Sellers could miss stating COD amount on the AWB for COD orders, then 3PL will not charge customer accordingly. → Sellers need to bear the loss for the unpaid COD

DO NOT use any AWB that are NOT generated by Seller Center!