Not getting issues for a SKU despite receiving a LISTINGS_ITEM_ISSUES_CHANGE notification about it

[franclin]

I received a LISTINGS_ITEM_ISSUES_CHANGE notification for an item but when I run the getListingsItem operation to fetch the errors about the item, I am not getting anything useful.

Here is the body of the notification as well as its timestamp:

{"version":"0","id":"b8fad6ff-f6f7-2ab3-ae86-36079cd9cd58","detail-type":"LISTINGS_ITEM_ISSUES_CHANGE","source":"aws.partner/sellingpartnerapi.amazon.com/nnn/amzn1.sp.solution.050aaa","account":"xxx","time":"2025-01-11T20:21:29Z","region":"us-east-1","resources":[],"detail":{"NotificationVersion":"1.0","NotificationType":"LISTINGS_ITEM_ISSUES_CHANGE","PayloadVersion":"2023-12-13","EventTime":"2025-01-11T20:12:11.392Z","Payload":{"SellerId":"xxx","MarketplaceId":"ATVPDKIKX0DER","Asin":"1642555541","Sku":"9781642555547","Severities":["ERROR"],"EnforcementActions":[]},"NotificationMetadata":{"NotificationId":"b416e535-452c-4654-b7d0-0c0aaad1dcad","SubscriptionId":"4e6bd920-14db-4332-a1bb-6ed0b6570104","ApplicationId":"amzn1.sp.solution.050aaa","PublishTime":"2025-01-11T20:21:28.853Z"}}}

Then when I run the getListingsItem with the following request:
GET /listings/2021-08-01/items/xxx/9781642555547?marketplaceIds=ATVPDKIKX0DER&includedData=summaries%2Cissues%2CfulfillmentAvailability HTTP/1.1

I get this response headers:

200 OK
Date: Sat, 11 Jan 2025 20:50:40 GMT
x-amz-rid: S2HQ6GYSEJFGDT9VPY2S
x-amzn-RateLimit-Limit: 5.0
x-amzn-RequestId: 7c29fd0c-28ef-442e-b789-ed2e279c8606
x-amz-apigw-id: OPF7c29fd0c28ef
X-Amzn-Trace-Id: Root=1-6782d9a0-7c29fd0c28ef442e

Body:

{"sku":"9781642555547","summaries":[{"marketplaceId":"ATVPDKIKX0DER","asin":1642555541,"productType":"ABIS_BOOK","conditionType":"new_new","status":["BUYABLE","DISCOVERABLE"],"itemName":"The Empty Wagon: Zionism's journey from identity crisis to identity theft","createdDate":"2018-05-23T10:35:27.797Z","lastUpdatedDate":"2023-12-31T15:38:54.387Z","mainImage":{"link":"https:\/\/m.media-amazon.com\/images\/I\/41F6UiaEq0L.jpg","height":500,"width":335}}],"issues":[],"fulfillmentAvailability":[{"fulfillmentChannelCode":"DEFAULT","quantity":1007}]}

How should I fetch the issues about the troublesome SKU as I am merely following this guide: https://developer-docs.amazon.com/sp-api/docs/building-listings-management-workflows-guide#list-an-offer-for-an-item-that-already-exists-in-the-amazon-catalog?

Thanks

[jawheral]

Hi @franclin,

Your sku doesn't seem to have any issues currently. The sku is both in the Buyable and Discoverable status and has no issues as per the getListingsItem response. Are you experiencing any actual issues with the listing, its product detail page or other?
It could be that the notification was due to a certain issue tagged on the listing but more validations/processing were run later on and eventually issues got removed and the listing became healthy again. It could also be a one-time incorrect notification push.
Are you regularly receiving error notifications for your listings or was this a single occurrence? If this is regular, please create a case with Developer Support. If this is not frequent, and no actual issues are experienced with the listing, then I would suggest to ignore the notification.

Best,
Jawher
Selling Partner Developer Services

[franclin]

Thanks for your response @jawheral
We received this notification from time to time. Are you saying that in the future, receiving a notification with a Severities array set to ERROR doesn't guarantee that we will get the actual errors when invoking the getListingsItem operation?

Regards,
Franclin

[jawheral]

Hi @franclin,

No. What I'm saying is that if the getListingsItem operation returns no issues and you are not experiencing any actual issues with the listing then the notification itself could be misleading - either because of a notification bug or an actual issue that got validated and removed soon after. I'm also saying that if this is a repetitive experience and not a single occurrence then reach out to developer support so our teams troubleshoot the causes for the notification.

Best,
Jawher
Selling Partner Developer Services