JSON_LISTINGS_FEED - valid, but Seller Central status "Missing offer" ?

[nightcoding2021]

I have uploaded the below template with fully valid data. The price, quantity, SKU all populate on the correct locale and the listing appears in results of "Manage Inventory".

However, the status is "missing offer", and I noticed the listing price isn't showing on the "manage inventory" results page. If I follow the product link, all required data (including our price) is populated in the data. If I then click "save", the listing goes live and the "missing offer" message has disappeared. However, I've added absolutely no additional data.

Therefore, why is JSON_LISTINGS_FEED not correctly setting the offer to live? I assume something is missing from the JSON below, but what? Why would Amazon have designed a system that is so easily able to fail?

Finally, it is totally absurd for Amazon to even be enforcing JSON files for price/availability updates on pre-existing product detail pages. In my view, the system and documentation obviously isn't up to the job - and if one considers how many billions of dollars in sales Amazon gets from these listings, it's simply unbelievable Amazon is enforcing a change to a system where users (and by extension, Amazon customers) are guaranteed to be worse off.

`{
"header": {
"sellerId": "valid_seller_id",
"version": "2.0",
"issueLocale": "en_US"
},
"messages": [
{
"messageId": 1,
"sku": "valid_sku",
"operationType": "UPDATE",
"productType": "PRODUCT",
"requirements": "LISTING_OFFER_ONLY",
"attributes": {
"condition_type": [
{
"value": "new_new",
"marketplace_id": "valid_marketplace"
}
],
"merchant_suggested_asin": [
{
"value": "valid_asin",
"marketplace_id": "valid_marketplace"
}
],
"fulfillment_availability": [
{
"fulfillment_channel_code": "DEFAULT",
"lead_time_to_ship_max_days": 2,
"quantity": 1
}
],
"list_price": [{
"marketplace_id": "valid_marketplace",
"value_with_tax": 0.00,
"currency": "EUR"
}],
"purchasable_offer": [
{
"audience": "ALL",
"marketplace_id": "valid_marketplace",
"currency": "EUR",
"our_price": [
{
"schedule": [
{
"value_with_tax": 5.00
}
]
}
]
}
],
}
}

]
}`

[nightcoding2021]

By way of update - on checking early the following day, the listings were "active" - so the above JSON is correct. But... WOW... this processing is slow. This is going to put Amazon at a massive self-inflicted disadvanatge - new listings appear just about instantly everywhere else. Result will be "everywhere else" takes the sales instead of Amazon.

The way things are, this JSON_LISTINGS_FEED enforcement is definitely happening. The only way to adapt I'm seeing is to (a) accept amazon sales will be decimated, and (b) accept sales will be elsewhere instead - as per above example proves.

[weilinggu]

@nightcoding2021

Adding some additional information here that might help speed up your updates. High priority updates and/or updates that require faster processing are generally better off submitting via the Listings API(PUT/PATCH) instead of JSON_LISTINGS_FEED. By calling the API directly you can skip the queueing of JSON_LISTINGS_FEED and overhead of batch processing and can get immediate feedback about whether or not your listing was successful. Do note that there is additional processing that will happen after the API call.

Thanks
Weiling
Amazon Selling Partner Services

[nightcoding2021]

I appreciate the suggestion but that isn't going to work. The Listings API is throttled at 5 updates per second. JSON_LISTINGS_FEED has a maximum of 10k lines and only allows submission once every 5 minutes (actually it's more like every 7 minutes). I don't yet know if those limits apply per account or per locale? This is totally unworkable. The existing arrangement of XML or flat files works fine, processes files in parallel (not sequentially) and there are two upload types - Inventory Loader or Price&Quantity. With JSON it's just JSON_LISTINGS_FEED and only one file per 7 minutes. JSON_LISTINGS_FEED adds absolutely nothing of value for sellers who are listing on pre-existing product detail pages only, and is in fact a major downgrade for a multitude of reasons. Including seemingly cancelling all the database processing improvements of the last 30 years.

Amazon need to realize this has been poorly designed and will simply not cope with the modern age of 2025. Updates need to be immediate, not taking between 6-12 hours after upload. There is zero visibility into the Listings API processing queue, or ability to delete anything that is queued.

Amazon needs to CANCEL this unbelievable proposal, especially when billions of dollars GMV are at stake, which is the case with this disaster. If Amazon is going ahead that's their call and mostly their billions to lose.

[weilinggu]

Hi @nightcoding2021,

Feed processing taking about 6-12 hour is abnormal, can you please open a support case to investigate?

getFeeds can provide visibility for processing status based on the feed type you provide.

Thanks
Weiling
Amazon Selling Partner Services