Pricing Updates using JSON_LISTINGS_FEED vs. Listings API -- how long does it take to update prices?? Process OK but prices never change?

[MetaMan2023]

I'm trying to transition from XML to JSON for pricing updates before the deadline.

I first tested a JSON feed, as I was using XML feeds for pricing before so it was the most logical. My feeds were accepted and process fine (no errors), however my prices never changed. I was wondering if there is a long delay.

Q#1: When the documents say it can take "minutes to hours" for feeds to process, does that mean for them to return with an error status -- or does that mean even AFTER they return with no errors, does it still take hours for them to "complete" on the back end? I get back the status like "messages processed = 10, errors = 0" but nothing changes.

I then switched to try the Listings API, thinking the pricing change would happen more quickly -- I ran some tests, and received back "ACCEPTED" status with a submission ID and no issues.

Q#2: How long does the Listings API take to process a price change once accepted? Again, can that mean "minutes to hours" AFTER being accepted?

It's very hard to trouble shoot these APIs with such minimum errors and these delays.

[nightcoding2021]

FYI, I believe they extended the deadline from 31 March to 30 June.

However, that doesn't change the fact this is a complete disaster. Possibly there was some merit in Amazon moving product creation to JSON, but for price/availability updates this is totally uncalled for.

Personally, I'm wondering if we'll even be selling on Amazon after 30 June. The JSON_LISTINGS_FEED has absurdly low limits.

The error reporting is a joke and all the report now refers to is whether or not the JSON file was parsed. Nothing about the actual inventory upload results - dumb or what? Sellers combined will be selling billions of dollars, all maintained via existing flat file and XML price/inventory status updates. So for those billions of dollars, Amazon is now turning off inventory results reports? Say what?! Amazon will say to obtain via other means, but it isn't the same as tied to the exact inventory file update.

Looks like the biggest disaster since eBay GTC in April 2019!

Amazon can eliminate this by cancelling the proposed switch off in respect of price/inventory update files.

[weilinggu]

Hi @nightcoding2021,

You can use includedData in the feed header to get additional information such as issues on the listings you submitted in the feed.

See announcement and workflow guide.

Thanks
Weiling
Amazon Selling Partner Services

[jawheral]

Hi @MetaMan2023,

Price update reflection depend on multiple factors, feed processing time is not the only factor. For instance, some listings may be given higher priority and get updated faster than others, others are delayed. For faster processing of your prices updates, make sure to consider the following recommendations:

• use the patchListingsItem operation to update the offer/price for a 1x1, faster update of a listing
• are you sending full updates of your listings, with potential duplicate data, with the price changes? Ensure the JSON feed only includes messages with price patches
• Are you sending price updates with the same price? remove unnecessary updates by pre-checking current prices either with getListingsItem or using your caches
• Always check listings issues after processing by adding issues within includedData parameter in your getListingsItem operation or your json feed options. Or subscribe to LISTINGS_ITEM_ISSUES_CHANGE notification for updates regarding post-processing issues.

Best,
Jawher
Selling Partner Developer Services

[nightcoding2021]

Q#2: How long does the Listings API take to process a price change once accepted? Again, can that mean "minutes to hours" AFTER being accepted?
It's very hard to trouble shoot these APIs with such minimum errors and these delays.

It seems to take at least a few hours and perhaps more... and that was my trial run of just two - yes TWO - updates! The speed is obviously totally unworkable more akin to something out of a bygone age, as opposed to 2025. it's as if Amazon decided to throw away all modern database management and speed, and revert to something like pen and paper. Perhaps they actually have someone printing out these updates, and someone else then manually typing them in? Now of course, I'm joking, but... if that was true it'd explain the delay.

I think people need to see the writing on the wall - Amazon know what they are doing. The message I've inferred is to pack my bags and go elsewhere.

[hsbrendan]

I'm also experiencing this same problem... with only 2 weeks to go until the only API that works is being deprecated.

Please escalate.

[ritikacd]

Hi @hsbrendan

Can you please explain the issue you are experiencing?

Thanks,
Ritika

[hsbrendan]

Thanks @ritikacd . My price update is accepted via the API, but never appears on the site. It appears that internally, it still retains the previous price and reverts to that price - see screenshot (redacted) - the previous price was 3.49 and I updated the price to 4.22, but it says "match lowest price" and still somewhere is keeping the £3.49.

[danielsan1398]

Same problem, have you found the issue or a workaround?

[ritikacd]

Hi @hsbrendan

Accepted means submissions are accepted for further processing. It is possible that issues occur on listings items during asynchronous processing after acceptance.

Have you checked for the asynchronous errors? You can use getListingsItem operation to retrieve the list of issues by specifying issues in the includedData parameter.

If you don't see any issues and price still doesn't reflect, please reach out to our developer support team.

We recently published a Postman collection on updating a listings item using best practices. Check it out here.

Thanks,
Ritika