Please enter a valid Tracking ID - Stamps/Franking
Since a couple of days back I’ve started to get the red “Please enter a valid Tracking ID” when confirming orders as shipped by “Royal Mail 2nd Class Stamps/Franking” option. If I click confirm again and just ignore it then it all goes through fine.
Anyone else getting this? I feel it is a purposeful “glitch” by Amazon to hint that the franking options will soon not be okay? I’m just a bit concerned these orders are going to show up on my VTR in a couple of weeks!
32 replies
Seller_ZQyopdiwkUHOZ
It seems to have started being rolled out last Friday, with it hitting accounts at different points this week. So far as we know, you can just do as you’re doing. Keep an eye on the forums in case that changes, though.
Seller_AhQJGf0tCpM25
There is - right at the bottom of the drop down menu - “Stamps/Franking”. Use that. DON"T use 2nd class/Stamps/Franking.
My VTR is n/a and has been for weeks.
Seller_JVrK6emk6S3ur
I dispatch everything through click and drop, but it sets the postage method on Amazon as 2nd class untracked, is there anyway for it to automatically set everything as stamps/franking ? i dont want to sit there and manually change everything everyday.
Seller_x1xMSBwZsJrTE
It’s their way of weilding the big stick and dropping hints that you belong on the naughty step.
Seller_QyPYkLGi6rr1f
Isn’t it to do with news topic from 13th October ? -
13 October 2021 ### Carrier and tracking information will be required starting November 1
Seller_B9p4s6plEXSDE
Same here, that’s what I am thinking too 
Seller_a71PzvzRJM0fe
cant they see this will be the death of cheap items on amazon? amazes me how stupid this all is.
Seller_qs0SIvVwguCY5
Not sure what’s going on here but we are still not seeing a request for tracking when we dispatch letter sized items, both when we dispatch individual orders, or in batch.
We are still dispatching with:
Ship From: GB
Royal Mail 2nd Class Stamps/Franking (this is set as our default)
Our VTR is currently 100%
Our OTDR is currently 100%
We will keep monitoring this and report if anything changed. It may be that our own account has not been updated with this new development yet. Hard to understand why some dispatching in exactly the same way are seeing the warning and some ae not.
