I neglected to post the URL to Kai’s NSFE post of 060726 (Glass house and all):
Mea culpa…
In another example of the FMT-CMT posting inaccessible links, Christine did that for a Seller University Module in this 060826 post:
Christine’s link to the “Report Abuse in the Amazon Store” Module is here, and it redirects to a 404 page (‘broken’ for display in Discourse):
That module did once exist - prior to 2024’s Seller University Structural Revision Initiative, when Modules were logically arranged by subject in Courses, and SU’s entire content was readily browsable w/o the current AI gatekeeping, it was Module # 36 (of 56) in the “Account Health and compliance” Course - and Amazon was so proud of it that it actually heralded its deployment in a 072622 News Headline titled “Seller University: How to report abuse in the Amazon store.”
That headline is n/l/a as a result of another 2024 change, the Amazon News Structural Revision Initiative, but the 072622 News Headline-accompanying NSFE discussion “Seller University: How to report abuse in the Amazon store” is still available @ Seller University: How to report abuse in the Amazon store :
https://sellercentral.amazon.com/seller-forums/discussions/t/1c77347646b95cc5879e8bbd575412fc
The Amazon News/News_Amazon link back then was this, and it, too, now yields a 404 error:
In both cases, we can see that the RID (“Resource ID”) for the “Report Abuse in the Amazon Store” module was “a52a9432-add0-48f2-99fb-953e3fe50171”; using that, we should normally be able to plug it into one of the current naming conventions Amazon is using for Seller University Moules to find the sought-for resource.
I’m currently aware of two separate conventions in use (there could well be more that I’m not yet aware of); ‘broken’ for display in Discourse, these are their “Raw” forms:
https: //sellercentral.amazon.com/su/learn/s?learningModuleId={ADD RID}
https: //sellercentral.amazon.com/learn/learning-module/{ADD RID}
These 2 formats seem, generally, to be interchangeable - for instance, substituting a known RID, like that of the “Drive repeat purchases with Subscribe & Save” Module (which is “315ebb81-9097-42d3-9873-086e1c754360”) into either ‘Raw’ URL allows navigation to that video by either path:
https: //sellercentral.amazon.com/su/learn/s?learningModuleId=315ebb81-9097-42d3-9873-086e1c754360
https: //sellercentral.amazon.com/learn/learning-module/315ebb81-9097-42d3-9873-086e1c754360
We can see that both are viable URLs, leading to the same resource (n.b. the difference in the web elements used to provision those pages); the same is true of other SU modules, such as “Report a violation” (whose RID is “e0bd7a7b-b7d4-47d1-a097-e307ab524797”):
https: //sellercentral.amazon.com/su/learn/s?learningModuleId=e0bd7a7b-b7d4-47d1-a097-e307ab524797
https: //sellercentral.amazon.com/learn/learning-module/e0bd7a7b-b7d4-47d1-a097-e307ab524797
The same is not true for the “Report Abuse in the Amazon Store” Module; substituting in its RID (“a52a9432-add0-48f2-99fb-953e3fe50171”) yields these URLs, which also produce 404 errors like the other two:
https: //sellercentral.amazon.com/su/learn/s?learningModuleId=a52a9432-add0-48f2-99fb-953e3fe50171
https: //sellercentral.amazon.com/learn/learning-module/a52a9432-add0-48f2-99fb-953e3fe50171
Finding all 4 of these approaches unnavigable was enough to lead me to conclude that it was most likely that the module had been deprecated since the last time I’d viewed it, but I tried another method of finding it by using the ever-execrable Seller University search engine, with the actual title of the wayward module “Report Abuse in the Amazon Store” as the search term; that returns 10 modules that the AI gatekeeping mechanism thinks are applicable - it’s wrong, because none of them are.
Refining that term to simply “Report Abuse” yields only two modules as a result (notably, neither of them appear in the earlier search results) and the first one is the aforementioned “Report a violation” module - which is why I included it in the second example of working pages, above, and which itself is badly in need of updating, as it references the now-superseded workflow installed after the AHT Initiative for the Report Abuse (link) Dashboard, when it looked like this (if an SoA Account had access to all 9 choices; not all did):
As we all likely know by now (link, SAS), that workflow was suppressed in Q3 of 2025 w/ the advent of yet another Amabot gatekeeper, this one taking the triage reins for case creation and Help Hub content.
The insidious forces of ignorance and inertia would seem to be combining to stir up a poisonous brew…