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

[nightcoding2021]

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

What end users (sellers) would like to see is Amazon include the JSON_LISTINGS_FEED feed final processing results back on the "Check upload status" page. I understand that won't appear immediately - it doesn't already for flat files. Please can that be discrepancy between the two fixed with urgency?

The initial parsing JSON results is useful but that's all it provides. The entire file contents could have failed processing.

[MetaMan2023]

I have been testing the Listings API (transitioning from XML feeds) using a "put" call and am finding a similar issue, that:

• A new listing appears quickly (within a few minutes)
• I can convert to MFN / FBA and set inventory and it appears in a few minutes
• I can set a price and it shows in the EDIT of seller central

However the listing keeps showing "Missing Offer" for extended periods of time... it seems the price, while set in the EDIT area of seller central does not appear in the Price column of the Manage All Inventory list.

Is there a large delay between the price appearing in EDIT and appearing in the "Price" field of the listing? Is this what is causing the "Missing offer" issue?

[nightcoding2021]

Is there a large delay between the price appearing in EDIT and appearing in the "Price" field of the listing? Is this what is causing the "Missing offer" issue?

What you describe is what I've also witnessed. It seems the "missing offer" message takes varying time to clear - presumably sometimes hours - I give up and call it a day. In the morning, the "missing offer" message is gone. This is one reason (along with others) why this JSON_LISTINGS_FEED (or Listings API) change will cost Amazon billions in lost GMV. The offers won't even be there to buy on Amazon. I've pointed this out to Amazon but so far they've ignored it. Not much else I can do - seems they're going ahead anyway. One thing I'd mention is: should Amazon pick up the phone to eBay and let them know billions of GMV are being gifted to them?

[krzemian]

@MetaMan2023 @nightcoding2021 it seems I'm experiencing the very same issue when using flat files.

• Flat files are processed correctly
• In "Manage All Inventory", listing status shows a red "Missing Offer"
• Price is empty (0.00, red input field border)
• When pulling up a Category Listing Report, the prices show up correctly under the Your Price column
• For all above SKUs, I'm able to quickly update the price via Seller Central (i.e. through "Manage All Inventory") which removes the "Missing Offer" (replaced with "Out of Stock")

However, this is most definitely not a viable solution for me. I'm leaving it out there in case there's anyone else out there with a potential fix

EDIT (fix): I'm not entirely sure if this is useful for API users directly, but in case any lost soul comes here desperately looking for any fix, the way I solved was through using the Price & Quantity flat file template. It allowed me to update the price & fix the “Missing Offer” error in bulk. While it's not ideal (2 file uploads rather than a clean, single-step solution), it definitely gets stuff done

[nightcoding2021]

What you are witnessing is identical to JSON file uploads and the initial "missing offer". Most likely, if you allow more time (it can be hours) then the Amazon systems will apply the other data e.g. price.

[krzemian]

In my case it didn't resolve after 48+ hrs, so I resorted to Price & Quantity file uploads