search

amzn / selling-partner-api-models

This repository contains OpenAPI models for developers to use when developing software to call Selling Partner APIs.
Apache License 2.0
612 stars 737 forks source link

[BUG] [SP-API] [Issue] Inventory feed creates random listings when no matching SKU found (POST_INVENTORY_AVAILABILITY_DATA ) #2474

Closed DevBrent closed 1 year ago

DevBrent commented 1 year ago

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Feature request
[ ] Documentation issue or request
[ ] Other... Please describe:

SP-API Name and Version or Report/Feed Type

/feeds/2021-06-30/feeds POST_INVENTORY_AVAILABILITY_DATA

Expected Behavior

Should only update inventory availability for existing products.

Current Behavior

Amazon support explained that since the 3rd party uses feed files to upload stock counts, it will create a new listing if it does not find any matching SKU on our inventory page on Amazon. This will cause the "random listings being created" and "unknown batch ids" being generated on our account.

Context

This feed is the only way to make bulk updates to inventory data for an account. It is unreasonable to require that third-party platforms run reports that could take 20+ minutes to generate in order to double-check none of the SKUs have changed. Without an opt-out for this bad behavior, merchants will continue to see rogue listings created when they change SKUs on Amazon causing the POST_INVENTORY_AVAILABILITY_DATA to create new products the next time stock sync is run from those platforms.

Your Environment

Amazon Canada

DevBrent commented 1 year ago

amzn/selling-partner-api-models#2179 has a similar issue where Amazon is reporting in the feed response:

This SKU is not in the Amazon catalog. If you are receiving this message after submitting a multi-marketplace inventory file and the designated marketplace for this error is different than the marketplace in which you submitted your file, this error is an indication that the Detail page for this item does not exist in the designated marketplace. Amazon is attempting to create the Detail Page for this item on your behalf. If successful, your listing will be created in the designated marketplace within 48 hours.

This sounds like very incorrect behavior.

Can this be opt-in only?

We expect the SKUs we've been told to work with to continue to work or fail.

If the SKUs change, all interested parties would prefer to NOT create new products out of those SKUs. Our customers just need to know the SKU errored and to run a listings sync on our end to catch up to the updated SKUs on Amazon's side.

As it stands, we would need to export all product data just to find out which SKUs still matched from the last time before we submit each inventory feed.

github-actions[bot] commented 1 year ago

This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one.

github-actions[bot] commented 1 year ago

closed for inactivity