05-05-2025 11:17 AM
I am a UK seller and have just found out for second time in 2 months ALL my postage policies have been changed WITHOUT my knowledge from GSP enabled to GSP not enabled. Luckily I only have 25 policies so I have just re-enabled them. I have reported this again to eBay Concierges. Annoying as a seller as we have no idea this has changed. I had begun to wonder why my international sales had dropped to zero
06-05-2025 7:57 AM
Similar problem here. For the second time in a few months, one of my postage policies has had the GSP option remotely turned off too (sometime in the last week - I only realised because I had noticed that there were no GSP sales again).
It is the policy that use most often, with nearly 3000 listings.
There is an additional bug though. When I go to 'revise postage policy' and turn the GSP option back on, it won't let me save the new setting. After clicking the 'save' button, I get the following error in a red banner:
'Policy with identical attributes already exists'
As though I had tried to create a new policy.
06-05-2025 8:06 AM - edited 06-05-2025 8:08 AM
Best I can suggest for policy that will not update is to create a new one then transfer all listings to new policy, then delete the old one. I have had to do this with a couple of mine.
Contact eBay CS and report the issue. The more sellers who report this the quicker it will be resolved
07-05-2025 9:57 AM
Thanks for the reply stampsnallsorts.
I have contacted eBay CS and a nice lady couldn't help me but has promised to open a ticket for the tech team to look at.
I know this can take a while if anything happens at all (you probably know this too) but luckily I have managed to find a work around.
To get around the 'Policy with identical attributes already exists' error, I had to change something else, in addition to turning the GSP back on. I my case, I just increased the Special Delivery option price by £1
It seems to be working, I didn't get the error at least, and for now, GSP is showing up as being switched on again. It seems as though the program just wasn't recognising if the button was on or off.