Perhaps not, but they do have ever-evolving “brush-off” (aka “kiss of death”) templates that resurrected ‘mod’ profiles can use, like this one I just ran across over in the Wastes of WOE NSFE (emphasis mine):
Especially when new posting profiles keep coming out of the woodwork like this newest one I’ve run across, w/ a very-1st post made 4 days ago (011626):
Having read many of his posts, I don’t believe that Joey_Amazon is an automaton, but I’d be willing to wage that his 012326 tutorial post - like many I’ve seen the FMT-CMT produce over the last several quarters - was crafted w/ the ‘aid’ of one:
Leaving aside the concerns re: Amazon foisting off chargebacks to a non-processing entity, my complaint is that the second embedded link - purportedly to the SHC’s “Chargebacks” @ https: //sellercentral.amazon.com/help/hub/reference/48781, apparently - simply is the same URL as the first link to the Chargebacks Dashboard.
23Dec`25 was an even more popular Day One than I previously thought; just saw a post by another new mod profile with the same starting date as the three linked above:
Apparently, the memo still hasn’t reached all-intended recipients; the brand spanking new (link, Post # 308) Maria_Amazon posted this earlier 2026-02-02T05:00:00Z:
I feel fortunate that I’m not cursed with any susceptibility to migraines - were it otherwise, the headaches these folks continue to cause could well lay me low…
Maria_Amazon made this reply to a 3P Seller seeking to remove PII from a UK (DE) Forum discussion s/he’d created back on 122025:
True to her word, Maria posted this reply over in the European thread, directing the seller to see the Amazon Seller Forums FAQs (link) for instructions on how to edit or delete NSFE posts:
The problem with reading comprehension comes starkly into focus when we note what the FAQs actually have to say on this matter (emphasis mine):
The 24 hour window elapsed, of course, back on 122125 (the day after the discussion was created) - and even if there had not already been other replies (there were, including one by Xander_Amazon), Maria’s own post, by definition, would in & of itself have triggered the ‘has-response’ threshold’s post-locking mechanism.
I do an almost weekly post telling the mods on the Canadian site that Amazon’s Buy Shipping is NOT available to us. It is their go-to reply to posts regarding A-Z claims with the word shipped anywhere in the post. I have gotten to the point of yelling it in CAPS. No response from any of them.
There too we are also experiencing the addition of new mod names. And the drill is usually one mod will spend a few hours answering posts, then nothing for a few days, then a different one goes on a short spree, rinse and repeat. Methinks this topic title “Training” has not happened.
It’s been mentioned before (link, 090424 SAS post) how dangerous a dependence upon AI can be to human health (something that’s been demonstrated in spades, IRL, over the 18 months since that post), but the potential for causing financial harm is also great - especially should people follow advice regurgitated by AI queries, as appears to be the case with Manny_Amazon’s 020426 post here (emphasis on the risible portion italicized):
Had Manny actually bothered to read the pertinent published policy - found in the SHC’s “Returns processing fee” @ https: //sellercentral.amazon.com/help/hub/reference/64LS955WNFT6EDP - he’d likely have noticed that it states this in the very-1st ¶:
Reading further, we can see the reason for the Apparel and Shoes Category carveout stated there:
Reading along further, we can see from the first table, listing “Return Rate Thresholds,” by Category, which trigger the Returns Processing Fee, that the BMVD Categories ARE included - and that the threshold for them is >5.1%; it’s also noteworthy that NO Category in the Amazon Global Catalog is exempt, as is plainly stated in the page’s first ¶.
For the past dozen years and more, a common refrain amongst 3P Sellers has been a bemoaning of the fact that, often enough, they themselves knew more about how Amazon actually works than its support personnel do.
Given the headlong & heedless rush to embrace AI technologies - heightened under Andy Jassy’s watch, as he made no bones about in his Message to Stockholders last fall (and even before) - and the increasingly-frequent appearance of Cyrano-generated (link, 012826 SAS post) mendacity like Manny’s post, I can only expect that the chasm will widen further…
This particular bit of misinformation continues to obstinately refuse to fade from the scene, as may be seen from Indy_Amazon’s 021026 post recommending use of the supposedly deprecated (& long ineffectual) Community Help Team’s email address [email protected] (bolded, italicized, & underlined emphasis mine):
I would reiterate, again with all due respect where it’s due for the taking of literary license:
…
Y’all are only coming through in waves
Your lips move, but we cain’t trust what you say
When I was a rook, I caught reviling glimpse
Just past your thumb in my eye
I turned to look, it was not gone
The sad refrain roils on and on
Given Amazon’s propensity to tack on a leading “G” to SHC Identifiers - in this case, presumably, “NGYMYPKATHYPHJN,” which isn’t one that I’ve seen before - I suspect that this is the ‘simplified’ URL for that resource:
Whether or not either supposition is true of what help resource Ram’s attempting to reveal, the fact remains that, as of this writing, neither of those URLs returns anything other than the second-most common 404 error found for Seller Help Content webpages, “There was an error displaying this topic..”
This is hardly the first time that members of the FMT-CMT have used that exact phrase, “SAFE-T Coverage and Eligibility Help Page”, in one or another variation to link SHC pages in their posts, as they demonstrably have been doing so since the early years of the OSFE* - but those, more typically, have directed to the “SAFE-T Coverage and Eligibility” section of “Reimbursement for seller-fulfilled orders” (link).
Given that just a bit more than 24 hours have passed since the post was published - i.e., only enough time for a single daily refresh cycle of Amazon’s Enterprise Domain to have completed - it’s possible that my SoA Accounts have yet to be granted access (something I’ve seen many times over the years for varied modalities, features, & the like, albeit but rarely in regard to accessing newly-produced and/or freshly-revised Help Content pages).
Given, as well, the current state of flux on the SAFE-T Claim front resulting from several pertinent recent initiatives, I wouldn’t think it entirely outside the realm of possibility that there is indeed an intent to create such a new published-policy page as this presently-accessible one purports to be - but I do remain perturbed that we so often continue to find members of the FMT-CMT failing to proofread their work before posting it publicly.
Sigh.
*
The “OSFE” (‘forumese’/“SASsese” for “OLD Seller Forum Experience”) is generally taken to be reference to the period between 020218 - the date that Amazon shifted the ASF (“Amazon Seller Forums”)-hosting software from the Jive Platform to the Discourse Platform - and 012623, the date that Amazon shifted to it’s execrable home-brewed ‘solution’ underpinning the present paradigm of the NSFE.
I hear ya’ Dog! At least once a week I post a correction on the Canadian site to whichever mod tells a seller to use Buy Shipping or SAFE-T claim to solve their problems. Neither is available on the Canadian platform. I have even resorted to yelling at them in CAPS, hoping they will take notice. Alas, it seems it is not to be.
The URL embedded in Xander’s “SAFE-T Coverage and Eligibility” - which is, somewhat inexplicably, directing to the ‘external’ version, and didn’t properly embed in the actual NSFE post - is this:
No matter how one chooses to navigate to the intended resource, it, too, returns the same “There was an error displaying this topic.” 404 warning that Ram’s (linked in the previous post) does - so, STRIKE TWO; it’s decidedly difficult to know what “additional protections” Xander’s writing about when ya can’t see them…
I’ll not be in the least surprised to find that Strike Three soon appears…