Brand Registry: Fix 'Trademark Already Enrolled'

The "trademark is already enrolled" error means the brand is already in Brand Registry, and you don't enroll it again. If your account doesn't hold it, the fix is a role request: ask a current Administrator to add you as an additional user, or continue to apply with the same trademark and share your contact information.

The question usually arrives in one line:

"We're trying to enroll our brand in Amazon Brand Registry and getting the 'trademark is already enrolled' error. What do we do?"

ChatGPT, Claude, Perplexity, Microsoft Copilot, and whatever comes next know nothing about your business out of the box. Your competitors use those tools too. Kuudo gives those same tools your edge: your data, your rules, and the way your business operates. That means your account as it is right now, your judgment running every time, and your call before anything changes.

For this error, that works out as:

• Amazon Agent Atlas retrieves Amazon's Brand Registry rules, so each branch cites Amazon's own help pages.
• A Skill your team writes walks those rules as a decision tree and asks for the facts that pick the branch.
• The Selling Partner MCP adds catalog context: which listings carry your brand name.
• A person submits every Brand Registry step. Brand Registry has no Selling Partner API, so no agent reads or files there.

"Trademark is already enrolled" means the brand has an Administrator, and Atlas says the fix is a role request

The Enrollment error messages page, retrieved from the amazon_sellers corpus, is plain about it: the error means your brand is already enrolled and you don't have to enroll it again. A brand approved for one store is registered for all regions, so first check whether your own account already holds it.

If it doesn't, the Brand Registry FAQ gives the rule: when a trademark is already enrolled, you contact the brand's Administrator and request to be added as an additional user.

An Administrator exists because enrollment creates one. The Brand Registry protection roles page says the user who enrolls a brand is automatically assigned the Administrator and Rights Owner roles. There are three protection roles:

• Administrator: adds and changes protection and selling roles. Only Administrators assign roles, and a brand can have more than one.
• Rights Owner: the intellectual property owner, or their designated employee, with access to the Report a Violation tool.
• Registered Agent: a third party the Administrator authorizes to use Report a Violation. One account can't hold both this role and Rights Owner for the same brand.

Amazon also publishes a Brand Registry Access: Troubleshooting Guide for this exact message.

The Skill routes you: ask a known Administrator, or continue to apply and share your contact information

The first branch is the shortcut. The protection roles page says that if you know the identity of a current Administrator, you reach out directly and request an invitation. Before you ask, create your Brand Registry account and accept its terms and conditions.

On the Administrator's side, the invitation takes three steps:

1. Open User Permissions from the gear icon.
2. Click Invite a user to your brand and enter the email address on your Brand Registry account.
3. Click Send invitation. You accept it to be granted the protection role.

With no name to call, the FAQ covers the next branch. If you're unsure who to contact, or the current Administrator is inactive, you can continue to apply with the same trademark. Eligible users get a step in the application to share contact information with the Administrator.

Approval is discretionary. An active Administrator uses that information to add your Brand Registry account to the brand, if they choose to do so. The request lands in their User Permissions tool under Access requests, where they approve or decline it.

The decision plan the Skill assembled

The Skill turned those rules into a plan, each branch traced to a retrieved page:

decision_plan:
  trigger:
    error_message: "This trademark number is already enrolled in Brand Registry"
    surface: "Brand Registry enrollment flow, after Verify"
  facts_to_gather:   # answered by a person from the Brand Registry site
    - already_yours: "Does your own Brand Registry account already hold this brand?"
    - administrator_known: "Do you know the identity of a current Administrator?"
    - administrator_active: "Is that Administrator active and reachable?"
    - other_brand_enrolled: "Do you have at least one other brand enrolled in Brand Registry?"
  branches:
    - id: already-yours
      condition: "Your account enrolled the brand, perhaps for another store"
      action: "Nothing to redo: a brand approved for one store is registered for all regions"
    - id: administrator-known
      condition: "You know a current Administrator"
      prerequisite: "Brand Registry account created, terms and conditions accepted"
      action: "Reach out directly and request an invitation as an additional user"
      admin_side: "User Permissions > Invite a user to your brand > Send invitation"
      outcome: "You accept the invitation and get the assigned protection role"
    - id: administrator-unknown
      condition: "Unsure who the Administrator is"
      action: "Continue to apply with the same trademark"
      during_flow: "Share your contact information (step shown to eligible users)"
      admin_side: "Request lands in User Permissions > Access requests"
      decision_rule: "Approved or declined at their discretion (if they choose to do so)"
    - id: no-active-administrator
      condition: "The Administrator is inactive or has left the company"
      paths:
        - id: appeal-form
          entry: "Same flow: 'use this form' opens the Share Contact Information form"
          action: "The link at the bottom of that form opens Appeal Submission"
          gate: "Appeal Submission link is visible only to eligible users"
          outcome: "Success adds you with Administrator and Rights Owner roles"
        - id: brand-registry-support
          gate: "At least one other enrolled brand plus Brand Registry site access"
          action: "Open a case; select 'Update brand ownership' as the topic"
          outcome: "Request reviewed; response follows"
  submitted_by: "A person, in Brand Registry; the agent drafts the messages"

Atlas maps two paths when no Administrator is active: the appeal form and an "Update brand ownership" case

If the Administrator is inactive, the FAQ says to click use this form to submit your request. The FAQ's answer for an Administrator who has left the company spells out the steps:

1. Apply with the same trademark number as the enrolled brand.
2. A warning appears, offering a link to a form for sharing your contact information.
3. That link opens the Share Contact Information form.
4. At the bottom of the form, a link available only to eligible users leads to the Appeal Submission form.

Neither page defines who counts as eligible, so a missing appeal link may simply mean the gate. When an appeal succeeds, you're added to the brand with the Administrator and Rights Owner roles.

The second path has its own gate. If you have at least one other brand already enrolled in Brand Registry and you can access the Brand Registry site, you can submit the request through Brand Registry Support and select Update brand ownership as the topic. Your request is reviewed, and you receive a response.

Amazon asks you to identify the nature of a Brand Registry error before contacting support, since not every question is technical. The decision plan does that step first, then routes you to the path your account qualifies for.

When you submit a new application, Atlas gives the clock: 10 business days to review, 3 days to finish, 10 days to return a code

A new Brand Registry application, such as one you correct and resubmit after a rejection, takes an average of 10 business days to review, per the Brand Registry application process page. Amazon may need more information to verify your identity, which can extend the review.

Two deadlines come from the same page. An application not submitted within three days shows Expired. And if Amazon sends a verification code to a contact that meets its verification requirements, you reply to the application's case within 10 days with the code and the case ID.

Every application appears on the Brand applications page with one of eight statuses: Approved, Rejected, Pending submission, Expired, Ineligible, Pending review, Withdrawn, or Removed from Brand Registry. A rejected application can't be edited: locate it, click Copy, correct the details, and submit the new application.

Before a resubmission, the Skill runs the pre-checks Atlas holds:

• Only trademarks with a Registered or Pending status can be accepted (Manage Brand Registry application issues).
• The brand name must match the trademark text exactly.
• The mark must be a word mark, or a design mark with words, letters, or numbers. Design-only marks and logos aren't accepted for initial enrollment.
• For a US trademark, the Supplemental register is ineligible.
• A pending mark that is similar to an existing registered brand can be rejected under uniqueness verification; you may reapply once it is registered.

What happens next: a person submits each Brand Registry step, and the agent keeps the dates

The plan becomes a checklist the team works through. A person does each Brand Registry step and reports the status and the date, and the agent tracks the three-day submission window and the 10-day verification-code reply against the case ID.

If an outreach request goes unanswered and the Administrator turns out to be inactive, the plan moves to the appeal and support paths instead of waiting on someone's memory.

Brand Registry sits outside the Amazon Agent Data layer:

• The Selling Partner MCP and the Amazon Ads MCP cover the account's selling and advertising data, and Agent Flow lands it in a lake you own.
• Brand Registry has no Selling Partner API, so nothing here runs through an MCP write tool. The agent drafts and a person submits, the same boundary as human approval before an audience activation.

That's the whole pattern: rule out the brand you already hold, walk Amazon's real decision tree, and keep the deadlines on a list instead of in someone's head.

Next in the series: letting the agent fix a failing listing without editing it blind, the same read-first, approve-before-ship discipline pointed at your live catalog.