Skip to main content

Amazon unknown events issue (August 13 and later)

Who this affects

This issue affects only ConnectStock users who are on the Amazon ledger system in ConnectBooks. If you do not use the ledger, your numbers are correct and no action is necessary.


What happened

Amazon reports inventory movements in the Inventory Ledger Summary report. One of the movement types is called "unknown events". This type covers units that Amazon cannot match to a known reason, such as a receipt, a sale, or an adjustment.

Since August 13, the unknown events numbers in the Ledger Summary report are wrong. They do not agree with the Inventory Ledger Detail report. They do not agree with any other Amazon report.

Example: a SKU shows 400 units of unknown events in the Summary report. The Detail report shows 0 unknown events for the same SKU and the same date. Amazon gives no record of the 400 units.

This is a problem on the Amazon side. It is not a ConnectBooks calculation error. The issue is still ongoing as of today.

What we did

We stopped the use of unknown events in all inventory calculations for ConnectStock users. We also deleted the unknown event records that Amazon sent from August 13 and later.

Your inventory numbers now come only from movement types that Amazon reports correctly.

What you must check

The bad data was in the system from August 13 to August 25. If you did one of these tasks in that period, you might have to do the task again:

  • FBA adjustments. A FBA adjustment that you made for dates in this period can be based on wrong unknown event numbers. Double check if the numbers are correct and make sense.

  • Settlement exports. An export that you made for data that is in this period can contain wrong quantities. Delete and re-export the settlement for those dates.

If you did not do these tasks in this period, no action is necessary.

What happens next

We monitor the Amazon reports each day. When Amazon corrects the data, we will load the correct unknown events again.

If your numbers still look wrong after August 25, contact support.

Did this answer your question?