Amazon Not Recognising Case Sensitive Tracking ID's - Affecting VTR
Our Valid Tracking Rate (VTR) is now 71%, upon downloading the Valid Tracking Rate Report, Amazon is now marking over 40 of our shipments by an Amazon integrated courier (Panther), as Invalid. The Tracking ID is correct, but these are case sensitive. On the report, Amazon has converted all of these Tracking ID's into uppercase, which is why the Tracking Link does not work. This was previously not an issue, and we have reached out to the courier (AIT), who say there is no problem with their integration, so Amazon should be receiving scan events. Other Tracking ID's by the same courier are Valid, so it appears to potentially be a bug within Amazon that the case sensitivity of Tracking ID's are sometimes recognised, and sometimes not.
1 reply
Seller_i2m3ibhaEHcv7
Panther seem to think it's not a case sensitivity issue as they've stated the below in my emails with them:
"They use our API integration which supports uppercase tracking ids, so this wouldn’t and shouldn’t be an issue"
They're still trying to figure out the problem but my conversations with seller support suggest Amazon are looking at a different courier called Panther (Panther Premium Logistics), not Panther Warehousing (now rebranded as AIT).
