I am seeking an urgent escalation to a Community Manager regarding a recurring technical database failure that has prevented me from managing my business and protecting my Intellectual Property for nearly 12 months!!
I have two legally distinct brands and trademarks that continue to be merged at the database level by Amazon’s internal systems. This is a recurring "ghost" merge that prevents me from editing listings and utilizing Brand Registry protection tools.
Trademark 1 (Brand ID: 6770698)
Trademark 2 (Brand ID: 1683916)
On 26 January 2026, just before taking legal action, (Case #12042500632), I received a formal assurance from the Managing Director’s Escalation Department that a "permanent resolution" had been applied at the database level to separate these entities. However, within weeks, the brands reverted and merged again.
In my current active investigation (Case #12165932362), Brand Registry Support has identified that Trademark 1 (ID: 6770698) is currently in a "tombstoned" status within the database. This appears to be the root cause of the recurring corruption.
Additionally, an executive escalation case was opened by the MD’s office (Case #12166702002), but this case is currently invisible in my Seller Central Case Log, leaving me with no transparency on the progress.
Because Amazon’s systems cannot maintain the separation of these two unique brands, my Trademark rights are being actively blocked! I have exhausted all standard support channels over the last year. I am now again at the stage of preparing formal legal notice to protect my intellectual property, as the "permanent" technical assurances provided by Amazon have been breached time and time again.
Request: I am asking for a Moderator to bridge the gap to the Global Brand Registry Technical Leadership. I need a specialized engineer to manually purge the "tombstoned" records and ensure the 1-to-1 mapping of these trademarks is stabilized once and for all.
@Seller_iTgjdgiRqiPsn @Seller_DNQGSsdC7DccM @Seller_RSwABJNHpHnEZ @Seller_TSXM2A5nxWSuH Please, could you review the notes in Case #12165932362 regarding the "tombstoned" status and escalate this to a team with the authority to perform a final database purge? @Seller_PIHyltK09pbl3 also already helped to resolve this once before, but it re-merged. The MD team then assured me their fix was permanent, but again it has reverted and no further comms on this issue!