11-28-2024 05:02 AM - edited 11-28-2024 05:03 AM
We are seeing an issue with the API and specifically the inventory_item endpoint when getting the full inventory list from it
We are using the inventory_item endpoint to get the ebay stock levels in bulk of all our products to see which ones we will need to update in terms of stock levels.
https://api.ebay.com/sell/inventory/v1/inventory_item
Since the 7th of November at roughly 23:00 (UTC) this endpoint seems to have stopped updating stock levels of the products returned in bulk as a list. Or from this point it at least seems the values returned are not correct.
The reason for my suspicion that it is not updating at all is that we from this time forward see an incrementally growing number of products being reported back with the wrong stock.
The endpoint is still returning the correct data for single SKU lookups.
I don't know if this could be something in our setup on ebay or a bug in the API or what might have caused it. But I'm sure this is happening.
As an example for one of our SKU:s, comparing it to the results when getting the data for just one product, defining the SKU:
This is the response from bulk getting the full inventory list on
https://api.ebay.com/sell/inventory/v1/inventory_item
```
{:sku "1234",
:locale "en_GB",
:product {:title "product name",
:aspects {:Brand ["brand name"], :Type ["Daily Use"]},
:ean ["0123456789101"],
:imageUrls ["image"]},
:condition "NEW",
:packageWeightAndSize {:weight {:value 0.0, :unit "KILOGRAM"}},
:availability {:shipToLocationAvailability {:quantity 1}}}
```
And this is the response from the single SKU request for the same SKU on
https://api.ebay.com/sell/inventory/v1/inventory_item/{SKU}
```
{:sku "1234",
:locale "en_GB",
:product {:title "product name",
:aspects {:Brand ["brand name"], :Type ["Daily Use"]},
:ean ["0123456789101"],
:imageUrls ["image"]},
:condition "NEW",
:packageWeightAndSize {:weight {:value 0.0, :unit "KILOGRAM"}, :shippingIrregular false},
:availability {:shipToLocationAvailability {:quantity 3, :allocationByFormat {:auction 0, :fixedPrice 3}}}}
```
As you can see the quantity differs in the two responses here:
:quantity 1 / :quantity 3
Calls were made within 5 seconds of eachother and there were no purchases for this SKU anywhere close to this time.
Viewing this SKU on the portal, we can see that 3 is the correct quantity (as returned from inventory_item/{sku} ) and that the bulk response with the full list of products is returning the wrong stock level (1).
For us calling all SKUs individually would take very long as we have a high number of SKUs on the platform, so for us this is not an option.
Don't know if anyone else has experienced the same issue and there is something we could do about it on our side, or if anyone at Ebay reviews this forum if this is potentially a bug.
Would be very thankful for any help regarding this.
11-29-2024 06:24 AM
I encountered the same issue; it seems that the value reported in :shipToLocationAvailability is completely made up. It doesn’t appear to be outdated.
11-29-2024 08:15 AM
The same issue is happening between getInventoryItem and getInventoryItems API calls.
getInventoryItem is returning the current values but getInventoryItems is sometimes showing information that is over 2 weeks old.
This is causing our system to think that hundreds of SKUs have the incorrect/outdated details.
We have a 10-day old ticket open but are still waiting for a resolution. No notice of this issue on the API status page yet.
12-03-2024 09:36 PM
yup, exact same thing happening to me.
12-11-2024 02:25 AM
@hausofbrillianceDid you get any updates on your ticket?
12-12-2024 10:15 AM
We've received quite a few replies stating that they have "synchronized" the data but it does not appear to be fixed. We are providing them with rlogs and are still waiting for an actual fix.