Amazon Notification Log
Amazon Notification Log shows the push notifications from Amazon that have arrived through the Amazon Notification API, newest first. There are entries only if push notifications are set up for your company; ALTENBRAND support takes care of that. Without them, the page stays empty, and orders and cancellations come in with the order import.
Opening the Page
- Via search: Amazon Notification Log
- Via the Amazon Administration → Related → Notification Log
Fields
| Field | Description |
|---|---|
| Entry No. | Sequential number of the entry. |
| Notification Type | Type of notification, e.g. ORDER_CHANGE or FEED_PROCESSING_FINISHED. |
| Status | Processed (green), Failed (red) or Ignored (gray): the notification did not require anything of the connector; Error Message gives the reason (see below). |
| Received At | Time the notification was received. |
| Processed At | Time of processing; empty for Failed. |
| SKU, ASIN | SKU and ASIN of the offer for LISTINGS_ITEM_STATUS_CHANGE; for ANY_OFFER_CHANGED and B2B_ANY_OFFER_CHANGED only the ASIN. The SKU is shown the way Amazon keeps it (upper and lower case are preserved). |
| Amazon Order ID | Order of an ORDER_CHANGE notification. |
| Notification ID | Identifier that Amazon gives the notification. The connector uses it to recognize a notification that arrives a second time. |
| Error Message | The reason if processing failed (only then shown in red), or why a notification was ignored. |
Ignored notifications
Ignored means: the notification arrived but did not require anything of the connector, and the connector changed nothing. Error Message gives the reason:
| Reason | When |
|---|---|
| Notification for another seller account | The Seller ID is not the Merchant ID in the Amazon Settings. |
| Marketplace without participation | The notification is for a marketplace that is not one of your marketplace participations (see Amazon Marketplace Participations). |
| Listing status change without SKU | LISTINGS_ITEM_STATUS_CHANGE names no SKU. |
| Order change without Amazon order ID | ORDER_CHANGE names no order. |
| Type the connector does not process | for example an inventory change; see Amazon Notification API. |
| Not readable | no valid JSON, or the type or payload is missing. |
| Delivered again | Amazon delivered the same notification (same Notification ID) once more; it is not processed again. |
Actions
| Action | Description |
|---|---|
| Reprocess | After you confirm, processes a failed notification again. If this succeeds, the entry is set to Processed or, if the notification requires nothing, to Ignored with the reason, and the stored payload is deleted. If processing fails again, the entry remains unchanged. An entry without a payload cannot be reprocessed. |
| Clear Old Entries | After you confirm, deletes the processed and ignored entries that were received more than 30 days ago (Received At). Failed entries remain until they have been reprocessed or the nightly PII_RETENTION job deletes them. |
| Open Amazon Item | Opens the Amazon Item Card for the SKU of the entry. Only the Amazon items are searched: first by SKU, then for an Amazon item without its own SKU whose item number is the SKU. If the entry has no SKU, as with order and offer notifications, the action reports this. |
Tips
Which data is kept
Only a failed entry keeps the payload of a notification, that is, the data Amazon sent, so that Reprocess can process it again. A processed entry has done its job and keeps no payload, and neither does an ignored one; a notification about an order can contain order data. There is no action that displays the payload.
Retention
The PII_RETENTION job deletes entries older than 30 days every night, regardless of their status.