Inspect the Inventory Change History
To inspect the history of inventory adjustments and the reset of physical counts for a specific item variation (for example, to create an audit log), call the RetrieveInventoryChanges endpoint, while specifying the item variation with the catalog_object_id
URL path parameter value. You can also use the location_id
query parameter to filter the result by location.
To inspect the history of inventory changes for multiple item variations, call the BatchRetrieveInventoryChanges endpoint, while specifying the desired input parameters in the request body.
On this page
The cURL example retrieves the change history of the item variation identified by its ID value of 6F4K33KPNUVDWKZ43KUIFH6K
.
A successful response is shown as follows.
In this example, the history includes:
An adjustment that adds 100 units to the inventory when the inventory state changed from
NONE
toIN_STOCK
.An adjustment that marks 2 units as damaged items when the inventory state changed from
IN_STOCK
toWASTE
.A reset of the in-stock count by an actual physical count.
The following cURL example retrieves the change history of the item variations identified by their ID values of 6F4K33KPNUVDWKZ43KUIFH6K
and IJBAQDICELYUAUTHM352X3AI
. The input values are specified in the catalog_object_ids
of the request body.
A successful response is shown as follows. In this example, the change history includes:
An adjustment that adds 100 units of the first item variation (
6F4K33KPNUVDWKZ43KUIFH6K
) to the inventory when the inventory state changed fromNONE
toIN_STOCK
.An adjustment that marks 2 units of the first item variation (
6F4K33KPNUVDWKZ43KUIFH6K
) as damaged items when the inventory state changed fromIN_STOCK
toWASTE
.A reset of the in-stock count of the first item variation (
6F4K33KPNUVDWKZ43KUIFH6K
) by an actual physical count of 95.A reset of the in-stock count of the second item variation (
IJBAQDICELYUAUTHM352X3AI
) that adds 75 units to the inventory.
If you need more assistance, contact Developer Support or ask for help in the Developer Forums.