Listing getting deleted and stranded inventory

Countries

Read only
Australia
Belgium
Brazil
Canada
Egypt
France
Germany
India
Italy
Japan
Mexico
Netherlands
Poland
Saudi Arabia
Singapore
Spain
Sweden
Turkey
United Arab Emirates
United Kingdom
United States
United Kingdom
imgSign in
user profile
Seller_E83uuzTny2KeZ

Listing getting deleted and stranded inventory

Hey forum members.

I've updated a few of our listings this evening with a couple new pictures, refreshed the bullet point information and matched our A+ content with the bullet points for consistency across the product listing.

After doing 4 or 5 listings, all of them were deleted with FBA inventory set to stranded. I did not delete any listings or break any rules in regards to policy, it seems very odd that after updating pictures all listings got deleted.

Any idea why this might have happened or the best way to reinstate the listings so that I don't have to pull all the stock out of FBA warehouse and remake 5 new listings with new EAN numbers?

691 views
35 replies
Tags:A+ content, ASIN, Listing deactivated
30
Reply
35 replies
user profile
Seller_WLiKCF7aslXSR

Yeah same, 32 listings deleted.

Very strange

00
user profile
Seller_GcvaP0gT1T0l2

Us too. About 23 ASINs stranded.

10
user profile
Seller_WLiKCF7aslXSR

Got a listing relisted only for it to be deleted again.

00
user profile
Seller_E83uuzTny2KeZ

post.If this is happening to multiple people then surely it's a glitch, I'm scared to do any updates now incase it deleted more listings.

20
user profile
Seller_hSaVHsK7VePKI

I got my two listing first stranded and then deleted, I pressed on create new listing and seems they are back..? glitch?

00
user profile
Seller_hSaVHsK7VePKI

Hi,

Just happend again overnight....... not sure what to do has anyone got any help from customers support?

00
user profile
Seller_J4rf2ctoJPysT

Do any of you use 3rd party software for listing updates / stock management?

00
user profile
Seller_J4rf2ctoJPysT

Anyone resolved the issue yet? Seems like this is something more in Amazons backend then our fault.

00