Disappointed am I in the event itself, but not in the expectation - STRIKE THREE had already occurred with another of Xander_Amazon’s posts, this one from 030226, which includes yet another faulty URL (in-text link ‘broken’ for Discourse display):
Let us recap:
On 030226, Xander made two separate posts, w/ two different dead links, and on 030526 Ram provided a third.
The chinks in the armor grow wider and wider…
At some point between 020526 - when last I recorded one of Ammy’s posts - and 2026-03-10T04:00:00Z, the name has changed to “Amyy_Amazon”:
https: //sellercentral.amazon.com/seller-forums/profile/d870dc51-a941-4141-8e9d-f30c1d1de3f4
There’s a new ‘About my business’ statement/blurb as well:
The change in the latter alone would seem to me strongly suggestive of some conscious volition on the part of the user, but I find a change from “Ammy” to “Amyy” somewhat strange - especially when the ‘About me’ statement has not changed from what it was on 122425:
Or, mayhaps, it’s just yet another example of how its software deployments increasingly elude Amazon’s control…
The ongoing foibles w/ posting inaccessible links marches on:
The link currently embedded in Sandy’s “Amazon Product Support page” is this:
https: //s3.amazonaws.com/OnDemandProd/%2F739c9191590942c59f900fe42453a38a/69a04ea2000122353012ab456691e918_69a04ea2000122361754b885d6712d5e?response-content-disposition=inline%3B%20filename%3D"Seller_Central_02_25_26-1.pdf"%3B%20filename*%3DUTF-8’'Seller_Central_02_25_26-1.pdf&response-content-type=application%2Fpdf&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20260313T162144Z&X-Amz-SignedHeaders=host&X-Amz-Expires=60&X-Amz-Credential=AKIASBHFXT6MHAVEE7XQ%2F20260313%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Signature=9ed6a4b93974d1aa4f641b7dedf7ace20f376c078aba3accd22581f4e287f835
It’s not clear to me whether the intended target is the Home/Landing page (aka Enrollment Portal) “Welcome to Product Support” @ https: //sellercentral.amazon.com/productsupport - which has already made an appearance here, in Post #258 upthread - or the SHC’s “Amazon Product Support” @ https: //sellercentral.amazon.com/help/hub/reference/K4MGCBF7LJYKGQM, or to something else entirely (n.b. that there appears to be a .pdf doc, revised 022526 & perhaps titled “Seller_Central_02_25_26-1.pdf,” in the target string).
This continuing debacle is hardly the never-ending story I’d like to be living…
Oops - I neglected to include the NSFE URL for this discussion, and missed the 15-minute Editing Window to add it, so here it is:
https://sellercentral.amazon.com/seller-forums/discussions/t/c44d226f-1927-4efe-905a-b96c1db5ddac
Mea culpa…
And I like Sandy – she’s generally one of the better ones. Which reminds me, I need to clean out or modify some of the templates I rely on for responses there…
Maybe next month….
I cannot speak to anything but our own SoA Accounts, but the path which Xander indicates for accessing the Payments Dashboard in this 031326 post (emphasis mine) has been deprecated since 2024, when (@ least for us) the Payments link was segregated from the Reports sub-section of the page-left Seller Central Menu in favor of a sub-section of its own:
I’ve mentioned before (link, Post #263 upthread) that Xander was apparently one of the early adopters among the FMT-CMT in using GenAI to generate content for NSFE replies, and a significant portion of the posts he’s made over the last several months seem to exhibit an increasing devotion to that paradigm.
Unless I once again miss my guess, I suspect that this post is one of those.
I am always annoyed when Amazon creates a new Case ID in our Lobby, simply to tout one or another service, as a SAS Core operative did today; it’s even more annoying when the Message Body includes links ensconced behind the M.A.P. (improper grammar and/or syntax always gets my goat when it appears in Professional Business Correspondence as well; n.b. - I’ve ‘broken’ many of these URLs to accommodate display on the Discourse Platform):
The correct SoA Account-accessible URL for the “FBA Inventory tool”/Inventory Planning Dashboard isn’t what was embedded in the examples found in this solicitation:
https:
//www.sellercentral.amazon.dev/inventoryplanning/manageinventoryhealth,
but rather this:
https: //sellercentral.amazon.com/inventoryplanning/manageinventoryhealth;
The embedded URL for the SHC’s (utterly useless, other than as a placeholder) “deals reference”/“Amazon Deals” page is also behind the M.A.P.:
https://www.sellercentral.amazon.dev/help/hub/reference/202043110
While the correct URL for that page is this:
https: //sellercentral.amazon.com/help/hub/reference/202043110
As that page really is of little use, it would perhaps have been better had this been directed - as did the first “Amazon Deals” link in the message, in “G”-prefixed fashion - to the more-fleshed out “Amazon Deals” SHC page , which in ‘simplified’ form may be found here
https: //sellercentral.amazon.com/help/hub/reference/202111490
The embedded URL for the account-specific Excel file “20690180315_ASIN List.xlsx” - a la Sandy’s link reproduced above in Post #328 - is also malformed:
Sadly, the seams continue to split under the strain…
You have been email link spammed
THIS is their reason for you to cut prices? 12 bucks?
How much can you (or anyone!) cut prices so that they do not exceed that 12 bucks during the “sale” period proposed?
Or do they expect you to cut prices and take a loss greater than the storage fees? If so, why?
If THEY are short on warehouse space, then they should incentify the sale with some discount matching for the sale they want to put on.
None of this makes any objective sense, and the more I read of Amazon’s “suggestions” the more I see that they are not worth paying any attention to, as they are nothing but attempts to con the seller into slitting his own throat for a very short term and insignificant “gain” for Amazon.
Nail, meet hammer.
It is also noteworthy that “…We noticed you have a number of ASINs that have excess levels of inventory that we are sharing attached…” refers to a single solitary ASIN (the source of the $12.04 Aged Inventory Fee), and is thus little more than a bald-faced lie.
I use a LOT of templates (saves me from carpal tunnel) but I always have to double check to see if the template has references that are not needed or just plain wrong in each situation.
The Amazon BOTS don’t bother and their English may or may not be a work in progress directed by bigger, badder BOTS and AI geniuses.
It’s a work in devolving the site…
It more and more feels like the Amazon theme song is https://youtu.be/_38SWIIKITE?list=RD_38SWIIKITE
Because I always advocate responding to Amazon in short, succinct fashion, I came up with this reply:
Submitting that might not have been the best idea I ever came up with; because of the fact that there are no Amazon Delivery Drones currently operating w/in about a 1500-mile radius of me, I’m becoming quite concerned that there’s now a bevy of 'em buzzing my fields… 
Ruh-roh, Josh…
May God help Mr. Seymour, because Amazon won’t - and neither will its sorry-assed Gen AI LLMs scraping data years past its expiration date…
And more than a year after Manny posted that tutorial, Seller Support is STILL recommending use of this no-longer-monitored e-mail address (to be fair, even in the years when it was active, it was generally useless, but still):
It would also perhaps be informative to know what Ram left out of this sentence:
As Ram is referring to an in-case recommendation from SeSu, the blame mostly falls @ other feet - but one might hope that, even in one of the most ill-siloed organizations ever known to humankind, @ least all members of the same team - in this case, the FMT-CMT - were on the same page @ all times.
A boy can dream, can’t he?
The bots are fighting again
I really hate this too.
Not the first time I’ve seen this from the mods over the last year or so, and it may not be the last; I can point to the recent change in published-policy language in an applicable SHC page that leads to this interpretation, even if Ram didn’t, and to others that directly contradict it (Silo Manglement raises yet another ugly head) - but I’m always incensed when I see Amazon come up with ways to throw sellers under this or that bus in its never-ending efforts to balk at its own policies whenever it thinks it can cobble together ill-gotten gains (emphasis mine):
Greed, thy name be Amazon.
